Downtime Log Template
A free downtime tracking log that ranks your losses for you. Record every stop by machine, reason and duration, and watch an automatic Pareto surface the causes that cost the most time. Export to CSV or print, no signup.
Your downtime log
One row per stop. Pick a loss category so the totals map to the six big losses, and the Pareto below updates as you type.
| Date / shift | Machine / line | Reason | Category | Minutes | |
|---|---|---|---|---|---|
| Total downtime | - | ||||
Top downtime reasons (Pareto)
Ranked by total lost minutes. Fix the top of this list first.
Want the editable spreadsheet version?
We'll email a spreadsheet copy of this downtime log plus the 2026 Manufacturing OEE Benchmark. One email, no spam.
No spam. Unsubscribe anytime.
Track it live, free, no spreadsheet to maintain.
The free OEE Tracker logs each shift and instantly shows your OEE, your downtime Pareto and how you compare to your industry, then keeps your history and builds your trend for you.
Open the free OEE TrackerThe stops you never log are usually the biggest loss.
A manual log catches the breakdowns and changeovers, but the short, frequent micro-stops slip through, and together they often cost more than the headline failures. Fabrico reads stops straight from PLC signals and uses computer vision to pin the true cause of each one, then closes the loop to an automatically routed work order. EU-built with EU data residency, ISO 27001 / 20000-1 / 9001 (supports audit-readiness).
Book a Fabrico demoHow to use this downtime log template
- Log every stop as it happens. A stop caught in the moment carries a real reason; one reconstructed at the end of the shift becomes "misc".
- Name the machine or line so you can later see which asset loses the most time.
- Write a specific reason ("infeed jam", "tool change", "waiting on material"), not just "down".
- Pick a loss category so your totals roll up to the six big losses: breakdown, setup and changeover, minor stop, reduced speed, startup or material.
- Enter the duration in minutes. The Pareto ranks reasons by total minutes so the biggest cause is obvious.
Downtime is the Availability side of OEE. To turn these minutes into a full OEE figure, use the OEE tracking template or the downtime cost calculator to put a number on the lost hours. For the loss framework, read the six big losses, and to chase a recurring cause see root cause analysis.
What should a downtime log capture?
Date or shift, machine, a specific reason, a loss category and the duration in minutes. Those five fields are enough to total downtime and rank the reasons, which is what this template does automatically.
How does the Pareto help?
It ranks reasons by total lost minutes, so the handful of causes behind most of your downtime rise to the top. Fixing the top reason first gives the biggest return for the effort.
Daily or per-event logging?
Per event is far more useful. A single daily total tells you that you lost time; an event log tells you where, why and how to stop it happening again.
Can I export it?
Yes. Download CSV opens the full log in any spreadsheet, and Print / PDF gives a clean shift report.
All OEE Lab tools · OEE tracking template · PM checklist template