> ## Documentation Index
> Fetch the complete documentation index at: https://docs.batchlane.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Production

> Schedule runs, consume FEFO input lots, capture actuals, and sign off output.

Production converts active [recipes](/recipes) into batch records. A signed production run consumes input lots, creates output lots, writes inventory movements, and gives [traceability](/traceability) the link between inputs and finished goods.

## Prerequisites

* Active recipe exists.
* Required input lots are available in [Inventory](/inventory).
* Production and QA roles can complete signoff steps.
* Required COAs or batch documents are known. See [Documents and QA](/documents-qa).

## Run lifecycle

| Status      | Meaning                                                      |
| ----------- | ------------------------------------------------------------ |
| Planned     | Scheduled but not started.                                   |
| Blocked     | Cannot proceed because of shortage, hold, or workflow issue. |
| In progress | Production work is underway.                                 |
| Completed   | Operational work is captured but final signoff may remain.   |
| Signed off  | Inputs, outputs, movements, and signoff are finalized.       |
| Cancelled   | Run 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](/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](/recipes), [Inventory](/inventory), [Documents and QA](/documents-qa), [Traceability](/traceability), [Common errors](/common-errors).