Why track production plan vs actual hourly instead of per shift?

Because lost production can't be recovered in retrospect. An hour the line ran slow is gone, so the only time to respond is while the shift is still running. Hourly tracking makes the gap visible early and localizes the cause to specific hours, turning a vague shift shortfall into an investigable event.

How do you set the hourly production target?

Derive it from takt time (available time divided by customer demand) or from the line's demonstrated best rate, then hold it flat across the shift. Account for planned breaks openly by lowering that hour's target or excluding the break from the requirement, on the board, never by quietly moving the line.

What should a plan vs actual board include?

Hourly plan and actual, cumulative plan and actual, the signed gap between them, a reason code for every short hour, and a brief comment field. The reason code is essential: it turns a column of red hours into a Pareto of causes that feeds downtime and loss analysis.

What do you do when the actual falls behind plan?

Respond the same shift, guided by the reason code already attached to the short hours. Fix the cause rather than pressuring the line to sprint, which usually trades a production miss for a quality miss. Then feed the reason codes forward so recurring causes get eliminated, not just recorded.

Is plan vs actual the same as adherence to plan?

They're related but different. Plan vs actual is the hour-by-hour, in-shift comparison. Adherence to plan is the period-level summary of how reliably the operation hit what it committed to. The hourly board feeds the adherence number: consistent hourly misses show up as poor adherence over the week or month.

Plan vs Actual Production Tracking

Q: What is plan vs actual production tracking?

It's a running comparison of what a line should have produced against what it actually produced, updated hour by hour and posted at the line. The cumulative gap between planned and actual output is the signal; tracked hourly, it becomes something the crew can act on mid-shift rather than review the next day.

Q: How does plan vs actual relate to OEE?

They're the same reality at different resolutions. Plan vs actual is the live hourly view of pace; OEE is the diagnostic view of how productively planned time was used, split into Availability, Performance, and Quality. An hourly board with reason codes decomposes into the same losses OEE measures.

Building an hour-by-hour plan-vs-actual board so the gap gets caught mid-shift, while the crew can still recover it, not discovered the next morning.

Plan vs actual production tracking compares what a line should have produced by a given point in the shift against what it actually produced, updated hour by hour and posted at the line. Done right, a widening gap becomes a signal the crew can act on this shift, not a variance discovered the next morning, when the shift that lost it is already gone.

Most plants track plan vs actual once a day, at shift end, in a spreadsheet nobody sees until the meeting. By then the information is an autopsy: you can explain the miss but not recover it. The whole value of the technique is timing. An hourly board turns the same comparison into a live scoreboard the crew reads between passes, so a slow start gets answered at 9 a.m. instead of mourned at 6 a.m. the next day. This guide covers what goes on the board, how to set the “plan” half from takt, and how to make every miss carry a reason. It pairs naturally with OEE and adherence to plan.

What is plan vs actual production tracking?

Plan vs actual production tracking is a running comparison of cumulative planned output against cumulative actual output across a shift. The plan is what the line should have made by each hour if it ran to rate; the actual is the counter. The gap between the two cumulative numbers is the story, and because it accumulates, a small early miss that never gets recovered grows into a visible shortfall long before shift end.

The international KPI standard frames the same idea as comparing actual production quantity against planned production quantity. What makes the shop-floor version powerful is not the arithmetic but the cadence and the placement: hourly, at the line, where the people who can change the outcome will see it. A monthly plan-vs-actual is a report. An hourly one is a tool.

The board's whole purpose: the shaded gap is legible by mid-shift. Caught here, a slow start can still be worked; caught tomorrow, it's just a number.

Why track it hour by hour instead of per shift?

Because a per-shift number arrives too late to change anything. Production loss is not recoverable in retrospect, an hour the line ran slow is gone. The only window in which a miss can be answered is while the shift is still running, and that requires seeing the gap open in near-real time, not totaling it at the end.

Hourly cadence also localizes the cause. A single shift-end shortfall of 70 units tells you nothing about when or why. The same 70 units spread across an hourly board points straight at the two hours that bled, the slow start after a changeover, the jam-plagued hour before lunch, which turns a vague “we were down 11%” into a specific, investigable event. That specificity is what connects the board to downtime and to the six big losses. A shift total closes the loop once a day; an hourly board closes it eight times a shift.

What goes on a plan vs actual board?

Keep it to what a crew can read in five seconds between passes. A working board has six things and no more:

Hourly plan (target) the units the line should make each hour at rate.
Hourly actual the counter for that hour.
Cumulative plan and cumulative actual the running totals whose gap is the real signal.
The gap cumulative actual minus cumulative plan, shown with a sign so ahead/behind is instant.
A reason code for every short hour a one- or two-word cause from a fixed short list.
A short comment field room for the detail a code can't hold.

