Batch Hold State

Batch hold state is the formal status applied to a batch (or portion of one) indicating that material is locked from forward processing until a QA decision authorises release, rework, reject or other disposition. Hold is a quality-system control, not a process-execution state — the underlying batch may have completed all manufacturing steps and still be on hold for testing or investigation.

• Status visible across MES, WMS and ERP — material is logically and physically segregated.
• Hold reason code captured from controlled vocabulary.
• Hold initiator (system, operator or QA) and authorisation role recorded.
• Material physically tagged or moved to quarantine zone where industry requires.
• Hold release requires defined authorisation, typically QA disposition, not the initiator.

• Deviation occurred — material held pending investigation outcome.
• OOS or OOT result — batch held until re-test or investigation concludes.
• Supplier alert — incoming material lot affected by supplier recall or quality alert.
• Equipment issue — material processed on suspect equipment held pending equipment investigation.
• Cross-contamination concern — campaign-changeover anomaly triggers hold on first-batch product.
• QA hold — discretionary, based on investigation findings outside the immediate batch.
• Customer hold — specific customer order on hold for commercial reasons (rare but real).

• Logical — system status prevents downstream consumption; WMS will not allocate held material to a pick; MES recipe execution refuses to charge held material.
• Physical — material tagged with hold label, moved to quarantine zone or designated hold-state location.
• Some industries (sterile manufacturing, controlled substances) require physical separation regardless of logical controls.
• Bypass attempts (operator overriding system to consume held material) require elevated authorisation with full audit and typically generate immediate deviation.

1. Hold reason investigated — deviation closed, retest completed, supplier issue resolved.
2. Disposition determined by QA: release, conditional release, rework, reject, or further hold.
3. Disposition recorded with rationale, supporting evidence (test results, investigation report), and QA signature.
4. If released, hold flag cleared; material returns to available status; downstream allocation re-enabled.
5. If rejected, material moves to reject status; destruction or return-to-supplier workflow initiated.
6. If reworked, rework batch created with parent-child link to held batch; original batch closed.
7. Audit trail captures the complete hold-to-disposition lifecycle.

• Pharma — batch held pending stability investigation when an early time-point assay drifts low; release decision after extended testing.
• Biopharma — batch on hold pending bioassay; release after potency confirms specification.
• Medical device — lot on hold after a customer complaint suggests a sterility breach; released after investigation closes.
• Food — production lot on hold pending micro lab confirmation of pathogen-negative result.
• Cosmetics — bulk batch on hold pending preservative-efficacy retesting after supplier change.
• Supplements — finished lot on hold pending heavy-metals confirmation per USP 232/233 limits.

• Hold not enforced in WMS — operator picks held material for production without challenge.
• Hold reason codes too coarse — analytics shows 'investigation' without root-cause patterns.
• Hold release by initiator instead of QA — separation of duties broken.
• Hold material commingled with available material in physical storage — eventual mix-up.
• Aging-holds dashboard not maintained — long-held material forgotten, expiration risk.
• Hold extended repeatedly without investigation closure — material aging into rejection.
• Conditional release used without time-limit and revocation criteria — back-door release.