An hour-by-hour production board is a board at the line with one row per hour: target, actual, gap and reason. The team fills it in every hour, so they see right away when they are behind and why. Set the target from the plan, not from top machine speed.
What the board is
An hour-by-hour production board is a whiteboard or screen at the line with one row for each hour of the shift. Each row shows the target, what was made, the gap and the reason for the gap.
It is the simplest form of short interval control. The team sees within an hour that they are behind, and the reason is written next to the number while people still remember it.
The columns
| Column | What goes in it | Who fills it |
|---|---|---|
| Hour | Clock time of the block | Printed on the board |
| Target | Planned good units for the hour | Supervisor, at shift start |
| Actual | Good units made in the hour | Operator or team lead |
| Gap | Actual minus target, and a running total | Operator or team lead |
| Reason | Why, in words or a code, only if the gap is negative | Operator or team lead |
| Action | What will change, with a name | Team lead or supervisor |
Six columns. Add nothing else until these are filled in every hour for a month.
How to set the hourly target
Do not use the top speed of the machine. It makes every row red, and the board gets ignored. Use the planned output, which includes the losses you expect.
Example: 30 cases/min × 60 min × 75% = 1,350 cases
For an hour with a break, use the scheduled minutes only. If a 30-minute break falls in the hour, the target is 30 × 30 × 0.75 = 675. A known changeover works the same way: take its minutes out of the scheduled time or set a lower target for that hour.
Where does the planned OEE come from? From your own history, not from a book. See how to set OEE targets. For the ideal rate, see ideal cycle time.
Worked example: a filled-in board
Example: a case packing line, shift 06:00 to 14:00, break at 10:00 to 10:30. Ideal rate 30 cases a minute, planned OEE 75%.
| Hour | Target | Actual | Gap | Running gap | Reason |
|---|---|---|---|---|---|
| 06:00 | 1,350 | 1,380 | +30 | +30 | |
| 07:00 | 1,350 | 1,290 | -60 | -30 | Carton misfeed |
| 08:00 | 1,350 | 1,350 | 0 | -30 | |
| 09:00 | 1,350 | 1,100 | -250 | -280 | Case erector jam, about 11 min |
| 10:00 | 675 | 690 | +15 | -265 | Half hour (break) |
| 11:00 | 1,350 | 1,360 | +10 | -255 | |
| 12:00 | 1,350 | 1,320 | -30 | -285 | Slow restart |
| 13:00 | 1,350 | 1,250 | -100 | -385 | Waiting for pallets, about 4 min |
| Total | 10,125 | 9,740 | -385 | 96.2% of target |
Example numbers, not real data. Target total: 7 × 1,350 + 675 = 10,125. Actual total: 9,740. Gap: -385.
The 09:00 row is the one the board is for. A gap of 250 cases is about 11 minutes at the target rate of 22.5 cases a minute (1,350 ÷ 60).
Someone writes "case erector jam" while the operator can still say what happened. At the end of the shift, that detail would be gone.
How to run it
- Fill it every hour, within five minutes. Not at the end of the shift.
- Use two pen colors. Black for on or above target, red for a gap. The pattern is clear from across the room.
- Keep a short list of reasons. Eight to ten codes is enough. No "other". See downtime reason codes.
- Put it where the whole team can see it. Next to the line, not in an office.
- Agree what happens at the second red. For example, the supervisor comes to the line.
- Carry the totals to the next meeting. The daily production meeting uses the board as its first slide.
Turn a week of boards into a Pareto
The board is also a data source. At the end of the week, add up the minutes by reason. Use the gap and the target rate to turn units into minutes.
| Reason | Times | Minutes | Share |
|---|---|---|---|
| Case erector jam | 9 | 98 | 37.7% |
| Carton misfeed | 14 | 70 | 26.9% |
| Waiting for pallets | 11 | 52 | 20.0% |
| Slow restart after stop | 8 | 40 | 15.4% |
| Total | 42 | 260 | 100% |
Example week, 10 shifts, hypothetical numbers. The first two reasons are 64.6% of the minutes.
Now the team knows where to look. The case erector is the first target, then the carton misfeed. This is a downtime Pareto built from a whiteboard. It does not need software.
Also look at how often each reason came up. Fourteen misfeeds that take five minutes each are a different problem from one long jam. Frequent short stops are the micro-stops that reports usually hide.
Special hours: start-up and changeovers
The first hour after a start or a changeover is slower than the rest. Do not hide that in the target.
Set a lower target for it, based on what the line really does, and write "start-up" as the reason. Then you can see whether the start-up gets shorter over time.
For changeovers, write the clock time at the start and at the first good unit. That one number is the base for measuring changeover time.
Paper or screen?
Start on paper. A whiteboard costs almost nothing and teaches the routine. The weak point is the count: if it is typed in by hand, it is only as good as the person counting.
A screen helps when counts come from the machine, because the actual column fills itself and nobody has to remember. If you want to stay low-cost, see free shift report software, and for paper sheets the downtime log template and the OEE tracking template.
Common mistakes
- The target is the ideal rate. The board is always red and everyone stops reading it.
- Filling it from memory at the end. The reasons become guesses.
- Too many columns. Each extra column makes the board slower to fill in.
- Reasons like "machine problem". That does not point to an action. Name the machine part or the event.
- No one reads it. If the supervisor does not look at it, the team stops filling it in.
- The board is used to compare crews. That pushes people to hide gaps. Use it to find causes.
What to do next
Build the board for one line this week. After two weeks, add up the reasons you wrote. The top three are your first improvement list. Take them to a gemba walk, and use the downtime Pareto to show the team where the minutes go.
A board is only as good as its count. Fabrico takes counts and stops live 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, so the actual column and the reason column are filled from the machine and the people who run it. See live OEE tracking per line and shift.
What people ask next
How do I set the target for each hour?
Multiply the ideal rate per minute by the scheduled minutes in the hour and by your planned OEE. For example, 30 cases a minute × 60 minutes × 75% = 1,350. Take out breaks and known changeovers first.
How often should the board be updated?
Once an hour, within five minutes of the end of the block. If the line is very fast, use 30 minutes. Do not wait until the end of the shift.
What if we run several products in one shift?
Set a separate target for each product run, using its own ideal rate, and write the product on the board. Split the row where the product changes. See changeover reduction for the time lost between runs.
Paper board or digital screen?
Paper is a good start and costs almost nothing. A screen is better when the counts come from the machine. The routine matters more than the tool.
How is the board different from the OEE number?
The board shows output against plan hour by hour, so you can react in the shift. OEE shows how well the scheduled time was used, as one number for the shift. See what is OEE.
Related guides: OEE on 12-Hour Shifts: Comparing Crews Fairly · OEE Dashboard Examples: 6 Layouts That Work · First Hour of Shift Losses: Why Output Drops · Takt Time Board: What to Show and How to Run It · Takt Time Board: What to Show and How to Run It