Every field, status, tab, and control on a production run — the runs list, line items and batches, output records, cooking and cooling logs, and the exports the floor and auditors need.
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
The teriyaki line started weighing at six, the marinade crew rolls in at eight, and you need one screen that says what's due today, how far each recipe has gotten, and whether last night's cooling temperatures ever got signed off. That screen is a production run. Open Production runs and each day's work is one run you drill into. This page names every field, status, tab, and control on the list and on a run, and where each figure comes from.
Kitchen+The list opens on Production runs — every run on the floor, newest at the top. Above it sit a New button, which opens a blank run, and a WIP inventory link across to work-in-progress stock. A row of filters narrows the list:
PR-7.Each row is one run. It carries the run's name and reference, a status badge, and a
second line reading the run's date, its departments, and the recipes on it — up to
four, then +N more. On the right, a counter and bar show how many of the run's line
items are finished. When a run has cooking or cooling readings that haven't been
exported to a PDF yet, a warning sits under its name, like Cooking Log PDF not
generated. An empty list reads No production runs found.
A run's status is figured from its line items, not set by hand — so it moves on its own as the floor works:
A run is named when you create it; leave the name blank and it shows as Production
Run #N. Its reference — PR- followed by a number — is assigned for you and never
changes.
A run opens across a row of tabs. Recipes and Output records always show; the two log tabs and the staff tab appear only when the run calls for them:
Operator and supervisor views
A toggle on the right switches between an Operator view and a Supervisor view. Which one you land in — and whether you can switch at all — comes from your role. If a role you hold sets its default production view to Supervisor, you open in the supervisor view and can switch to the operator view; otherwise you see the operator view alone. The operator view keeps the floor on the batch in front of them; the supervisor view adds scheduled-versus-produced figures, staff attendance, and the controls that change the run.
When a run spans more than one department, a Department dropdown under the tabs filters everything below it to one department.
Each row on the Recipes tab is one . A row carries the recipe's name, its allergen badges, and a status badge, over a line naming its plan and scheduled date. When a line still owes work, red and amber badges spell it out: Weigh inputs (N) for ingredients left to weigh, Weigh output (N) for output left to record.
A button on the right opens the line — labeled Start on a pending line, Continue on one underway, and View on a finished one. Beside it, a Finish button and a Remove button sit on any line that isn't finished yet, for anyone who can change the run.
Above the rows, filter tabs narrow the list to the lines that need a particular kind of attention — All, Weigh inputs, Weigh output, Pending, and Finished — each with a count, and each shown only when it has lines to show.
A recipe runs in one of two input formats, which decides how its batches are counted:
In the supervisor view, an info button on each line opens its schedule details — a read-only panel of the fields behind the line:
The Output records tab lists every batch on the run and tracks what it produced. One row per batch:
While a batch is open, a Weigh button records output as a scale reading, and a Count button appears when the recipe is packaged, so output can be tallied as full containers plus loose units instead.
When a recipe on the run carries a , the run grows a Cooking Log or Cooling Log tab. Each consolidates every recipe's batches into one table, grouped by regulatory authority (FDA or USDA) when the run mixes both:
172 → 171 → 170 °F.A cooking batch reads Missing with nothing logged, Incomplete or Partial as readings come in, Complete once every reading is in and within limit, and Alert when a logged temperature falls below the recipe's minimum. Cooling batches run the same way but have no Alert state — a cooling breach surfaces on the individual reading rather than as a batch status.
Above each log table sit export buttons — one per document template that fits the recipe's authority and log:
Each button opens a print-ready PDF of that log in a new tab; when a department filter is set, the export covers only that department. These PDFs are the run's batch records — the paper an auditor asks for. Print labels and export batch records walks the procedure.
A run reports live: while the floor weighs and finishes, the list and the run refresh on their own, so a supervisor watching from the office sees the same picture as the crew on the line.