A Trial Master File (TMF) checklist is only useful if it’s organized the way the documents actually get filed and inspected — by the TMF Reference Model‘s zone structure, not as a flat, undifferentiated list. This guide is that checklist: a practical, zone-by-zone working document you can use to build or audit a sponsor TMF, an Investigator Site File (ISF), or an eTMF index, grounded in the essential-documents framework of ICH E6(R2) Section 8.
This page assumes you already know what a TMF is and why it exists — if you need that grounding first, start with the Trial Master File (TMF) definition, the eTMF definition, or the TMF Reference Model entry, which explains the Zone / Section / Artifact / Sub-Artifact hierarchy in more depth. What follows is the applied version: what to actually check for, zone by zone.
Why Organize a Checklist by TMF Reference Model Zone
ICH E6(R2) Section 8 defines essential documents as “those documents which individually and collectively permit evaluation of the conduct of a trial and the quality of the data produced,” and groups them by when in the trial lifecycle they arise: before the clinical phase begins, during the conduct of the trial, and after the trial is completed or terminated. That three-part grouping tells you when a document should exist, but not where it should live relative to everything else, or how a monitor, auditor, or inspector should expect to find it. The TMF Reference Model — originally a Drug Information Association (DIA) initiative, now maintained under CDISC — solves that second problem by defining a shared taxonomy of Zones, Sections, and Artifacts that nearly every commercial eTMF platform now uses as its default filing structure.
Using the Reference Model’s zones as your checklist structure means the same checklist works whether the TMF is filed on paper, in a homegrown shared-drive structure, or in a commercial eTMF system — and it means gaps show up as a specific, nameable missing artifact in a specific zone, not a vague sense that “something might be missing.”
Before You Start: TMF Plan and Index
- A written TMF management plan exists, naming who owns TMF completeness (sponsor, delegated CRO, or a shared model) and how often it’s reviewed.
- A TMF index or table of contents is maintained and kept current as documents are filed, not reconstructed retroactively before an inspection.
- Filing conventions (naming, version control, placeholder/tracking-log use for expected-but-not-yet-received documents) are documented and consistently applied across sites and vendors.
- Quality control review of the TMF happens on a defined cadence, not only in reaction to an announced inspection.
These points sit logically outside any single zone but should be the first thing checked, since a TMF with complete zone contents and no governing plan or index is still an audit finding waiting to happen.
The Checklist, Zone by Zone
Secondary industry sources describe the current TMF Reference Model as organizing content into 11 zones, each broken down further into sections and individually numbered artifacts. The exact artifact list, numbering, and count vary by Reference Model version and should be checked against the current CDISC release for a definitive, version-specific list — what follows maps the representative essential-document categories from ICH E6(R2) Section 8 onto each zone, as a working checklist rather than a claim to the canonical artifact catalog.
1. Trial Management
- Trial management plan and TMF plan/index itself
- Kick-off / study initiation meeting materials and minutes
- Study team contact list and organizational chart
- Team training records and role-specific certifications
- Communication plan and general trial correspondence log
2. Central Trial Documents
- Protocol, all amendments, and protocol synopsis
- Investigator’s Brochure (IB) and IB updates/addenda
- Sample Informed Consent Form (ICF) and subsequent versions
- Case Report Form (CRF) design and completion guidelines
3. Regulatory
- IND/CTA (or equivalent) application and submission correspondence
- Regulatory authority approvals, acknowledgements, and clock-start letters
- Annual reports, safety updates, and other periodic regulatory submissions
- Import/export licenses where applicable
4. IRB/IEC and Other Approvals
- IRB/IEC approval letters for the protocol, amendments, and consent forms
- IRB/IEC membership roster or statement of compliance
- Continuing/annual review approvals
- Approved subject-facing materials (advertisements, recruitment scripts)
5. Site Management
- Signed Clinical Trial Agreement (CTA) and any site-level amendments
- Delegation of Authority (DoA) log
- Investigator and sub-investigator CVs, licenses, and financial disclosure forms
- Site initiation visit report and subsequent monitoring visit reports/logs
- Site-level Investigator Site File (ISF) completeness — see the note below on how the ISF relates to the sponsor TMF
6. Investigational Product (IP) and Trial Supplies
- IP shipment and receipt records
- Drug/IP accountability log (dispensing, return, destruction)
- Temperature monitoring and excursion records
- Randomization and unblinding procedures for IP handling
7. Safety Reporting
- Serious adverse event (SAE) reports and expedited safety reports to the regulator
- Safety letters/notifications distributed to investigators
- Data Safety Monitoring Board (DSMB) charter and meeting minutes, where a DSMB oversees the trial
8. Central and Local Testing
- Laboratory certifications and accreditations for each lab used
- Lab normal reference ranges, current for the trial period
- Lab manual and sample handling/shipping procedures
9. Third Parties
- Vendor/CRO oversight agreements and scope-of-work documentation
- Vendor qualification and audit records
- Written transfer-of-obligations documentation where sponsor duties have been delegated (mirrors the specificity ICH E6(R2) Section 5.2 requires for any transferred duty)
10. Data Management
- Data management plan and CRF completion guidelines (may also be cross-referenced under Central Trial Documents)
- Edit-check specifications and query logs
- Database lock documentation and sign-off
11. Statistics
- Statistical Analysis Plan (SAP) and any amendments
- Randomization scheme and blinding/unblinding procedures from the statistical side
- Final statistical report/analysis
Sponsor TMF vs. Investigator Site File (ISF): Don’t Check Only One
A checklist run only against the central sponsor TMF will miss real gaps, because the Investigator Site File (ISF) is a parallel, site-level record — largely mirroring the Site Management zone plus site-specific versions of regulatory and safety documents — that is not automatically complete just because the sponsor’s own TMF is. Confirm as part of the checklist exercise that:
- Documents that legitimately exist only at the site (e.g., source documentation) are correctly excluded from the sponsor TMF gap analysis rather than flagged as missing.
- Documents that should exist in both places (signed ICF, DoA log, site-specific IRB/IEC approvals) are reconciled between the two, not assumed to match.
- Where a CRO holds delegated responsibility for TMF completeness, the written transfer of that duty is itself filed and current — ICH E6(R2) Section 5.2 is explicit that anything not documented in writing as transferred remains the sponsor’s responsibility.
Using This Checklist for Inspection Readiness
The essential-documents list in ICH E6(R2) Section 8 exists specifically so that a trial’s conduct and data quality can be evaluated after the fact — which is exactly what a sponsor audit or a regulatory inspection does. Running this zone-by-zone checklist as a periodic self-audit, not only in the run-up to a known inspection, is the practical way to keep pace with that requirement. See the related guide on clinical trial auditing for how sponsor audits of the TMF typically differ from monitoring visits, and Good Clinical Practice (GCP) for the broader compliance framework this checklist sits inside.
Paper, Hybrid, or eTMF: The Checklist Doesn’t Change
Whether the TMF is filed on paper, in a hybrid arrangement, or in a dedicated eTMF platform, the zone structure and the underlying essential-documents requirement are the same — what changes is how completeness is tracked and how quickly a gap can be found. Most commercial eTMF systems ship with the TMF Reference Model (or a vendor-mapped variant of it) built in as the default folder structure specifically so that a checklist like this one maps directly onto the software’s own filing tree. See Clinical Data Management Tools for how eTMF fits alongside EDC, CTMS, and RTSM as part of the broader trial technology stack.
Frequently Asked Questions
How many zones does the TMF Reference Model have?
Secondary industry sources consistently describe the current TMF Reference Model as organizing content into 11 zones (for example: Trial Management, Central Trial Documents, Regulatory, IRB/IEC and Other Approvals, Site Management, Investigational Product and Trial Supplies, Safety Reporting, Central and Local Testing, Third Parties, Data Management, and Statistics), each broken down further into sections and numbered artifacts. Exact section and artifact counts vary by Reference Model version.
Is a trial master file checklist the same as a TMF index?
Related but not identical. A TMF index is the living table of contents for a specific trial’s actual TMF — it lists what has and hasn’t been filed for that trial. A checklist like this one is a template used to build or audit that index: it tells you what categories of document to expect in each zone before you go looking for them in the trial’s own records.
Who is responsible for TMF completeness — the sponsor or the CRO?
Under ICH E6(R2) Section 5.2, a sponsor may transfer TMF-related duties to a CRO in writing, but ultimate responsibility for trial data quality and integrity always remains with the sponsor, and any duty not explicitly documented as transferred is retained by the sponsor by default. In practice this means the sponsor should confirm TMF completeness even where day-to-day filing has been delegated.
Does this checklist apply to both the sponsor TMF and the Investigator Site File (ISF)?
Yes, with adjustment. The ISF is a site-level record that overlaps heavily with the Site Management zone and site-specific copies of regulatory/safety documents, but it does not need to contain sponsor-only content (e.g., vendor oversight agreements under Third Parties). Treat the zone list as a shared vocabulary, not an assumption that every zone applies identically to both files.
What happens if a TMF checklist item is missing during an inspection?
A missing essential document is a common driver of inspection findings, but the regulatory consequence depends on what’s missing and why. FDA classifies inspection outcomes as No Action Indicated (NAI), Voluntary Action Indicated (VAI), or Official Action Indicated (OAI); an isolated, promptly explained gap is far less consequential than a pattern suggesting the TMF wasn’t actively maintained during the trial. That’s the core reason to run this checklist periodically rather than only before a scheduled inspection.
