Regulations and compliance · Practical guide

GxP data exports: how to identify, assess and close gaps

Gaps in a GxP export often surface when someone revisits an old transaction. The report survives but its amendments or attachments are missing. Define the purpose of the export, assess the missing relationships and document how GMP records from human medicines manufacturing will remain usable.

Table of contents

At a glance

How should we handle a GxP data export that omits important information?

Identify which records and relationships the export needs to preserve. Compare the export with the authoritative source, including relevant versions, attachments, identities and histories. Fill gaps through supplementary transfers or continuing controlled access. A successful export and matching file count alone do not demonstrate that the required record remains complete and understandable.

  • The export purpose determines the required content and context.
  • Identical file counts can mask missing versions or relationships.
  • Supplementary exports must be traceable to a usable record.

1. Clarify the intended use of the export purpose prior to determining the file format

Source date: 7 October 2026. For the human medicinal product GMP process described herein, Chapters 4 and Annex 11, in their current versions, are materially applicable. The work aid does not require that every exported document replace the complete electronic original record.

A report for a single technical query, an inspection copy, a data migration, and an archive transfer serve distinct objectives. A limited report may be appropriate for its specific query but may still be insufficient for the decommissioning of the source system. Explicitly define this boundary.

Define which subsequent question must be answerable: What value was in effect at the time of release? Who modified it? Which method and which appendix were associated with it? Only after this can it be determined whether PDF, structured data, or a combination is required.

Sources: [1] [2]

2. Systematically document missing contents

An export inventory links professional documentation with its constituent elements. It should not serve as a generic compilation of all technical protocols. Context is relevant for understanding, reconstructing, and evaluating the intended process.

PIC/S PI 041-1 outlines the importance of raw data, relevant metadata, data storage, and hybrid records. The guideline supports professional interpretation but does not replace existing requirements or the evaluation of your specific data format.

Which gap changes what the evidence can establish?
ComponentPossible export gapConcrete testing decision
Technical Values and Units Only final results, no necessary individual values Is the report sufficient for the intended purpose?
Version and Release Status Only current version instead of released version Ensure the historical record with its decision is secured
Appendices Reference remains, file missing Verify file and correct assignment.
Relevant change history Change detectable, previous value not reconstructible Provide supplemental history with process identification
Method or configuration reference Identification without legible previous content Maintain needed status and relationship

Sources: [3] [1]

3. Distinguishing Static and Dynamic Records

A static document can retain its intended meaning as a verified copy. In contrast, the later evaluation of dynamic data may depend on functions that a flat document cannot carry: for example, a mutable view, a context of analysis, or the traceable selection of a processing pathway.

Therefore, there is no general requirement for PDFs or a blanket statement that PDFs are always inappropriate. Assess the data functionality. Chapter 4 requires understanding and documenting relationships between records in complex or hybrid systems; Annex 11 addresses the readability and accessibility of archived data.

A supplier format may be technically appropriate if it remains usable over the long term. This includes assessing the required application, license, configuration, or description for reading purposes. An unknown binary file stored in a secure location does not constitute a practical accessible evidentiary proof.

Sources: [1] [2] [3]

4. An export comparison with apparently complete file count

The following example considers three released test reports, P01 through P03. Each report is accompanied by a required appendix. For report P02, a value was corrected prior to release; the correction must remain traceable for the intended archival purpose. The export program reports the generation of three PDF reports and no technical errors.

The comparison will be performed against the leading batch, not based on a self-prepared list derived from the export. Otherwise, the same filter error could both limit the results and the purported comparison benchmark.

The finding is not automatic evidence of a erroneous test result. It initially indicates an incomplete transfer of documentation. Whether prior decisions are affected must be evaluated based on the missing content and its significance.

Example: Comparison of Intended vs. Actual Results for Three Test Reports
Item under testExpected evidenceExport certificateInference
P01 Report and Appendix A01 Both present and correctly linked This comparison point is covered
P02 Approved report, A02 and relevant correction history Report and A02 available, history missing Additional traceable historical export required
P03 Report and Appendix A03 Report available, A03 missing Select the attachment for transfer and link it correctly
Total scope Three reports and three appendices with required context Three reports, two appendices Report number correct; archive purpose not yet fulfilled

Sources: [2] [1]

5. Design additional pathways such that the relationship is preserved

A possible solution is an additional export of histories or attachments. Define clearly which persistent identifiers link the files together, which version was exported, and how the user locates the overall process. Two complete files with no apparent relationship may still leave gaps in traceability.

Another option is controlled access to the source system or an appropriate read-only environment. Assess its actual durability, permissions, support, and recovery capabilities. A server that is still technically operational alone is not a viable archival solution.

If the gap cannot be closed, document its specific extent, remaining questions, and impacts on usage or decommissioning. A signature does not create missing original information retroactively. The authorized decision must take visible account of the limitations.

Sources: [2] [1]

6. Define acceptance criteria prior to inspection

Prior to finalizing, define what must be present and correctly associated. General criteria such as "export successful" or "files open" are too vague when historical releases or attachments are required. Also verify that special characters, units, time references, and status indicators retain their intended meaning.

For certain attributes, a complete automated comparison is appropriate. For others, specifically selected professional cases are required. A justified testing scope considers data classes, special conditions, known defects, and the consequences of an undetected gap; a random small sample is not automatically sufficient.

The assignment of documentation, findings, and decision constitutes part of the closure process. Clearly maintain the compared records so that a subsequent reviewer can identify the basis for the result.

Sources: [2] [4]

7. Checklist for a Reliable Export Release

