English 
French 
Closing a clinical trial does not close the lifecycle of its Trial Master File. The documents and data that demonstrate how the trial was managed may need to remain complete, legible, traceable and accessible for decades.
That creates a practical question for sponsors, investigators and Clinical Research Organisations: what exactly must an archived electronic Trial Master File preserve?
An archived eTMF may need to preserve documents together with relevant metadata, relationships, history and evidence of control.
What is a Trial Master File?
The Trial Master File, or TMF, is the collection of essential documents and records used to manage a clinical trial and demonstrate that it was conducted in line with the protocol, applicable requirements and Good Clinical Practice.
An electronic Trial Master File, or eTMF, applies the same principles in a digital environment. It may include documents, structured metadata, workflows, version history, approvals, correspondence, system records and audit-trail information held across a sponsor, investigator, CRO and service-provider landscape.
EMA guidance describes the TMF as supporting trial management by the investigator, sponsor and CRO and enabling monitors, auditors and inspectors to evaluate trial conduct and data quality. That purpose continues after the active trial has ended.
How long must a TMF be retained in the EU?
Article 58 of Regulation (EU) No 536/2014 requires the sponsor and investigator to archive the content of the clinical trial master file for at least 25 years after the end of the clinical trial, unless other Union law requires a longer period.
The same Article requires the archived content to be readily available and accessible to competent authorities on request. It also requires the media used for archiving to keep the content complete and legible throughout retention, and any alteration to the content of the TMF to remain traceable.
Medical files of trial subjects follow applicable national law, so they should not be treated as if the TMF retention rule automatically determines every clinical record category.
What should be preserved when an eTMF closes?
Essential documents and records
The archive needs the applicable essential documents, not only a convenient subset. Scope should be based on the trial, responsibilities and the records required to reconstruct and evaluate conduct.
Examples can include protocol and amendments, approvals, investigator documentation, safety information, monitoring records, communications, reports and versions of the Investigator's Brochure that are relevant to the trial history.
Metadata and filing context
Documents without filing context are difficult to assess. Preserve the metadata that identifies the trial, artefact, country, site, milestone, owner, status, version and other relevant classifications.
The archive should retain enough structure to explain where each record belongs and how related records fit together.
Version and approval history
Final documents alone may not explain which version was effective, who approved it or when it entered use. Relevant version, signature and approval evidence should remain associated with the record.
Audit trail and traceability
Article 58 of Regulation (EU) No 536/2014 requires any alteration to the content of the TMF to be traceable. As a preservation practice, migration and preservation actions should also be documented.
The archive should be able to show what was ingested, when it arrived, what validation occurred and whether later actions changed a representation, metadata field or access state.
Ownership and responsibility
Clinical trials commonly involve distributed responsibilities. Contracts and records should make clear which party is responsible for maintaining and archiving each relevant part of the TMF.
If ownership transfers, the transfer and the new responsible party should be documented.
System and validation context
Where an eTMF depends on application behaviour to explain records, relevant system documentation, procedures and validation context may form part of the preservation scope.
The objective is not to preserve every technical artefact indiscriminately. It is to retain the evidence needed to understand and assess the archived records after the original system is no longer available.
The risks of exporting an eTMF to folders
A bulk export may preserve document files while weakening the TMF as evidence. Common losses include:
- filing structure and relationships;
- workflow and approval context;
- version history;
- complete audit-trail information;
- original identifiers;
- evidence that all expected records were transferred;
- controlled access and retention rules.
The result can be a large collection of readable files that is difficult to reconcile, search or defend during an inspection.
A controlled eTMF archiving process
1. Define closure and archive responsibilities
Agree who closes the TMF, resolves outstanding quality issues, approves the archive transfer and remains responsible during retention. Responsibilities across sponsor, investigator, CRO and vendors should be explicit.
2. Establish the preservation scope
Define the documents, data, metadata, audit evidence, relationships and system context that form the archive package. Document exclusions and their rationale.
3. Perform completeness and quality checks
Use the applicable TMF plan and expected-document model to identify missing, misfiled, duplicated or unresolved records. Archive transfer should not silently convert known quality issues into permanent uncertainty.
4. Export deterministically
Record the export method, selection rules, timing, software version and responsible parties. Freeze or control changes during transfer so source and export can be reconciled.
5. Reconcile source, export and archive
Compare counts, identifiers, file sizes and hashes where appropriate. Preserve manifests and exception reports so the transfer can be explained later.
6. Preserve content and context
Ingest records with their metadata and relationships. Preserve authoritative originals and document any normalisation or format migration.
7. Apply retention and access governance
Retention should reflect the applicable legal and organisational requirements. Access should be restricted, reviewable and logged, with a practical route for authorised inspection retrieval.
8. Test retrieval and export
An archive is not ready merely because ingest succeeded. Test representative searches, document viewing, relationship navigation and evidence exports before retiring the source system.
Can the original eTMF system be retired?
It may be possible to retire the application once the organisation has demonstrated that the archive preserves the required records and context, supports applicable access and retrieval requirements, and retains sufficient evidence of a controlled migration.
The decision should be risk-based and documented. Keeping an obsolete system alive is not automatically safer. It can create cybersecurity, support, licensing and validation burdens while still providing poor long-term evidence portability.
How digital preservation strengthens eTMF archiving
Digital preservation treats the eTMF as a governed evidence set rather than a static document collection. It combines content, metadata, provenance, integrity controls, retention, access logging and preservation actions so the trial record remains understandable beyond the lifespan of the source platform.
Docbyte Vault is designed to preserve records and their evidence context, provide controlled retrieval and help organisations reduce dependence on retired operational systems. It does not replace sponsor oversight, TMF quality management or validation responsibilities.
For the broader regulatory context, read GxP Archiving Requirements: A Practical Checklist and What ALCOA+ Means for Long-Term Data Integrity.
Review your eTMF archive approach
If your archive plan depends mainly on a document export, review whether metadata, relationships, audit history, completeness evidence and inspector access will remain defensible after the eTMF platform is gone.
Discuss your life-sciences archiving requirements
