A production log is a running record of what was made: one row for each run, written the day it happens, with the date, the product, the batch or lot, when it started and ended, how many units were planned, how many came out good, and a note. It answers three questions later, when nobody remembers: what did we make and when, how much came out against the plan, and how fast does the line really run. It isn't the batch record, which holds one batch's ingredients and checks, and it isn't the plan. Below is a week of a made-up hummus maker's log, what to read from it, how it differs from the other papers with similar names, and the file.
The short version
- One row a run, written the same day by whoever ran it.
- Date, product, batch or lot, start, end, planned, good, rejected, who, a note.
- Good units ÷ planned says how the run went. Good units ÷ hours says how fast the line is.
- The note is the part people skip and the part that's worth most a month later.
- The log is the index. The batch record is the detail.
- TaroStack keeps a record for every batch, with the lots it used. More below.
An example week
| Date | Product | Batch or lot | Start | End | Hours | Planned | Good | Rejected | Good, of planned | Good units an hour | By | Note |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Nov 16 | Classic hummus, 10 oz | HC-1116 | 7:00 | 10:30 | 3.50 | 480 | 468 | 12 | 97.5% | 133.7 | AK | 12 short fills, caught at the scale |
| Nov 16 | Roasted garlic hummus, 10 oz | HG-1116 | 11:00 | 1:30 | 2.50 | 240 | 240 | 0 | 100.0% | 96.0 | AK | |
| Nov 17 | Classic hummus, 10 oz | HC-1117 | 7:00 | 11:00 | 4.00 | 480 | 420 | 6 | 87.5% | 105.0 | DM | Tahini ran out: the last kettle wasn't made |
| Nov 18 | Red pepper hummus, 10 oz | HR-1118 | 7:30 | 10:00 | 2.50 | 240 | 236 | 4 | 98.3% | 94.4 | AK | |
| Nov 19 | Classic hummus, 2 lb tub | HT-1119 | 7:00 | 9:00 | 2.00 | 120 | 120 | 0 | 100.0% | 60.0 | DM | |
| Nov 20 | Classic hummus, 10 oz | HC-1120 | 7:00 | 10:15 | 3.25 | 480 | 474 | 6 | 98.8% | 145.8 | AK |
Six runs, 17.75 hours, 1,958 good units against 2,040 planned: 96.0%.
What each column is for
Date and product. Obvious, and the two columns every later question starts from.
Batch or lot. The code that's also on the tub. With it, the row leads to the batch's own record and to the shops that got it. Without it, the log says a batch of classic was made on Tuesday and nothing about which tubs those were. How to build a code is in how to create lot numbers.
Start and end. Clock times, not "about three hours". The sheet works out the hours.
Planned, good, rejected. Planned is what the day's plan asked for. Good is what went to the cooler. Rejected is what was made and thrown out. They needn't add up: on November 17, 480 were planned, 420 were good, 6 were rejected, and 54 were never made because the tahini ran out.
Made by. Initials. Not for blame: so there's someone to ask.
Note. Anything that made the run different, in a few words, written that day.
What the week says
The classic 10 oz ran three times, at three speeds. 133.7, 105.0 and 145.8 good units an hour. The slow one is the short run: four hours on the clock, the last of them spent finding out there was no more tahini. The other two say this line makes 130 to 150 an hour when nothing goes wrong. That's the number to plan next week with, and it came from the log, not from a guess. Turning it into a week's capacity is in how to calculate production capacity.
One run missed, and the note says why. Sixty units short on the 17th, and the cause was a material, not the line. Without the note, the month's review would show a slow Tuesday and nobody would know it was a purchasing problem.
Rejects are small and have a cause. Twelve short fills on Monday point at the filler's setting, six on each of two later runs don't point at anything yet. A month of rows will.
Production log, batch record, production report
The names get used for each other. On a small floor they're three different papers.
| Paper | One of them for each | What's on it | Who reads it |
|---|---|---|---|
| Production log | Run, as a row in a running list | When, what, how many, who, a note | The owner, looking back |
| Batch record | Batch, as its own sheet | Ingredients and their lots, weights, steps, checks, sign-off | Anyone tracing a problem |
| Production report | Day or week, as a summary | Totals against the plan, downtime, reasons | Whoever plans the next one |
The log is the index: it's short enough to scan a year of. The batch record is where the lot of chickpeas is written: see what is a batch record. The report adds the log's rows up: see production report template. A one-day sheet that tells the floor what to make is a different thing again: what is a production sheet.
Keeping one
- Write the row when the run ends, before cleanup. End-of-week logs are fiction.
- One log for the room, on a clipboard by the door or a shared sheet. Two logs disagree.
- Never erase. Cross out and initial, or add a row. A log with clean corrections is believed. One with white-out isn't.
- Count good units at the cooler, not at the filler.
- Keep it as long as you keep the batch records it points to.
Get the template
Download the production log template. One sheet and a read-me: the example week, with the hours, the share of the plan and the units an hour worked out as you type. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The log is typed by hand after the fact, and it points at other papers. The lot code in the third column is only as good as the batch sheet in the binder with the same code on it, and the question a shop asks is never "what did you make on the 17th". It's "which chickpeas were in the tub I'm holding", and that takes the log, the batch sheet, the receiving log and an hour.
How TaroStack does it
In TaroStack the log isn't a separate thing to keep: it's the list of batches.
Each batch is a record with its recipe, the amount planned and the amount made, when and by whom.
The batch notes which lots it used, automatically, as it's recorded. The lot it makes carries your code and its dates.
Your own checks are fields on the batch: tick boxes, numbers, text, initials. A printable batch-record form carries them.
Actual against standard: what the batch used and made, set against what the recipe says it should.
One report for a lot: which supplier lots went into it, and which customers got it.
| The question | Paper log | In TaroStack |
|---|---|---|
| What was made this week | Read the rows | The list of batches |
| Which lots went into HC-1117 | Find the batch sheet | On the batch |
| Who got HC-1117 | The delivery book | On the lot's report |
| Does the recipe yield what it says | Add up a month by hand | Recipe truth, from your batch history |
TaroStack doesn't time a run or count units off a machine: what was made is what someone records. Recipes, batches and lots are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
