Regulations and compliance · Practical guide

TMF retention: keeping electronic trial records usable over time

Retaining an electronic trial master file requires more than storage space for 25 years. The sponsor and trial site need to identify the right records, the applicable basis for retention and a workable means of long-term access. Distinguish the Clinical Trials Regulation rule from requirements for patient medical files, and test archive handover, migration and provider exit.

Table of contents

At a glance

What applies to retention of electronic TMF records?

For trials under Regulation (EU) No 536/2014, the sponsor and investigator retain TMF content for at least 25 years after the end of the trial unless other Union law requires longer. Patient files follow national law. Electronic archives must preserve complete, readable and accessible records and traceable changes. Treat supplier changes and migration as controlled handovers.

  • The CTR-TMF deadline is not a one-size-fits-all retention period for all patient records.
  • Long-term usability includes context, access, and traceable changes.
  • Contract end and minimum retention period do not replace a justified decision on transfer or deletion.

For which documentation does the 25-year rule apply?

Article 58 of Regulation (EU) No. 536/2014 requires the Sponsor and the Investigator to retain the contents of the Trial Master File for at least 25 years after the completion of the clinical trial, provided that no other Union law prescribes a longer retention period. The same provision treats patient records differently: for these, national law applies. Therefore, retention of the same duration does not automatically follow from the term "clinical basis" for each individual item.

Source date: 7 October 2026. Basis is the consolidated CTR version dated 5 December 2022. The supplementary EMA-TMF guideline from 2018 outlines organizational structure and archiving requirements, including historical references to inspections under the previous directive 2001/20/EG. These historical references are not applied as alternative deadlines for current CTR inspections. This article addresses clinical investigations involving human medicinal products, and does not cover general GMP document retention.

Sources: [1] [2]

The retention plan begins with the data object

List the required records and their owners. Under Article 57, the sponsor and investigator each maintain a trial master file containing essential documents. Their contents may differ because their responsibilities differ. Identical duplication is not generally required, and not all trial site records belong in the sponsor archive.

The following work aid separates objects, deadline basis, and practical task. The specific assignment must be derived from the study context. A contractual clause or internal directive may include additional requirements, but it does not replace the evaluation of the relevant legal framework.

Define objects prior to the establishment of a retention period
ObjectApplicable assessmentPractical Clarification
Content of the CTR-TMF At least 25 years after the completion of the review; longer union rights reserved Study completion, responsible party, and actual archive holdings are identified.
Patient Record National storage requirements Determine the relevant national basis separately; do not unconditionally adopt the CTR deadline.
Electronic essential records Content, context, and required usability are ensured Verify required metadata, signatures, audit trails, and display-dependent relationships.
Draft or technical support file Assess function within the testing inventory Not only from file extension or storage location derive a deadline.
Historical review within the applicable framework Establish which law applied at the time and which provisions continue to apply Do not automatically transfer outdated guideline deadlines to CTR reviews.

Sources: [1] [2]

Archiving does not begin only with the last upload

Before release, verify that essential documents are complete, correctly assigned, and available on time. The EMA refers to risk-based quality controls of the TMF. A formally closed project with dispersed documentation, unknown owners, and unresolved references does not constitute a credible archive.

Make deviations visible: Which document is actually missing, which is located at an agreed alternative location, and which linkage is defective? Not every file needs to reside in a single system. However, access to the required documentation must remain clearly organized, even if the involved service providers or personnel are no longer available.

Sources: [2] [1]

Example: The contract ends prior to the retention obligation

Example: A sponsor terminates the contract with a eTMF provider. The export package includes the approved inspection protocol, a subsequent version update, and a signed document with attached supporting material. The provider's access shall cease upon transfer. As required, the authorized archivist shall be able to independently retrieve the relevant version and its associated relationships from the target repository.

The first access shows: The documents are readable, but the attachments link still directs to the old platform. Furthermore, the significance of the signature in the export is not apparent. A complete file counter would fail to detect both issues. The handover remains pending until context and access rights are verified against the defined scope of use.

Audit assignment for actual archive retrieval
Item under testExpected result in this exampleEvidence and Decision
Protocol and Latest Revision Status Each version is identifiable and correctly assigned. Retrieval from target batch, comparison of identifiers and container instructions.
Signed document Required signature information remains associated with the document. Control content, meaning, and assignment; do not mark open gaps as completed.
Linked appendix The attachment can be retrieved without access to the former provider. Identify defective links, establish relationships within the target dataset, and retrieve again.
Permission Archive managers receive the required access; unauthorized persons do not. Appropriate access tests conducted with the actual archive procedure.
End of the supplier service Required information and responsibilities remain available. Document the transfer closure and remaining obligations prior to the end of source access.

Sources: [2] [1]

Readability is an ongoing archiving responsibility.

Article 58 requires media to ensure completeness and readability throughout the retention period. For electronic records, this may necessitate the maintenance of an environment, appropriate emulation, or controlled migration. An archive therefore does not need to remain technically unchanged for decades; it must retain its required information and attributes.

Plan how changes to formats, keys, software, and permissions will be detected and managed. A migration requires appropriate evidence that the required attributes of the existing system are preserved. Generic directives such as "all as PDF" may lose the necessary relationships and usage capabilities when applied to dynamic data.

Sources: [1] [2]

Further reading:

External storage does not transfer all responsibility.

An external archive provider may take on agreed tasks. Define the actual storage location, access, protection, continuity, return of records and response to closure of the business or termination of the contract. The EMA expressly addresses these arrangements. Preserve the required trial site control over its records.

Article 58 also regulates the transfer of ownership of TMF content: it must be documented; the new owner assumes the responsibilities specified therein. A change in the technical data storage service is not automatically equivalent to the same event. In any specific transfer, clearly identify what is being transferred: the service, the data inventory, ownership, or a combination of these aspects.

