The MHRA inspectorate published a case in which a commercial sponsor received a major finding for oversight of its trials. The sponsor did hold some oversight records electronically. They were not part of the TMF, the TMF index had no sponsor oversight file, and the quality system did not identify where the records were. The inspectors concluded it was "not possible to reconstruct how the sponsor maintained oversight of the CRO" (MHRA Inspectorate, Sponsor Oversight Part 2).
The same inspection found problems the sponsor had not seen:
A later site inspection found further major issues that monitoring had not detected.
The rules behind that finding have only become more explicit. ICH E6(R3) says a sponsor may transfer any or all of its trial activities to a service provider, but keeps ultimate responsibility and should oversee important transferred activities (ICH E6(R3), section 3.6). The EMA TMF guideline expects the sponsor to have remote access to the CRO-held eTMF, or at least regular access to relevant documents (EMA/INS/GCP/856758/2018).
Each of the gaps below is a place where oversight happens but leaves no evidence in the TMF.
Oversight records such as governance minutes, CRO performance reviews and audit reports often sit in email or team drives. If the TMF index does not define where they go, inspectors cannot find them. Define a sponsor oversight section in the TMF plan, held by the sponsor even when the CRO holds the rest.
A sponsor may read every CRO monitoring visit report and still leave no record of doing so. The MHRA case cited missing evidence of when reports were reviewed, by whom and with what outcome. A review step with a dated sign-off turns reading into evidence.
Deviation listings sent as spreadsheets are reviewed in meetings that are not minuted against the data. Sponsors need a documented review of deviations by site and category, filed in the TMF.
The EU CTR requires the TMF to contain essential documents "at all times". If the sponsor sees the CRO-held TMF only at close-out, missing documents surface when they are hardest to recover.
In both MHRA case studies, safety problems were found at the service provider: late SUSARs in one, and an unapproved reference safety information version that led to missed SUSARs in the other. Safety reporting delegated to a CRO still needs sponsor visibility of timelines and RSI versions.
The EMA guideline lists what the contract should define: which party holds which part of the TMF, its structure, access, filing timelines, availability to inspectors, and what happens at trial end. Gaps here appear at transfer, when documents, metadata or audit trails do not come across.
Which gaps matter most depends on how much is outsourced and how many CROs are involved.
|
Sponsor type |
Typical outsourcing model |
Gaps that carry most risk |
|---|---|---|
|
Large pharma |
Several CROs and FSPs across a portfolio, often with a sponsor-owned eTMF |
1 and 6: consistent oversight files and validated transfers between systems |
|
Mid-size biopharma |
One or two preferred CROs, a small in-house ClinOps team |
2 and 3: documented review of reports and deviations without extra headcount |
|
Emerging biotech |
Full-service CRO holds the TMF; few internal staff |
4 and 5: visibility of TMF completeness and safety timelines during conduct |
|
Medical device |
CROs plus specialist vendors for imaging or core labs |
1 and 6: many vendor files, each needing a defined place in the TMF |
|
Role |
What they need to show an inspector |
Gaps |
|---|---|---|
|
eTMF managers and directors |
A complete index, including the oversight file, and a clean transfer |
1, 4, 6 |
|
QA and compliance directors, QA auditors |
Documented review of CRO outputs and safety timeliness |
2, 3, 5 |
|
ClinOps directors and associate directors |
Governance records that tie decisions to study data |
1, 2, 3 |
Platforms like Cloudbyz, among others, are built so that oversight activity is recorded where it happens, in the same system as the TMF. How much of each gap that closes depends on the access model and workflows agreed with your CRO.
|
Gap |
How Cloudbyz handles it |
|---|---|
|
Oversight file (1) |
A configurable TMF Reference Model, so a sponsor oversight section can be defined in the index with its own permissions |
|
Monitoring report review (2) |
With Cloudbyz CTMS and eTMF on one platform, visit reports move through review and approval workflows with 21 CFR Part 11 e-signatures, then file to their TMF artifact automatically |
|
Deviation review (3) |
Deviations and issues tracked centrally in CTMS, with reports and dashboards |
|
Completeness during conduct (4) |
A Sponsor Portal and real-time dashboards that give sponsor teams visibility of their documents for verification and monitoring |
|
Safety visibility (5) |
Cloudbyz Safety & Pharmacovigilance on the same platform, for sponsors that want safety cases in the same environment as the trial record |
|
Transfer and archiving (6) |
TMF export with metadata and complete audit trail |
The AI eTMF Agent helps keep the file current during conduct. It classifies incoming documents, flags quality issues such as missing signatures, and alerts on personal data that needs redaction, while people approve what is filed.
Book a demo to walk through a sponsor oversight view: TMF completeness, visit report review and deviation tracking for an outsourced study.
Book a Cloudbyz eTMF demo or email info@cloudbyz.com.