What it means
A failed test is repeated, passes, and the first result vanishes from the release packet. Manufacturing retest authorization evidence rate checks whether each retest had a valid reason, scope and permission before the new result was used.
Define what counts as a retest under the product and inspection plan, since a scheduled second sample is different from a repeat ordered because the first result failed. Distinguish retest from reinspection after approved rework, because Oracle describes reinspection of initially rejected work-in-process units after they are reworked and that sequence has its own trace.
Preserve the original result and raw evidence, so a later passing value does not silently overwrite a prior failure or create a false impression of first-pass quality. Identify the trigger, such as instrument fault, sample damage, procedure error, confirmed data import problem or approved rework, because unsupported dissatisfaction with a failing result is not a sound rationale.
Record who can authorize a repeat under the control plan, since the operator who sees the failure may not have authority to decide the retest scope alone. State whether approval was needed before a new sample or only before using its result, and link the authorization to unit or lot, test characteristic, method, sample plan and maximum repeats where relevant, because a general permission to try again is too broad.
When equipment failure is claimed, retain instrument logs and investigation, as a passing result from a different device does not itself prove the first device was wrong. If the sample was mishandled, preserve chain-of-custody and sampling evidence, otherwise it is difficult to distinguish a true invalid sample from convenient resampling.
Where a test is destructive, choose a new sample under the approved plan, because retesting the same unit may be impossible or may change its properties. If rework occurred, link the rework instruction, completion and new inspection plan, and for serial-tracked products ensure the new result attaches to the same serial or approved replacement, since results from a neighbouring unit cannot cure a failure.
For batch testing, document whether the new sample represents the same material population, because mixing or sorting after the first sample changes the population being judged. Record each attempt in sequence with date, analyst, method and outcome, as an average of results may be inappropriate unless the approved procedure explicitly permits it.
The US FDA has product-specific guidance for investigating out-of-specification results in pharmaceutical production, which is a regulatory example, not a universal rule for all manufacturing. Keep investigation and final disposition separate from authorization, because a retest can be properly authorized yet still fail or leave product on hold, and if an unauthorized repeat was done, retain the data and investigate the process since deleting the repeat would compound the record problem.
Define the denominator as retest events requiring authorization, not every routine replicate, and classify missing reason, wrong approver, late approval, excessive attempts and missing original data separately, as each points to different corrective action. For urgent production establish an available qualified approver rather than waiving review informally, audit selected retests backward from final disposition to all attempts, and show patterns by product, instrument and shift, remembering that the target is justified retesting and clear evidence, not a high pass rate after enough attempts.
In practice
Real-world examples.
Example
A test instrument faults during a run. Quality documents the fault, approves a repeat on the affected unit and keeps both records.
Example
An operator reruns a failed test until a passing value appears, without investigation or authorization. The event fails the evidence check.
Example
A unit is reworked under approval and reinspected. The rework and new result remain linked to its first failure.
Formula
Calculation
Illustrative rate = retest events with complete required justification, scope, approval and first-result history / retest events requiring authorization x 100.
Worked example. An invented plant logs 40 retest events requiring authorization in a quarter, and 34 have a documented reason, approved scope, the right approver and the retained first result.
- Rate = 34 / 40 x 100 = 85%.
- The 6 incomplete events (15%) are then split into missing reason, wrong approver, late approval, excessive attempts and missing original data.Case study
Seen in the real world.
This fictional case follows Stonebridge Medical Components. A test bench generated intermittent invalid files. Quality reviewed device logs, approved bounded repeats and kept the failed exports and retest results together. The case is invented. No product-regulatory compliance conclusion follows from it.
Watch out
Common mistakes.
- 1. Replacing a failed result with a later passing result.
- 2. Treating an equipment-fault claim as proven because a second test passed.
- 3. Counting preplanned replicate measurements as unauthorized retests.
Questions
People also ask.
Can a retest pass after an initial failure?
Yes, but the first result, reason, authorization and final disposition must remain clear under the applicable plan.
Is reinspection after rework the same thing?
No. It follows an approved change to the unit and should retain that rework history.
Does authorization guarantee release?
No. The product still needs the required evidence and final disposition.
From the founder's library

Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related
