Request a demo specialized to your need.
For decades, "essential documents" in a clinical trial meant a fairly standard checklist the same core set of records, generated the same way, for nearly every study regardless of size, risk, or design. ICH E6(R3) changes that starting point. Under Appendix C, the nature and extent of the records a sponsor generates and maintains is expected to depend on the trial's design, its conduct, and how relevant that specific record actually is to the trial. That's a meaningful shift from "file everything on the standard list" to "justify why each record belongs."
Here are six practical changes this creates for how sponsors, eTMF managers, and QA teams need to think about essential records going forward.
1. "Essential" is now a judgment, not a fixed checklist
Appendix C doesn't hand sponsors a universal document list and call it done. It asks for a risk-proportionate approach — meaning a low-risk, single-site study and a complex, multi-country trial with decentralized elements may reasonably generate different essential record sets. Treating every study identically, the way many TMFs have operated under legacy checklists, no longer aligns with the guidance's intent.
2. Record-keeping decisions need a documented rationale
If the extent of essential records is meant to reflect risk and relevance, sponsors need to be able to show how that determination was made not just present a completed folder structure. A defensible TMF under E6(R3) increasingly means being able to explain why a given category of record was included, excluded, or handled at a particular level of rigor.
3. Trial design directly shapes what belongs in the TMF
A study with a simple, well-established protocol and a study using novel decentralized elements do not carry the same documentation risk profile. Appendix C expects the essential record set to reflect that difference, which means TMF structure decisions increasingly need to be made study-by-study, informed by design and risk, rather than defaulting to a single template across the portfolio.
4. Site-level proportionality complicates uniform TMF templates
Within a single study, sites can vary meaningfully in complexity, enrollment volume, and risk profile. A rigid one-size-fits-all site-level TMF structure sits uneasily with a genuinely risk-proportionate approach. This doesn't mean abandoning consistency it means building enough flexibility into TMF governance to reflect real differences without losing overall standardization.
5. Annex 2 extends this thinking to decentralized and real-world-data elements
ICH E6(R3)'s core Principles and Annex 1 were finalized in January 2025 and came into effect in the EU on 23 July 2025. Annex 2 covering additional considerations for non-traditional trial designs, including decentralized elements, pragmatic elements, and the use of real-world data was adopted by the ICH Assembly on 3 June 2026, with an EU effective date currently set for 15 January 2027. For sponsors running or planning decentralized or hybrid trial elements, this means the essential record question extends beyond traditional site documents to how data from remote visits, digital consent, and non-traditional data sources gets captured and justified as part of the TMF.
6. Inspection readiness now includes defending proportionality decisions, not just completeness
Under the legacy checklist model, inspection readiness was largely a completeness question is everything on the list present? Under a risk-proportionate model, an inspector can reasonably ask why a particular record category was scoped the way it was. Being "TMF complete" and being able to explain the proportionality rationale behind that completeness are now two related, but distinct, readiness requirements.
What changes in practice
| Legacy Approach | Appendix C Approach |
|---|---|
| Fixed essential document checklist for every study | Record set scoped to trial design and risk |
| Completeness measured against a universal list | Completeness measured against a justified, risk-based scope |
| Uniform site-level TMF templates | Site-level structure informed by relative risk and complexity |
| Inspection readiness = document presence | Inspection readiness = presence plus documented rationale |
| Decentralized/RWD elements handled ad hoc | Annex 2 gives these elements defined GCP consideration |
Why this matters for eTMF Managers, QA, and Clinical Operations
This shift changes the kind of conversation eTMF Managers and Directors need to have with QA and Clinical Operations early in study setup not just "what documents do we need," but "what does our risk and design profile justify, and can we show our reasoning." QA and Compliance Directors preparing for inspection now need evidence of a proportionality rationale sitting alongside document completeness metrics.
Clinical Operations teams designing decentralized or hybrid elements need to factor essential-record planning into study design conversations from the start, rather than treating documentation as something that gets sorted out after the protocol is finalized.
How Cloudbyz's eTMF tools approach this
Cloudbyz's eTMF Agent is built to support a study-specific approach to essential records rather than forcing every study through an identical template. Folder structures and expected-document configurations can be adapted per study, and classification, quality control, and completeness scoring operate against the configuration set for that specific trial not a single fixed list applied uniformly across a portfolio.
As proportionality rationale becomes part of what inspection readiness requires, having a system that reflects study-specific record scope, rather than a one-size-fits-all structure, makes it easier to keep that reasoning documented and consistent as studies move through their lifecycle.
What this means by role
- eTMF Managers & Directors get study-specific configuration instead of retrofitting a universal template onto every trial.
- QA & Compliance Directors and QA Auditors get a system that can reflect and support a documented proportionality rationale, not just a completeness percentage.
- Clinical Operations Directors and Managers planning decentralized or hybrid trial elements get a platform that can adapt as Annex 2 considerations become part of standard study design.
Appendix C isn't asking sponsors to file less it's asking them to file deliberately, with a rationale that holds up under inspection. That's a different discipline than working through a static checklist, and it's worth building into study setup now rather than reacting to it later.
Book a demo with Cloudbyz
Subscribe to our Newsletter
