Independent and not affiliated with the FDA, MHRA, ISPE, PDA, or any agency. Get the appgoutham@madhadi.com
madhadi.comData Integrity & GxP Quality
Browse all topics → Articles Templates & Procedures Learning paths GlossaryScenariosToolsRegulatory ReferencesLearning PathsTopics About Start here
Log Plug-and-play starting point Data Integrity

Log: True Copy Certification Register

A plug-and-play register that records every certified true copy: the original identity, record type, copy method, verification evidence, certifier, date, and original disposition, with field definitions, retention, and a filled specimen set.

Document type: Log

Read and copy the template below into your own quality system. It is a generic starting point for your own internal use, provided as is, with no warranty; see the Terms and License. Adopting it does not by itself create compliance.

This is a ready-to-use register for recording certified true copies. It is the single place an inspector or auditor can go to see that a given original was copied faithfully, verified, certified, and, where relevant, retired under control. Replace every <<FILL: ...>> placeholder, keep one row per certified copy (or per certified batch of copies), and maintain the register under document control. A field-definition table, the blank register, instructions, retention, and a filled specimen follow. Verify each cited source against the current version. This is general guidance to adapt, not legal or regulatory advice. This register captures the certification step of the SOP: True Copy Generation, Verification, and Certification.

Why this register exists

A true copy is only defensible if you can show, later, that it was verified and certified before any original was retired or relied on. A scattered set of certification statements filed with each record does not answer “show me every original you replaced with a copy and prove each copy was verified.” A register does. It also lets QA confirm that no original was destroyed without a preceding certification, which is one of the most serious findings in this area.

Field definitions

FieldFormatRequiredWho entersDefinition
Register IDText (e.g. TCR-YYYY-NNNN)YesCertifierUnique identifier for this certification entry.
Date certifiedDateYesCertifierThe date the copy was certified (must predate any original destruction).
Original identityTextYesCertifierDocument number, batch, study, sample, or project that identifies the original.
Record typeStatic / DynamicYesCertifierWhether the original is static or dynamic.
Media / targetTextYesCertifierMedia or system the copy was made into.
Copy methodTextYesCertifierManual scan, or the named validated export/migration process.
Verification evidenceTextYesCertifierComparison record, checksum/hash result, record count, reprocess test result.
Certified byName / processYesCertifierThe person or the validated process that certifies the copy.
QA reviewName, dateYesQAQA review of the certification (especially for electronic batches).
Original dispositionRetained / Archived / DestroyedYesCertifierWhat happened to the original after the copy.
Destruction authorizationRef / N/AConditionalQAThe authorization reference if the original was destroyed.

Blank register

Register IDDate certifiedOriginal identityRecord typeMedia / targetCopy methodVerification evidenceCertified byQA reviewOriginal dispositionDestruction auth
<<FILL>><<FILL>><<FILL>><<FILL: Static / Dynamic>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL: Retained / Archived / Destroyed>><<FILL: ref or N/A>>
<<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>><<FILL>>

Instructions

  1. Create one entry per certified copy, or per certified batch when a validated process copies many records at once (record the count in the verification evidence).
  2. For a dynamic original, the verification evidence must include an integrity check (checksum or hash) and a reprocess sample test, not just a visual comparison.
  3. The date certified must be on or before any original destruction date. If original disposition is Destroyed, the destruction authorization reference is required and its date must be after the certification.
  4. Do not backfill. Enter the certification when it happens, so the register itself is a contemporaneous, attributable record.
  5. QA reviews entries on a defined cycle to confirm no original was destroyed without a preceding certification.

Retention

Retain the register under document control for not less than <<FILL: retention period, at least the longest retention of any record it certifies>>. The register outlives the individual copies it certifies, because it is the evidence that each copy was defensible.

Filled specimen

Register IDDate certifiedOriginal identityRecord typeMedia / targetCopy methodVerification evidenceCertified byQA reviewOriginal dispositionDestruction auth
TCR-2026-008718 Jul 2026CDS project ARCHIVE-2021-Q3, HPLC-07, 1,284 filesDynamicVendor-neutral archive storeValidated export ARC-EXP v3.2SHA-256 match 1,284/1,284; 25-file reprocess test passedProcess ARC-EXP v3.2 + M. OkaforM. Okafor, 19 Jul 2026Archived (source retired)N/A
TCR-2026-008820 Jul 2026Analytical Worksheet WS-2026-0412, Batch B-77310, pp. 1-4StaticScanned PDF in QC archiveManual scanPage-by-page comparison, complete and legibleA. Patel (verifier: L. Duarte)R. Gomez, 21 Jul 2026Retained in QC archive box QC-A-219N/A
TCR-2026-009125 Jul 2026Logbook LB-QC-014 (full, closed)StaticScanned PDF + controlled destructionManual scanEvery page verified; closed bookJ. Nkemi (verifier: L. Duarte)R. Gomez, 26 Jul 2026DestroyedRD-2026-0033 (28 Jul 2026)

The specimen shows all three common cases: a dynamic electronic archive certified by a validated process plus QA, a static paper copy retained alongside its original, and a static original destroyed after certification with the destruction authorization dated after the certification. Note the destruction date is after the certification date, never before.

Common inspection findings this register prevents

  • An original was destroyed and no certification predates the destruction.
  • A dynamic copy was certified on a visual comparison only, with no integrity or reprocess check.
  • Certifications exist scattered with records but cannot be produced as a complete list on request.
  • Register entries were backfilled after the fact rather than recorded contemporaneously.

How to adapt this register

  1. Set your Register ID scheme and align it with your document control numbering.
  2. Add a link or reference to the underlying certification statement and verification evidence for each row.
  3. If most of your copies are high-volume electronic batches, add a per-batch record-count column.
  4. Automate the checksum and reprocess-test evidence capture where your validated tools support it.
  5. Confirm the retention and destruction references against your records retention SOP before issue.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.