Regulations and compliance · Practical guide

Original records and true copies: demonstrating completeness

After a system change, the supplier delivers a proposed true copy. The files open and the row count matches, but does the package retain the original evidence? Define the content, context and future review capability needed. The example helps QA, IT and process owners verify a copy for human medicinal product GMP documentation.

Table of contents

At a glance

When is a copy complete enough to preserve the original evidence you need?

A true copy is a verified copy that preserves the required information in the original record and its context. This can include metadata, relevant history and necessary dynamic features as well as the displayed result. Identify the full record and use a demonstrated copying process or documented verification. Neither a PDF nor a native export is a complete verified copy solely because of its format.

  • Before export, define what constitutes the complete record.
  • Check content and significance, not just file or line counts.
  • Required dynamic properties and reading tools are considered.
  • Copy verification, archive operation, and deletion decision to be evaluated separately.

The original is more than the final result view

In electronic records, the original record may consist of multiple interconnected data elements. A results report may display only a portion of these elements. For a laboratory case, for example, raw signals, parameters, sample references, and processing statuses may be required to reconstruct the activity.

Define this boundary based on intended use and applicable requirements. Chapter 4 addresses raw data and its significance for quality decisions. The specific record definition should therefore be explained by the functional area and mapped to IT systems at the actual storage locations.

Sources: [1] [2]

What is meant by True Copy

The MHRA defines a verified copy in which information including context, content, and structure is retained. The use of an alternative storage format is not automatically excluded. However, its suitability must be demonstrably justified.

A "True Copy" stamp does not substitute for this evaluation. Identify the original, the scope of the copy, and the procedure by which its equivalence is verified. It must remain evident whether a single copy has been validated or a suitable copying process has been employed.

Sources: [2] [3]

Define the scope of copying as a technical requirement.

The following table serves as an example of an electronic inspection record. It is not a comprehensive list for every application. Specifically review which information is truly required for traceability and how its linkage is maintained after export.

Own specified template for a inspection record
Data segmentWhy is it required in the example?Acceptance question
Record and sample identification Prevents incorrect assignment. Is each identifier uniquely and accurately linked?
Measurement values and units Explains the basis of the results. Are values and units still clearly understandable?
Processing parameters Enables traceable evaluation. Is the parameter set used for the result status clearly identifiable?
Relevant change history Explains correction and reevaluation. Can the intervention be traced to the original state?
Evaluation and release basis Identifies the version that was used. Is the decision linked to the correct record?

Sources: [1] [2]

Static representation and dynamic properties differ.

A printed copy of an evaluation can be clearly readable, while a more detailed view may be required for a subsequent review. In such cases, the printed output is insufficient. Conversely, not every originally electronic record necessitates advanced editing functions within the archive.

Assess which interactions are required for integrity verification and subsequent validation. Document the necessary functionality instead of mandating unbounded continued operation of the original application. An appropriate alternative must enable the required understanding and evaluation.

Sources: [2] [3]

Example: Four lines are still not a complete copy

For the export example, four records—Q-01, Q-02, Q-03, and Q-04—are specified. The independent expectation includes exactly these four distinct identifiers, each associated with the previously defined data segments. A defective export package contains Q-01, Q-02, Q-03, and Q-03 again. The number of rows remains four, but only three expected identifiers are present; Q-04 is missing.

Additionally, Q-02 includes a controlled correction to a sample description. For the required evidence, this historical record must be retained. The example therefore verifies identity, content, and profile. It features a separate target matrix and no performed export test of a product.

Own acceptance matrix for sample export
Export variantObservation in this examplePre-defined evaluation
Four lines, Q-03 duplicated Q-04 is missing despite matching row count. Incomplete; no decrease by number alone.
All identifiers, only final values Missing required correction reference for Q-02. The specified record scope is insufficient.
Complete data, unknown file format The content cannot be reliably opened in the target. Determine and provide evidence of usability prior to acceptance.
Complete statement with appropriate presentation Identifiers, contents, and relevant history comply with the required comparison. Can be evaluated as an appropriate copy after documented verification.

Sources: [1] [2]

Copy review ensures reproducibility

State the export batch, selection criteria, and tools used. Prior to execution, define which attributes are to be compared. A hash can indicate whether a specific file has been modified; however, a hash alone does not confirm that the export contains all required source data.

For larger volumes, automated comparisons can provide support. The suitability of such approaches and the handling of exceptions also require justification. A sample inspection is neither automatically sufficient nor fundamentally excluded. What is critical is whether the procedure can reliably detect specific types of errors.

Sources: [4] [2]

Do not equate archive, copy, and original destruction.

The successful copy validation does not fully address all questions regarding storage. Access control, readability, accountability, and future retrievability must function for the required duration. The decommissioning of an application also requires a controlled transition to future operations.

A planned destruction of originals constitutes a separate decision based on the currently applicable requirements. The article does not provide a general authorization for such action. Document the basis for the future decisive evidence, identify any exceptions, and specify how the responsible party will justify the decision.