Sources: [1] [2]

Do not automatically delete after 25 years

The CTR specifies a minimum duration with explicit reservation for longer EU regulatory requirements. Therefore, prior to deletion, applicable additional provisions and the actual status must be verified. Furthermore, an internally recorded end date must be based on the correct study end date and proper subject assignment.

A documented decision regarding the termination of a record should specify which documents are affected, what prerequisites have been evaluated, and who is responsible. This does not constitute a requirement for indefinite retention. The objective is a justified end that does not arise from a generic system timer or from an ambiguous equating of the TMF and patient record.

Sources: [1] [2]

Checklist for Electronic TMF Archiving

A practical retention strategy links legal assignment, responsibilities, and verifiable usability. Review the following points at archiving initiation and at relevant operational changes.

  • Assessment and regulatory framework have been identified; historical studies will be treated separately.
  • TMF documents, patient records, and supporting files are differentiated based on their actual function.
  • The minimum duration and reference to study completion are clearly defined and traceable.
  • Responsibilities of the sponsor and trial site and the scope of external services are clear.
  • Completeness, versions, and required relationships are verified prior to transfer.
  • Readability and authorized access function without unintended legacy vendor dependence.
  • Changes, migrations, and ownership transfers remain traceable.
  • A subsequent deletion occurs only after a renewed assessment of the relevant prerequisites.

Sources: [1] [2]

Project experience and collaboration

Test future TMF retrieval before handover

With TMF and study owners, we choose a historical question that must remain answerable after the supplier relationship ends. An authorised user searches for the document versions, relationships and evidence using the proposed archive alone. Focused retrieval tests may suffice with suitable tools. Missing context or technical dependencies need a further solution. We support technical handover and evidence planning. Patient records and other documents are assigned separately to their applicable retention basis.

Frequently asked questions about Trial master file retention

How long must CTR-TMF documentation be retained?

In accordance with Article 58 of Regulation (EU) No 536/2014, at least 25 years after the end of the clinical trial. Other Union law may provide for a longer retention period. Therefore, document the end of the study and the applicable framework instead of calculating the deadline solely from upload or completion of an IT project.

Sources: [1]

Does the 25-year retention period apply to every patient record?

No. Article 58 expressly refers patient medical files to national law. Determine the relevant basis separately. A file can be relevant to a clinical trial without falling under the same retention rule as every document in the trial master file.

Sources: [1]

Must the sponsor and trial site maintain identical archives?

Not mandatory. Article 57 takes into account different responsibilities and accordingly different TMF contents. What is essential is that each party provides its required documentation in a timely and compliant manner. A central platform must not obscure questions of responsibility and access.

Sources: [1] [2]

Is a backup simultaneously sufficient as a TMF archive?

Not solely due to its existence. A backup may support recovery, but it is not required to enable long-term retrieval of specific documents and versions. Assess completeness, readability, access, and retention in accordance with archival purposes; the technical designation alone does not determine suitability.

Sources: [1] [2]

Must all electronic documents be converted to PDF format?

No. The sources specify no universal target format. The replacement must preserve content, context, and required attributes. Static PDFs may be inadequate for dynamic records. Select and evaluate the format based on the actual data object and its long-term purpose.

Sources: [2]

Can the archive be migrated into a new system at a later date?

A migration is not inherently excluded. It requires appropriate controls to ensure the retention of required information and usability. Following the transition, specifically verify versions, documentation, metadata, and access records. A technically successful import alone does not constitute sufficient professional evidence.

Sources: [2] [1]

What must be agreed upon during a supplier change?

The specific scope of transfer, actual access, remaining responsibilities, and handling of contract termination or business cessation. Verify retrieval from the target system prior to loss of source access. If additional ownership of TMF content is transferred, Article 58 requires documentation of such content.

Sources: [2] [1]

Can the Sponsor fully take over the inspection site documentation?

Central archiving does not automatically require this. Protect identifying information and the trial site's control over its required records. Specify which records pass to which party and how intended access will be preserved.

Sources: [2]

Can a record be automatically deleted after 25 years?

The 25-year period is a minimum retention period, subject to longer EU regulatory requirements. Prior to deletion, verify the specific data holdings, the exact start date, and any other applicable provisions. An automatic retention period without such assessment may lead to premature expiration; it does not follow that unbounded data storage is implied.

Sources: [1]

How do we demonstrate that the archive is actually accessible?

Retrieve representative, selectively selected documents together with their required appendices, versions, and contextual information via the intended archiving pathway. Justify the audit scope based on risk and existing inventory. Document identified gaps and their closure; a simple list of files does not demonstrate practical usability.

Sources: [2] [1]

Sources and review date

Source date: 7 October 2026. EU Human Medicinal Product GCP within the respective areas of application described. Tables and case examples are standalone reference tools. Regional regulatory requirements and study documentation remain decisive; no equivalence between guidelines, EU regulation, and product function.

  1. EU: Regulation (EU) No. 536/2014 on clinical trialsConsolidated version as of 5 December 2022, version status verified on 7 October 2026. Articles 57–58 relating to the TMF and its archiving.
  2. EMA: Content, management and archiving of the clinical trial master fileGuideline dated 6 December 2018, effective from 18 June 2019. Sections 4.1.3, 4.2, 5.1–5.4 and 6.1–6.3.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Design TMF archiving as a verifiable process

We support you with data inventories, archiving requirements, and specific evidence for transfer, access, and long-term usability of electronic records.

  • GxP system decommissioning →

    Retire legacy systems while preserving data, context and auditability. We plan and manage the decommissioning so that data, metadata and audit trails remain readable and retrievable after shutdown.

Send a project enquiry Customer testimonials →