The batch is done. What exactly did you make?

The pots are washed and the answer is already evaporating: what actually went in, who ran the cook, whether the pH check happened, what it cost. By the time an auditor, a customer or your own curiosity asks, the recipe has moved on and the batch cannot testify.

A finished BatchDash batch seals its record: the recipe as it ran, the weighed quantities, the parameters and checks, the lots in, the lot out, and the real cost. Edit the recipe tomorrow, the record does not move. It is the production history your certifier keeps asking whether you have.

Request access Sign in

01Batch records

Written while the batch is running

The run page is the worksheet. What was planned sits beside a box for what actually went in, and the lots it came from go on the same row. The check the recipe demanded is there with its target and an empty field, and it stays counted as outstanding until somebody fills it. Time is per person and it is their own time on the batch rather than a share of it, with a link to take the elapsed clock if one was running. Then what came out against the yield you expected, and how it went: a score, tasting notes, process notes, defects.

The capture block on a running batch in BatchDash: planned against actual for every ingredient with its lots, the check still to record, the time per person, the observed output against the expected yield, and the tasting notes.

02Batch records

Sealing is a decision, not a formality

Closing a batch asks for the three things that turn a worksheet into a record: what came out, the lot code it will answer to from here on, and whether the finished product passed. It names who is signing, which need not be whoever did the work, and says plainly that signing adds nothing to the labor cost. A check still outstanding is on the dialog before you press the button, not discovered afterwards. And it tells you where the output is about to land.

Completing a batch in BatchDash: observed output, the lot code, who is signing it off, the finished-product check, and a warning that one check is still to record.

03Batch records

And then it stops changing

The sealed record is the recipe as it ran. The lot, the operators and the hours each of them put in, the yield against the plan, and every check with its target, its reading, and the name and minute it was recorded at. Under that: what was actually consumed and what that cost, the packaging that went on it, and the supplier lot behind every single line. Edit the recipe tomorrow and none of it moves.

A sealed batch record in BatchDash: lot code, operators, the checks taken with who recorded them, yield against expected, the cost of the batch, and the supplier lot behind every ingredient.

04Batch records

Sealed with its own price tag

Expected cost is a plan; the record keeps what the batch really cost:

Ingredients at the ledger cost of the lots actually drawn.
Labor from recorded minutes, per operator, at each one’s rate.
Equipment amortization for the tools the steps really used.
Yield included: 17.5 liters out of an 18-liter plan reads as its true per-liter cost.

05Batch records

Trials that cost you nothing but the tasting

A test batch runs against real stock, because trials that pretend to consume nothing teach nothing. Score it by tasting; if it stays an experiment, revert it and the consumed stock comes back at the cost it left. The bench notes and the score stay, so even the dead ends leave knowledge behind.

06Batch records

Everything downstream points back at it

The lot printed on the label is this record’s lot. The trace walks from a delivery note into this batch and back out to the customer who received a jar of it. The margin on the product reads this batch’s real cost rather than its plan. A record nobody can reach from the thing that made them ask is a filing cabinet; this one sits in the middle of the system, which is the only reason it stays true.

Works with

TraceabilityAny lot, forward or back, in minutes PlannerThe week, checked against stock CostingReal prices, margins that stay true Batch manufacturing softwareThe whole system on one page, with its screens

Completing a runIn the help center