Split Batch

A split batch operation takes the homogeneous output of a parent batch and divides it into multiple child batches. Each child receives a new batch ID, inherits the parent's quality profile at the moment of split, and proceeds with an independent batch record and disposition path.

• Parent — fully complete, with known disposition or pending disposition at the moment of split.
• Split point — defined transfer event with quantity per child captured.
• Children — new batches with new IDs, each linked to the parent via the genealogy graph.
• Quality inheritance — children inherit the parent's identity test, assay, microbial results, etc., unless re-tested per recipe.
• Independent disposition — each child can be released, held or rejected separately.

• Multi-SKU packaging — one bulk lot split across different pack sizes, languages or markets.
• Multi-customer allocation — one production batch divided to fulfil multiple customer orders.
• Re-pack — bulk drum content split into smaller commercial units.
• Sub-lot for stability — a defined portion split off for the stability program with its own retention.
• Sample sub-batch — formal split for engineering or pilot use with distinct quality tracking.
• Capacity-driven — bulk pool too large for a single downstream unit; split across multiple runs.

• Parent batch ID and quantity at split moment.
• For each child: new batch ID, target quantity, actual quantity post-transfer, container/equipment used.
• Cumulative reconciliation — sum of children quantities + accounted losses = parent quantity.
• Operator/signature for the split event per SOP.
• Equipment used (split device, scale, transfer line) for CIP/cleaning context.
• Time-of-split timestamp (UTC) and any conditional data (temperature, hold-time start).

• Identity assurance — each child must be uniquely identifiable; relabel and segregate at split.
• Cross-contamination — split equipment that has held a different product must be CIP-verified before splitting.
• Homogeneity assumption — split presumes parent is homogeneous at the split point; if not, children inherit heterogeneity (sample plan must account).
• Hold-time impact — splits may impose new hold-time clocks for each child if process-relevant.
• Disposition decoupling — child can fail QA without affecting siblings; clear data isolation required.

• Split event captured as a first-class record with type 'SPLIT', parent batch ID, child batch IDs and quantities.
• Each child's BMR opens with the split event as its first entry, linking back to the parent BMR.
• Parent BMR captures the outbound split, with all children listed for forward traversal.
• Reconciliation entry confirms quantity balance with any losses categorised.
• Operator signature per child or per split event per SOP — second-witness verification on regulated material.

• Biopharma — bulk drug substance split across multiple drug-product fill batches (different vial sizes or fill volumes).
• OSD pharma — one coating sub-lot split across bottling, blister-pack and physician-sample SKUs.
• Food — one production tank split across multiple SKU fill lines.
• Cosmetics — bulk emulsion split across SKU (tube, bottle, jar) packaging lots.
• Chemicals — drum-fill split from a master batch across multiple customer orders.
• Veterinary pharma — bulk batch split across multiple species-specific final pack lots.

• Children sharing the parent's batch ID — recall scope cannot distinguish; disposition decoupling impossible.
• Quantity reconciliation not enforced — silent material drift over time.
• Quality inheritance recomputed differently per child — children released against different identity results.
• Split equipment not captured — CIP investigation later cannot trace cross-contam risk.
• Manual lot-label print at split — typos create identity mismatches between physical and electronic record.
• Hold-time clock not reset per child where required — children released past their effective expiry.
• Engineering or sample splits not flagged — accidental commercial release.