Table of contents
At a glance
How can a GxP archive remain usable after several years?
A GxP archive should keep required records available, readable and understandable in context throughout the applicable retention period. File existence alone is insufficient. Test search, display, metadata, access and technical dependencies. Format or viewer changes may require a new suitability assessment.
Scope and Applicability
The focus is on the long-term accessibility of archived records. Specific retention periods are derived from applicable regulatory requirements and data type; this article does not establish a uniform deadline for all GxP data.
Readability means more than simply being able to open a file.
A record is only acceptable for its intended purpose if the content and meaning remain clear. A numerical value may require a unit, a method status, and a specific assignment. A document may be incomplete without an appendix or a prior version. Therefore, evaluate specific historical inquiries rather than simply opening a file.
Annex 11 addresses archiving considerations regarding access, readability, and integrity. The required implementation depends on data type and intended use. A general requirement for a specific file format cannot be derived therefrom. An appropriate format for a static SOP may be inadequate for dynamic laboratory information.
Capture formats, viewers, keys, and other technical requirements. Fonts, external links, or proprietary analysis software may influence interpretation. File size and a successful copy operation do not prove usability. The inventory should list required components and their respective responsibilities.
Design a readability and searchability test
Start with the intended user and their question. What information must they find, what relationships must they understand, and what decisions must they be able to justify? Identify both typical and critical edge cases. A random sample of only simple documents may overlook important dynamic interrelationships.
Document the incoming inventory, target state, and expected statement. The test may include retrieval, display, export, and, if necessary, additional processing. Not every historical dataset needs to be arbitrarily re-computable. What is essential is identifying the function required for the intended retention and traceability purposes.
| Retrieval scenario | Required context | Own acceptance question |
|---|---|---|
| Test result | Probe, unit, method and evaluation | Is the previous statement clear? |
| Corrected record | Original and revised version, with the reason for change | Can the change be traced? |
| QMS-Investigation | Relationships and Appendices | Is the investigation completely justifiable? |
| Electronic Decision | Person, Significance, Timing, and Record Reference | Was is the previous approval justifiable? |
| Long-term format | Viewer and technical requirements | Does the intended access in the target system function? |
Example: PDF contains results but not the relevant dynamics
A chromatographic process is documented as a PDF. The printed output displays the reported value. However, for subsequent investigation, information regarding the underlying processing and any result modification is required. The PDF extract alone does not address this question.
Assess the additional information required and how it can be obtained through the archiving pathway. This may include an appropriate data package with supplementary contextual information or controlled access to a suitable application. The article does not prescribe a universal archiving architecture. The decision must cover the actual scope of evidence required.
Subsequently, review the complete audit case file. A duly authorized reviewer is provided only with the intended archive information and attempts to answer the historical question. Missing relationships or non-readable components are treated as findings. A simple completeness count might have failed to identify this gap.
| Test step | Action | Expected finding |
|---|---|---|
| Find | Investigate the referenced process | Unique identification |
| Read | Show value, unit, and context | The content is understandable |
| Explain | Trace historical decisions | Required relationships available |
| Check for changes | Investigate correction case | The original and amended versions can be explained |
| Limit access | Use unauthorized role | Selected information protection provides protection. |
Evaluate dependencies and format changes
Review the dependencies. Proprietary file formats may require specific viewers, licenses, or operating systems. The presence of a viewer alone is insufficient if keys, reference data, or documented access pathways are missing. Archive responsibility must therefore encompass the entire usage pathway.
When changing format, it is necessary to assess which information is retained. A flat view can be suitable for certain records; in the case of dynamic data, evaluability or context may be lost. Successful technical export alone does not prove the suitability of the target archive.
Demonstrate integrity and readability separately
A checksum can verify the bit-level integrity of data when properly implemented. It does not confirm the correct interpretation or completeness of the original export. An incomplete file may remain unchanged. Therefore, technical integrity checks should be combined with professional reconciliation and verification.
Conversely, a file may be easily readable even if it has been uncontrolledly modified after the fact. Review access rights, change pathways, and the need for traceability. The appropriate control measures may vary depending on the archive. A single term such as "revision-safe" does not replace a detailed description of the actual procedure and its limitations.
Evaluate export transformations. A deliberate change in format or structure may be required, but must not result in loss of required information. Document source, target, rule, and reconciliation. For deliberate reduction, provide justification explaining why the omitted information is not necessary for the intended use.
Consider technological changes and restoration efforts
An archive format may currently be supported and could become difficult to read in the future. Assign responsibility for changes to viewers, operating systems, storage, or keys. The assessment should verify whether previous retrieval cases continue to function. A blanket annual re-migration cannot be inferred therefrom.
Test a suitable restoration pathway. Following this, investigate known historical cases. Successful restoration of a folder does not prove that permissions, links, and viewer functions are operational. The test scope should reflect the actual technical dependencies.
When an archiving migration is required, treat it as a controlled change. Establish and maintain traceability between the original dataset, the transformation process, and the new target system. The same historical case can serve as a comparative scenario before and after the migration. This ensures not only the technical replication but also the preserved usability of the data.
Assign ongoing archive responsibility
Identify professional data ownership and technical support. The functional area defines the required historical traceability; IT ensures appropriate access and recovery capabilities. Both perspectives are necessary. Technical oversight cannot alone assess functional completeness based on storage capacity alone.
Document the access path, search criteria, and known limitations. An archive is of limited practical value in daily operations if only the original project participant can locate the correct file. A practical handover, including routine and critical search scenarios, demonstrates whether the intended model functions as expected.
Review the need for consideration of relevant changes. New insights from an investigation may indicate that a previously unconsidered context is required. Such insights should feed back into inventory and archiving concepts. Storage is thus an integral part of the data lifecycle, not merely a technical task of data retention.
Draft: responding to a historical inquiry from the archive
Use the table to answer specific historical questions, such as the method status of a corrected result. Document the information identified and where the evidence ends. The same reference case may later trigger a format change: prior to and after the change, the required statement must remain intact, even if the stored bytes change due to transformation.
| Search field | Example entry | Acceptance question |
|---|---|---|
| Activity | Historical result E-90. | Unambiguously identifiable? |
| Context | Probe, unit, method and specificity. | Is the statement clear? |
| Change | Original and corrected versions. | Can a change be justified? |
| tool | Designated viewer in the intended use. | Actually usable? |
| Access | Authorized reviewer without project-specific rights. | Practically achievable? |
| Recovery | The same case after appropriate retry. | Is the required usage available? |
Formatting decision: to assess the required subsequent action test
Select the archive format based on historical considerations. A PDF is well suited for representing a static report. A CSV file can transport structured values, but relationships, data types, or leading zeros may be lost if export and import mechanisms are not properly aligned. A native format enables dynamic usage, but requires appropriate software and a controlled technical lifecycle. No format is inherently fully suitable solely based on its name.
Example: A reviewer must distinguish between results, the applied method, and a subsequent re-evaluation of a measurement. A PDF containing the latest result addresses only part of the information. A tabular export may include values, but does not adequately explain the methodological context. The decision may therefore require a combination of sources. Evaluate this based on actual practice, not on an abstract preference for open or native formats.
| Required action | Possible limit | Suitable acceptance step |
|---|---|---|
| Read the report | Missing page or cropped content | Compare complete known report |
| Evaluate values | Data type or unit changed | Independent reading of reference dataset |
| Understand relationships | Link not exported | Investigate related objects |
| Review history | Only the latest version is available | Change and original differ |
| Leverage dynamics | Viewer or logic missing | Required function to be executed for control check |
| Understand signature | Context of content separated | Review and verify the recording and statement jointly |
Evaluate export and subsequent import as two processing steps
A correctly generated file may be interpreted differently upon subsequent opening. Spreadsheet applications may automatically detect date values and identifiers. Therefore, verify the intended viewer or import pathway. Document format, character encoding, delimiters, units, and any required metadata in sufficient detail. The future user must have adequate context to correctly understand the information.
When multiple formats collectively form an archive package, their assignment is verified. A file containing measurement data and a separate method PDF must unambiguously belong together. A manifest or another controlled structure may assist; the specific format is determined by internal methodology. Assess the maintenance and recovery procedures. A collection of readable individual files does not constitute a reliable traceable evidence set if the professional interrelationship between components has been lost.
Next steps
- Define data types, storage requirements, and required retrieval media.
- Document technical and organizational dependencies.
- Check readability and professional context with appropriate examples.
- Regular and occasion-based inspections and responsible parties to be defined.
Project experience and collaboration
Answer a historical question with the tools that will remain available
Your Quality and archive owners select a historical transaction. Using only the planned archive tools, we try to reconstruct the conclusion drawn at the time. We record missing method versions, data relationships and access rights separately. A static record may call for a different solution from a dynamic analysis. With IT, we check viewers, licences and whether the material can be found again. This gives you a practical basis for maintaining readability and ownership after the original system retires.
Frequently asked questions about Archive readability
Is PDF always an adequate archiving format?
How often must readability be verified?
Annex 11 does not specify a fixed calendar interval. Stored data must be verified for accessibility, readability, and accuracy (7.1); for archives, item 17 addresses accessibility, readability, and integrity. Following significant system changes—such as modifications to hardware or software—the retrievability must be ensured and validated. The ongoing schedule should be determined based on risk assessment. A supplier change or end-of-support for viewing tools represents typical additional triggers.
Is a backup an archive?
Does a checksum serve as adequate archive evidence?
It may support an appropriate technical integrity check. It does not verify completeness, correct context, or readability alone. Supplement with required comparisons and specific retrieval tests. An unaltered, originally incomplete file remains incomplete even when correctly checksummed.
Must dynamic data always remain in the original system?
Not mandatory. An appropriate, validated pathway can provide the required assurance. Assess which dynamic properties and contextual information are required for the intended purpose. A static representation may be insufficient. The decision will be justified based on specific historical queries and the actual target architecture.
Should readability tests include only simple files?
No, if the required archiving purpose involves more complex interrelationships. Supplement with appropriate cases including appendices, corrections, or dynamic context. Selection will be derived from historical queries. A large number of seamlessly opened simple PDFs does not validate untested complex data relationships.
What do we do when an older viewer is no longer supported?
Assess technical risks, required usage, and potential alternative pathways. An alternative viewer or archival migration could be suitable, but requires appropriate supporting evidence. Review content and context using reference cases. The mere installation of new software does not validate the integrity of historical data.
Is an open file format always better than the native format?
Not at all. Open formats can support long-term accessibility, but lose needed dynamics or relationships. Native formats can get more context, but need suitable software and operation. Check the required historical action and, if necessary, a controlled combination of both approaches.
Why must the subsequent opening of a CSV file also be verified?
Since the employed viewer may automatically interpret values differently, for example date formats or leading zeros, verify the intended import pathway using reference data. Format descriptions and metadata support correct usage. A file that remains unaltered does not guarantee accurate technical representation.
Sources and review date
Annex 11 encompasses stored and archived data, Chapter 4 covering the associated records; PIC/S supplements the data integrity framework. Incidents related to readability and format comparisons in the article are proposed evaluation criteria for the content required later.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)§§ 7 and 17: Readability, accessibility, and integrity in the intended archive purpose. Current version as of EudraLex on 14.10.2026; no universal project or deadline specification.
- European Commission: EU GMP Chapter 4, Documentation (2011)Document referencing and records. No general specification regarding the number of pages for an SOP.
- PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.
Sources checked: .
Later archive search to practically ensure security
We support you in assessing the current situation, clarifying responsibilities, and implementing appropriate evidence within operations. The type of support that is most effective depends on your system, your team, and the specific objective.
- 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.