The reason code is the part most boards omit and the part that makes the board pay. A column of red hours with no causes is a complaint; the same column with changeover, jam, material-out, jam beside it is a Pareto in the making. Resist adding more, efficiency percentages, OEE, quality counts, onto the hourly board. Those belong on the shift review. The hourly board has one job: make the gap and its cause visible now.

How do you set the hourly plan?

Set it from takt or demonstrated rate, not from a hope. The hourly plan is simply the rate the line must hold to meet the shift's requirement, and there are two honest ways to derive it. The first is takt time: available time divided by customer demand gives the pace the line must run to satisfy orders, and the hourly plan is that pace expressed per hour. The second is demonstrated best rate: the ideal cycle time the line actually achieves on a good run, which is also what feeds the Performance factor of OEE.

Two disciplines keep the plan honest. First, hold the hourly target flat across the shift unless there is a real reason not to, a “ramp” that conveniently lowers the early-hour targets is just the no-demand game wearing work clothes. Second, decide up front how planned events land: if there is a 30-minute break in hour 5, either lower that hour's target explicitly or exclude the break from the shift requirement, but do it visibly, on the board, not by quietly moving the line. A plan the crew doesn't believe is a plan they will ignore, which is why the target has to be derived, defensible, and stable, the same logic behind honest production scheduling.

How do you build a plan vs actual board step by step?

Start small, make it visible, and wire the misses to reasons. The sequence:

Set the shift requirement and derive the hourly target. From takt or demonstrated rate, compute the flat units-per-hour the line must hold, and account for planned breaks openly.
Put the board where the crew works. A whiteboard at the line beats a spreadsheet in an office. It must be glanceable from the operator's normal position.
Log actuals every hour, from the counter. Machine count where possible; a tally where not. The point is a real number on the hour, every hour, not a reconstruction at break.
Show the cumulative gap with a sign. Running plan, running actual, and the difference, so “behind by 40” is unmistakable without mental math.
Attach a reason code to every short hour. From a fixed short list that maps to your downtime categories. No blank red hours, a miss without a reason is a miss you can't fix.
Trigger a response at a set threshold. Define the gap that summons the supervisor or team lead, and act on it the same shift, which is the entire reason the board exists.

What do you do when the gap opens?

Respond while the shift is live, guided by the reason code. The board's job ends at “behind by 40, cause: material-out”; the crew's job begins there. A gap driven by material-out calls for a different move than one driven by slow cycles or repeated jams, and because the code is already attached, the response can be specific and immediate instead of a general exhortation to go faster.

Two habits keep the response honest. Fix the cause, not the number: pressuring the line to sprint and recover units usually trades a plan miss for a quality miss, and first-pass yield pays for the sprint later. And feed the codes forward, today's reason column is next week's loss Pareto, which is how an hourly board stops being a daily ritual and becomes an improvement engine. The board catches the gap; the reason codes tell you which recurring problem to actually kill.

The reason codes are the payoff. Summed over a week, the same column that flagged each short hour becomes a Pareto that names the single change worth making first.

What do the standards and data say?

Two anchors put the practice in context, stated with their provenance:

The manufacturing-KPI standard ISO 22400-2:2014 defines a formal production KPI comparing actual production quantity against planned production quantity the standardized version of exactly what a plan-vs-actual board shows, just computed per period instead of per hour. The hourly board is that KPI made visible while the shift is still live. See the ISO 22400-2 catalog entry.
For macro context, the U.S. Federal Reserve's G.17 industrial production and capacity utilization release reports manufacturing capacity utilization in the mid-70s percent range in recent releases, a reminder that even in aggregate, plants run well under plan, and that the gap between intended and actual output is the norm, not the exception. See the current G.17 release.

How does plan vs actual relate to OEE and adherence to plan?

They are three views of the same reality at different resolutions. Plan vs actual is the live, hourly view: are we keeping pace right now? OEE is the diagnostic view: of the time we planned to run, how much was truly productive, split into Availability, Performance, and Quality? Adherence to plan is the summary view: over the period, how reliably did we hit what we said we would? An hourly board that carries reason codes feeds both of the others, its misses decompose into the same losses OEE measures and the same variances adherence summarizes.

The connective tissue is data capture. A board rekeyed from memory at break drifts, and a drifting board erodes the crew's trust in the plan. Boards that pull actuals from the machine and let operators tag misses at the station stay honest, the approach behind computing production numbers from real signals rather than end-of-shift estimates, the way Harmony turns line data into live, searchable records (see the platform). For a real-floor example of the shift from paper to real-time, read how one specialty manufacturer replaced paper production logging with real-time visibility and cross-check the effectiveness side of the story in the OEE calculator. For how this rolls into the broader scoreboard, see manufacturing KPIs.