TrialTrack - Clinical Trial Project Management
All posts

Compliance

Trial Master File Checklist: Essential Documents by Phase

Dejan Murko

At a glance

  • The TMF is the collection of essential documents that lets monitors, auditors, and inspectors verify a trial was run per protocol and GCP. The checklist below is organized the way a trial runs: before, during, and after.
  • There is no single definitive document checklist. The authoritative essential-document set lives in ICH GCP, and regulators are explicit it is not an exhaustive, fixed list, so treat any checklist as a usable starting point, not a gated download.
  • A list is not enough. You also need a completeness-QC routine: are all essential documents present, filed correctly, indexed, added on time, and access-controlled?
  • The data-management SOP is what keeps the TMF current day to day, so you are not reconstructing it in a panic before an audit.
  • “Inspection-ready” has a concrete meaning: complete, legible, contemporaneous, and accurate, and readily available to the authorities.

Most TMF checklists you find are either a flat document dump with no verification step, or a download-gated vendor PDF that says “be inspection-ready” without explaining how to confirm completeness. Almost none connect the TMF to the SOP that governs how documents are filed and QC’d. This guide gives you a phase-structured, usable checklist, a completeness-QC routine you can actually run, and the data-management SOP that keeps the file current. It deliberately stays on the checklist-plus-verification-plus-SOP deliverable; the full TMF/eTMF explainer, study startup, and audit-trail mechanics each have their own guides.

What a trial master file is, and what it has to prove

The TMF exists to make a trial verifiable. EMA defines it as the collection of essential documents used by sponsors, CROs, and investigators to manage the trial and by monitors, auditors, and inspectors to review and verify whether the trial was conducted in line with applicable regulatory requirements and GCP (EMA TMF, §2). The standard it has to meet is reconstruction: the documentation should be sufficient to adequately reconstruct the activities undertaken in conducting the trial, along with the decisions and justifications made, and should collectively permit confirmation of compliance with the protocol and GCP without needing additional explanation from staff (EMA TMF, §2).

There is one TMF per trial, but it has two parts. EMA notes the TMF is usually composed of a sponsor TMF held by the sponsor and an investigator TMF (often called the investigator site file, or ISF) held by the site, with some documents deliberately segregated (for example, the subject identification code list in the investigator TMF only, the master randomisation list in the sponsor TMF only) (EMA TMF, §3.1). The investigator/institution is responsible for, and should retain control of, all essential records it generates (ICH E6(R3) §2.12.11). When duties are outsourced to a CRO, the sponsor remains responsible and must maintain oversight and access to the CRO-held parts of the TMF (EMA TMF, §3.2).

The TMF essential-documents checklist, by phase

A caveat first, because it is the whole point of the differentiation: there is no fixed, definitive checklist. EMA is explicit that the ICH GCP essential-document list should not be used as a definitive checklist for TMF content and is not exhaustive, and that the sponsor and investigator should include any documentation that facilitates reconstructing and evaluating the trial (EMA TMF, §3.5.1). A risk-proportionate approach can also justify reducing some documentation, with the justification itself documented in the TMF (EMA TMF, §3.5.1). So use the phased lists below as a usable starting point, then tailor.

Before the clinical phase

Representative essential documents established at startup (filed before enrollment begins):

  • Protocol and amendments, and the investigator’s brochure
  • Informed consent form(s) and any participant-facing materials
  • Ethics committee / IRB approvals and favourable opinions
  • Regulatory authorisations as applicable
  • Signed agreements (sponsor-investigator, CRO, vendors)
  • Financial and insurance documentation
  • Delegation log and staff CVs/qualifications

During trial conduct

Documents generated as the trial runs:

  • Protocol amendments and updated IB versions, with date of receipt and implementation
  • Monitoring records and visit reports
  • Safety reports and serious adverse event documentation
  • Relevant correspondence necessary to reconstruct key decisions, including with ethics committees and regulators (EMA TMF, §3.5.3)
  • Data management and statistics documentation, such as the data management plan, data validation plan, and statistical analysis plan, and trial-specific system validation records (EMA TMF, §3.5.1)
  • Superseded versions of controlled documents, retained to enable reconstruction (EMA TMF, §3.5.2)

After completion or termination

Close-out and final documentation:

  • Final report and, where available, audit certificate(s)
  • Investigational product accountability, return, and destruction records
  • Close-out monitoring records
  • Archiving records and the archive index/log

Completeness QC: how to verify the TMF is actually inspection-ready

