Hour-by-hour board explained

An hour-by-hour board is a sheet at the end of a line where the team leader writes the planned and actual output every hour, with the reason for any miss. It shows a problem in the hour it happens, while the team can still do something about it.

Matt Savas · Reviewed October 2026 · About 6 minutes

What an hour-by-hour board is

The board has one row for each hour of the shift. Each row holds the plan and the actual for that hour, the running totals for the shift, the cause of any miss, what the team did about it, and a signature. It is also called a production analysis board.

The board works alongside andon. An andon call brings a team leader to a station the moment something goes wrong. The board keeps a record of each problem across the shift, so the ones that come back can be found and worked on.

Why record output every hour

Many plants find out how a shift went from a report the next morning. By then the shift is over, and nobody remembers why output was low. The causes in the report are guesses.

With an hourly count, the team leader sees a miss within the hour. They can ask what happened while the people who saw it are still at the line. They can also act before the problem costs the rest of the shift.

How to read the board

A board has five columns: the time, the plan and actual for the hour, the running totals, the cause of each miss with what the team did about it, and a signature. The cause column matters most. Every hour that falls short gets a written reason.

The five columns of the board
Select a column to see what goes in it.
Line
Final Assembly #7
Team leader
Benny Li
Shift
A, 16 operators
Shift plan
690 pieces
Takt time
40 seconds
Plan per hour
90 pieces
06:00–07:0090 / 9090 / 90–B. Li
07:00–08:0090 / 88180 / 178Leak tester timeoutB. Li
08:00–09:0090 / 90270 / 268–B. Li
09:10–10:1090 / 85360 / 353Scratch on front coverB. Li
10:10–11:1090 / 85450 / 438Scratch on front cover againB. Li
11:40–12:4090 / 90540 / 528–B. Li
12:40–13:4090 / 86630 / 614Bent connector pin from the supplierB. Li
13:50–14:3060 / 56690 / 670Bent connector pin from the supplier againB. Li
1. Time

One row for each hour of the shift. The board fills from top to bottom, so a problem shows up in the hour it happens.

How to run the board

  1. 1
    Work out the plan for each hour
    Divide the working seconds in the hour by takt time. Take planned breaks out first. With a 40-second takt, a full hour plans 90 pieces. A 40-minute period plans 2,400 ÷ 40 = 60.
  2. 2
    Put the board at the end of the line
    Hang it where finished pieces are counted, in sight of the team. A board in an office does not get read during the shift.
  3. 3
    Write the actual at the end of every hour
    Count the pieces that came off the line and add them to the shift total. Do it on the hour, not at the end of the shift from memory.
  4. 4
    Write a cause and a response for every miss
    Name what happened: "scratch on front cover", not "quality". Then write what the team did. Either they fixed it at the line, or they contained it and sent it to problem-solving.
  5. 5
    Sign each hour
    The team leader initials every row. A supervisor signs at breaks and at the end of the shift.
  6. 6
    Add up the causes every day
    Total the pieces lost to each cause and sort them, largest first. The top cause goes to problem-solving.

The free hour-by-hour board tool works out the plan for each hour from your takt time, adds up the causes for you and prints a board for the wall.

A shift on Final Assembly #7

Final Assembly #7 runs from 06:00 to 14:30 with three breaks. Takt time is 40 seconds, so a full hour plans 90 pieces. The last period is 40 minutes long and plans 60. The shift plan is 690.

Three problems hit the line. The team fixes one on the spot. The other two can only be contained that day.

Hour-by-hour board, shift A
Play the shift, or step through it one hour at a time.
Line
Final Assembly #7
Takt time
40 seconds
Plan per hour
90 pieces
Shift plan
690 pieces
Clock
06:00
TimeHour plan / actualShift plan / actual
06:00–07:00––
07:00–08:00––
08:00–09:00––
09:10–10:10––
10:10–11:10––
11:40–12:40––
12:40–13:40––
13:50–14:30––
Pieces behind plan, shift so far
0
06
0
07
0
08
0
09
0
10
0
11
0
12
0
13
Ready

Press Play to run the shift, or Step to go one hour at a time.

Fixed at the line The cause is gone.Contained Bad parts are stopped, but the cause is still there.

What the shift shows

The leak tester cost 2 pieces once. The team reset it, and it did not come back. The cover scratch and the bent pin were only contained, so both came back later in the shift. Between them they cost 18 pieces.

The shift column shows that the team never made up the lost pieces. A pace that runs to plan every hour cannot recover a loss. A contained problem keeps costing output until someone finds its cause.

Which losses get a full investigation

One shift shows three causes. A week of them shows which ones matter. Add up the pieces lost to each cause over five shifts and sort them, largest first. This is a Pareto chart. The free Pareto chart tool sorts them for you.

The top cause is one that a quick fix has not stopped. It is the one worth a full root cause investigation.

Losses on Final Assembly #7 by cause
Five shifts of causes from the board, added up.
Pieces lost this week
Scratch on front cover
47
Bent connector pin
31
Changeover overrun
9
Waiting for material
6
Leak tester timeout
2

How the board fits into daily management

The team in the example used the five whys to find the cause of the scratches. A larger problem may need an A3. Many plants run the review at three levels, each at its own pace.

  • Every hour, at the board. The team leader records plan and actual. They fix what can be fixed at once, contain what cannot, and write down the cause.
  • Every day, at the Pareto. The supervisor reviews the causes added up so far and gives the team the top one that keeps coming back.
  • Every week, in problem-solving. The team finds the root cause, changes the standard, and checks that the loss gets smaller on the board.

Common mistakes

  • Planning a full hour that has a break in it. A 10-minute break leaves time for 75 pieces, not 90. The team misses every time and stops trusting the board.
  • Writing vague causes. Nobody can act on "quality" or "downtime". Write what happened, at which station, to which part.
  • Filling it in at the end of the shift. Causes written from memory are vague, and it is too late to respond.
  • Using the board to blame people. If a miss leads to blame, the counts get padded and the causes stop being written down.
  • Never adding up the causes. A board that is wiped clean each shift only catches quick problems. The ones that come back show up only when a week of causes is added up.

Frequently asked questions

What is an hour-by-hour board?
It is a board at the end of a line or cell. Every hour, the team leader writes the planned and actual output for that hour and for the shift so far, the cause of any miss, and what was done about it. It is also called a production analysis board. Its job is to show a problem in the hour it happens, while there is still time to act.
How do you work out the hourly target?
Divide the working seconds in the hour by takt time. With a 40-second takt and a full 3,600-second hour, the plan is 3,600 ÷ 40 = 90 pieces. Take planned breaks out first. An hour with a 10-minute break has 3,000 working seconds, so it plans 75.
What is the difference between an hour-by-hour board and an andon?
An andon call gets help to a station the moment a problem happens. The hour-by-hour board keeps a record of plan, actual and causes across the shift. Andon deals with the problem now. The board shows which problems keep coming back, so the biggest ones can be worked on.
What do you write in the problem column?
The specific reason the hour missed, such as "scratch on front cover" or "leak tester timeout". A category like "quality" or "downtime" is too vague to act on. Then write the response: fixed at the line, or contained and sent to problem-solving.
How does the board connect to problem-solving?
Add up a week of causes and sort them into a Pareto chart. Problems fixed at the line stop showing up. The ones a quick fix could not stop rise to the top. The top cause gets a root cause investigation, such as the five whys or an A3, and the standard changes. Many plants review the board every hour, the Pareto every day and problem-solving every week.