🏭 Production Runs
Schedule a run, capture yield, complete it — and how runs feed back into recipe analytics.
5 sections · ~5 min read
A Production Run = one batch on the line
Three states: Pending (proposed), Scheduled (date locked), Completed (run done, yield captured). Factory drives the dates and the actuals.
Open Production Plan
The schedule view across recipes and dates.
📍 In RecipeHub: Production Plan page
+ Schedule Run
Add a planned batch: pick recipe, factory line, date, target weight. Status starts Pending until the date is locked.
📍 In RecipeHub: Production Plan page
Role-specific notes
FACTORY: You schedule and complete runs. Other roles only read.
OPS: Production is factory-only — you can't edit runs from here.
Indicative vs Validated yield
At Production Trial, Factory records the indicative yield — the first real reading. Once the recipe is approved and goes into regular production, the validated yield from real runs replaces the indicative figure. Both feed costing; the validated number wins when present.
📍 In RecipeHub: Production Plan page
Completing a run
When the batch is done, Factory marks it Complete and enters the actual output weight. The system computes actual yield, which feeds back into recipe analytics and food cost %.
📍 In RecipeHub: Production Plan page
Role-specific notes
FACTORY: Be honest with the actuals — they drive cost decisions downstream.