Free Downtime Tracker Excel Template
Log every minute a machine is down and which reason caused it. Surface the top 5 causes of lost capacity — usually 80% of total downtime sits in 4 reasons.
What you get
A working downtime log that captures start time, end time, machine, reason code, and operator. Calculates MTBF and MTTR automatically. Use it for 90 days and the patterns are obvious.
Free 30-day trial · No credit card required · Used by manufacturers since 1991
Why manufacturers still use Excel for this
Every shop knows machines go down. Few shops can tell you, with data, which 4 reasons cause 80% of total downtime. That gap costs more capacity than any other single thing you can fix.
A downtime tracker exists to convert anecdotes ("the press kept jamming on Tuesday") into a Pareto chart ("press jams account for 38% of total downtime — fix the feed roller and we recover 18 hours a month"). The format does not need to be fancy. The discipline of capturing every event does.
This template gives you the smallest workable structure: timestamp in, timestamp out, machine, reason code, operator, and notes. After 90 days of daily logs, the analysis tabs surface the real causes. Then RMX or EDGEBI can give you the live version pulled directly from machine signals.
What's inside the template
Downtime event log
One row per downtime event with start time, end time, duration, machine, reason code, operator, and free-text notes.
Reason code dictionary
A standardized list of downtime reasons (setup, breakdown, material wait, no operator, planned PM, etc.) so the data aggregates cleanly.
MTBF calculator
Mean Time Between Failures by machine — formula-driven from the event log.
MTTR calculator
Mean Time To Repair by machine and by reason code.
Pareto chart of reasons
Automatic top-10 chart showing which reason codes account for the most cumulative downtime hours.
Availability % rollup
Scheduled hours minus downtime hours, by machine and by shift, expressed as a percentage.
How to use this template
A practical walkthrough, from the sample data to a plan built on your own numbers.
- 1
Define your reason codes upfront
Before logging anything, agree on 15–25 standard reason codes. Free-text reasons make aggregation impossible. The template ships with a starter list — edit to fit your shop.
- 2
Log every event of >5 minutes
Anything shorter is noise. The threshold matters — if operators log 30-second pauses, the data drowns.
- 3
Review weekly, not daily
Daily noise hides patterns. Weekly Pareto charts surface the real culprits. Set a 30-minute weekly review meeting.
- 4
Pick one reason per quarter
Do not try to fix all 25 reasons. Pick the #1 from the Pareto, fix it, then move to the next. Most shops recover 15–25% of lost capacity in the first year.
When you outgrow this template
Excel is the right answer for early-stage planning, until it isn't. These are the warning signs that you need a real production scheduling tool.
If three or more of these apply, you have outgrown spreadsheet planning. EDGEBIC, the current generation of RMDB, is User Solutions' finite capacity scheduling and production planning software. It imports the same orders, routings, work centers and stock from Excel, CSV or your ERP, schedules them against real machine, labor and material limits, and shows the result on a drag-and-drop Gantt chart. It is a one-time license: EDGEBIC APS is $25,000, and EDGEBIC Complete, which adds MRP, inventory and purchasing, is $35,000.
See EDGEBICNot ready to decide? Read what actually changes when you move off the spreadsheet, or see the published price before you talk to anyone.
Frequently asked questions
What downtime reason codes should I use?+
Start with 15–25 codes covering setup/changeover, mechanical breakdown, electrical fault, no material, no operator, planned PM, quality hold, tool wear, and miscellaneous. Adjust based on your equipment. Avoid "Other" — it becomes a dumping ground.
How do I calculate MTBF and MTTR?+
MTBF (Mean Time Between Failures) = total uptime hours ÷ number of failures. MTTR (Mean Time To Repair) = total downtime hours ÷ number of failures. The template calculates both automatically from your event log.
How long should I track before drawing conclusions?+
90 days minimum. Shorter windows over-weight one-off events. After 90 days the top 5 reasons are usually stable — those are the ones worth fixing.
Should I track planned downtime separately from unplanned?+
Yes — planned PM should not be in the same bucket as breakdowns. The template separates planned and unplanned in the availability rollup. You manage them differently: planned gets optimized, unplanned gets eliminated.
Start with the spreadsheet. Move to EDGEBIC when it breaks.
The template handles the math for a small plan. EDGEBIC is what manufacturers move to when orders, routings and capacity change faster than a spreadsheet can follow: published one-time pricing, and implementation measured in days.