Downtime Log Template for Excel (Free) — Track Every Stoppage

Downtime Log Template for Excel (Free)

Every reliability metric your operation might ever report — MTBF, MTTR, availability, OEE — is built from one humble input: an honest record of when things stopped and when they started again. No downtime log, no trustworthy numbers. It's that direct.

This template is the minimum structure that makes downtime data usable. Three sheets:

Sheet 1: The Downtime Log

One row per stoppage. The columns that earn their place:

• Stop time and restart time — actual clock times, not estimates made on Friday. The gap between "it stopped around 10" and "stopped 10:07, restarted 12:41" is the gap between a log and folklore.
• Planned / unplanned — the single most important split. Planned maintenance isn't a failure, and mixing the two quietly wrecks your MTBF.
• Reason code — from a fixed list (sheet 2), not free text.
• Work order reference — connects the stoppage to the repair record, parts used, and labour.

Sheet 2: Reason Codes

Free-text reasons produce twelve spellings of "bearing failure" and zero usable analysis. The template ships with 13 codes across five categories — mechanical, electrical, operational, planned, external — and the right number for your operation is somewhere between 10 and 15. Fewer and everything lands in "other"; more and technicians stop reading the list.

The external category matters more than teams expect: waiting on parts and waiting on contractor are downtime causes that no amount of maintenance skill fixes — they're parts inventory and planning problems, and they only become visible when they get their own codes.

Sheet 3: Monthly Summary

Roll the log up per asset each month: total downtime hours, unplanned event count, top reason code. Two of those numbers are the direct inputs for the MTBF calculator and MTTR calculator — run them quarterly and you have a reliability trend for every critical asset, from a spreadsheet.

The summary is also where patterns surface. Three months of MECH-01 against the same pump is a bearing specification conversation. A rising EXT-01 count is a stores conversation. The log gives you the argument; the summary makes it visible.

The Logging Discipline That Makes It Work

Templates don't fail on structure — they fail on habit. Three rules:

1. Log at the event, not at the end of the week. Memory-based logging systematically underestimates both frequency and duration. If the log lives on a shared drive nobody opens on the shop floor, it will be fiction by March.
2. Log the small stops too. Ten 6-minute jams a shift is an hour a day — invisible in memory, obvious in a log, and usually cheaper to fix than the big dramatic failures.
3. Never punish what the log reveals. The moment downtime numbers get used against operators, the numbers get creative. The log measures the equipment and the system around it, not the people.

When the Spreadsheet Stops Being Enough

Same story as every maintenance spreadsheet: it works until the moment of logging moves away from the person holding the file. Multiple lines, multiple shifts, technicians on mobile — that's when stoppages start getting logged from memory or not at all. A CMMS logs the stop from the floor, stamps the times, ties the work order automatically, and turns the monthly summary into a live dashboard. Until then: this template, kept honestly, beats most systems kept badly.

More Free Templates

• CMMS Excel Template — the four-sheet hub: assets, work orders, PM schedule, and log
• Maintenance Log Template — the audit trail of work done (the repair side of this log)
• Parts Inventory Template — fix the "waiting on parts" rows
• Preventive Maintenance Schedule Template — reduce the unplanned rows altogether