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
Form Plug-and-play starting point Cell & Gene Therapy

Form: Chain of Identity / Chain of Custody Verification Log (CGT)

A plug-and-play COI/COC verification log for autologous and patient-specific CGT: field definitions, two-identifier and condition checks at each handoff from apheresis to administration, with a filled specimen row set.

Document type: Form

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 log for recording chain-of-identity and chain-of-custody verification at every handoff in a cell or gene therapy journey. Replace every <<FILL: ...>> placeholder. A field-definition table, the blank log, instructions, and a filled specimen follow. This is general guidance to adapt, not legal or regulatory advice.

FieldEntry
Form number<<FILL: e.g. FORM-MFG-040-01>>
Linked SOP<<FILL: chain-of-identity/custody SOP-ID>>
COI identifier<<FILL: e.g. COI-XXXXXX>>
Product / protocol<<FILL>>
Batch / lot<<FILL>>

Field definitions

FieldFormatRequiredWho entersWhen
StepDefined handoff nameYesReceiving partyAt each handoff
Site / locationTextYesReceiving partyAt handoff
COI identifierControlled identifierYesReceiving partyAt handoff
Second identifierDOB or controlled site IDYesReceiving partyAt handoff
Identity check resultPass / FailYesVerifierAt handoff
Custodian in / outName or orgYesBoth partiesAt transfer
Condition in band?Yes / No (from logger)YesReceiving partyAt receipt
Verified byName + badge/IDYesVerifierAt handoff
Date/time (UTC)YYYY-MM-DD HH:MMYesVerifierAt handoff

Blank log

StepSiteCOI ID2nd identifierIdentity resultCustody in/outCondition in band?Verified byDate/time (UTC)
Apheresis collection<<FILL>><<FILL>><<FILL>>Pass / Fail<<FILL>>NA<<FILL>><<FILL>>
Receipt at mfg site<<FILL>><<FILL>><<FILL>>Pass / Fail<<FILL>>Yes / No<<FILL>><<FILL>>
Start processing<<FILL>><<FILL>><<FILL>>Pass / Fail<<FILL>>NA<<FILL>><<FILL>>
Cryopreservation<<FILL>><<FILL>><<FILL>>Pass / Fail<<FILL>>Yes / No<<FILL>><<FILL>>
Final release ship<<FILL>><<FILL>><<FILL>>Pass / Fail<<FILL>>Yes / No<<FILL>><<FILL>>
Receipt at center<<FILL>><<FILL>><<FILL>>Pass / Fail<<FILL>>Yes / No<<FILL>><<FILL>>
Thaw<<FILL>><<FILL>><<FILL>>Pass / Fail<<FILL>>Yes / No<<FILL>><<FILL>>
Administration<<FILL>><<FILL>><<FILL>> + name confirmed bedsidePass / Fail<<FILL>>NA<<FILL>><<FILL>>

Instructions

  1. One log per COI identifier (per patient product). The COI identifier on this log must match the batch record.
  2. Complete a row at every handoff. A receiving party never accepts custody until both the identity check and the condition check pass.
  3. Any Fail on the identity check, or any “No” on condition in band, stops the flow: quarantine the product and raise a deviation per the linked SOP. Do not advance.
  4. Two independent identifiers are mandatory at each step. The COI number alone is not a two-identifier check.
  5. Retain this log with the batch record for the regional traceability period (EU ATMP: 30 years after product expiry; US per 21 CFR 1271 and cGMP).

Acceptance criteria

  • Every row is complete with two identifiers and a named verifier.
  • No identity Fail and no condition “No” is left open; each has a deviation reference and disposition.
  • The COI identifier is identical across every row and matches the batch and final-product label.

Filled specimen

The following shows a completed log for an example product. Details are illustrative; replace with your own.

StepSiteCOI ID2nd identifierIdentity resultCustody in/outCondition in band?Verified byDate/time (UTC)
Apheresis collectionTreatment center ACOI-7F3A21DOB 1979-04-12PassSite A to Courier XNARN badge 44712026-03-02 09:14
Receipt at mfg siteManufacturingCOI-7F3A21DOB 1979-04-12PassCourier X to MfgYesOp badge M1182026-03-03 07:50
CryopreservationManufacturingCOI-7F3A21Batch BR-7F3A21PassMfg internalYesOp badge M2042026-03-10 16:05
Final release shipManufacturingCOI-7F3A21Lot 7F3A21-FPPassMfg to Courier YYesQA badge Q072026-03-12 11:20
Receipt at centerTreatment center ACOI-7F3A21DOB 1979-04-12PassCourier Y to Site AYesPharm badge 99122026-03-13 06:40
AdministrationTreatment center ACOI-7F3A21DOB 1979-04-12 + name confirmed bedsidePassSite ANAMD badge 33202026-03-13 13:35

Every row carries the same COI identifier, two identifiers were checked by a named person at each handoff, and the condition stayed in band, so the end-to-end reconciliation ties out: one patient in, one product out.

Common inspection findings this log prevents

  • A handoff recorded with one identifier only.
  • A custody leg with no identified custodian.
  • An out-of-band condition reading accepted without a deviation.
  • A COI identifier that does not match the batch record or the final label.

How to adapt this form

  1. Set the form number and link it to your COI/COC SOP.
  2. Match the step rows to your actual process map (add or remove handoffs).
  3. Define your two acceptable secondary identifiers.
  4. Confirm the regional retention period before use.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.