Quality · The complete guide

Partial Batch Release

TL;DR

Partial batch release is the controlled disposition of a portion of a batch — typically split sub-lots — while other portions remain on hold or under investigation. It is what allows commercial throughput to continue when one sub-lot has a quality question and others are clean: release the clean sub-lots, hold the suspect one. Done with discipline, partial release is a powerful tool; done sloppily, it is a route to mixed-status material in distribution and recall confusion.

Reviewed June 3, 2026· By V5 Ultimate compliance team· 2,100 words · ~10 min read

AI · Explain it for MY operation

How does Partial Batch 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.

Your industry

Your scale

01What partial batch release is

Partial batch release is the formal QA disposition of one or more portions of a batch independently of the rest. The 'portions' are typically split sub-lots, each with its own batch ID and independent quality history. QA evaluates each portion separately and releases those that meet specifications while holding, rejecting or reworking those that do not.

Predicated on splits — the batch must have been split into identifiable sub-lots with distinct IDs.
Each sub-lot evaluated independently against release criteria.
Released sub-lots proceed to distribution; held sub-lots remain locked.
Each sub-lot's disposition is recorded individually with its own QA signature.
Genealogy graph reflects per-sub-lot status, not parent-batch status.

02When partial release applies

Multi-SKU split — bulk batch split across pack sizes; only one SKU has a label issue; the others release normally.
Multi-customer split — customer A's portion has a documentation issue; customer B's portion releases on schedule.
Multi-line packaging — one packaging line had a deviation; the other line's sub-lot is clean.
Selective re-testing — one sub-lot fails micro and is re-sampled; others have clean micro and release.
Geographic split — sub-lots for different markets with different regulatory requirements; release per market readiness.
Stability sub-lot held — formal stability portion held back for retention while commercial portion releases.

03Data discipline required

Split events captured rigorously with per-sub-lot quantities, equipment and operator (without splits, there is no partial release).
Per-sub-lot test results — sampling plan must support sub-lot-level disposition, not just batch-level.
Per-sub-lot deviation tracking — deviations isolated to the affected sub-lots, not blanketing the whole batch.
Per-sub-lot disposition records with QA signature and rationale.
Distribution and shipment records keyed to sub-lot IDs so recall queries land on the right portions.

04Release criteria per sub-lot

Each sub-lot must independently meet all release criteria:

All required tests completed with results within specification.
All deviations affecting the sub-lot investigated and dispositioned.
Batch record (or sub-lot record) reviewed and approved.
Stability program retention secured if applicable.
QP certification (EU) or equivalent QA disposition signed.
Customer-specific requirements (CoA, certificates) generated.

Partial release does not lower the bar — each released sub-lot meets the same criteria as a normal full-batch release.

05Implications if a held sub-lot is later rejected

Common scenario: sub-lot A is released, sub-lot B held pending investigation, investigation later reveals quality issue. Now what?

If the issue isolates to sub-lot B only, sub-lot A remains released and the affected B is rejected or reworked.
If the issue is parent-level (raw material, equipment, recipe), sub-lot A may need recall — investigation must reach this verdict explicitly.
QA decision is documented with rationale for why sub-lot A was or was not affected.
Recall preparedness is exercised — having released sub-lots in distribution makes the genealogy traversal essential.

06Cross-industry examples

Pharma — multi-SKU split released as labels are produced for each market; first markets release while later markets await labels.
Biopharma — DP fill split across multiple vial sizes; each vial size sub-lot tested and released individually.
Medical device — packaging sub-lots released as customer-specific labeling completes.
Food — bulk production split across multiple SKU package sizes, each released as line clearance and labeling complete.
Cosmetics — bulk emulsion split across multiple container types, each released independently as filling completes.
Veterinary pharma — sub-lots split by species-specific packaging, released as label approvals for each species clear.

07Common mistakes

Per-sub-lot disposition with parent-batch testing only — assumption of homogeneity unproven; release risk.
Sub-lot IDs not propagated to distribution — recall queries cannot isolate affected portions.
Held sub-lots' status not enforced in WMS — accidentally shipped alongside released siblings.
Deviation written at batch level when issue affects only one sub-lot — every sub-lot held unnecessarily.
Conditional release used to push held sub-lots out the door — back-door release.
Partial release records lacking explicit 'why this sub-lot is released independently' rationale.
QA reviewer pressured to release early sub-lots before investigation completes on later ones — quality decision compromised.

08How V5 Ultimate handles partial batch release

Partial release in V5

V5 treats partial batch release as the natural disposition path for split sub-lots. Each sub-lot carries its own quality record — test results, deviations, hold status — independent of siblings, supporting per-sub-lot disposition decisions. Release workflows operate at the sub-lot scope; QA signature is captured per sub-lot with rationale text that explicitly addresses why this sub-lot can release independently of its siblings (which is the quality-defensible articulation auditors expect). Held sub-lots remain locked from allocation, pick or shipment regardless of how the request originates — system enforcement, not operator vigilance. Distribution records carry sub-lot IDs; recall queries traverse the genealogy graph at sub-lot granularity, scoping affected portions accurately. Aging dashboards surface long-held sub-lots before they become quality issues. If post-release investigation widens to implicate previously released sub-lots, V5's forward-traversal queries identify every distribution endpoint in seconds, supporting timely recall scope decisions instead of multi-day genealogy reconstruction exercises.

Frequently asked questions

Q.Is partial release allowed by FDA?+

Yes — 21 CFR 211.165 requires meeting specifications for release; it does not prohibit per-sub-lot disposition. The key is that each released portion meets all release criteria independently and the disposition rationale is documented.

Q.Does EU QP release allow partial release?+

Annex 16 allows the QP to certify portions of a batch in defined circumstances. Per-sub-lot certification follows the same QP responsibilities; the QP is accountable for each certified portion meeting all requirements.

Q.Can partial release apply without splits?+

Difficult — without distinct sub-lot identity, you cannot defensibly release 'some' of a batch while holding the rest. The practical pattern requires the split to create identifiable, separately-trackable portions.

Q.What if testing reveals that the held sub-lot was actually the safe one?+

Re-evaluate the released sub-lot's safety against the new information. If the investigation widens, recall the released portion. QA decisions are not irreversible — the genealogy enables corrective action.

Q.How does partial release affect CoA generation?+

Each released sub-lot gets its own CoA with the data and disposition for that sub-lot. Aggregating multiple sub-lots into one CoA only works if all sub-lots share identical relevant data; per-sub-lot variation requires per-sub-lot CoA.