The following checklist is suitable for preparing an export audit or for evaluating an existing package. It does not replace a product-specific review and does not require the use of any specific tool.

  • Purpose, data coverage, and relevant time periods shall be documented in writing.
  • Leading comparative reference independent of export identification.
  • Required values, versions, appendices, and relationships documented.
  • Evaluated relevant histories and release assignments.
  • Format, readability, and required technical aids verified.
  • Additional exports linked uniquely to stable identifiers.
  • Test scope and acceptance criteria defined prior to evaluation.
  • Gaps with implications, actions, and authorized decision documented.
  • Access and retention secured following a possible system shutdown.

Sources: [2] [1]

8. Department, IT, and Supplier Aligned on the Same Question

The department ensures that future decisions remain traceable. IT evaluates data structure, export capabilities, and technical dependencies. The supplier clarifies which content is actually included in a specific export and which is excluded. Quality assurance assesses the significance of open items within the intended GMP process.

For a small and medium-sized enterprise (SME), this alignment is more effective than a blanket request for a "complete export". Instead, request a content description and a meaningful sample including edge cases. This makes additional effort and potential limitations visible, as long as access to the source remains available.

Consider recurring exports within the change control process. New fields, altered statuses, or modified file associations may render a previously valid export incomplete, even though the program ends without error messaging.

Sources: [2] [1]

Project experience and collaboration

Check that the exported transaction retains its original meaning

With the process owners, we first define the question a future export must answer. We follow selected records, attachments, status, changes and relevant relationships through to the target view. A different export selection may restore a missing link. If technical limits remain, an additional controlled means of preserving the evidence needs assessment. We compare the records and assess remaining gaps. A matching file count does not demonstrate a complete business transaction.

Frequently asked questions about Gaps in data exports

Does the same number of files indicate that the export is complete?

No. Files may be duplicated or may lack required attachments, versions, and relationships. Compare unique identities and required contents against the master record. An appropriate number is a useful checkpoint but not a complete validation.

Sources: [2] [1]

Must every data export include the entire source system?

No. The content aligns with the intended use. A detailed report may be more concise than an archive package. When the source system is to be decommissioned, the required records together with necessary context must remain accessible and understandable elsewhere.

Sources: [2] [1]

Can we use PDF reports as archives?

This depends on the data format and the required evidence. Verify that value, meaning, and necessary context are preserved. For dynamic data, a PDF may lose significant evaluation capabilities; for appropriate static records, a reviewed copy may suffice.

Sources: [3] [2]

What do we do when the standard export does not contain an audit trail?

First assess which history is required for the intended purpose. Check for an additional history export or controlled further access. The assignment to the relevant technical datasets and readability must remain traceable.

Sources: [2] [3]

Can a screenshot of missing structured data be used as substitute evidence?

Only when it reliably retains the information required for the specific purpose and its context. For extensive relationships or dynamic records, this is often not the case. Assess suitability, rather than permitting or excluding screenshots indiscriminately.

Sources: [1] [3]

Is the absence of an annex automatically considered a product deviation?

First, a finding at the export stage is available. Its further significance depends on the content of the annex, the availability of the source, and the relevant decision-making processes. Assess these implications and derive appropriate actions, rather than classifying every export error as equivalent.

Sources: [2] [4]

Can a supplier verify the completeness of the data alone?

A concrete manufacturer confirmation can bear part of the proof. However, check whether it includes your export scope, the version used and the relevant data states. Open application-specific questions remain to be closed by appropriate supporting documents.

Sources: [2]

Do we need to manually compare all data sets?

A universal manual individual inspection is not required. Combine appropriate automated controls with professional inspections whose scope is justified. Consider particularly known gaps and data types that cannot be captured through simple quantity checks.

Sources: [2] [4]

When can the old read access be discontinued?

When required records and their necessary context are otherwise reliably available and the previous access no longer supports any remaining traceability function, consider retention, readability, recoverability, and pending findings prior to making a decision.

Sources: [2] [1]

How do we prevent the same gap after an update?

Take the export scope and relevant data relationships into account during the change evaluation. Assess whether new fields, statuses, or linkages alter the existing acceptance criteria. Recompute the affected controls with appropriate cases.

Sources: [2]

Sources and review date

Source date: 7 October 2026. Human medicinal products – GMP; purpose-specific evaluation of export and storage documentation. No general obligation to include every technical protocol element in every export. Tables and case examples are standalone reference tools, not results of conducted product testing. Draft versions do not establish enforceable additional requirements.

  1. European Commission: EU GMP Chapter 4, DocumentationJanuary 2011; effective from 30.06.2011; Principle and Sections 4.1, 4.8–4.10: Data relationships, records, and integrity during storage
  2. European Commission: EU GMP Annex 11, Computerised SystemsJanuary 2011 revision, applicable from 30 June 2011. Sections 3, 4.8, 7–10, 13 and 17 address supplier evidence, transfer, output, histories, changes and archiving.
  3. PIC/S: PI 041-1, Data Management and IntegrityPIC/S PI 041-1, 1 July 2021. Sections 9.1.3–9.1.5 and 9.9–9.10 cover data formats, relevant metadata, storage and hybrid records.
  4. EMA/ICH: Q9(R1), Quality Risk ManagementEMA/CHMP/ICH/24235/2006 Corr.2, published 31 January 2025. Q9(R1) has applied since 26 July 2023. Sections 4.3–4.6 and 5.1 cover assessment, control, review and appropriate formality.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Identify export gaps prior to system decommissioning

We help you define the required scope of evidence, evaluate existing export options, and systematically investigate open interrelationships. Thus, a collection of files is transformed into a traceable retention or transfer record.

  • 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.

Send a project enquiry Customer testimonials →