A free machine downtime tracking spreadsheet (and when it stops working)

Every shop tracks downtime eventually. The only question is whether it gets tracked in a system, or on whatever was nearest when the machine stopped: a whiteboard, a notebook, the back of a packing slip. A spreadsheet is the honest first step up from that, and for a small shop it is a perfectly good place to start.

So here is a template you can use today, the rules that keep it alive past the second week, and the point where the spreadsheet itself starts costing you downtime. All three parts matter. Most downtime logs do not fail because the columns were wrong. They fail because nobody could fill them in fast enough.

The template

One row per stop. That is the whole design. The columns: date, machine, start time, end time, minutes down, what happened, a category (breakdown, changeover, no material, no operator, quality), who reported it, who fixed it, parts used, and notes. Nothing else. Every extra column you add is a reason for the row to never get written.

Download the free downtime log template (CSV, opens in Excel or Google Sheets)→

The category column is the one that pays. Minutes down tells you how much you lost. The category tells you where to aim. A month of rows split by category is usually the first time a shop sees that changeovers, not breakdowns, are eating the line, or the reverse.

Rules that keep it alive

• Log every stop longer than five minutes. Under that, the logging costs more than the data is worth.
• One owner per shift. A log that belongs to everyone belongs to no one.
• Write the row while the machine is still down, not from memory at the end of the shift.
• Pick categories from a fixed list. Free-text reasons turn into soup nobody can sort.
• Review it weekly, sorted by machine and by category. A log nobody reads teaches the floor to stop filling it in.

Give it two to four weeks and patterns show up. The same press, the same fault, the same hour of the shift. That is the entire point of the exercise: downtime stops being a feeling and starts being a list you can attack.

When the spreadsheet stops working

The other side deserves honesty, because every shop that runs the spreadsheet long enough meets it. The log lives on one computer in the office, so the person at the machine is not the person typing. Rows get written at the end of the shift, from memory, and memory is generous. Two people edit two copies and the versions drift. Nobody gets alerted about anything, because a spreadsheet cannot raise its hand. And the moment you want availability or OEE per machine, someone becomes the person who builds pivot tables every Monday.

That is the point where software earns its keep, and not before. In vMaint, the operator taps running, idle, or down at the machine, the downtime clock starts on its own, the reason gets picked from the same fixed list, and the minutes roll into availability and OEE without a pivot table. If your spreadsheet is still being filled in on time and read every week, keep it. It is doing its job, and it is free.

How downtime turns into OEE, without an MES→

Whichever tool you use, the principle is the same. The value is never the log. The value is the ten minutes a week someone spends reading it, and the one decision a month it changes.

The best downtime log is the one that gets filled in while the machine is still down.