Skip to main content
Production converts active recipes into batch records. A signed production run consumes input lots, creates output lots, writes inventory movements, and gives traceability the link between inputs and finished goods.

​
Prerequisites

  • Active recipe exists.
  • Required input lots are available in Inventory.
  • Production and QA roles can complete signoff steps.
  • Required COAs or batch documents are known. See Documents and QA.

​
Run lifecycle

StatusMeaning
PlannedScheduled but not started.
BlockedCannot proceed because of shortage, hold, or workflow issue.
In progressProduction work is underway.
CompletedOperational work is captured but final signoff may remain.
Signed offInputs, outputs, movements, and signoff are finalized.
CancelledRun should not proceed.

​
Production flow

  1. Schedule a run from an active recipe.
  2. Review component readiness and shortage warnings.
  3. Select or confirm FEFO input lots.
  4. Capture actual usage, waste, deviations, and output quantity.
  5. Upload batch attachments when needed.
  6. Complete operations and QA signoff.
  7. Confirm output lots appear in Inventory.

​
What signoff does

Signoff is the point where operational history becomes durable. It consumes inputs, creates output inventory, writes movements, records signoff, and preserves the recipe version used.

​
Common production issues

  • Create an active recipe before scheduling production.
  • Shortages usually mean lots are missing, unavailable, held, quarantined, expired, or in the wrong unit.
  • If the wrong recipe was used, cancel and reschedule before signoff when possible.
  • If a signed run has wrong output, use auditable correction workflows instead of silently editing history.
  • If QA cannot sign off, check role permissions and required documents.
Related pages: Recipes, Inventory, Documents and QA, Traceability, Common errors.