Table of contents
At a glance
What belongs in a GxP archiving project?
In a GxP archiving project, map records to activities, repositories, retention requirements and future retrieval needs. Define when completed records enter the archive and which relationships with the active system must remain. Test transfer and retrieval. Assign responsibility for ongoing controls, archive migrations and eventual disposal. The source system can remain in operation. A successful export addresses only part of the project.
- Derive the retention period from the actual record type and applicable framework.
- Data values without relationships, versions, or meaning may be insufficient.
- Archiving can occur from active systems and requires a clear distinction from the current inventory.
- Retrieval, relevant changes and the end of storage are part of the supervised operation.
Which records are grouped together?
Start with activities whose execution must be demonstrably traceable. During a testing procedure, samples, methods, raw data, and results may be interrelated. In a quality process, deviations, associated corrective actions, and their evaluation are typically linked. Chapter 4, Section 4.10 requires clear assignment of a record to the relevant activity and its storage location, along with effective controls that ensure data integrity throughout the retention period, and where appropriate, validation.
A usable plan therefore specifies more than one folder. It defines the type of record, responsible department, primary storage location, required relationships, and the basis for deadlines. It must also indicate whether the record is still under processing or has been finalized. The mere presence of an archival function in the system does not prove that any given record is suitable for offsite storage.
First, align with the archiving consultant to establish this technical foundation. A documentation matrix can assist QA, the functional department, and IT in identifying gaps and deciding on their resolution. A blanket commitment to migrate all data into a single format would bypass this clarification.
Record retention periods, start dates, and exclusion reasons to be separately documented.
There is no universal retention period for all GxP data. Chapter 4 section 4.11 sets a minimum for batch documentation of one year after batch expiry or five years after certification by the Qualified Person, whichever is longer. Section 4.12 addresses other critical documents, including raw data supporting the marketing authorisation, generally for as long as the authorisation remains valid. These examples concern particular document types in human medicines GMP. Additional legislation and product-specific requirements may apply.
The responsible personnel determine deadlines and suspension grounds; a records archivist can structure the assignment and its technical implementation. Use the table to link these decisions to specific inventory holdings. No general authorization for destruction is derived from file extension, storage age, or license expiry.
| Entry in own timeline plan | What the team holds firm | The decision thereby becomes possible |
|---|---|---|
| Recording type and reference | Affected activity, product, or batch | Select the appropriate foundation base |
| First rule and significant event | Justified rule with required reference data | Determine the period for the specific inventory balance |
| Authoritative repository and context | Archive holdings, relationships, and required representation | Prepare a complete retrieval at a later date |
| Responsibility and Exclusion Grounds | Responsible role, open investigation, or other justified suspension | Hold or present for decision an isolation. |
| Decision and Implementation | Rationale, scope of impact, approved action | Handle results in a traceable manner |
What must remain readable and understandable later?
For some records, a static readable format is sufficient. Other records require additional data structures or features to ensure their meaning remains interpretable. The FDA Data Integrity Guidance distinguishes in this context between static and dynamic records. Do not derive a blanket requirement for a specific archiving product from this distinction.
Review the questions in the table for the actual data types and future retrieval purposes. This enables justification for which information and presentation options must be retained.
| Component | Possible significance | Assessment question |
|---|---|---|
| Data value | Content of the record | Has the value been completely and accurately transferred? |
| Unit and Reference | Technical Interpretation | Can he be assigned to the right process? |
| Version | Version applicable at the time | Which method or instruction applied? |
| Relationship | Relationship of multiple information sources | Are the sample, result, and documentation linked? |
| Change history | Traceability of relevant changes | Is the original contextual information still available? |
| Presentation | Later Use and Justification | Can a responsible employee understand the record? |
Archive completed records from a system that remains active
Define a justified boundary between ongoing processing and archived inventory. A completed inspection task may be handled differently than a process whose results are still under evaluation. Whether specific cases can be deferred depends on the process and the demonstrated capabilities of the employed system. Annex 11, Section 17, does not require system decommissioning for archiving purposes.
Before outsourcing, clarify which system will provide the authoritative record and how personnel will locate it. Will references from the active inventory remain valid? Will future enhancements be required? How is it ensured that two differently maintained copies will not produce conflicting statements? These questions are more specific than a general choice between cloud and local storage.
Allow the intended pathway to be demonstrated on a defined, representative dataset. Verify data transfer, relationships, rights, and access using the actually intended tools. Cleaning of the source repository will follow a separate, independently assessed decision; successful copying alone is not sufficient justification.
Plan technical changes and archive migrations as separate tasks.
Even an already archived record may change. The storage platform, file format, viewer, or archiving software can change, while the retention continues. For each specific transition, define source, target, affected inventory, transformation processes, and required documentation. When transferring to a different format or system, Annex 11 Section 4.8 addresses the preservation of data value and/or meaning. According to Section 17, retrievability under relevant system changes must be ensured and validated.
Counts and checksums can provide technical evidence. If the presentation changes, also check that reviewers can still establish what they need to know. Identify reference cases, outstanding differences, fallback options and the person or group authorised to decide. An unchanged total does not establish that attachments or versions are linked correctly.
In the care assignment, determine who is responsible for identifying impending supplier changes and assessing their impact. A supplier change project is considered completed when the actually affected archived inventory has been transferred together with appropriate documentation. A successful demonstration using a few unnamed files does not adequately represent the scope of this requirement.
Example: Archive completed test assignments from an ongoing LIMS system
Assume a laboratory continues to use its LIMS but wishes to transfer completed test assignments from a defined time period to an appropriate archive. Ongoing activities remain in the operational system. The team defines which assignments are considered completed and which links are required for future complaint or quality-related inquiries. This example does not describe a manufacturer function.
In the pilot scenario, an authorized employee is assigned a specific task: to locate a designated older inspection assignment and explain the results using the then-applicable method and the required associated documentation. The pilot also assesses the transition from daily working environment to the archive repository. The pilot demonstrates that a clear assignment can suffice, or that additional relationships and presentation tools may be necessary.
Only from the evaluated results is the subsequent offloading process derived. A next batch may contain different data types or dependencies, requiring an adjusted assessment. Ongoing maintenance includes responsibility, retrieval checks, and relevant changes; it does not end with the first successful export.
Verify deletion and integrity in the ongoing archive operation
Provide a specific question to a responsible employee, for example regarding a previous result. They should be able to locate the required record, open it, and explain it with the necessary context. Verify access rights and actual tools available. A file may exist technically but remain unreadable within the intended working environment.
Annex 11 Section 7.1 addresses access throughout the entire retention period. Section 17 requires verification of archived data for accessibility, readability, and integrity. Following relevant system changes, retrievability must be ensured and validated. Therefore, establish and define review triggers and responsible parties, along with appropriate additional controls for ongoing operation. A mandatory annual retrieval test for all archives is not inferred from this.
A verifiable inspection result must include a specified inventory, verified sample request, used environment, identified gaps, and their resolution. Protection, backup, and recovery procedures also require appropriate authorities. A service provider report with a general green status does not replace these information elements.
When storage ceases
Prior to a planned exclusion, the responsible roles assess whether the applicable deadline has expired and whether legitimate blocking reasons exist. The authorized action and its actual scope are clearly justified. This represents an independent organizational procedure, not a general deletion rule applicable to all GxP data. Chapter 4, Section 4.12 addresses the specific case where certain records are replaced by a complete new dataset; in such cases, a documented justification is required. This scenario does not constitute a blanket release for the deletion of older files.
A meaningful consultation assignment specifies actionable outcomes: documentation and deadline plan, evaluated archiving route, pilot and transfer review, operational retrieval controls, change pathway, and decision route at the end of retention. Additionally, arrange internal involvement, open prerequisites, and handover to your team. According to Annex 11, Section 3.1, responsibilities for external services must be clearly defined.
If archiving is part of a system decommissioning, additional tasks related to interfaces, access points, and dependencies arise. A dedicated guideline for the procedure of GxP system decommissioning is available for this purpose. This article addresses the archiving process within the ongoing lifecycle.
- Assign activities, records, and primary retention locations.
- Identify the time limits, required reference data and blocking grounds.
- Active inventory and archived inventory controlled to be delineated.
- Review aborts and relevant archive modifications with specific cases.
- Decision on separation and transfer of service providers can be arranged in a comprehensible manner.
Project experience and collaboration
Plan archiving as an ongoing process
With the process owners, QA and IT, we start with a defined collection of records. We identify which relationships future users will need and how they will retrieve one specific record. A pilot can then establish which transfer and retrieval checks are necessary. Whether records remain in the current system, move to external storage or transfer to a different archive depends on retention periods, intended use and the functions available.
Frequent Questions on GxP Data Archiving
Must we decommission the source system for archiving purposes?
How often must the subsequent retrieval be verified?
Annex 11 No. 17 requires that accessibility, readability, and integrity be verified, and that retrievability be ensured and tested in the event of relevant system changes. This section does not specify a fixed annual inspection interval. Establish justified controls, triggers, responsible parties, and procedures for handling results within your archiving process.
Sources: [2]
How long must we retain the data?
The duration follows the type of record, product, and regulatory area, as well as other applicable requirements. Chapter 4 distinguishes, among other things, batch documentation and critical documents forming the marketing authorization basis. Ensure that the rule, start date, and required reference data are clearly documented. Solely relying on storage or file age does not constitute an exemption.
Sources: [1]
What evidence do you need when changing archive software?
Identify affected stocks, transformations, required context, and future usage. Assess appropriate technical and subject-matter reference cases. Upon transfer to another format or system, Annex 11 Section 4.8 addresses value and/or meaning; Section 17 requires assured and tested retrievability for relevant changes.
Sources: [2]
Can expired deadlines automatically lead to destruction?
Prior to initiating a release, verify the applicable expiry basis, the actual inventory level, and any potential blocking reasons with the relevant responsible roles. A technical date alone is insufficient to justify this decision. Document clearly and traceably who determines the scope of the action and how the authorized measure is implemented.
Sources: [1]
What information does a records archiving specialist need for a specific task?
Useful are documentation types, leading systems, deadline bases, intended offloading activities, and specific future retrieval questions. Supplement with interfaces, display methods, responsible parties, and known gaps. Agree on results for pilot, transition, and ongoing operation separately; unknown prerequisites remain visibly identified.
Sources and review date
Primary source date: October 17, 2026. Focus is on electronic records within the human medicinal product GMP environment. Retention periods vary by document type and regulatory framework. Context matrix, retention period schedule table, task breakdown, and the example are standalone planning aids. The FDA distinction between static and dynamic records represents a complementary U.S. perspective; therefore, no universal archive format exists.
- European Commission: EU GMP Chapter 4, Documentation, January 2011 revisionControlled documentation and records; official EudraLex entry with original chapter.
- European Commission: EU GMP Annex 11, Computerised Systems, January 2011 revisionHuman medicinal products – GMP; in particular, §§1–4, 7, 10–13, 16–17; specific application for each section.
- FDA: Data Integrity and Compliance With Drug CGMP – Questions and Answers, December 2018Data integrity in pharmaceuticals under CGMP; no reinterpretation of new tests into historical records.
- ICH Q9(R1): Quality Risk Management, official text from the European CommissionRisk-driven decisions, appropriate formalities, and handling of subjectivity; own matrices are implementation proposals.
- European Commission: EU GMP Chapter 7, Outsourced ActivitiesOutsourced GMP-related activities, suitability, responsibilities, agreements, and monitoring.
Sources checked: .
Concretely describe an archive question from ongoing operation
Select a documentation type with a leading retention location, primary deadline basis, and a subsequent retrieval query. Specify whether an active inventory is to be offloaded, an existing archive is to be modified, or an operational gap is to be addressed. From this, a verifiable first request can be developed.
- 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.

