How to use itOperators log every stop with a reason code. Each week, total downtime by reason and fix the top causes first.
Who logs itMachine operators or line leads
WhenEvery stop longer than your set minimum
Time neededUnder a minute per stop
ReviewWeekly totals by reason code with the team
Where the downtime log fits
Downtime that is not recorded cannot be reduced. A simple log with consistent reason codes is enough to start.
Separate planned stops, like changeovers, from unplanned breakdowns.
12 items. Fill it in on screen or print a copy.
Each stop
Weekly review
Example reason codes
Example reason codes
Field
What to write
MECH
Mechanical breakdown
MAT
Waiting for materials
CHG
Changeover
STAFF
No operator available
QUAL
Quality hold
Putting the downtime log to work
Agree reason codes.
Log every stop over a set length.
Review weekly.
Fix top causes.
Track trend.
A real-world example
A bottling plant’s log shows that 40% of unplanned downtime comes from waiting for materials. A line-side supply schedule cuts that reason by half in a month.
What the equipment downtime log protects you from
Repeating causes of lost production often go unnoticed until stops are written down the same way every time. A log with reason codes and responders turns scattered stops into a ranked list for maintenance and planning to work through.
A filled-in equipment downtime log
Machine
Oven 2 conveyor
Start and end
1:12 pm to 1:47 pm
Duration
35 minutes
Planned or unplanned
Unplanned
Reason code
E-02, drive belt slipping
Action taken
Belt tensioned, inspected for wear
Responder
Abdul, maintenance
Sample for Cascade Bakery in Tacoma, Washington. The reason code comes from a fixed list, so this stop is counted with every other belt problem in the weekly review, and duration is written out to save a step when minutes are totaled.
Equipment downtime log mistakes
Logging only the big breakdowns. Many short stops add up to more lost time than one long one, so set a low minimum, such as two minutes, and log everything above it.
Letting operators type their own reasons in free text. ‘Jam’, ‘jammed’ and ‘stuck’ end up as three causes, so agree a short code list and add an ‘other’ box for notes.
Leaving changeovers and cleaning off the log because they are planned. Record them as planned downtime so you can work on shortening them too.
Other versions of the equipment downtime log
Small shops with a few machinesStart with a paper sheet clipped to each machine and move to a spreadsheet once the codes settle.
Multi-line plantsUse the same reason codes on every line so you can compare lines and share fixes.
Quick winBefore the first week, ask operators to guess the top three causes. Comparing their guess with the data after a month starts a useful conversation.
Questions about the downtime log
What counts as downtime?
Any stop over the minimum you set.
Why reason codes?
They make totals comparable.
Should changeovers be logged?
Yes, as planned downtime.
Who logs?
The operator or lead.
Should waiting for maintenance be logged apart from repair time?
Yes, split the stop into time waiting for a responder and time spent fixing it. The split shows whether the answer is faster response, such as a technician on every shift, or better upkeep of the machine itself.
How do I turn the log into a percentage of available time?
Divide total downtime by planned production time for the same period and multiply by 100. For example, 90 minutes of downtime in a 480-minute shift is 18.75% of planned time.
Once the downtime log is in place, the next question is usually about shifts and hours. Book a demo to see how EZTime handles scheduling and time tracking.
