Every result on the release testing summary is within limit. The batch record is signed. The recommendation says the batch is “consistent with previous batches.” That last sentence carries the decision, and nothing in the file shows where it came from.
In this article
A passing result feels like the answer because it answers the question that was asked.
The test asked whether a sample met a limit. It did. The release decision asks something larger: is this batch suitable to release, and is the process still doing what the file says it does? The two questions sound close. They are not the same question, and the distance between them is where judgment sits.
It is also where records go quiet. “Within specification” is easy to write and easy to sign. The step from that sentence to “consistent” or “no concern” is the one nobody writes down, because everyone in the room made it the same way, instantly.
That is the habit to break. A reviewer who cannot say which words in the recommendation are measurements and which are conclusions has not yet reviewed the decision.
What the results show, and what they do not.
The case is synthetic, from The Record in Practice: a solid oral dosage form with release testing complete. The unspecified-impurity result for this batch is 0.09% against a limit of 0.10%. The three batches before it read 0.04%, 0.06% and 0.07%. No real batch, product, person or site is involved.
| Statement | Kind | Why |
|---|---|---|
| The impurity result is 0.09%. | Observation | A measured value for one sample. |
| The result is within the 0.10% limit. | Observation | It compares the value to the limit. It does not say whether the margin is wide enough for the method’s variability, or what produced the value. |
| The last four batches read 0.04%, 0.06%, 0.07% and 0.09%. | Observation | Four values in sequence. |
| The process is consistent. | Conclusion | It claims a property of the process. No single result states it. |
| The increase from 0.04% to 0.09% is normal variation. | Conclusion | An explanation. Nothing was measured that says why the values rose. |
| The batch is suitable for release. | Conclusion | The decision itself, which also rests on evidence outside this table. |
Three of the six statements are measurements. The other three carry the decision. None of the three is wrong because of that. They are the part that needs a basis on the record.
What the conclusion adds.
To get from the first three rows to “consistent,” a reviewer has to assume several things. The four values are for the same impurity. They came from the same method performing the same way. The margin to the limit is wide enough that ordinary method variability could not hide a true value above the limit. The sequence reflects variation, not a drift. Each of those is a claim.
Some of them will have evidence in the file: method validation, system suitability for each run, the reference standard. Some will have none. Neither case is a defect in itself. The defect is when the assumption is never named, so nobody can tell which case they are in.
Write three sentences before signing.
The third sentence is the one that changes the decision. When its evidence is on file, the conclusion has a basis. When it is not, the sentence reads “not established,” and that is a decision point for Quality, not a formality. The next article takes it from there: what else could explain the result.
What the decision record should contain
The Four Lenses keep the conclusion from running ahead of the results. Applied to the synthetic case, a record that preserves the reasoning reads as follows. This is a fictional example, not a template for a real decision.
| Lens | What the record contains | Question before closing |
|---|---|---|
| EvidenceWhat was known? | The impurity result for this batch, the three previous results, and system suitability for each run. | Which statements in the recommendation are measurements? |
| JudgmentHow was the evidence evaluated? | “Within limit” is read as an observation. “Consistent” and “normal variation” are conclusions that the results alone do not support. | Is each conclusion tied to the assumption it rests on? |
| RiskWhat remained uncertain? | Whether the rise is drift, what caused it, and what the next batch will read. | What is still unknown, and what could it affect? |
| AuthorizationWhat was decided? | The authorizing person records the conclusion, the assumption under it, and the evidence for it, or records that the evidence is not on file and what happens next. | Is the decision made on a conclusion the record supports? |
What the record should explain
A passing result tells you a sample met a limit. The release decision tells you something about the batch and the process. A record that explains the decision shows the step between them, in words, with the basis for each assumption in it.
Make the review answer four questions.
- What did each result measure? Only what the sample showed against the limit.
- What did the conclusion claim beyond the results? Name each claim.
- What did the conclusion assume? Write the assumption in a sentence.
- What is on file for each assumption? Evidence, or a plain statement that there is none.
For a related situation, where a retest passed and the question is whether the first result is resolved, read the retest that passed.
Regulatory context and sources
For finished pharmaceuticals, 21 CFR 211.165(a) requires appropriate laboratory determination of satisfactory conformance to final specifications for the drug product, including the identity and strength of each active ingredient, prior to release. 21 CFR 211.165(e) requires the accuracy, sensitivity, specificity and reproducibility of the test methods to be established and documented. 21 CFR 211.192 requires production and control records to be reviewed and approved by the quality control unit to determine compliance with established, approved written procedures before a batch is released or distributed. It also requires any unexplained discrepancy, and the failure of a batch or any of its components to meet any of its specifications, to be thoroughly investigated, with the investigation extended to other batches that may have been associated with it and a written record of the conclusions and followup. In the synthetic case above no result fails a specification. Whether the increase is an unexplained discrepancy under 21 CFR 211.192 is for Quality to decide under the site’s procedure; the regulations do not say which explanation fits the numbers.
Source context: Regulatory requirements: 21 CFR 211.165, Testing and release for distribution; and 21 CFR 211.192, Production record review. The batch, the results and the explanations are a synthetic case used in the ComplianceWorxs The Record in Practice; the record example and the Four Lenses review are CW editorial examples, not regulatory mandates. This article has not been reviewed by a practitioner for regulatory sufficiency. ComplianceWorxs does not provide regulatory or legal advice and does not judge whether any record or release decision is adequate.