Weigh & Dispense Workflow
The end-to-end weigh-and-dispense workflow on a modern GMP shop floor — from work-order release through lot selection, kiosk-guided weighing, tolerance checks, verification and eBR sign-off. The workflow is where potency, moisture and salt corrections meet the operator, and where most cross-contamination and data-integrity findings originate.
On this page · 7 sections
How does Weigh & Dispense Workflow 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.
01The workflow, end to end
- Work order released → MMR snapshotted into a control recipe for this batch.
- Materials called forward from staging by system-suggested lot (FEFO + status = released).
- Line clearance signed off on the booth/room and equipment.
- Operator logs into kiosk (Part 11 e-sig session).
- Kiosk presents the recipe step + suggested lot; operator confirms or overrides (with reason).
- Corrections computed live (SBF, LOD, PF, overage) from lot and item attributes.
- Operator zeros/tares the balance; kiosk verifies the balance is calibrated and above minimum weight for the target.
- Material added; live scale display shows target ± tolerance.
- In-tolerance weight accepted; e-signed by operator and (where required) verifier.
- Container labelled with barcode + step + lot + weight + operator; moved to accumulation.
- Next step, or batch weigh-out complete → materials handed off to processing.
- eBR renders the full weigh-out record automatically.
02Before the first weigh — the pre-conditions
| Pre-condition | Enforced by |
|---|---|
| Booth line-cleared and signed | Kiosk gates workflow entry |
| Operator trained on this SOP/product | Skills matrix / kiosk gate |
| Balance in calibration + above USP <41> minimum weight for target | Balance metadata + routing rule |
| Material released (status = released, within retest/expiry) | Inventory status attribute |
| MMR version locked into control recipe | WO release snapshot |
| Overage/PF/SBF/LOD attributes present on every material | Recipe validation at WO release |
03The scale-side experience
The operator sees one screen per dispense: the step name, the lot ID (barcode-verified), the corrected target mass, the tolerance band, and a live scale reading. Colour changes as the reading enters the band; a green confirm is enabled only inside band; out-of-band requires a deviation flow rather than a re-weigh loop.
- No manual arithmetic. The four-factor stack (SBF → basis → PF → moisture) computes live from typed attributes; the operator sees the math but doesn't type it.
- Verifier co-sign required for high-risk actives (recipe-configured, not operator-decided).
- Partial containers get an in-process expiry stamp and go back to staging with an updated remaining-mass tag.
- Rejects and re-weighs are audit-trailed; a re-weigh doesn't erase the failed attempt.
04Verification models under 21 CFR 211.101(d)
Section 211.101(d) requires each component addition to be done by one person and verified by a second — OR verified by one when done using automated equipment under §211.68. Three verification models are common:
| Model | Description | When used |
|---|---|---|
| Two-person contemporaneous | Operator weighs, verifier watches and co-signs on the kiosk | High-potency APIs, controlled substances, complex recipes |
| Barcode-verified single-person | System verifies lot identity, balance identity, calculated target against the recipe — no second person | Automated dispensing lines qualified under §211.68 |
| Delayed independent review | Operator weighs and signs; a second reviewer reviews the eBR entry before batch release | Lower-risk excipients; must be documented as compliant path |
05Labelling and handoff
Every dispensed container carries a barcode label with: work order, step, material and lot, net weight, tare, dispensing operator, timestamp, and (where applicable) in-process expiry. Downstream processing scans the label to consume — the kiosk-side chain and the process-side chain reconcile in the eBR.
06Common mistakes
- Weigh-out spreadsheet parallel to the kiosk 'for convenience' → two records, one of which is unofficial and wrong.
- Operator overrides FEFO without a documented reason → older lot dispensed after newer, or wrong lot dispensed entirely.
- Tare not re-verified after a container change → tare from previous container carries forward as false net weight.
- Line clearance signed off after the workflow starts → GMP paperwork lie visible to the auditor.
- Balance below USP <41> minimum weight for the target → readings are noise, not measurements.
- Partial container returned to staging without in-process expiry tag → next batch pulls it as if fresh.
07How V5 Ultimate handles the workflow
Frequently asked questions
Q.Do we need a separate booth per product, or can one booth handle multiple?+
One booth can handle multiple products with disciplined line clearance and appropriate airflow/pressure design. Cross-contamination risk is managed by clearance, not by dedicating hardware.
Q.Can the operator over-ride a suggested lot?+
Yes — the workflow allows override with a documented reason (e.g. 'oldest lot has been sampled for retest and is pending'). The override is audit-trailed; the reason field is not free-text but a controlled vocabulary.
Q.How does the workflow handle add-and-check patterns (add half, check, add rest)?+
The kiosk supports add-and-check as a configured sequence per step. Each add is a scale reading; the final in-tolerance reading is the accepted net; all intermediate readings are audit-trailed.
Q.What happens if the network drops mid-workflow?+
The kiosk buffers the record locally and continues on cache. On reconnect, records reconcile with the server. This is a Part 11 requirement — no in-progress dispense can be lost or altered by network state.
Primary sources
Further reading
Want to see how Weigh & Dispense Workflow could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.