A Production Tracking Sheet That Tells You Why You Missed, Not Just That You Did
Most production tracking sheets only record the damage. Here is the loss-reason version that drives your daily huddle and gets problems owned, plus a sample hour-by-hour layout.
I have walked a lot of production floors, and I can usually find the tracking sheet in the first five minutes. It is taped to the side of a machine or clipped to a board near the line. It has a column for the plan and a column for the actual, and somewhere down the bottom there is a total that nobody likes. The supervisor fills it in at the end of the shift, the numbers go red, and then the sheet does absolutely nothing.
That is the problem. Most production tracking sheets only record the damage. They tell you that you ran 820 units against a target of 1,000, which you already knew the second the count came up short. What they do not tell you is the one thing that actually matters: why.
A number with no cause attached is not information. It is a complaint. And you cannot run a Monday morning huddle off a complaint.
This post is about the version of the sheet that earns its place on the wall. It is part of my Manager’s Playbook series, and it is the piece I wish someone had handed me my first week as a line supervisor instead of letting me discover it the hard way over about three years.
Why the Plan-Versus-Actual Sheet Fails You
The standard sheet has two jobs in the designer’s head: prove the line ran, and flag when it did not. Both of those are backward-looking. They are accounting, not management.
Here is what happens in practice. The line misses by 180 units. The sheet shows the miss. The plant manager sees red at the standup and asks what happened. Now your supervisor is standing there at 6:45 in the morning trying to reconstruct, from memory, a shift that ended eight hours ago and was run by someone else. The answer comes out as “I think we had some downtime on the press” and everyone nods and moves on. Nothing gets fixed because nothing got captured.
The miss was real. The cause evaporated. That is the entire failure mode, and it repeats every single day on thousands of lines.
The fix is almost embarrassingly small. You add a column.
The One Column That Changes Everything: Loss Reason
The whole game is a loss-reason column sitting right next to actual output, filled in by the operator in the moment, not reconstructed later. When the line drops behind in a given hour, the person running it writes down why before the cause is gone.
Now the sheet stops being a logbook and starts being a diagnosis. At the end of the shift you do not have “we missed by 180.” You have “we missed by 180, and 140 of it was a single changeover that ran long and the other 40 was a material stockout at hour three.” That is a sheet you can act on. That is a sheet that points at an owner.
The catch is that the column only works if you control what goes in it. Hand an operator a blank box labeled “reason” and you will get forty different spellings of “machine broke,” half of them too vague to count and the other half too specific to group. Free text feels honest and detailed. It is actually the enemy, because you can never add it up. Three months of free-text reasons cannot be sorted into a Pareto, and if you cannot Pareto it, you cannot prioritize the fix.
So you standardize. You give the floor a short fixed list of codes, and the only acceptable entries are from that list.
Keep the Code List Short and Standardized
A good loss-reason code list is short enough to memorize and broad enough to catch the real world. Six buckets covers most discrete and batch manufacturing:
- Changeover - setup, teardown, tooling swaps, first-piece approval time.
- Breakdown - the equipment stopped when it was supposed to be running.
- Material - no parts, wrong parts, parts late from the previous operation.
- Quality - scrap, rework, holds, a defect you had to stop and chase.
- Manpower - short-staffed, late start, training, an operator pulled to another line.
- Waiting - blocked or starved by something upstream or downstream that is not yours (forklift, inspection, a full downstream buffer).
That is the whole list. Six codes. You can put it on a laminated card the size of a business card and clip it to the board.
The reason short and fixed beats long and detailed is not laziness, it is math. With six codes, after two weeks you can look at the sheet and say “61 percent of our lost time this month is Changeover” and walk straight to the biggest fire. With forty free-text variations you have a pile of words and no direction. Standardized codes are what turn the sheet from a record into a ranked to-do list.
A few rules that keep the codes honest:
- One code per loss event. If a breakdown caused a material starve downstream, code the root, which is Breakdown. Do not double-count.
- Define the codes in writing, one sentence each, and post the definitions. “Waiting” versus “Material” causes the most arguments, so settle it on paper before the floor settles it for you, inconsistently.
- Resist adding a seventh code every time something weird happens. Weird things go under the closest bucket. The discipline of a short list is the whole value.
What the Sheet Actually Looks Like
Here is the artifact. This is a single-shift, hour-by-hour layout for one line or one machine. Run-by-run works the same way if your cycle is long: swap the hour rows for run or batch rows.
LINE / MACHINE: Press 4 DATE: ____________ SHIFT: ____ OPERATOR: __________
HOUR | TARGET | ACTUAL | +/- | LOSS CODE | SHORT NOTE (optional, 5 words max)
----------+--------+--------+------+-----------+------------------------------------
6-7 | 125 | 125 | 0 | -- |
7-8 | 125 | 90 | -35 | CH | tooling swap ran long
8-9 | 125 | 110 | -15 | MT | waiting on blanks
9-10 | 125 | 125 | 0 | -- |
10-11 | 125 | 70 | -55 | BD | hydraulic line
11-12 | 125 | 120 | -5 | QU | rework one tote
12-1 | 125 | 125 | 0 | -- |
1-2 | 125 | 100 | -25 | MP | covering break, short one
----------+--------+--------+------+-----------+------------------------------------
TOTAL | 1000 | 865 | -135 |
ROLLUP (this shift, lost units by code):
CH Changeover 35 MT Material 15
BD Breakdown 55 QU Quality 5
MP Manpower 25 WT Waiting 0
TOP LOSS THIS SHIFT: BD Breakdown (55) -> OWNER: __________
LOSS CODE LEGEND
CH = Changeover setup, teardown, tooling, first-piece approval
BD = Breakdown equipment stopped that should have been running
MT = Material no parts, wrong parts, late from prior operation
QU = Quality scrap, rework, holds, chasing a defect
MP = Manpower short-staffed, late start, training, operator pulled
WT = Waiting blocked or starved by something not yoursNotice what the bottom third does. The rollup adds the lost units by code and names the single biggest loss for the shift, with a blank line for an owner. That blank line is the entire point of the sheet. It is the handoff from “something happened” to “someone is handling it.”
The short-note column is optional and capped on purpose. Five words is enough to jog a memory the next morning. Any more and you are back in free-text territory, and people stop writing anything at all.
How the Bottom of the Sheet Runs Your Huddle
A tracking sheet that lives and dies on the line is a waste. The value gets unlocked when the rollup feeds the morning standup, because that is where causes turn into actions and actions get an owner.
The flow is simple. The off-going shift completes the rollup before they leave. The top loss code and its number ride straight into the daily huddle as a talking point, not a surprise. Instead of a plant manager asking “why were we down” and getting a shrug, the supervisor opens with “Press 4 top loss was Breakdown, 55 units, hydraulic line at hour five.” Now the conversation is about the fix and who owns it, which is exactly where you want eight minutes of everyone’s morning to go.
If you run a tiered board, this is the input that makes the Productivity line on your SQDIP actually mean something instead of a green dot somebody colored in. I walk through how those two pieces connect in the daily production huddle agenda and the SQDIP board tier-meeting run script. The tracking sheet is what feeds them. Without the loss codes, the huddle is a status read. With them, it is a problem-solving session.
One discipline that matters: the top loss each day needs a named owner before the huddle breaks, even if the action is just “watch it again today.” A loss code with no owner is the same dead number you started with, just better organized. The whole chain only works if it ends in a name.
Start Small, Then Let It Earn Its Keep
You do not roll this out plant-wide on Monday. Pick your worst line, the one that misses most and explains least. Print the sheet, walk the legend out to the operators, and tell them the only new thing they have to do is write two characters in a box when the line falls behind. That is the entire ask. Two characters.
Give it two weeks. At the end of two weeks you will have something you have probably never had on that line, which is a ranked, countable picture of where your hours actually go. Nine times out of ten it is not what the floor swore it was. The “we always have breakdowns” line turns out to be 70 percent changeover, and now you know where to aim.
The sheet is not the win. The win is that misses stop disappearing and start getting owned. The sheet is just the cheapest tool I know for making that happen.
I keep a clean, printable version of this hour-by-hour layout with the loss-code legend already built in, alongside the rest of the Manager’s Playbook tools, if you would rather start from a template than draw it on a whiteboard. Either way, add the column. It is the smallest change on this list and the only one that turns a record of your misses into a plan for fixing them.
Related notes
Liked this? Get the free SOP Writing Cheat Sheet.
The 6-step SOP format on one page. Free.