- Published
- Updated
- Sources checked
Long-term retention is useful only if authorised people can find and interpret the retained records. Plan archive retrieval before terminating a platform contract or accepting a vendor’s final export.
Define archive contents
Define an archive manifest covering data, documents, metadata, audit history and the tools needed to read them. Assign custody and access responsibility. Set the retention schedule from applicable study and regional requirements rather than assuming one duration fits every record.
Test an eTMF migration
For an eTMF migration, compare the source and destination inventory, document versions and relationships. Test a representative retrieval request using the future custodian’s access. Record missing features, unavailable signatures or unreadable attachments and resolve their impact before system retirement.
Archive retrieval checks
- Validate export completeness with documented comparisons.
- Preserve indexes, format information and necessary viewing instructions.
- Test access after staff and supplier responsibilities change.
Accept the custodian handover
Accept the archive after the receiving custodian acknowledges the manifest and demonstrates retrieval of a complete activity trail. Maintain a controlled process for later migrations and authorised changes. Storage invoices or a list of exported filenames do not demonstrate that the retained study can be reconstructed. Test retrieval of prior versions and their relationships as well as the latest file; readability alone may not preserve the history needed to explain changes.
Frequently asked questions
- Is a PDF export always sufficient?
- Assess whether it preserves the needed content, context and traceability for the specific record.
- When should retrieval be tested?
- Before system exit and again when significant format, access or custody changes create new risks.