When an audit finds the same blank on fifteen batch records, the first question is not “who forgot to sign?” It is “what does the rest of the evidence say happened at that step?”
In this article
A blank entry has two possible meanings.
A record is supposed to show that a step was done, by whom, and when (21 CFR 211.188(b)). When an entry is missing, the record has stopped answering that question. There are two broad explanations, and they lead to very different responses.
In the first, the step was performed and the documentation was not completed. Other records corroborate the work: equipment logs, in-process results, material reconciliation, a second person's check. The gap is in the writing.
In the second, the missing entry is the only visible trace of a step that was skipped, shortened, or done differently from the written procedure. The other records do not corroborate the work, or they contradict it. The gap is in the operation, and the documentation is simply where it surfaced.
The practical test: if you removed the missing entry from consideration, would any other record show that the step happened? If yes, you are probably looking at a writing problem. If no, you do not yet know what happened at that step.
Look for patterns before you look for people.
Random gaps spread across shifts, operators, steps, and products tend to point toward documentation habits. Gaps that cluster tend to point somewhere else. Useful questions include:
Points toward a writing problem
- Gaps spread across shifts, steps, and operators
- Equipment, instrument, or system logs show the step ran
- In-process results exist for the step
- A second person's check or later entry confirms the work
Points toward an operation problem
- Gaps cluster on one shift, line, step, or crew
- No independent record shows the step ran
- Timing or yields differ from batches without gaps
- The step is long, awkward, or competes with another task
Neither column settles the question on its own. They tell the reviewer where to look next and how much investigation the gap warrants.
An illustrative scenario
Retraining on documentation would have answered the question the audit asked: why are initials missing? It would not have answered the question the evidence raised: was the step performed? If it was not, the people would have been retrained to sign for work that may still not be happening.
The pattern changed the scope of the decision. A documentation lapse is one kind of question. A step that may not have been performed on fifteen batches is a discrepancy that has to be explained, and the investigation, its reach to associated batches, and its conclusions belong in the record.
What the decision record should contain
The Four Lenses keep the response from running ahead of the evidence. Each asks a different question about the same gap. Applied to the illustrative scenario, a record that preserves the classification decision might read as follows. This is a fictional example, not a template for a real investigation.
| Lens | What the record contains | Question before closing |
|---|---|---|
| EvidenceWhat was known? | Fifteen batch records with missing initials at one step; all on second shift; no matching equipment-log entries for that step on those batches; comparison with batches that have complete entries. | Does any independent record show the step was performed on the affected batches? |
| JudgmentHow was the evidence evaluated? | The clustering by shift and step, together with the silent equipment log, does not support a documentation-only explanation. The gap is treated as a possible failure to perform the step. | Is the classification based on what the records show, rather than on the corrective action that was proposed first? |
| RiskWhat remained uncertain? | Fifteen batches with an unconfirmed step; other batches on the same shift and step that may be associated; the effect of the step on the product not yet assessed. | Which batches could be affected, and what remains unknown? |
| AuthorizationWhat was decided? | The Head of Quality declines the documentation-only action, opens an investigation under the site's procedure, names an owner, and records the conditions under which the classification would be revisited. | Is the accountable authority deciding the scope of the response with the evidence in view? |
What the record should explain
A record gap is evidence that the record stopped answering a question. Whether the answer is “the work happened and nobody wrote it down” or “the work may not have happened” depends on the other records, not on the gap itself. A Head of Quality should require the classification, and the evidence behind it, to be on the record before the corrective action is chosen.
Make the classification answer four questions.
- What exactly is missing? Name the entry, the step, the batches, and the period.
- What else shows the step happened? List the independent records reviewed and what each one shows or does not show.
- Is there a pattern? Record whether the gaps cluster by shift, step, line, crew, or product, and what that suggests.
- What response does the evidence support? State the classification, the level of investigation, the corrective action, and who decided.
For a related look at what a complete record still may not explain, read objective evidence and the GMP decision record or good documentation practices and the decision record.
Regulatory context and sources
For finished pharmaceuticals, 21 CFR 211.188(b) requires batch production and control records to document that each significant step was accomplished, including the identity of the people performing and directly supervising or checking each significant step. 21 CFR 211.100(b) requires written production and process control procedures to be followed and documented at the time of performance, and any deviation from them to be recorded and justified.
21 CFR 211.192 requires the quality control unit to review and approve production and control records, and requires any unexplained discrepancy to be thoroughly investigated, with the investigation extended to other batches that may have been associated with it and a written record that includes the conclusions and followup. 21 CFR 211.22(a) gives the quality control unit responsibility for reviewing production records to assure that no errors have occurred or, if errors have occurred, that they have been fully investigated.
Source context: Regulatory requirements: 21 CFR 211.22, Responsibilities of quality control unit; 21 CFR 211.100, Written procedures; deviations; 21 CFR 211.188, Batch production and control records; and 21 CFR 211.192, Production record review. The illustrative scenario, the fictional record example, and the Four Lenses review are CW editorial examples, not regulatory mandates. ComplianceWorxs does not provide regulatory or legal advice and does not judge whether any record or corrective action is adequate.