English 
French 
GxP archiving must preserve regulated records and the context needed to interpret them throughout the applicable retention period, even after the people, suppliers and computerised systems that created them have changed.
A defensible archive preserves the record together with enough context to explain what it is, where it came from, whether it is complete and how its integrity has been maintained.
This checklist provides a practical framework for planning that archive. The exact controls and retention periods still depend on the record class, jurisdiction, quality system and intended use.
1. Define the records and responsibilities in scope
Start with record classes, not storage locations. A GxP archive can include clinical, laboratory, manufacturing, quality, safety, regulatory and validation records held across several systems.
For each class, establish:
- the authoritative record;
- the business owner and archive owner;
- creation, review and approval responsibilities;
- applicable retention rules;
- expected users, auditors and inspectors;
- legal-hold or investigation requirements;
- responsibilities shared with CROs, laboratories, vendors or other third parties.
Ambiguous ownership is a preservation risk. If responsibilities or ownership transfer, the change should be documented.
2. Preserve the complete record, not only the visible file
The evidence value of a GxP record may depend on more than its rendered content. The archive scope may need to include:
- content and attachments;
- business and technical metadata;
- identifiers and relationships;
- version and approval history;
- relevant audit-trail events;
- electronic signatures and validation context;
- applicable retention and access information;
- documentation of migration and reconciliation.
The required evidence package should be defined before extraction. Otherwise, archive projects tend to preserve what is easiest to export rather than what is needed later.
3. Apply ALCOA+ throughout retention
ALCOA+ describes qualities associated with reliable regulated data: attributable, legible, contemporaneous, original, accurate, complete, consistent, enduring and available. Some guidance and quality systems also make traceability explicit.
Where these data-integrity principles apply, the relevant qualities need to remain demonstrable through archiving. For example:
- identity and approval context should remain attributable;
- formats and representations should remain legible;
- timestamps and event sequence should remain understandable;
- authoritative originals or verified copies should be identifiable;
- content, metadata and relationships should remain complete;
- records should remain retrievable for authorised use.
See What ALCOA+ Means for Long-Term Data Integrity and Archiving for a detailed explanation.
4. Control the source-to-archive transfer
Migration is part of the evidence lifecycle. It should be planned, repeatable and documented.
A controlled transfer normally includes:
- Approved scope and selection rules.
- A controlled source state or documented cut-off.
- Repeatable extraction and transformation methods.
- Reconciliation of records, identifiers, files and exceptions.
- Integrity checks such as hashes and manifests where appropriate.
- Review and approval of migration results.
- Retention of the reports needed to explain the transfer later.
Successful ingest alone does not demonstrate completeness. A documented reconciliation between the source, export and archive is an important control for demonstrating that the intended records were transferred.
5. Maintain metadata, provenance and audit evidence
Metadata explains the record. Provenance explains its origin and history. Audit evidence helps show what happened to it.
An archive should preserve enough of each to answer questions such as:
- Who created, changed, reviewed or approved the record?
- Which process, study, product, batch or system produced it?
- Which version was authoritative?
- What happened during migration and ingest?
- Who accessed or exported it later?
- Which retention rule or legal hold applied?
Not every source-system event needs to become an archive event. The preservation scope should be risk-based, documented and sufficient for the record's intended evidential use.
6. Keep records legible and usable
Long retention exposes records to format obsolescence, lost software dependencies and changing user expectations.
Preservation planning can include:
- format identification and risk monitoring;
- retention of authoritative originals;
- controlled creation of usable representations;
- documented format migration when required;
- preservation of structured data and its schema or explanatory context;
- validation after any preservation action.
The archive should not depend indefinitely on an unsupported source application for ordinary retrieval.
7. Govern retention, legal hold and disposal
Retention rules should be linked to record classes and applicable triggers. The archive should support documented extensions, legal holds and controlled review before disposal.
Deletion must be as governable as retention. A defensible process identifies what is eligible, records who approved the action and preserves the required audit evidence.
Avoid applying one generic retention period to every life-sciences record. Clinical trial, manufacturing, quality, safety and subject medical records can follow different rules.
8. Protect access and preserve traceability
Access should follow role, purpose and need. Controls may include role-based and attribute-based access, time-limited external access, segregation of duties and approval for sensitive exports.
Access and archive actions should be logged in a form that remains reviewable. Inspectors and auditors should be able to receive the records they need without exposing unrelated content or relying on broad administrative access.
9. Support timely inspection retrieval
Availability is an operational requirement, not a theoretical property. Test whether users can:
- search by relevant business identifiers;
- retrieve authoritative records and related context;
- understand versions and relationships;
- produce controlled exports;
- provide evidence of integrity and archive history;
- do so within the organisation's inspection procedures.
For Trial Master Files, EU requirements explicitly address ready availability, direct accessibility, completeness, legibility and traceability throughout long-term retention. See eTMF Archiving After Clinical Trial Closure.
10. Validate the archive in its intended use
Archiving technology alone does not make a process compliant. The organisation remains responsible for its quality system, risk assessment, procedures, configuration, migration controls, training and validation decisions.
Validation should reflect intended use and risk. It should cover the workflows and controls that matter in practice, including ingest, integrity verification, retention, access, retrieval, export and relevant administrative actions.
Supplier documentation can support this work, but it does not replace customer-side validation and governance.
When should a legacy GxP system be retired?
Retirement should follow evidence that the required records and context have been transferred completely, the archive operates as intended and authorised users can retrieve what they need.
Keeping a legacy system running can retain cybersecurity exposure, unsupported software, licensing costs and operational dependencies. A governed archive can provide an alternative when the migration and decommissioning decision is risk-assessed, documented and properly controlled.
A concise GxP archive readiness test
Before approving an archive or system retirement, ask:
- Can we define the authoritative record for every in-scope class?
- Can we demonstrate completeness from source to archive?
- Are metadata, relationships, audit evidence and signatures preserved where needed?
- Do ALCOA+ qualities remain demonstrable after migration?
- Can we explain every transformation or preservation action?
- Can authorised users and inspectors retrieve records without the source system?
- Are retention, legal hold and disposal governed and traceable?
- Can we export records with sufficient context for independent review?
If several answers depend on institutional memory or an ageing application, further evidence or remediation may be needed before archive approval or source-system retirement.
How Docbyte Vault fits
Docbyte Vault is designed as a long-term preservation and evidence layer downstream of operational GxP systems. It preserves records with metadata and evidence context, supports governed retention and controlled access, and helps organisations reduce dependence on source applications retained only for historical lookup.
Vault does not replace the customer's pharmaceutical quality system, validation responsibilities or regulatory assessment. It provides archive capabilities and supporting evidence that can be incorporated into a controlled GxP process.
Discuss your GxP archiving requirements
