When a sponsor outsources trial work, it keeps legal responsibility for the trial master file (TMF). The CRO holds the file and is accountable for what it contains. The European Medicines Agency's TMF guideline says the sponsor needs remote access to the CRO-held eTMF, "or at least regular access to relevant documents from it", to maintain oversight (EMA/INS/GCP/856758/2018, section 3.2).
The same guideline lists what the CRO contract should define for the TMF. The list includes:
The EU Clinical Trials Regulation adds that the TMF "shall at all times contain the essential documents". The guideline reads "at all times" as a requirement to file documents in a timely manner throughout the trial, not at close-out.
For a mid-size CRO running studies for eight or ten sponsors, every one of those obligations is multiplied by the number of sponsors. Each sponsor brings its own index preferences, quality-check expectations and audit schedule. Each sponsor's auditors will ask the same question: can you show us the file, complete and current, today?
The EMA guideline asks for one primary TMF system and says the number of other systems holding essential documents "should be minimised". Mid-size CROs often end up with the opposite: a document system, a CTMS, shared drives, email and sometimes each sponsor's own eTMF. Every extra location is another place an inspector can find a gap.
The guideline is specific about three hand-offs that tend to fail:
|
TMF task |
Shared drives and a generic document system |
Purpose-built eTMF |
|---|---|---|
|
Structure |
Folder trees that differ by sponsor and by study lead |
One indexed structure based on the TMF Reference Model, adjustable per sponsor |
|
Filing timeliness |
Unknown until someone audits the folders |
Filing dates captured as metadata and tracked against the TMF plan |
|
Monitoring visit reports |
Downloaded from CTMS and uploaded by hand |
Filed to the right artifact automatically once signed |
|
Sponsor oversight |
Exports and zip files sent on request |
Role-based sponsor access to that sponsor's studies only |
|
Quality checks |
Spot checks recorded in spreadsheets |
QC workflow with findings and e-signatures in the audit trail |
|
Audit trail |
File system history, if anything |
Date, time, user and reason for each upload, change and deletion |
|
Inspection access |
Staff pull documents while inspectors wait |
Read-only inspector access to an indexed file |
A CRO needs one system, not one per sponsor, but each sponsor must see only its own studies. Role-based permissions should restrict access by sponsor, study and document type. The EMA guideline also calls for restricted access to unblinding material such as randomisation codes and unblinded adverse event data.
The guideline recommends a standardised overall index across the organisation. Starting every study from the TMF Reference Model, with sponsor-specific additions configured rather than rebuilt, keeps the structure consistent across sponsors. Ask how quickly a new study can be set up from a template.
Because the TMF must contain essential documents "at all times", filing timelines in the TMF plan need to be measured. The system should capture document date, receipt date and filing date as metadata. A dashboard of documents filed late, by study and by function, gives QA a number to manage instead of a feeling.
Monitoring visit reports, site activation records and correspondence are generated in CTMS. When CTMS and eTMF are connected, a signed report can be filed to its predefined artifact without a download and upload. That removes one of the transfers the EMA guideline says must be validated.
Sponsors are expected to oversee the CRO-held file. A sponsor portal or read-only access lets sponsor teams review documents, completeness and QC status for their studies without requesting exports. It also gives the CRO an audit trail showing that the sponsor reviewed the file.
The guideline asks for risk-based QC that checks whether documents are present, correctly indexed, filed on time and accessible only to the right roles, plus a review of the audit trail. The eTMF should route documents through QC, record findings, and capture approvals with 21 CFR Part 11 compliant e-signatures.
At study end, the CRO may transfer the TMF to the sponsor or archive it on the sponsor's behalf. The guideline requires the eTMF to be archived with its audit trail, and the transfer to retain all metadata. Ask for a sample export: the index, the documents, the metadata and the audit trail should all come out together.
Full-service mid-size CROs hold the whole sponsor TMF for many studies. Sponsor separation (1), templates (2) and archiving (7) carry the most weight, because the same system must serve every client for 25 years or more under EU CTR Article 58.
Functional service providers handle parts of a study, often filing into the sponsor's own eTMF. The validated transfer between systems and clear ownership of each document matter most. A connected CTMS (4) reduces the number of documents that move by hand.
Specialist CROs in device, oncology or early phase studies carry extra essential documents, such as device accountability or IMP traceability records. A configurable index (2) lets these sit in the structure without workarounds.
|
Role |
What they need from the eTMF |
Capabilities |
|---|---|---|
|
eTMF managers and directors |
One structure across sponsors, and completeness and timeliness metrics |
1, 2, 3 |
|
QA directors and QA auditors |
QC evidence, audit trail review, inspection-ready access |
3, 6, 7 |
|
ClinOps directors and associate directors |
Study-level status for sponsor governance meetings |
3, 5 |
|
CRAs |
Signed visit reports filed without manual upload |
4 |
Platforms like Cloudbyz, among others, are built around the idea that a TMF document should be created, filed and checked in one connected system. How much manual work that removes depends on how your TMF plan, QC steps and sponsor agreements are configured.
|
Capability |
How Cloudbyz eTMF handles it |
|---|---|
|
Sponsor separation (1) |
Granular permissions and access controls by study and user role |
|
Standard index (2) |
Configurable TMF Reference Model with metadata management, plus one-click folder creation |
|
Timeliness (3) |
Real-time dashboards and reports on TMF status |
|
CTMS filing (4) |
With Cloudbyz CTMS on the same platform, signed monitoring visit reports file to predefined TMF artifacts, with no download and upload |
|
Sponsor oversight (5) |
A Sponsor Portal that gives sponsor teams visibility of their documents for verification and monitoring |
|
QC workflow (6) |
Review and approval workflows with 21 CFR Part 11 compliant e-signatures and a full audit trail |
|
Export and archiving (7) |
TMF export with metadata and complete audit trail for transfer or inspection |
The AI eTMF Agent adds intelligent intake: documents are dragged in, classified and checked, and issues such as missing signatures or personal data are flagged for review. Configurable thresholds decide which documents need a person to approve them. Your team stays in control of what is filed.
A global CRO that moved from paper and disconnected tools to Cloudbyz eTMF used the Sponsor Portal to give sponsor teams direct access for document verification. That replaced a cycle of requests and exports.
Book a demo to walk through study setup from a template, sponsor access, CTMS filing and a TMF export, using a study structure you already run.
Book a Cloudbyz eTMF demo or email info@cloudbyz.com.