Shop floor reporting records what happened at the line, such as time, counts, scrap and stops per order, and sends it to the people who decide and to the systems that plan. A working setup has three layers: a shift handover, a daily review and a weekly trend. Every report must balance: run time plus stops equals scheduled time, and good plus rejects equals total.
Two jobs under one name
People use "shop floor reporting" for two different things. Sort out which one hurts before you change any forms.
- Booking production: confirming quantities, scrap, time and material per order, so that planning, stock and costing are correct. This usually lands in the ERP.
- Reporting performance: telling a supervisor or manager how the line ran and why, so that they can act. This is where OEE, stops and causes belong.
The two share raw data but need different timing. A booking can wait until the order closes, while a performance report loses value by the hour.
Which report does which job
Each report should exist because someone decides something with it. If you cannot name the decision, remove the report.
| Report | Reader | Holds | Decision |
|---|---|---|---|
| Shift handover | Next shift lead | Output against plan, open problems, line state | What to watch or fix first |
| Daily review | Supervisor and team | OEE, top three stops in minutes, scrap | Who does what today |
| Weekly trend | Production manager | OEE per line, largest losses, open actions | Where to put people and money |
| Order booking | Planning and finance | Good units, scrap, hours, material per order | Stock, cost, next order |
The daily review is built for the daily production meeting. The weekly page has its own structure in the plant manager KPI list.
A one-page shift report
Most shift reports are too long because they try to serve everyone. Fill in the fields below and stop there.
- Header: line, date, shift, lead's name, product and order.
- Time: scheduled minutes, total stop minutes, run minutes.
- Count: total units, rejects, good units, plan.
- Top three stops: cause and minutes each, with the stop time left over shown as "other".
- Handover: what is broken, what is on hold, what the next shift should do first.
Keep the stop details in a separate log, such as the downtime log template. For a page to send around, use the downtime report template or the OEE report template.
Worked example: make the report balance
A report that does not add up cannot be trusted, and a meeting will spend its time arguing about it. So build the check into the form.
Example: a line has 480 scheduled minutes and an ideal rate of 40 units a minute. The sheet says 45 stop minutes, 14,400 total units and 300 rejects.
The check is one sum: 480 - 45 = 435 run minutes, and 14,400 / 40 = 360 minutes of ideal time. That leaves 75 minutes that the sheet calls running but the count does not support.
Those minutes are short stops that nobody logged, or slow running. OEE here is 14,100 / 40 / 480 = 73.4%, and the report should say out loud that speed and short stops are its largest loss.
The second check: booking against reality
Compare what the report says with what the ERP says, at least weekly for a month. Gaps between the two often show a routine problem and not a typing error.
Example: the line counter shows 14,400 and the order booking shows 14,250 good plus 150 scrap, which matches at 14,400. Our sheet above says 300 rejects, so 150 rejects were booked as good and stock is overstated by 150 units.
Check for the usual sources: rework booked as good, partial pallets booked at full quantity, or a shift's scrap booked the next day. The good count guide explains what should and should not count.
How to shorten the time from event to report
The clock that matters is the one from the stop until a person who can act knows about it. Every hand-off in the chain adds to it.
A number written on paper and typed in later gets entered twice and can go wrong twice. Enter it once.
The cause is clearest during the stop, and a pick list beats a free-text note written at shift end.
A sensor or PLC signal saves people from timing stops. They still supply the cause.
Stop sending one for a week. If no one asks, drop it for good.
The page on shop floor data collection compares paper, tablets, sensors and PLC links, one data type at a time. Choose by what you are missing, not by what looks modern.
Habits that waste the report
- Reports that describe and never decide. End each one with the action, the owner and the date.
- Averages without minutes. A week at 71% hides which line and which stop caused it, so show minutes.
- A big "other" row. If it exceeds the top real cause, the report points at nothing. See unknown downtime.
- Different formulas per site. Write down how breaks, changeovers and rework count, then keep to it.
- Everything is emailed. A report that nobody reads still costs someone an hour to prepare.
- Editing a bad number. Log the correction with a note, since a silent fix hides the routine that caused it.
Test last week's sheets
Take last week's shift reports for one line and do the two sums above on each. How many balance, and how large is the part left unexplained?
That answer tells you whether to fix the form, the routine or the source of the data. If the numbers are sound but arrive too late, read about shop floor visibility next.
Reports balance more easily when time and counts come from the machine. Fabrico takes stops, speed and counts live from PLCs or IoT sensors, and operators tag the cause at the line, which gives OEE per line and shift without retyping sheets. See how Fabrico records stops.
What people ask next
What should a shop floor report include?
At minimum it needs the line, date, shift, order, scheduled and stop minutes, total and good units, the top stops by minutes and any open problems. Add only what someone will act on. The OEE report template gives a ready format.
How often should production be reported?
Stops and output should be visible at least hourly on the floor, with a shift handover and a daily review on top. Managers usually need a weekly trend. Orders are booked when they close, or more often if stock depends on it.
What is the difference between shop floor reporting and shop floor control?
Reporting says what happened. Control uses that information to release, sequence and change work on the floor. An MES commonly does both, while a paper sheet only does the first.
Why does my report not match the ERP?
Common reasons are rework booked as good, scrap booked a day late, and partial pallets booked at full quantity. Compare one order line by line with the machine counter to find out which it is. The good count guide helps set the rule.
Can shop floor reporting be automated without a full MES?
Time and count data can come from sensors or PLC signals with no large system, but people still supply causes and many quality decisions. See OEE data collection methods for the options and limits.
Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.