Production reporting: the daily figures a plant is actually run on

Report against a commitment, not against a hope

A production figure means nothing without the number it was measured against, and that reference has to be something the line agreed to rather than something a spreadsheet allocated. A shift target built from the schedule, the manning actually present and the known equipment condition can be defended and discussed. A target that assumes full manning and perfect running is dismissed by everyone who reads it, so the gap gets explained away rather than investigated. The discipline is settling the commitment before the shift starts, not deriving it afterwards from whatever would have made the result look reasonable.

Cadence and who is expected to act at each level

A working rhythm has short, standing reviews close to the work and progressively longer ones further from it. At the line, a brief handover-style review each shift covering output against plan, stoppages, quality holds and anything left unresolved for the next crew. Daily, a plant-level review where each area brings its gap and its cause, and where cross-area problems get an owner and a date. Weekly, the pattern rather than the incident: recurring losses, trends, actions overdue. Each level should end with named actions; a review that only shares information becomes optional and then stops happening.

Credibility dies quietly, one reconciliation at a time

Reported output drifts away from reality through small accommodations: units counted at the machine rather than after inspection, rejects booked next shift, a stoppage recorded as a changeover. Nobody intends deception and the numbers become useless anyway. Reconciliation is the antidote — reported good output against what stores actually received, reported consumption against physical stock movement, reported downtime against the shift length. Doing this periodically and visibly, and treating discrepancies as system faults to fix rather than as accusations, is what keeps a plant's figures worth arguing with.

A gap without a cause and an owner is just a complaint

The purpose of reporting a shortfall is to trigger a response, so the format should force three things: the size of the gap, the specific loss that caused most of it, and the person now responsible for the countermeasure. Vague attribution — machine issues, staffing, supplier quality — moves nothing. Naming the machine, the failure and the engineer does. Where the same cause appears repeatedly in the daily review, it has outgrown the daily cycle and needs an engineering or investment decision, which is the point at which reporting starts earning its cost rather than merely documenting decline.

What to stop reporting

Metric sprawl is the standard failure. Areas accumulate measures because someone once asked, and supervisors spend hours a week producing numbers that change nobody's behaviour. Test each one: who reads it, what decision does it inform, and what would happen if it stopped. Anything that fails all three should go. A small set of measures that people genuinely respond to beats a comprehensive dashboard that gets exported and filed. It also frees the supervisory time that gets spent compiling figures instead of standing where the work is happening.

Frequently asked questions

Should production reporting be done on paper or on a screen?

Whatever gets filled in accurately at the moment the event happens. Paper at the machine, transcribed once a shift, often produces better data than a terminal the operator has to walk to and log into. The choice that matters is not the medium but the distance between the event and the record. If the person recording has to remember, reconstruct or guess, the format is wrong regardless of how modern the interface looks.

How do we stop the daily review turning into a blame session?

Fix the agenda so it asks what stopped the process rather than who missed the target, and insist every gap ends with a countermeasure and an owner rather than an explanation. Chair it consistently and cut off retrospective argument about attribution — disputed causes get parked and checked with data, not settled by volume. Once people see problems they raise being acted on, reporting improves sharply, because honest numbers stop being personally expensive.

Who should present the numbers at the daily production meeting?

The person accountable for the area, not an analyst. Ownership of the figure and ownership of the response have to sit together, or the review becomes a performance for management with no consequence. A supervisor who has to stand up and explain their own shortfall learns their own losses fast. Analysts are useful for preparing the underlying data and for the weekly pattern review, but they should not be the voice explaining the shift.