Note to File in Clinical Research: When to Use One

A Note to File (NTF) is a standalone memo filed in a clinical trial’s regulatory binder or Trial Master File to document a fact, explain a gap, or record a decision that isn’t captured by any other required form. Used correctly, it is a legitimate and expected part of Good Clinical Practice (GCP) documentation. Used as a substitute for actually fixing a recurring problem, it is one of the most consistently flagged patterns in site audits and regulatory inspections. This guide covers both sides: what makes an NTF appropriate, and what turns a stack of them into a finding.

What a Note to File Is For

Under ICH E6(R2) Section 8, the essential documents that make up the regulatory binder/TMF exist so that a monitor, auditor, or inspector can reconstruct “the conduct of a trial and the quality of the data produced” without having to ask anyone what happened. Most of the time, the standard forms — the delegation of authority log, the source documentation, monitoring visit reports — do that job on their own. An NTF exists for the gap: a fact worth preserving that has no other home.

That makes an NTF a genuinely useful, GCP-consistent tool for things like:

• Explaining a minor, one-off administrative discrepancy after the fact — a lab requisition filed under the wrong visit label but corrected the same week, a training log missing an initial that the coordinator confirms and dates retroactively.
• Documenting a decision that was made correctly but isn’t captured elsewhere — why a specific staff member was granted a delegated task outside the usual pattern, or why a particular source document exists in a non-standard format.
• Recording the resolution of something that already happened and is already closed — not an open problem, not an ongoing risk, just the paper trail for a fact that needs to be on record.

The common thread: the matter is isolated, it does not affect participant safety, participant rights, or the reliability of trial data, and by the time the NTF is filed, there is nothing left to fix — the note is the fix. That profile matches what most sponsor and site SOPs mean by a minor protocol deviation: see the CASRAI comparison on protocol deviation vs. protocol violation for how that severity line is usually drawn.

What a Note to File Cannot Do

An NTF documents. It does not correct, and it does not substitute for the corrective process GCP actually requires once a problem is more than a one-off. ICH E6(R2)’s noncompliance provisions (Section 5.20) are explicit on this point: when noncompliance is discovered that significantly affects, or has the potential to significantly affect, participant protection or the reliability of trial results, the response required is a root cause analysis followed by corrective and preventive action (CAPA) — not a memo explaining what happened. A well-written NTF can be the record that a root cause analysis happened; it cannot be a replacement for one.

This is the distinction auditors are trained to look for. A single NTF explaining a single missed visit window is documentation. Five NTFs across five visits explaining five instances of the same missed visit window, each written as though it were the first time, with no CAPA opened and no change to the process that keeps producing the same deviation, is a site using paperwork to narrate a problem it has not actually addressed.

The Pattern Auditors and Monitors Are Trained to Flag

This isn’t a stylistic preference — it follows directly from what GCP actually requires once a deviation stops being an isolated event. FDA’s own regulatory framework for investigator conduct is built around exactly this distinction. Under 21 CFR 312.60, an investigator is responsible for conducting a study in accordance with the signed investigator statement and the investigational plan; under 21 CFR 312.66, changes and unanticipated problems must be reported to the IRB, not just filed away. A recurring deviation, by definition, means the study is no longer being conducted according to the plan — and FDA’s Bioresearch Monitoring inspections and warning letters to clinical investigators have long treated “failure to conduct the study according to the investigational plan,” evidenced by an unaddressed pattern of deviations, as a core finding, distinct from and more serious than any single deviation on its own.

FDA has also moved to formalize the deviation side of this directly: its draft guidance Protocol Deviations for Clinical Investigations of Drugs, Biological Products, and Devices (issued December 2024) sets out recommendations for how sponsors, investigators, and IRBs should define, categorize, and report deviations — a response, in part, to exactly the inconsistency that lets a pattern hide inside a folder of individually-worded NTFs instead of surfacing as a trend. The guidance’s premise is that a deviation needs to be classified and tracked as what it is (ordinary vs. “important”), not narrated case-by-case in a format that resists trending.

In practice, the tell an auditor or monitor looks for is less about any single NTF and more about the pattern across the binder:

• Recurrence without escalation. The same deviation type appears in NTF after NTF, each treated as a fresh, isolated event rather than cross-referenced to the others.
• No corresponding deviation log entry or CAPA. The site’s own CAPA tracker or protocol deviation log has nothing that ties back to the recurring issue — the NTF is the beginning and end of the response.
• Increasing frequency over the trial’s life, especially post-monitoring-visit, which suggests the deviation was identified by someone else and “resolved” with a memo rather than a process change.
• Language that explains rather than owns. An NTF that reads as a justification for why the deviation was reasonable, rather than an acknowledgment plus a stated fix, is a documentation style that both FDA inspectors and sponsor auditors are specifically trained to notice.

