Machine Downtime Log Template
You cannot reduce downtime you have not recorded. This template gives operators one simple page for logging every stop with a start, end, machine, loss category and note, and it maps the categories to the six big losses so the data goes straight into an OEE analysis.
Fill in
Machine Downtime Log Template
Machine Downtime Log
Plant: Acme Precision Ltd, Plant 2 Line or work center: Packaging Line 3 Period: 2026-10-19 to 2026-10-23 Log owner: Shift supervisor Log every stop of 5 minutes or longer. Shorter stops are counted as minor stops by the line counter or tally.
What is planned time
Breaks, scheduled maintenance, and no-demand periods are planned and are not logged here. Everything else is logged.
Downtime events
| Date | Start | End | Minutes | Machine | Loss category | Reason | Root cause or note | Logged by |
|---|---|---|---|---|---|---|---|---|
Loss category guide
| Category | Use for | Six big losses group |
|---|---|---|
| Breakdown | Equipment fault needing repair | Equipment failure |
| Changeover | Product, tooling or size change | Setup and adjustment |
| Adjustment | Tuning after setup or drift | Setup and adjustment |
| Material wait | Starved of parts or packaging | Idling and minor stops |
| Blocked | Downstream full or not running | Idling and minor stops |
| Quality hold | Stopped to inspect or contain | Process defects |
| Startup | Warm-up and stabilizing | Startup rejects |
| Other | Anything else, explain in note | As applicable |
Weekly review
Top three causes by minutes: 1. 2. 3.
Actions agreed, owner and due date:
Review sign off
Use consistent reason words so entries can be grouped. Add machine specific reasons once your top causes are known. Total the minutes per category each week and rank them. If you use an MES or an ERP with downtime codes, align this list with those codes first.
Replace the paper log with ERP downtime data
Optional: we can check whether your ERP or MES downtime codes are clean enough to feed an automated report.
Optional. The tool and every export work without this. No spam.
How to use the log
Print the log or export it to Excel, and keep one per line or work center. Set the minimum stop length that must be logged, commonly five minutes, so operators are not drowning in tiny entries. When a stop occurs, the operator or team lead writes the start, end, machine, a loss category from the guide and a short reason. At the end of the week, total minutes by category and by reason, rank them and agree actions. The review block at the end of the template gives a place to record the top three causes and who owns the fix.
Choosing loss categories
Keep the category list short, around eight entries, so operators can choose without thinking. The guide in the template maps each category to the six big losses used in OEE: equipment failure, setup and adjustment, idling and minor stops, reduced speed, process defects and startup rejects. Underneath each category, add a handful of specific reasons that match your equipment, such as feeder jam or label roll change. Long dropdowns of fifty reasons lead to everything being logged as other, which is the worst possible outcome for analysis.
- Eight categories or fewer for operators.
- Specific reasons under each category, added once top causes show.
- One owner for the list, reviewed quarterly.
Using the data
A week of clean entries is enough to build a Pareto chart. Sum minutes by reason, sort from largest to smallest and look at the first three bars. Those usually account for most of the lost time. Compare the list with the six big losses worksheet to see how much of the planned time they represent. The same log also feeds MTBF and MTTR figures for any asset that shows repeated breakdowns, since each breakdown entry gives a failure count and a repair duration.
Common mistakes
Stops logged at the end of the shift from memory are always rounded and incomplete, so ask for entries when events happen. Too many reason codes, or codes that overlap, make the Pareto meaningless. Entries of waiting for maintenance with no machine named cannot be acted on. Finally, a log nobody reviews dies within a month. Put a ten minute review on the weekly calendar and show operators what changed because of their entries.
Frequently Asked Questions
What should be included in a downtime log?
Date, start and end time, duration, machine, loss category, a short reason, a note on the root cause or action and who logged it. Keep it to one page so operators will actually use it.
How long must a stop be before I log it?
Many plants log stops of five minutes or more and count shorter ones as minor stops with a tally. Pick a threshold that fits your cycle times and stick to it, otherwise data from different shifts cannot be compared.
How do I link the log to OEE?
Sum logged minutes by loss category and subtract them from planned production time to get operating time and availability. Map each category to the six big losses so the same data supports a loss breakdown.
Should operators or maintenance fill it in?
Operators or team leads should log the stop when it happens, and maintenance should add the root cause after the repair. Splitting the entry this way gives accurate times and better causes.
If your ERP or MES already captures downtime codes, Netray can help build a read-only report that replaces the paper log with live data on your own systems. The template works without it.
Related Tools
Six Big Losses OEE Worksheet
An editable worksheet that records the six big losses per line and shift in minutes, computes OEE per row and totals each loss as a share of planned time.
Maintenance & ReliabilityMTBF and MTTR Worksheet
Track failures, operating hours and repair hours per asset and calculate MTBF, MTTR and availability for each row and for the fleet.
MES & Shop FloorShift Production Report Template
A fill-in shift report covering output versus target, scrap, downtime, safety, staffing and handover notes, exported as a ready to print document.
MES & Shop FloorPlex Downtime Reason Log and OEE Worksheet
Editable shift log of planned time, downtime, parts made and scrap that computes availability, performance, quality and OEE per workcenter.
Discrete ManufacturingManufacturing Downtime Cost Calculator
Combine lost contribution margin, idle labor, and absorbed overhead into a defensible monthly and annual downtime cost - with recovery effects modeled.
More MES & Shop Floor tools
See all- Oracle Fusion OEE Work Center Calculator
- Infor VISUAL Shop Labor Ticket Log Worksheet
- VISUAL Shop Load Versus Capacity Calculator
- VISUAL Shop Resource Capacity and Load Calculator
- IFS Shop Order Status and Lifecycle Reference
- Plex Smart Manufacturing Data Source Request Template
- Plex Production Scheduling Checklist
- Plex Go-Live Readiness Sign-Off Template
- OEE Calculator for Plex and MES Data