Why a Complete TMF Can Still Fail an Inspection

In MHRA inspections of commercial sponsors across three reporting periods, more than 80% of inspections had at least one TMF finding, and in one period 78% of those findings were graded major (MHRA, Trial Master Files presentation). MHRA can grade a finding as critical where the TMF is not readily available or accessible, or is so incomplete that it cannot form the basis of an inspection.

Most TMF programmes measure completeness: the share of expected documents that have been filed. Completeness matters, but inspectors look at more than whether a document exists. A TMF can reach 100% on a completeness report and still draw findings on the five points below.

What inspectors look at beyond completeness

1. Timeliness: filed, but filed late

The EU Clinical Trials Regulation requires the TMF to contain the essential documents at all times, and EMA's TMF guideline expects it to be kept up to date during the trial (EMA TMF guideline). Inspectors can see filing dates. A spike in uploads in the weeks before an inspection shows the TMF was assembled rather than maintained, even if it is complete on the day.

2. Quality: present, but not right

A document can be filed in the right place and still be the wrong version, missing a signature page or too poorly scanned to read. Completeness reports count it as present. An inspector reading it does not.

3. Scope: content outside the TMF system

Monitoring reports in CTMS, query history in EDC, safety correspondence and key decisions in email can all be TMF content. MHRA guidance states that all records in the TMF, including electronic records and emails, must be made available to inspectors (Regulatory Affairs News summary of MHRA guidance). If the TMF plan does not define which systems hold TMF content, those records can fall outside oversight.

4. Access: there, but hard to reach

Inspectors expect the TMF to be readily available. Slow retrieval, inconsistent naming, or reliance on one person who knows where things are can turn a well-kept TMF into a finding.

5. History: the story has gaps

The TMF should let someone reconstruct how the trial was run. That needs metadata and audit trails, and particular care when a CRO hands the TMF back to the sponsor. Where activities were subcontracted, the organisation must still be able to provide access to the relevant TMF.

TMF health metrics to track

Inspection readiness checklist

• TMF plan names every system that holds TMF content
• Timeliness target set in the TMF plan, with actions when it is missed
• QC applied as documents are filed, not in a pre-inspection sweep
• Version, signature and legibility checks built into QC
• Filing volume reviewed monthly for pre-milestone spikes
• A mock request for 20 random documents answered within the target time
• CRO-to-sponsor TMF transfer planned, with metadata and audit trail

What this means by role

• eTMF managers and directors: report timeliness and quality alongside completeness, or completeness will hide the risk.
• Clinical operations managers and directors: filing spikes before milestones point to a process problem, not a staffing one.
• Quality and compliance directors and QA auditors: test retrieval and the scope of the TMF plan, not just document counts.
• CRAs: documents collected at site should reach the TMF within the plan's window, not at the next close-out push.
• Clinical data managers: EDC records that are TMF content need to be defined in the TMF plan.

How Cloudbyz approaches this

Cloudbyz eTMF is built natively on Salesforce, on the same platform as Cloudbyz CTMS and EDC. It is designed around a configurable TMF reference model with metadata management, search and retrieval, QC and approval workflows, 21 CFR Part 11 compliant electronic signatures, dashboards, and export with metadata and a complete audit trail. Because CTMS and EDC share the platform, records such as monitoring reports can be linked to the TMF rather than held in a separate system. How much content is linked depends on configuration.

The Cloudbyz AI eTMF Agent is designed to classify incoming documents, extract metadata, validate it against the document content, raise QC issues for review, and flag personal data for redaction. Auto-approval applies only within thresholds the team configures; everything else goes to a person.

The Cloudbyz team can show how completeness, timeliness and QC are tracked together in Cloudbyz eTMF, and how the AI eTMF Agent handles incoming documents. Book a demo or visit cloudbyz.com.