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
Checklist Plug-and-play starting point Quality Assurance

Checklist: Batch Record Completeness and Review Readiness

A plug-and-play pre-review gate checklist that screens an executed batch record for the unreviewable criteria, attribution, corrections, and deviation references, before the formal QA review clock starts, with a filled specimen.

Document type: Checklist

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 checklist for the intake gate that runs before the formal, timed batch record review begins. Its purpose is narrow and specific: catch a record that cannot be meaningfully reviewed in its current state and return it for correction before the review clock starts, rather than discovering the same defects partway through a substantive review. Replace every <<FILL: ...>> placeholder. A filled specimen follows.

How to use this checklist

  • Complete this checklist first, before any substantive line-by-line review of the record’s content.
  • Any single Fail means the record is not reviewable as submitted: stop, return it for correction, and log the return.
  • This checklist does not replace the substantive review; passing it only means the record is ready to be reviewed, not that it is acceptable for disposition.
  • The person completing this checklist may be the assigned QA reviewer or a dedicated intake function, depending on site procedure.
FieldEntry
Product / strength<<FILL>>
Batch / lot number<<FILL>>
Screener<<FILL>>
Screening date<<FILL>>
Record typePaper / Hybrid / Electronic

Section A: Record identity

#ItemPass / FailEvidence reference
A1Batch number, product, and strength on the record match the batch to be reviewed<<FILL>>
A2Master record version referenced is the approved current version at time of manufacture<<FILL>>
A3Record is present in full: no missing pages, sections, or attachments<<FILL>>

Section B: Attribution and second checks

#ItemPass / FailEvidence reference
B1Every critical step has an individual name or ID recorded as performer, not a group or department<<FILL>>
B2Every critical step requiring a second check has a second, different individual recorded as verifier<<FILL>>
B3No step shows the same person as both performer and verifier where a second check is required<<FILL>>

Section C: Corrections

#ItemPass / FailEvidence reference
C1Every paper correction shows a single line through the original, with the original still legible<<FILL>>
C2Every correction is initialed and dated, with a reason where the procedure requires one<<FILL>>
C3No white-out, obliteration, erasure, or writing over an original entry is present<<FILL>>
C4Electronic corrections retain the original value in the audit trail alongside the corrected value<<FILL>>

Section D: Deviations and discrepancies referenced in the record

#ItemPass / FailEvidence reference
D1Every deviation mentioned anywhere in the record (comments, notes, exception flags) has a corresponding formal deviation record on file<<FILL>>
D2No value appears outside specification or the master record’s stated range without either a deviation reference or a documented explanation<<FILL>>

Section E: Required fields

#ItemPass / FailEvidence reference
E1No required field is blank without an explanation (“N/A” or equivalent, with basis, where genuinely not applicable)<<FILL>>
E2Every date and time entry is present and internally sequential (no step signed before a prior step it depends on)<<FILL>>
E3For an electronic record, no unexplained gap exists in automated data capture for the review period<<FILL>>

Signoff

FieldEntry
All items PassYes / No
Screening resultReviewable / Returned for correction
If returned, criterion failed and basis<<FILL>>
Screener (name, signature, date)<<FILL>>
Forwarded to substantive review on<<FILL: date, or N/A if returned>>

Acceptance criteria

A record is reviewable and may proceed to the substantive batch record review only when every item in Sections A through E is marked Pass. A single Fail returns the record for correction before the review clock starts; log the return with the batch record return-for-correction log so repeat sources of unreviewable records are visible in the trend.

Filled specimen (extract)

The following shows a completed extract for an illustrative biologics fill-finish batch that failed the screen. The batch and numbers are illustrative.

#ItemPass / FailEvidence reference
A1Batch number, product, strength matchPassBR-9903 header
B1Individual attribution on every critical stepPassBR-9903 pp. 1 to 38
B2Second check present on every critical step requiring oneFailStep 22 (final integrity check) has no second signature
C1Corrections properly madePassOne correction, step 14, properly lined and initialed
D1Every referenced deviation has a formal record on fileFailComment on step 31 references “see deviation,” no deviation number, and no matching record found
E1No unexplained blank fieldPassNo blanks found

Screening result: Returned for correction. Two failures: a missing second-check signature on a designated critical step (step 22, final container closure integrity check), and a deviation reference on step 31 with no corresponding deviation record on file. Both were routed back to manufacturing the same day; the record was resubmitted with the second signature obtained (with the verifier confirming the check itself was actually performed contemporaneously, not signed after the fact) and the deviation formally opened and referenced correctly. The record passed the screen on resubmission and proceeded to substantive review.

Common inspection findings this checklist prevents

  • A batch record accepted into the review queue with a missing critical-step signature that only surfaces late in the review, or not at all.
  • A deviation mentioned in passing in the record with no formal deviation record, discovered only if a reviewer happens to read the comment closely.
  • Time spent on a substantive review of a record that ultimately has to be returned anyway, inflating cycle time and obscuring where the delay actually originated.
  • No record of why a batch record was returned, so a site cannot see that the same line or product keeps failing the same screen.

How to adapt this checklist

  1. Add or remove items to match your record format (a fully electronic record may not need the paper-correction rows in Section C, but should keep an equivalent electronic-correction check).
  2. Decide who performs this screen at your site, a dedicated intake role or the assigned reviewer, and state it in the parent SOP.
  3. Set your own escalation rule for a record returned more than once for the same defect.
  4. Pair this checklist with the batch record review SOP so the screen and the substantive review are governed by one consistent procedure.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.