This is the step the gated checklists skip. A TMF is not “done” because the documents exist; it is done when you have verified completeness. EMA prescribes risk-based quality checks to ensure the TMF is up to date and all essential documents are filed, listing what to check: all generated essential documents are present, documents are filed in the appropriate locations, documents are added in a timely manner, documents are correctly indexed, access follows assigned roles and permissions, and (for an eTMF) the audit trail is reviewed (EMA TMF, §4.2). Run that as a routine, not a one-off.

The four quality attributes

“Inspection-ready” is concrete. The TMF must be complete, legible, and accurate (EMA TMF, §2), kept contemporaneous, meaning documents are filed in a timely manner during the trial, which is what EMA reads into the requirement that the TMF contain the essential documents “at all times” (EMA TMF, §3.5.4), and stored so it remains complete and legible throughout retention and can be made readily available to the competent authorities upon request (EMA TMF, §4.1.1). Complete, legible, contemporaneous, accurate, and available: that is the bar.

A simple completeness-check routine

1. Reconcile generated documents against your expected essential-document list (per phase)
2. Confirm each document is filed in the correct TMF section/location
3. Check filing timeliness (filed within your defined window of the document date)
4. Verify indexing and version visibility (current version identifiable)
5. Confirm access permissions match assigned roles
6. (eTMF) Review the audit trail for the period
7. Log gaps and assign corrective actions with owners and dates

Timely, contemporaneous filing is the attribute most often failed; EMA stresses defining the timelines for submission and filing of documents in your procedures or TMF plan (EMA TMF, §3.5.4).

The gaps that fail inspections

The completeness routine exists because the same failures recur. The most common is timeliness: documents filed late, or filed in a batch just before an inspection, which undermines the contemporaneous standard the TMF is supposed to demonstrate (EMA TMF, §3.5.4). Close behind are missing or out-of-date approvals, version confusion where the current version is not clearly identifiable, and documents filed in the wrong location so they cannot be found on request. Security and integrity matter too: the TMF must be managed securely at all times to ensure completeness and to prevent accidental or premature loss, unauthorised alteration, or destruction of documents (EMA TMF, §4.1), so a file anyone can quietly overwrite is itself a finding. The fix for all of these is the same: a routine completeness check against an expected document set, run on a cadence, with gaps logged and assigned, rather than a single heroic pass before the inspector arrives.

The data-management SOP that keeps the TMF current

A TMF stays inspection-ready because a procedure keeps it that way, not because someone scrambles before an audit. EMA requires the sponsor’s and any CRO’s quality management system to have procedures, such as SOPs, to manage all aspects of the TMF and assure it is complete, legible, and accurate, with the investigator/institution managing to the same outcome (EMA TMF, §2). ICH E6(R3) sets the records-management expectations the SOP should encode: records should be identifiable and version controlled where appropriate, include authors, reviewers, and approvers as relevant with date and signature, and be filed in a timely manner, with the location of all essential records recorded (ICH E6(R3) Appendix C.2).

What the SOP should govern

  • Filing conventions and the TMF index/structure
  • Naming and version control (current version visible on the document, not just the filename)
  • QC cadence (how often the completeness routine runs, and by whom)
  • Timeliness windows for filing after a document’s date
  • Roles, permissions, and access control
  • Retention: how long records are kept. Retention periods are set by applicable law; under the EU Clinical Trials Regulation, the sponsor and investigator shall archive the TMF for at least 25 years after the end of the trial unless other law requires longer, with subject medical files archived per national law (EMA TMF, §6.3). Confirm the requirement that applies to your trial.

Why an SOP beats a one-off pre-audit scramble

Reconstructing a TMF from memory before an inspection is how gaps, backdating risks, and missing approvals surface at the worst moment. A standing SOP with a regular QC routine turns inspection-readiness into a steady state rather than an event.

A note on tooling: a tool like TrialTrack can help a small team track document-collection tasks and their status. TrialTrack has no eTMF or document-repository module, so it does not store or manage the TMF itself; use it to track the work of keeping the TMF current, not as the file.

The bottom line

A useful TMF checklist is phase-structured and honest that no list is definitive. But the checklist is only half the job. Pair it with a completeness-QC routine, reconcile, check filing and indexing, review access and audit trail, and a data-management SOP that keeps the file current day to day. Aim for the real standard: complete, legible, contemporaneous, accurate, and available. Do that and an inspection finds a TMF that was always ready, not one assembled in a panic.

Sources

Dejan Murko

Dejan Murko

Dejan is the co-founder of Mayet, building software for biotech and pharma teams.