None of this means NTFs are inherently risky — a binder with zero NTFs is not necessarily healthier than one with a handful. What matters is whether the NTF is the whole response to a recurring issue, or one component of a response that also includes a logged deviation, a documented root cause, and a CAPA where the pattern warrants one.

Structuring an NTF So It Doesn’t Read as a Cover-Up

A defensible NTF, whether it’s documenting something genuinely minor or forming part of a larger corrective record, should cover:

• What happened, stated factually, without minimizing language.
• When it was discovered and by whom — self-identified is generally viewed more favorably than monitor-identified.
• Whether it meets the threshold for the protocol deviation log and, if applicable, IRB/sponsor reporting — an NTF is not an alternative reporting channel to either.
• Root cause, if known, or an explicit statement that root cause analysis is in progress and where that analysis will be documented.
• What was done immediately to address the specific instance.
• A cross-reference to the CAPA, if one was opened, rather than restating the fix inline as though the NTF itself were the corrective action record.

That last point is the one that separates an NTF used well from an NTF used to paper over a gap: the corrective action lives in the CAPA/deviation system, and the NTF points to it rather than trying to be it.

Note to File vs. Deviation Log vs. CAPA

These three documents answer different questions, and conflating them is exactly how a pattern goes unaddressed:

• Note to File — “Here is a fact that needs to be on record.” Appropriate for isolated, resolved, non-safety-affecting matters, or as a pointer into the other two systems.
• Protocol deviation log — “Here is every departure from the approved protocol, tracked so a pattern is visible.” The log is what makes recurrence detectable in the first place; an NTF that never makes it into the log defeats that purpose.
• CAPA — “Here is the root cause and the process change that stops this from recurring.” Required once a deviation is more than an isolated event, per ICH E6(R2) Section 5.20.

A site that reaches consistently for an NTF where a deviation-log entry and, eventually, a CAPA are what’s actually called for isn’t necessarily acting in bad faith — it’s often just a workflow default: the NTF template is the easiest form to fill out and file. The fix isn’t to ban NTFs; it’s to build a site SOP that routes a deviation to the log first and treats the NTF as one possible output of that process, not a bypass of it. See the SOPs a clinical trial site actually needs for where deviation handling fits into a site’s broader SOP structure, and running a mock FDA inspection for how this exact gap — NTFs with no corresponding log entry or CAPA — tends to surface under inspection conditions before it surfaces in a real one.

What This Looks Like From the Monitoring Side

A monitor reviewing the regulatory binder during a routine visit is doing essentially the same pattern check an auditor or FDA investigator would do later, just earlier and with more room to fix it. Cross-referencing NTFs against the deviation log, and flagging any NTF that describes something that should have generated a log entry but didn’t, is standard practice in a well-run monitoring visit; see writing the monitoring visit trip report for how that finding typically gets escalated in the report itself, and monitor vs. auditor for how the same binder gets a second, independent look later in the trial’s life.

Frequently Asked Questions

Is a Note to File required by ICH E6 or FDA regulations?

No. “Note to File” is not a term defined in ICH E6(R2) or FDA’s regulations — it’s an industry-standard practice, not a mandated form. What is mandated is that essential documents exist to support the conduct of the trial (ICH E6(R2) Section 8) and that noncompliance affecting subject protection or data reliability gets a root cause analysis and CAPA (Section 5.20). An NTF is one way sites choose to meet the first requirement; it is never a way to meet the second.

Can a Note to File replace an entry in the protocol deviation log?

No. If what’s being documented meets a site’s or sponsor’s definition of a protocol deviation, it belongs in the deviation log regardless of whether an NTF is also filed. The two aren’t interchangeable: the log is what makes a pattern visible across the life of the trial, and an NTF that exists instead of a log entry removes exactly the visibility the log is designed to provide.

How many Notes to File is “too many”?

There’s no regulatory numeric threshold. What matters to a reviewer isn’t the count, it’s whether the NTFs cluster around the same unresolved issue without a corresponding deviation log trend and CAPA. A binder with many NTFs covering genuinely distinct, minor, one-off matters is less concerning than one with three NTFs explaining the same missed procedure three separate times.

Who should write and sign a Note to File?

The person with direct knowledge of the fact being documented — typically the coordinator or investigator involved — should write it, and the Principal Investigator should review and sign, consistent with the PI’s overall responsibility for the conduct of the trial under 21 CFR 312.60. A note written by someone without firsthand knowledge of what happened carries less evidentiary weight if it’s ever reviewed.

Does a Note to File need to be dated at the time of the event, or can it be filed later?

It should be dated when it is actually written, and should state the date of the event it’s describing separately if the two differ. Backdating an NTF to make it appear contemporaneous with the event is a data-integrity problem in its own right, independent of whatever the note is trying to explain.