Conditional Release: Meaning, Evidence and Controls
For US PET drug products, conditional release means a final release made prior to completion of a required finished-product test because of a malfunction involving analytical equipment.

On this page · 11 sections
- 1What conditional release means for US PET drug products
- 2Where conditional final release is permitted: the exact malfunction conditions
- 3Sterility testing after release: timing, notifications and investigation findings
- 4In-process controls and batch history: what the evidence can support
- 5What to have ready before an equipment-malfunction decision
- 6The release decision: review, authorization and the subsequent-batch gate
- 7Worked PET cases: eligible malfunction, excluded test and pending sterility
- 8Audit trails and integrations: keep the decision connected to its evidence
- 9After an omitted-test failure: notification, disposition and recovery
- 10US versus EU: map the product and release approach first
- 11Common failures and a practical implementation review checklist
How does Conditional Release apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What conditional release means for US PET drug products
Conditional release, termed conditional final release for US PET drug products in 21 CFR 212.1, means a final release made prior to completion of a required finished-product test because of a malfunction involving analytical equipment.
For US PET drug products, the definition of final release in 21 CFR 212.1 concerns an authoritative decision by a responsible person in a PET production facility to permit use of a batch in humans. The central distinction is therefore between authorization to use the product, the evidence supporting that authorization, and the status used to control inventory.
| Term | Decision or status | Boundary | Basis |
|---|---|---|---|
| Conditional final release | US PET final release before completion of a required finished-product test. | The unfinished test results from an analytical-equipment malfunction. | US PET legal definition: 21 CFR 212.1. |
| Final release | Responsible person's authorization for human use of a US PET batch. | A decision, not merely an inventory label. | US PET legal definition: 21 CFR 212.1. |
| Batch release | Broader expression for batch disposition. | Does not itself identify the equipment-malfunction route. | Ordinary industry usage. |
| Quarantine | Restricted material or product status. | Describes use or movement restrictions, not release authorization. | Ordinary industry usage. |
| Real-time release testing | Release-testing approach using process and product information. | Describes an evidence strategy, not the equipment-malfunction route. | Ordinary industry usage. |
In practical terminology, these neighbouring concepts answer different questions: who authorized use, how quality was assessed, and whether stock remains restricted. None is a synonym for conditional final release. Keeping those meanings separate helps prevent a workflow label from being mistaken for a release justification.
This article addresses US PET drug products only. It is not a general conditional-release permission for other pharmaceuticals, supplements, food, devices or chemicals.
02Where conditional final release is permitted: the exact malfunction conditions
For US PET drug products, the conditional-final-release gate sits within 21 CFR 212. Read the conditions, exclusions and subsequent-batch restriction together.
For US PET drug products, 21 CFR 212.70(f)(1) states: "If you cannot complete one of the required finished-product tests for a batch of a PET drug product because of a malfunction involving analytical equipment, you may approve the conditional final release of the product if you meet the following conditions:"
For US PET drug products, 21 CFR 212.70(f)(1)(i) states: "You have data documenting that preceding consecutive batches, produced using the same methods used for the conditionally released batch, demonstrate that the conditionally released batch will likely meet the established specifications;"
For US PET drug products, 21 CFR 212.70(f)(1)(ii) states: "You determine that all other acceptance criteria are met;"
For US PET drug products, 21 CFR 212.70(f)(1)(iii) states: "You retain a reserve sample of the conditionally released batch of drug product;"
For US PET drug products, 21 CFR 212.70(f)(1)(iv) states: "You promptly correct the malfunction of analytical equipment, complete the omitted test using the reserve sample after the malfunction is corrected, and document that reasonable efforts have been made to prevent recurrence of the malfunction;"
For US PET drug products, 21 CFR 212.70(f)(1)(v) states: "If you obtain an out-of-specification result when testing the reserve sample, you immediately notify the receiving facility; and"
For US PET drug products, 21 CFR 212.70(f)(1)(vi) states: "You document all actions regarding the conditional final release of the drug product, including the justification for the release, all followup actions, results of completed testing, all notifications, and corrective actions to prevent recurrence of the malfunction involving analytical equipment."
For US PET drug products, 21 CFR 212.70(f)(2) states: "Even if the criteria in paragraph (f)(1) of this section are met, you may not approve the conditional final release of the product if the malfunction involving analytical equipment prevents the performance of a radiochemical identity/purity test or prevents the determination of the product's specific activity."
For US PET drug products, 21 CFR 212.70(f)(3) states: "You may not release another batch of the PET drug product until you have corrected the problem concerning the malfunction of analytical equipment and completed the omitted finished-product test."
Practical decision interpretation: assess the whole gate, not isolated favourable facts. Treat batch history and a retained sample as parts of the assessment—not independent authorization. Urgency is not a substitute for that assessment.
03Sterility testing after release: timing, notifications and investigation findings
For US PET drug products, 21 CFR 212.70(e) states:
"Sterility testing need not be completed before final release but must be started within 30 hours after completion of production. The 30-hour requirement may be exceeded due to a weekend or holiday. If the sample for sterility testing is held longer than 30 hours, you must demonstrate that the longer period does not adversely affect the sample and the test results obtained will be equivalent to test results that would have been obtained if the test had been started within the 30-hour time period. Tested samples must be from individual batches and not pooled. If the product fails to meet a criterion for sterility, you must immediately notify all facilities that received the product of the test results and provide any appropriate recommendations. The notification must be documented. Upon completion of an investigation into the failure to meet a criterion for sterility, you must notify all facilities that received the product of the findings from the investigation."
Practical record labels: sterility testing after release; malfunction-based conditional final release. For US PET drugs, pending sterility alone is not the malfunction-based release defined in 21 CFR 212.1. Track the initial failure notification separately from the later investigation-findings communication.
For US PET drug application reporting, check the current text of 21 CFR 314.81 for scope and timing; assess that reporting question separately from facility notifications.
04In-process controls and batch history: what the evidence can support
For US PET drug products, 21 CFR 212.70(a) requires specifications including criteria for identity, strength, quality, purity and, if appropriate, sterility and pyrogens. These specifications provide the reference point for reviewing historical results—not merely whether earlier batches were released.
For US PET drug products, 21 CFR 212.70(b) requires establishing and documenting accuracy, sensitivity, specificity and reproducibility before implementing a new test procedure in a specification. For US PET drug products using an established compendial procedure in a specification, that provision requires first verifying and documenting that it works under actual conditions of use.
For US PET drug products, the preceding-consecutive-batch criterion in 21 CFR 212.70(f)(1)(i) ties the historical evidence to batches produced using the same methods. As a practical review aid, build a chronological history linking each batch record to its production method, relevant method revisions, individual test results and deviations.
- Review a genuinely comparable sequence, rather than selecting only passing batches.
- Use change control records to explain revisions and assess whether they affect comparability; an unexplained method change weakens the inference.
- Use a batch comparison overlay to inspect individual results, not just a dashboard average that can conceal failures.
- Justify the historical review window through comparability and relevance rather than adopting an arbitrary universal batch count.
In practical review, current-batch process observations add context: they can identify differences worth investigating or support confidence in comparability. Keep that confidence separate from completion of a finished-product determination. Record observations as supporting evidence, not as a completed analytical result or a substitute for an excluded test.
05What to have ready before an equipment-malfunction decision
For a US PET drug equipment-malfunction decision, assemble a concise readiness package before seeking authorization. The following is a recommended operating design, not additional regulatory prerequisites or prescribed job titles. Keep supporting records accessible rather than copying them into disconnected summaries.
- Fault and evidence: identify the equipment fault, affected test and method, current-batch results, linked historical evidence, reserve-sample identity and proposed recovery owner. For US PET drugs, record the assessment against the radiochemical identity/purity and specific-activity exclusions in 21 CFR 212.70(f)(2)(2)).
- Sample usability: assess container identity, storage conditions, available quantity and handling history. Explain whether the planned delayed test remains scientifically meaningful for that sample and method; physical availability alone does not establish usability. Link the assessment to the sample record in the laboratory information management system, where used.
- Equipment recovery: distinguish diagnosing the fault, correcting it, demonstrating readiness for use and completing the omitted test. Give each stage an owner and an evidence endpoint. Where calibration is implicated, retain the distinction between as-found and as-left results.
- Contact readiness: maintain receiving-facility contact arrangements that work outside routine office hours. Name a communication owner, a backup person and an alternative contact route. Plan how unsuccessful contact attempts and acknowledgements will be recorded.
- Decision responsibilities: distinguish release authority from laboratory work ownership, maintenance ownership and notification ownership. Identify who performs each function and who can cover an absence; completing a repair is not the same operating task as authorizing release.
- Unresolved issues: give the decision-maker a readable summary of missing information, contradictory records and conclusions dependent on successful recovery. For each issue, identify its decision relevance, owner and proposed resolution rather than burying uncertainty in attachments.
- Contingencies: plan escalation for an unusable sample, unsuccessful repair or unavailable decision-maker. Identify who reassesses the proposed route and communicates the resulting decision. None of these contingencies should silently become an assumed waiver of the conditions described above.
06The release decision: review, authorization and the subsequent-batch gate
For US PET drug products, ordinary final-release procedures under 21 CFR 212.70(d)(1) include completion of the appropriate laboratory determination under paragraph (c). For US PET drug products, 21 CFR 212.70(d)(2) requires review of associated laboratory data and documentation demonstrating conformance to specifications, except for sterility. For US PET drug products, 21 CFR 212.70(d)(3) provides that a designated qualified individual authorizes final release by dated signature.
As an operational practice, organize the electronic release record around the decision, not merely the checklist. Record the release route, batch identity, decision-maker, decision time, evidence reviewed, unresolved test, rationale and assigned follow-up. Identify the evidence versions actually reviewed so later additions do not obscure the basis of authorization.
Recommended workflow design maintains distinct statuses for authorization, distribution, omitted-test completion and follow-up closure. A successful interface transmission or completed batch release checklist is not itself a human release decision. Keep production activity, inventory movement and release authorization separately named; completion of manufacture or transfer to dispatch should not be displayed as an approval.
For US PET drug products, the subsequent-batch restriction in 21 CFR 212.70(f)(3) prevents release of another batch of the product until the analytical-equipment problem is corrected and the omitted finished-product test is completed.
Implement that restriction through an explicit product-linked release gate, rather than an untraceable reminder. As a recommended control, connect the gate to the originating batch, equipment problem, correction evidence and omitted-test result. Record who reviewed the evidence and cleared the gate. Closing a maintenance task alone should not clear it. Keep the subsequent-batch gate separate from broader follow-up closure so each status communicates exactly what has been resolved.
- Classify routeIdentify the release route and applicable procedures.
- Check eligibilityConnect the malfunction, omitted test and exclusion assessment.
- Review evidenceLink batch history, remaining results and retained sample.
- Authorize DecisionRecord the human decision and distribution destinations.
- Track recoveryConnect equipment correction, test completion and release restrictions.
- Manage exceptionsCoordinate adverse-result communications, investigation and disposition.
- Close follow-upReconcile completed actions and recurrence-prevention evidence.
07Worked PET cases: eligible malfunction, excluded test and pending sterility
These are hypothetical decision exercises for US PET drug products under 21 CFR 212, not predictions of batch acceptability. Eligibility does not replace human review. Each case identifies the release route and the evidence needed to resolve the outstanding issue; none assumes an analytical result or a release outcome.
| Assumptions | Unfinished test | Route assessment | Follow-up |
|---|---|---|---|
| pH is a required finished-product test. Its analytical equipment malfunctions. Radiochemical identity/purity testing and specific-activity determination are complete. Assume the remaining paragraph (f) conditions can be demonstrated. | pH; no limit or result is assumed. | For this US PET batch, 212.70(f)(1) makes conditional final release a candidate route, not an automatic decision. Evidence review and responsible-person authorization remain necessary. | Connect the decision to the historical batch set, identified reserve sample, repair record and eventual omitted-test result. For US PET drugs, 212.70(f)(1)(iv) requires prompt correction and completion of the omitted test using that sample after correction. Consequence: assess eligibility now; resolve the analytical gap with the recorded result. |
| An analytical-equipment malfunction prevents specific-activity determination. Historical batches are favourable and delivery is urgent. | Specific activity. | For US PET drugs, 212.70(f)(2) excludes conditional final release when the malfunction “prevents the determination of the product's specific activity.” Favourable history and urgency do not override that exclusion. | Consequence: do not authorize this malfunction route. Restore the ability to perform the determination and obtain its result for review against the applicable acceptance criteria. |
| All ordinary pre-release conditions other than completed sterility testing are satisfied. Sterility testing starts 30 hours after completion of production. | Completed sterility-test result. | For US PET drugs, this falls under 212.70(e): starting at 30 elapsed hours meets its ordinary start-time requirement. The pending result is not evidence of analytical-equipment malfunction. | Consequence: assess release under the sterility provision, which permits completion after release. Record production completion and test-start timestamps; resolve the outstanding issue with the completed sterility result. This example calculates no completion deadline. |
As a practical record design, connect each decision to its batch record. Identify the historical batches actually reviewed in the pH case rather than relying on a general statement about past performance. Keep the original decision evidence distinguishable from later repair and test records so reviewers can reconstruct what was known when authorization occurred.
08Audit trails and integrations: keep the decision connected to its evidence
For a PET conditional-release workflow, the following is a suggested record design—not prescribed database fields or a standalone electronic-record compliance standard. Use persistent identifiers across systems rather than matching display names.
| Evidence object | Illustrative connection |
|---|---|
| Batch | Production identifier links the affected equipment incident and release decision. |
| Equipment incident | Maintenance identifier connects malfunction details, repair evidence and recovery review. |
| Release decision | Decision identifier links the batch, reviewer and evidence available at authorization. |
| Reserve sample | Sample identifier links the batch to laboratory accession and omitted test. |
| Test result | Result identifier links the sample, method, completion time and review. |
| Receiving-facility notification | Communication identifier links the batch, recipient, result communicated and sending record. |
Define integration boundaries: production owns batch context; maintenance owns equipment events; the laboratory owns sample and result records; distribution owns recipient and shipment records. Assign a named owner to the electronic release record. For laboratory integration, exchange identifiers and review status without allowing imported results to overwrite the original decision evidence.
- Preserve the evidence associated with the original decision separately from later results and actions. Retain correction author, time and reason to support review.
- Record event time separately from interface receipt time, so delayed imports do not obscure when testing, authorization or notification occurred.
- When an interface is unavailable, use controlled manual recording with source references. Name a reconciliation owner, detect duplicates using persistent identifiers, and route conflicting statuses for review rather than silently accepting the latest import.
At closure, use an audit-trail review workflow to compare the decision record with actual test completion, equipment recovery and communication records. An empty task queue alone is not evidence that those events occurred.
Batch
Identifies product and production event.
- batch_id
- product_id
- production_completed_at
Equipment Incident
Connects malfunction and correction.
- incident_id
- equipment_id
- affected_test_code
- corrected_at
Release decision
Preserves route and human authorization.
- decision_id
- batch_id
- route
- authorized_by
- authorized_at
Reserve Sample
Tracks identity and usability.
- reserve_sample_id
- batch_id
- storage_condition
- usability_assessment
Test result
Links sample to completed testing.
- result_id
- reserve_sample_id
- test_code
- result_status
- completed_at
Facility Notification
Tracks destination and communication outcome.
- notification_id
- batch_id
- receiving_facility_id
- trigger
- sent_at
- acknowledged_at
09After an omitted-test failure: notification, disposition and recovery
For US PET drug products conditionally released under 21 CFR 212.70(f)(1)(v), the notification condition is: “If you obtain an out-of-specification result when testing the reserve sample, you immediately notify the receiving facility”. Operationally, maintain an affected-facility list linked to the batch, assign a communication owner, and record contact attempts and confirmation of receipt. An unanswered message should remain an open communication task.
For US PET drug products, the receiving-facility definition in 21 CFR 212.1 excludes the common or contract carrier transporting the product. Contacting a carrier therefore does not substitute for identifying and notifying the receiving facility.
For US PET drug products, 21 CFR 212.71(a) requires rejection of nonconforming batches and procedures to identify and segregate product to avoid mix-ups. It also requires procedures to investigate causes, examining processes, operations, records, complaints and other relevant information. A rejected-inventory status supports tracking; it does not physically segregate material or contact recipients.
As practical response planning, separate the following states rather than treating all distributed material as recoverable:
- Remaining inventory: reconcile quantities, locations and segregation.
- In transit: establish destination and coordinate interception where feasible.
- Received product: confirm quantities, local control and use status where known.
- Administered product: support facility communication and clinical assessment; previously administered product cannot be physically recovered.
Use a case-specific disposition and recovery assessment, not an assumption that every adverse result follows an identical recall procedure. Record decision owners, rationale, unresolved quantities and follow-up responsibilities.
For US PET drug products, 21 CFR 212.71(b) requires documentation of the investigation, its results and what happened to rejected product; 21 CFR 212.71(c) requires corrective action to prevent recurrence of nonconforming product or another quality problem. Close the response through reconciled records and accountable decisions within the PET quality framework. Keep this reserve-sample notification trigger distinct from the sterility-failure communication route covered above.
10US versus EU: map the product and release approach first
Binding US regulation: for US PET drug products, 21 CFR 212.70(f) addresses conditional final release when analytical-equipment malfunction prevents completion of a required finished-product test. The conditions and exclusions discussed above govern that route.
| Product and market | Scope check before using the term |
|---|---|
| US PET drug products | Use the PET-specific provision discussed here. |
| EU medicinal products | Check the current text of EU GMP Annex 17 for the scope of real-time release testing and parametric release. |
| Non-PET drugs | Identify the applicable jurisdiction and release framework; this PET discussion is not an authorization. |
| Food, supplements, devices and chemicals | Identify the product category and destination-market release framework before interpreting a local conditional-release status. |
Scope caution: do not interpret an Annex 17 reference or real-time release testing as permission to release unfinished product. Keep the neighbouring concepts distinguished above separate.
Ordinary industry terminology: a local status name is not a legal release category. Suggested operational control: map each inventory status to its permitted actions, decision owner and documented authorization basis. Software labels are not a source of release authority.
11Common failures and a practical implementation review checklist
Use this operational practice checklist for US PET operations alongside the route conditions and evidence model covered above. It tests whether a decision remains reconstructable through laboratory follow-up, system interruptions and closure; it does not create additional regulatory prerequisites.
For every row, record Evidence location, Owner, Open issue, and Reviewer conclusion. Identify the specific record and version, assign a named action owner, and distinguish missing evidence from work awaiting completion.
| Failure mode | Practical control |
|---|---|
| A generic conditional status hides sterility testing versus an equipment-related omitted test. | Use an explicit route field linked to the release decision. |
| A favourable trend hides missing or incomparable preceding batches. | Keep traceable consecutive-batch history with a documented comparability assessment. |
| Maintenance closure is mistaken for omitted-test completion. | Maintain separate repair and laboratory completion records, linked to the same event. |
| The subsequent-batch gate remains open after an interface interruption. | Reconcile the product-level release restriction and define a manual contingency. |
| A message lacks a receiving facility or communication outcome. | Keep destination-specific notification records and escalate unresolved contacts. |
Use production context tagging to organise record associations and review MES to LIMS integration for interruption and reconciliation scenarios.
Reviewer reconstruction test
- Can you reconstruct the original decision from evidence available at authorization?
- Can you locate the retained sample and the omitted-test result, or identify its pending status?
- Can you identify affected destinations and unresolved contacts?
- Can you distinguish open actions from completed evidence?
- Can you explain who authorized closure and the basis for that conclusion?
Frequently asked questions
Q.How should a release record identify a batch awaiting only its sterility result?+
Use a status that distinguishes final release with sterility testing pending from malfunction-based conditional final release. For US PET drugs, 21 CFR 212.70(e) permits final release before sterility testing is completed but requires testing to start within 30 hours after production, subject to its weekend or holiday provisions. As a practical record design, the electronic release record should identify the authorization, pending sterility result, test-start timestamp, responsible reviewer and follow-up status without implying that the outstanding result has passed.
Q.What if an equipment fault affects both an otherwise eligible test and radiochemical purity testing?+
For US PET drugs, 21 CFR 212.70(f)(2) prohibits conditional final release when the malfunction prevents a radiochemical identity/purity test or determination of specific activity, even if the other conditional-release criteria are met. Practically, assess the fault against every affected test, rather than selecting only the potentially eligible omission. Record the affected critical quality attributes and unresolved determinations in the batch release checklist. Favorable historical results do not remove this US PET restriction.
Q.How should a reviewer justify the set of preceding consecutive batches used as evidence?+
For US PET drugs, 21 CFR 212.70(f)(1)(i) requires data from preceding consecutive batches produced using the same methods that demonstrate the conditional batch will likely meet established specifications. A practical justification identifies the sequence, explains method comparability and evaluates relevant results and adverse trends. Use a batch comparison tied to the batch execution history, rather than a selection of favorable results. Explain why the selected sequence supports this particular omitted test; avoid an unsupported universal batch-count rule.
Q.What should happen if the retained reserve sample is lost or becomes unusable?+
For US PET drugs, 21 CFR 212.70(f)(1)(iii)–(iv) requires retaining a reserve sample and completing the omitted test using it after correcting the malfunction. As a practical response, escalate the loss through a deviation, investigate the sample handoff, assess implications for the released batch and document the unresolved obligation. For US PET drugs, 21 CFR 212.70(f)(3) prohibits another batch release until the equipment problem is corrected and the omitted finished-product test is completed; sample loss does not satisfy either condition.
Q.Can a courier acknowledgment stand in for notification of the receiving facility?+
No—not merely because the courier transported the shipment. For US PET drugs, the 21 CFR 212.1 receiving-facility definition excludes a common or contract carrier transporting the product. For US PET drugs, 21 CFR 212.70(f)(1)(v) requires immediate notification of the receiving facility if reserve-sample testing produces an out-of-specification result. A practical notification record identifies the recipient facility, contact, message, time and delivery evidence. Keep this distinct from courier delivery or container status tracking.
Q.What should operations do when another batch is ready before the omitted test is completed?+
For US PET drugs, 21 CFR 212.70(f)(3) prohibits release of another batch of the PET drug product until the analytical-equipment problem is corrected and the omitted finished-product test is completed. As an operational control, keep the next batch in a clearly identified quarantine status and prevent dispatch from being mistaken for authorization. Assign ownership for checking both prerequisites. An equipment repair report alone is not evidence that the outstanding test has also been completed.
Q.How can the decision remain traceable when a laboratory or maintenance interface is offline?+
A practical contingency uses controlled records linking the batch, equipment fault, omitted test, supporting results, decision-maker, reserve sample and follow-up actions. Capture event times separately from later transcription times, and identify the original record for each entry. During a MES to LIMS integration outage, distinguish unavailable data transfer from unavailable testing: an interface failure alone does not establish an analytical-equipment malfunction. After recovery, reconcile entries, resolve discrepancies and preserve the decision history rather than replacing it with a clean retrospective summary.
Q.Can this US PET route justify an EU RTRT decision or a release in another industry?+
Do not use it as transferable release authority. For US PET drugs, 21 CFR 212.1 defines conditional final release as release before completing a required finished-product test because of an analytical-equipment malfunction. As a practical governance boundary, assess EU real-time release testing independently against the applicable EU framework and product authorization; do not describe it as permission to release unfinished product. For other drugs or industries, establish the applicable release basis separately rather than borrowing the PET terminology.
Primary sources
Explore this topic
Conditional Release sits inside 3 overlapping topic clusters in our glossary. Every neighbour is one click away.
Drug-product cGMP rules, ICH Q-series, and the regulators that enforce them.
PET / SPECT GMP, decay math, NRC controls and conditional release.
HCT/Ps, blood cGMP, donor eligibility, ISBT 128 labeling and forward-tracing lookback.
Want to see how Conditional Release could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
