Checklist: Hybrid Record Reconciliation and Second-Person Review

This is a ready-to-use checklist for one hybrid record, run by the second-person reviewer before the record is used to support any decision. It executes the reconciliation defined in the hybrid record control and reconciliation SOP and turns it into a set of questions with a recorded answer, so that a reviewer’s signature is backed by visible evidence rather than by assertion. Replace every <<FILL: ...>> placeholder, set your document numbers, and route the checklist through your normal document control. A filled specimen follows. Verify each cited regulation against the current source before you rely on it, and adapt this to your own processes rather than treating it as legal or regulatory advice.

The single rule that shapes the whole checklist: start from the electronic side and make the paper account for it. Starting from the paper only ever confirms that the paper is complete, and the paper is the half designed to look complete.

Document control header

When to use this checklist

Run it once per hybrid record, at the point of second-person review, before the result, batch step, or dataset is used to support a decision. Run it in full for every record from a hybrid classified High criticality in the hybrid inventory register. For Medium and Low criticality hybrids, run the sections your procedure specifies and record the sections marked NA with the reason. Do not run it retrospectively as a paperwork exercise weeks after the activity; the value of the check comes from the operator still being available to explain an exception.

Before you start

Have all of the following in hand. If any item is missing, stop and record the reason; a reconciliation performed without the electronic source is not a reconciliation.

How to complete

1. Enter the record identification block.
2. Work sections A to G in order. Do not skip forward; the count check in section B changes what you look for in every later section.
3. Mark each item Pass, Fail, or NA. NA requires a reason on the same line. A blank is not an answer.
4. Any Fail stops the review at that point for that item and routes to section H. Continue the remaining items so the full picture is captured, but do not sign the record as reconciled.
5. Complete the exception log, the disposition, and the signoff.

Record identification

Section A: setup and provenance

Section B: count

Section C: identity

Section D: value

Section E: time and sequence

Section F: audit trail

Section G: exceptions

Section H: signature and link

Exception log

Record every Fail and every NA that required a reason. One row per item.

Escalation triggers

Apply the classification below and act accordingly. Notify Quality Assurance the same working day for any classification other than “control functioned”.

Affected data is not released or used until every exception is resolved and dispositioned.

Disposition and signoff

Acceptance criteria

The reconciliation is acceptable when all of the following hold:

• The reviewer opened the governing electronic record and its audit trail, and the review began there.
• Count, identity, value, time and sequence all reconcile, and every difference was investigated and dispositioned rather than noted.
• Every critical audit trail entry in the period was identified and its recorded reason was assessed, not merely observed to exist.
• Every electronic action resolves to a named individual matching the paper signature for the same step.
• Every signature carries a printed name, a date, and a stated meaning that includes reconciliation and audit trail review.
• No item is blank. Every NA carries a reason.
• A different qualified person could repeat this checklist from the record alone and reach the same conclusion.

References

21 CFR 211.68, 211.180, 211.194. 21 CFR Part 11, in particular 11.10, 11.50 (signature manifestations), and 11.70 (signature and record linking, including handwritten signatures executed to electronic records). EU GMP Annex 11 (Computerised Systems) and EU GMP Chapter 4 (Documentation). FDA guidance, Data Integrity and Compliance With Drug CGMP, Questions and Answers (December 2018). MHRA GXP Data Integrity Guidance and Definitions (March 2018). PIC/S PI 041, Good Practices for Data Management and Integrity in Regulated GMP/GDP Environments.

Confirm the current version and clause numbers of each reference before issue.

Filled specimen

The following shows the checklist completed for an example standalone chromatography workstation with a paper analyst worksheet. Only the items with something to say are reproduced in full; the remainder passed with the evidence noted. Company, names, and numbers are illustrative.

Record identification

Selected item results

Exception log

Disposition

What makes this specimen defensible is not that it is clean, because it is not. The aborted injection is visible on both halves and linked to its repeat. The manual integration carries a reason that the reviewer actually assessed against the method rather than noting that a reason was present. And the one Fail is an honest recording of a known gap, with evidence that the compensating control operated on this specific day, rather than a Pass awarded because the gap is already on a list somewhere. A reviewer who had signed only the worksheet would have seen eleven tidy results and no evidence that a twelfth injection ever existed.

Common inspection findings this checklist prevents

• The reviewer signed the paper record but cannot demonstrate that the electronic audit trail was ever opened.
• Aborted, repeated, or reprocessed runs exist electronically and appear nowhere on the paper record.
• A gap in a printout counter, a result ID series, or worksheet page numbering is present and unexplained.
• Values were transcribed from the electronic source with no independent verification, and an error changed a reported result.
• A manual integration or reprocessing carries a reason that nobody evaluated against the method, so the reason exists but the review did not.
• A correction was made on one half of the record and never propagated to the other.
• Ink signatures approve electronic records with nothing linking the signature to the specific record it approves.
• The same person executed and reviewed the work, so the second-person check never happened.
• Review records are complete and uniformly clean across a period in which the system logged aborted runs, which tells an inspector the review is a formality.

How to adapt this checklist

1. Set your document number and point the parent SOP field at your real hybrid control procedure.
2. In section C, replace the generic phrase “machine-generated identifier” with the actual identifier each of your systems produces. Doing this once per system, in the hybrid inventory register, and then citing it here keeps the two documents consistent.
3. Set the acceptable clock offset in E5 from your time synchronisation procedure rather than picking a number here.
4. Decide which sections apply to Medium and Low criticality hybrids and state that mapping in the parent SOP, so reviewers are not making that judgement per record.
5. If your hybrid is a paper batch record dependent on a historian, add items under section B and F that name the specific electronic extracts the reviewer must attach: the trend for the batch window, the alarm and event list, and the operator action log.
6. If your hybrid is clinical, replace the sample and injection language in sections B and C with subject, visit, and form identifiers, and add an item confirming that the fields designated as direct data capture in the source data agreement were not also recorded on paper.
7. Print the reviewer signature meaning on the form itself rather than relying on the reviewer to write it, and check that the existing form has room for it.
8. Confirm every regulation in the references section against the current published version before issue.