Table of contents
At a glance
Which retention periods apply to GMP records?
For human medicinal product GMP, retention depends on the record’s type and purpose. For batch documentation, Chapter 4 specifies one year after expiry or at least five years after QP certification, whichever is longer. Determine the basis for other records separately. Preserve integrity, readability and access throughout the required period. Reaching a calculated date does not by itself authorise deletion.
- Purpose of recording to be clarified prior to selection of storage medium and filename.
- Compare both time references for batch documentation.
- Validation and approval timelines may continue beyond the initial period.
- Technical storage and justified retention or destruction decisions are separate responsibilities.
1. First determine the defined range
As of 6 October 2026, EudraLex Chapter 4 remains in effect in the version dated January 2011. The following deadlines apply to the named human medicinal product GMP scope. For investigational products, specific product categories, clinical documentation, active substances, or additional national and other applicable requirements, separate bases must be determined.
A laboratory report, a manufacturing instruction, and a data migration protocol serve distinct evidential purposes. Therefore, different timelines may therefore apply within the same application. Begin by asking which activity or decision is supported by a particular dataset. The organizationally simplest setting—“all records retained for seven years”—is neither automatically valid nor sufficient without explicit assignment to a specific activity or decision.
For a German operation, include section 20 AMWHV in the retention register. Subsection 1 specifies at least one year after expiry and at least five years for the records it lists. Certain product groups and investigational medicinal products have separate provisions. Map the records to the relevant EU GMP and German requirements before setting the retention period.
2. Compare the two time references for batch documentation
Chapter 4 §4.11 specifies for the currently considered batch documentation a period of one year after the batch expiry date or at least five years after qualification by the Qualified Person. The longer period is decisive. Therefore, the production date is not automatically the start date of the period. Similarly, considering only the remaining shelf life of the medicinal product is insufficient.
Maintain the certification date and expiry date with reliable traceability. If either of these dates is unknown or its significance has been altered during a migration, automated expiry calculations may be inaccurate. Additional evaluation of specific product requirements or other storage justifications must then be conducted. The expiry formula must not obscure such open questions.
Sources: [2]
3. Two batches with different applicable endpoints
Example calculation: Both batches were certified by a Qualified Person on 15 March 2026. For batch A, the exact expiration date is set as 30 September 2028; for batch B, it is 30 September 2032. The data are intentionally fully defined in this example; a labeling with only month and year would require a prior clear and unambiguous professional interpretation.
Five years after certification, both expire on 15 March 2031. One year after expiry, A expires on 30 September 2029 and B on 30 September 2033. Therefore, A has a longer certification anchor, while B has a longer expiry anchor. The table determines only the minimum endpoint from this specific rule, not an automatic destruction release.
| Batch | QP Certification + 5 Years | Expiry + 1 year | Longer endpoint |
|---|---|---|---|
| A | 15 March 2031 | 30 September 2029 | 15 March 2031 |
| B | 15 March 2031 | 30 September 2033 | 30 September 2033 |
Sources: [2]
4. Validation and approval may generate additional dependencies.
§4.12 deals with other types of documentation after the supported activity. Critical documents, including raw data, which support information of an authorisation, should be retained during their validity. For certain completely replaced data a justified separation can be considered. Among other things, relations to batch documentation remain relevant.
A new validation report does not automatically render previous validation records obsolete. Therefore, verify which released batches were based on the prior validation and determine whether a new, complete dataset truly supersedes the prior evidence. Document the scope of the supersession. An identical report title or the decommissioning of the old application does not constitute valid evidence of supersession.
Sources: [2]
5. A deadline register links evidence and decision-making
A practical register does not need to be comprehensive. It should indicate what needs to be retained, why, where the relevant version is stored, and who determines the endpoint. Entries for linked data context prevent reports from being lost, while preserving interpretable history without premature loss.
The following structure serves as an independent work aid. Supplement with additional applicable bases and specific storage considerations as needed. An empty time anchor remains visible as an open point; it is not replaced by an arbitrary creation date.
| Record type | How to determine the deadline | Context needed | Decision prior to isolation |
|---|---|---|---|
| Batch documentation | Both time anchors from §4.11 plus additional applicable requirements | Batch, Certification, Expiry, relevant changes | Was are the endpoint and additional attachments verified? |
| Regulatory Support Validation Data | §4.12: Purpose, Approval and, if applicable, Justified Replacement | Report, raw data and affected batches | Has full replacement been demonstrated? |
| System evidence | Supported process and still required data | Version, Configuration, Tests, Limitations | Is the evidence required for explaining retained data? |
| Technical Operating Log | Specific objective for detection and risk | Event reference, investigated incidents | Which events are relevant and for how long? |
6. Storage includes the availability of data
Annex 11 Sections 7 and 17 address access, readability, integrity, and retrievability. The presence of a data carrier is insufficient if the team is unable to meaningfully access or correlate the data. Determine which metadata, relationships, and, if applicable, software functions remain necessary for the respective validation evidence.
A PDF may be suitable for a specific audit trail, but it is inadequate for capturing dynamic data structures or critical change histories. The decision depends on the required content. When transitioning formats, validate with concrete datasets by assessing value, significance, identity, and context. An equal number of files serves only as a supportive indicator, not a complete integrity assurance.
7. Treat system end, contract end, and data end separately
A cloud termination does not eliminate the professionally required retention of data. Arrange in advance how data, including necessary context, will be obtained and maintained in accessible form. A technically successful backup does not substitute for long-term documentation and evidence decisions. The restoration of current operations and the review of a historical process are distinct validation objectives.
Before a separation, the responsible party should assess the current purpose, calculated endpoints, ongoing investigations, and any other applicable bindings. Document the scope, decision, and actual execution. This is a practical approach, not a claim; each login entry does not need to remain indefinitely or for the same duration as any batch record.
8. Checklist for the next deadline decision
For implementation, subject matter record owners, QA, and IT work together. The functional side defines the intent of the traceability, QA provides the applicable framework, and IT identifies storage locations and technical dependencies. A single export request alone cannot replace the first two decisions.
Start with a logging approach and a real-world workflow. Then verify whether the selected rule inadvertently captures other data types. Particularly, automated deletion rules require clear exceptions and a reviewed handling procedure for missing or modified triggers.
- Documentation type and supported decision to be named.
- Establish and define applicable bases with version and scope specified.
- Verify the time stamp and origin of the relevant data.
- Multiple endpoints and ongoing assay requirements are considered.
- Assign required raw data, relationships, and history.
- Plan readability and access duration for the required period.
- Automation in the absence of a trigger and for exceptions to be verified.
- Perform separation only after a documented business decision has been made.
Project experience and collaboration
Link deadlines to the batches actually affected
With Quality and archive owners, we classify records by purpose, including batch documentation, data supporting a marketing authorisation, investigational medicinal products and other holdings. We identify current conclusions that still depend on older evidence. A superseded document may warrant different treatment from raw data underpinning a process validation still in use. We develop a retention schedule with named owners. Disposal requires a separate authorised decision. A folder's age alone is insufficient.
Frequently asked questions about GMP record retention periods
Does a five-year validity period apply to all GMP data?
No. The five-year component described herein pertains to the rule for batch documentation and is compared against the expiry anchor. Other documents follow their intended purpose and applicable additional requirements. A universal five-year retention period for the entire application cannot be inferred.
Sources: [2]
Does the deadline start with manufacturing or QP certification?
For the specified five-year component, QP certification is the reference. Additionally, a one-year period after expiry is considered. Clearly record both events; the date of a file transfer or import does not replace either event.
Sources: [2]
Can we automatically delete at the calculated end date?
Does the storage period end with system decommissioning?
Must validation raw data always be retained indefinitely?
Not unlimited in all cases. Chapter 4, Section 4.12 requires that critical marketing authorization-supported documentation, including raw data, be retained for the duration of the marketing authorization. In the case of a fully replacing new dataset, a justified exemption may be acceptable. However, raw data from a process validation must be retained for at least as long as the documentation for all batches whose release is based on that validation. Therefore, determine first which ongoing statements depend on the old dataset.
Sources: [2]
Does a signed report without raw data suffice?
For regulatory support, validation and stability data, a signed report alone is insufficient: Chapter 4, Section 4.12 explicitly identifies the associated raw data as critical retained documentation. For other forms of evidence, the required documentation package shall be determined based on its intended use. A report must not obscure the information necessary to justify its conclusions or any quality decision derived from it.
Sources: [2]
Must all data be converted to PDF format?
Must each technical log be retained for as long as a batch record?
Not automatically. The significance of the logs, their linkage to GMP-relevant activities, and their actual purpose as evidence of compliance are decisive. Define relevant events and dependencies; an untargeted equating of all technical data with batch documentation is not effective.
Do these examples also apply to investigational medicinal products?
No. The calculation concerns authorised human medicines. For investigational medicinal products, the manufacturer must retain the product specification file and batch records for at least five years after completion or discontinuation of the last clinical trial in which that batch was used. See Article 8(3) of Delegated Regulation (EU) 2017/1569 and Chapter 4 section 4.11. Separate retention obligations may apply to the sponsor and investigator.
What do you do when the certification date is missing?
Sources and review date
Source date: 6 October 2026. The referenced current guideline versions are pertinent. Tables and test cases are standalone work aids and do not constitute completed product testing.
- EudraLex – Volume 4 – Good Manufacturing Practice guidelinesRetrieval issue; Human and veterinary medicines separately handled
- European Commission: EU GMP Chapter 4, Documentation (2011)Revision 1, January 2011; applicable from 30 June 2011.
- European Commission: EU-GMP Annex 11, computerized systems (2011)Revision 1, January 2011; applicable from 30 June 2011.
- EU: Delegated Regulation (EU) 2017/1569 on GMP for investigational medicinal productsArticle 8(3) addresses manufacturer retention of the product specification file and batch documentation for at least five years after completion or discontinuation of the last clinical trial using the batch. Official German text checked on 18 October 2026.
- Internet laws: § 20 AMWHV, Documentation retentionClause 1, together with specific provisions in clauses 2–5; German legislative text specifically reviewed on 18 October 2026.
Sources checked: .
Clarify responsibilities and documentation for your operations
We support you in translating relevant requirements into practical decisions, appropriate evidence, and controlled operations.
- 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.

