Last verified: 16 August 2026. This page reflects ICH E6(R2) Section 8 as the current, universally-applied essential-documents framework, and notes where ICH E6(R3)’s “essential records” reframing changes the picture as regional adoption proceeds — see ICH E6(R3): What Changed in Good Clinical Practice for the full regional adoption timeline before assuming R3 already governs a specific trial in a specific region.
What the Trial Master File Actually Is
The Trial Master File (TMF) is the organized collection of documents that lets a sponsor’s quality function, an auditor, or a regulatory inspector reconstruct how a trial was conducted and judge whether its data can be trusted. It is not one file or one binder — it is the complete set of what ICH E6(R2) Section 8 calls essential documents: those which “individually and collectively permit evaluation of the conduct of a trial and the quality of the data produced.”
That single sentence is the whole test for whether something belongs in the TMF. A document earns its place not because a checklist names it, but because its absence would leave a real gap in the story of how the trial was run — who approved it, who consented to participate, what was monitored, what went wrong, and how it was resolved.
Sponsor TMF vs. Investigator Site File (ISF)
The TMF has two parallel halves that are easy to conflate. The sponsor’s TMF — maintained by the sponsor directly or by a delegated CRO — is the central, trial-wide record: the full protocol history, regulatory correspondence, and every participating site’s approvals in one place. Each site independently maintains its own Investigator Site File (ISF): the local mirror of the same essential-document categories as they apply to that site specifically — its own IRB approvals, its own delegation log, its own consent forms and monitoring visit reports. A complete sponsor TMF with a thin or inconsistent set of site ISFs is still an inspection finding waiting to happen, since inspectors routinely check both.
Essential Documents by Trial Phase
ICH E6(R2) groups essential documents into three stages, matching when each document is normally generated in a trial’s lifecycle. The table below is the practical reference — what should exist, and when, before you get to the question of how it’s filed or organized (that’s a separate question, covered below).
| Phase | Document / Record | What It Establishes |
|---|---|---|
| Before the trial begins | Signed protocol and amendments | What the trial is designed to do and any changes agreed before enrollment |
| Investigator’s Brochure | Current known risk/benefit information supporting informed consent and protocol design | |
| Informed consent form template | What subjects will be told and asked to agree to | |
| IRB/IEC approval | Independent ethical review and approval to proceed | |
| FDA Form 1572 or equivalent investigator undertaking | Investigator’s formal commitment to conduct the trial per protocol and regulation | |
| Financial disclosure and clinical trial agreements | Documented terms and disclosure of potential conflicts of interest | |
| Insurance/indemnity documentation | Coverage for trial-related injury, where applicable | |
| During trial conduct | Protocol amendments and updated Investigator’s Brochures | Ongoing record of what changed and when, and why |
| Signed informed consent forms (initial and re-consent) | Evidence each subject actually consented, including to any material protocol changes | |
| Monitoring visit reports and correspondence | Evidence of ongoing sponsor oversight and issue follow-up — see clinical trial monitoring | |
| Delegation of Authority log | Who at the site was authorized to perform which trial-related task, and when | |
| Investigational product accountability records | Chain of custody and disposition of study drug/device | |
| Adverse event and safety reports | Evidence safety signals were captured and escalated as required | |
| After completion or termination | Final clinical study report | The trial’s own account of its conduct and results |
| Subject identification code list | Ability to re-identify subjects if medically necessary, without compromising blinding elsewhere | |
| Audit certificates and final IP accountability/disposition records | Closing evidence the trial and its investigational product were accounted for completely |
This before/during/after grouping is a useful planning structure, but it is not a filing structure — see the next section for why those are different questions, and where to go for the applied, document-by-document version of this list.
The TMF Reference Model: Should You Follow It?
ICH E6 tells you which documents are essential and roughly when they arise. It does not tell you where a document should live relative to every other document, or how a monitor or inspector should expect to find it. The TMF Reference Model — originally a Drug Information Association initiative, now maintained under CDISC — fills that gap with a shared taxonomy of zones, sections, and artifacts that nearly every commercial eTMF platform now uses as its default structure.
Following it is not a regulatory requirement — nothing in ICH E6 names the Reference Model specifically — but in practice it is the closest thing the field has to a common filing language. Adopting it means a CRO, a new TMF reviewer, or an inspector can navigate an unfamiliar TMF using the same zone logic they already know, rather than learning a sponsor-specific structure from scratch. For the applied, zone-by-zone version of what to check for, see the companion Trial Master File Checklist, which walks the Reference Model’s zone structure in full.
eTMF vs. Paper, and the Part 11 Implications
An electronic Trial Master File (eTMF) is the system — standalone or a module of a broader clinical trial management system — that stores TMF content, tracks completeness against an expected-document list in real time, and version-controls filings. A paper or informal shared-drive TMF avoids the system-validation burden entirely, but loses real-time completeness visibility, makes remote or distributed review harder, and puts more weight on manual version control.
For FDA-regulated trials, an eTMF that uses electronic records and electronic signatures generally falls within the scope of 21 CFR Part 11: the system must be validated, access-controlled, and produce a reliable audit trail, and any electronic signatures used within it must be attributable and bound to the record they sign. This is a system-level requirement layered on top of, not a replacement for, the underlying question of whether the right documents exist at all — a fully Part 11-compliant eTMF that is missing essential documents is still an incomplete TMF.
Completeness and Timeliness: The Question Behind Every Inspection Finding
Almost every serious TMF-related inspection finding traces back to one of two failures: a document that should exist and doesn’t, or a document that exists but was filed late enough to suggest it was reconstructed for the inspection rather than maintained as the trial went along. ICH E6(R2) Section 8’s own framing — documents that “permit evaluation,” present tense — assumes contemporaneous filing. A TMF assembled retroactively in the weeks before an announced inspection is, functionally, a different document from the one that should have existed the whole time, even if its final contents look similar.
This is why a TMF management plan, a maintained index or table of contents, and a defined quality-control review cadence matter as much as the document contents themselves — they’re what makes ongoing completeness demonstrable rather than asserted after the fact. See the GxP compliance guide for how this fits into the broader quality-system expectations spanning GCP, GMP, and GLP.
What FDA and EMA Inspectors Commonly Flag
FDA classifies clinical-investigator-site inspection outcomes into three tiers: No Action Indicated (NAI), Voluntary Action Indicated (VAI — objectionable conditions found, typically accompanied by a Form 483, but no formal regulatory action recommended), and Official Action Indicated (OAI — a compliance state serious enough to warrant regulatory or administrative action). See the inspection readiness entry for the full classification framework and the routine-vs-for-cause inspection distinction. Findings that recur across sponsors and sites include:
- Missing or incomplete essential documents — most often IRB continuing-review approvals, updated financial disclosures, or delegation log entries that weren’t updated when staff changed
- Consent form version-control gaps — subjects consented on an outdated version after an amendment, or re-consent not documented
- Investigational product accountability records that don’t reconcile (dispensed vs. returned vs. destroyed quantities)
- Monitoring visit follow-up items left open with no documented resolution
- A TMF index or completeness tracker that doesn’t match what’s actually filed — a structural finding independent of any single document’s content
Archiving and Retention
Retention requirements come from more than one source, and the applicable trial should follow whichever is longest and most specific to it:
- FDA — 21 CFR 312.62(c): an investigator’s records must be retained for 2 years following marketing-application approval for the studied indication, or, if no application is approved, until 2 years after the investigation is discontinued and FDA has been notified.
- EU — Clinical Trials Regulation (EU) No 536/2014: sponsors and investigators are commonly required to archive TMF content for a minimum period measured in decades after the end of the trial (widely cited as at least 25 years under Article 58) — confirm the current text against the regulation directly before relying on a specific figure for a specific trial, since national implementing measures can extend it further.
- ICH E6: essential documents/records should be retained per the applicable regulatory requirement(s) in each region where the trial was conducted, or per the sponsor’s own agreement/SOP, whichever is longer.
In practice, most sponsors set an internal retention SOP at or above the longest regulatory requirement across every region a multi-region trial touches, rather than tracking separate retention clocks per jurisdiction.
Source Data Verification and the TMF’s Role Under Risk-Based Monitoring
Source data verification (SDV) — comparing data recorded in the trial’s case report forms against the original source documents — is a monitoring activity, not itself a TMF document category. But it connects to the TMF directly: monitoring visit reports documenting SDV findings, and the monitoring plan describing how much SDV was performed and why, are themselves essential documents that belong in the TMF.
What has changed is how much SDV a trial actually performs, and why. FDA’s 2013 risk-based monitoring guidance explicitly does not mandate 100% SDV, and ICH E6(R2)’s Section 5.18.3 formally recognizes centralized, remote statistical monitoring as a valid alternative or complement to on-site SDV, provided the sponsor documents its rationale. A sponsor’s monitoring plan — itself a TMF document — now needs to explain why a given level and mix of SDV, centralized monitoring, and risk-based triggers was chosen for a specific trial, not just confirm that monitoring visits happened on schedule. For the fuller comparison of monitoring approaches, see on-site vs. remote vs. centralized vs. risk-based monitoring and the risk-based quality management (RBQM) guide.
How ICH E6(R3) Changes the Picture
ICH E6(R2) Section 8 is still the framework nearly every sponsor, CRO, and eTMF platform builds against today, and the essential-documents table above reflects it. But ICH E6(R3) — already in effect in the EU since 23 July 2025 and covered by FDA final guidance since September 2025, with adoption still proceeding region by region — reframes “Essential Documents” as “essential records,” deliberately technology-neutral language. The substance is the same test (can a sponsor or site reconstruct and demonstrate how the trial was conducted), but the framing no longer assumes a fixed list of named, paper-oriented documents in a specific format. For a trial run substantially through electronic systems and decentralized data sources, that’s a real change in what a well-run TMF needs to be able to show, not a cosmetic wording update. See ICH E6(R3): What Changed in Good Clinical Practice for the full structural comparison and region-by-region adoption dates before assuming R3 already governs a given trial.
Frequently Asked Questions
What is a Trial Master File?
It is the organized collection of essential documents that lets a sponsor, auditor, or regulatory inspector evaluate how a clinical trial was conducted and whether its data can be trusted, as defined by ICH E6(R2) Section 8 (reframed as “essential records” under ICH E6(R3)).
What is the difference between a TMF and an ISF?
The TMF is the sponsor’s central, trial-wide record. The Investigator Site File (ISF) is the site-level mirror of the same essential-document categories, maintained independently by each participating site.
Is following the TMF Reference Model mandatory?
No. ICH E6 does not name it specifically. It is a widely-adopted industry convention — the default structure in nearly every commercial eTMF platform — not a regulatory requirement.
Does risk-based monitoring eliminate source data verification?
No. FDA’s risk-based monitoring guidance does not mandate 100% SDV, and ICH E6(R2) permits centralized/remote monitoring as an alternative or complement to on-site SDV, but the sponsor must document the rationale for the level and mix of SDV actually used — and that rationale itself belongs in the TMF.
How long must a TMF be retained?
It depends on the applicable jurisdiction and the sponsor’s own SOP — FDA’s 21 CFR 312.62(c) sets a 2-year-after-approval floor for investigator records, EU rules are commonly cited as requiring decades-long retention, and most sponsors retain against whichever applicable requirement is longest.
Related CASRAI resources
- Clinical Data Management: Processes, Systems, and Standards — the parallel data-quality/database-lock workflow that generates much of the documentation a TMF has to hold and index.
- ICH E6(R3): What Changed in Good Clinical Practice
- ICH GCP (Good Clinical Practice) (dictionary term)