Sources: [2] [1] [4]

What should be available prior to the copy request

The department outlines records and required verification; IT details export capabilities and formats; QA evaluates the appropriate control. A supplier may provide technical documentation and sample exports without thereby automatically assuming responsibility for determining the required record set.

Inconsistent legacy records, broken links and missing reading tools are particular sources of effort. Investigate these early using a small, demanding data example. A clean standard record alone cannot show how the process handles corrections, attachments or uncommon formats.

  • Describe the original record and the expected scope professionally.
  • Define identifiers, metadata, history, and required functions.
  • Prepare normal conditions and at least one identifiable fault scenario.
  • Copy status, procedure, and release decision to be documented.
  • Clarify later access, protection, and responsible operation.

Sources: [2] [4]

Project experience and collaboration

Test the copy against a question you may need to answer later

Before a system change, process owners and QA select a record whose meaning must be preserved. We compare the original and copy, including required relationships, history and analytical functionality. A static record may be suitable if it retains the necessary context. Dynamic data may need a different copying or archiving method. With IT, we prepare traceable comparisons. Replacing or destroying an original requires a separate, reasoned decision by the customer.

Frequently asked questions about Original data and true copies

Is a PDF always a true copy?

No. A suitable copy may exist if the required information and attributes have been demonstrably obtained. A PDF containing only the final value may be incomplete in comparison to a more comprehensive original record. The format alone does not determine this question.

Sources: [2] [3]

Must the copy have the same file format?

A different format may be acceptable if it preserves meaning, context and the information needed for review. Assess the conversion against defined requirements for the records. Check for loss of relevant information that might otherwise go unnoticed.

Sources: [2]

Is a checksum comparison sufficient?

It can assess the identity or subsequent modifications of specific files. It does not verify that the correct volume of data was exported or that a field was semantically correctly transformed. Add the required attributes for your record to the comparison.

Sources: [4] [2]

Why does the same number of rows not suffice?

Duplicates can conceal missing content. In this example, four rows contain only three distinct expected identifiers. Compare identities, links and data content as well as totals.

Sources: [1] [2]

Which metadata must be retained?

Those relevant to content, context, reconstruction, and applicable requirements. This may include identities, time stamps, parameters, and change history. An unverified list of all technically available metadata would be no more useful than a blanket exclusion.

Sources: [2] [3]

Must dynamic evaluation be retained?

When a dynamic property relating to integrity or subsequent verification is critical, the copy strategy must take this into account. Describe the specific required function. It does not follow automatically that every original editing capability must remain permanently available.

Sources: [2] [3]

Can a scanned paper original replace the original?

Yes, under certain conditions. The MHRA Guidance states that a True Copy, such as a scan, may be retained instead of the paper original, provided a documented procedure verifies and records the integrity of the copy (6.11.2). The risk of destruction must be assessed separately. Additionally, verify the applicable retention requirements in your area before the original is disposed of. A PDF alone does not constitute a validated True Copy.

Sources: [2]

Who validates the copy?

Responsibility for inspection evaluation is defined within the quality system and must be commensurate with the required scope. According to the MHRA definition, two methods of verification are established: a dated signature or generation through a validated process (6.11.2). The selected method must demonstrate the same information, including context, content, and structure. A technical export notification does not serve as a substitute for this verification.

Sources: [4] [2]

Do we need to manually compare each data point?

The appropriate audit can integrate manual and automated components. The scope and methodology depend on data structure, potential errors, and existing evidence. Automated controls also require a clear and traceable justification of their suitability for the specific task.

Sources: [4]

How does the topic differ from archiving?

True Copy addresses the demonstrated information equivalence of a copy. Archiving additionally includes its regulated retention and subsequent access. Therefore, a passed copy test may serve as a potential basis, but remains insufficient as a complete archiving operational justification.

Sources: [2] [4]

Sources and review date

Source date: October 6, 2026. Scope and document status are distinguished within the text. Examples and work aids are proposed suggestions; they do not replace assessment of your specific process.

  1. European Commission: EU GMP Chapter 4, DocumentationJanuary 2011; Principle; Records; §§ 4.1, 4.8–4.12
  2. MHRA: GxP Data Integrity Guidance and DefinitionsRevision 1, March 2018; Sections 2–5; 6.1–6.11; Data review and archiving definitions
  3. FDA: Data Integrity and Compliance With Drug CGMP, Questions and AnswersFDA Data Integrity Q&A, December 2018: Questions 1(b) and 1(d) regarding metadata and dynamic records, as well as Questions 9 and 10 concerning copies and electronic laboratory originals.
  4. European Commission: EU GMP Annex 11, Computerised SystemsRevision January 2011; Principle; §§ 1–4, 7, 9–13, 17

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Clarify the specific decision jointly

We support your team in linking the applicable requirement to the actual data workflow and a traceable validation evidence. Starting point are your existing documentation and the open technical question.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →