The Equipment Downtime Log: The Ledger That Turns Breakdowns Into a Maintenance Budget

One line per breakdown, written the hour the machine comes back: which machine, how long it was down, what actually broke, what the fix was, what it cost, who fixed it, and — the column that pays for the whole page — whether it was preventable. Triaged for fifteen minutes every Friday, rolled up once a month, the log is where the maintenance schedule gets its frequencies, the spares list gets its evidence, and the repair-or-replace decision gets numbers instead of vibes.

1. The seven columns — recorded the hour it ends, not the week after

A downtime log that is filled in from memory on Monday is a short story collection. The entry takes ninety seconds while the details are still warm:

1. Machine — named the way the floor names it, plus the asset number from the asset inventory. "The walk-in" and "W-01" both go in the box, because the log is read by two audiences.
2. Started / ended, and the duration that matters — lost production time, not wrench time. A twenty-minute fix that lands mid-run on the only oven can cost more than an eight-hour fix on an idle Sunday; the log carries both clocks, and the lost-production clock is the one that pays.
3. What broke — the failure mode in plain words. Not "machine down," but "door gasket torn on the walk-in, coil iced over, compressor short-cycling on its overload." Six months of these lines is a textbook only your business owns.
4. The fix — what was actually done and which part went in. This column is where the spares list shops: every part that ended a stop is a candidate for the shelf.
5. Cost — parts, outside labour, and the production missed. Guessing is fine; consistency is not negotiable. The monthly roll-up is only as honest as this column.
6. Who fixed it — so the second occurrence finds the first occurrence's person, and the key-person risk of never writing the fix down becomes visible.
7. Preventable? Y/N + one line — what would have caught it: the gasket check, the vibration listen, the $45 part, the filter change. This column is the seed corn of the maintenance schedule.

2. The Friday triage — fifteen minutes that close the loop

A log nobody reads is a diary with extra steps. Once a week, scan the new lines and make three moves: every preventable = Y event becomes a candidate task on the maintenance schedule; any failure mode that has now appeared twice in ninety days jumps the queue, because repeat offenders are the machines writing your future; and any event whose one-line "what would have caught it" needs a part goes onto the spares list with the downtime tolerance attached. Fifteen minutes on Friday buys the week where the fix is a scheduled hour instead of a scheduled crisis.

3. The monthly roll-up — the page where money appears

Once a month, sum the downtime hours and the cost column per machine. Two findings usually fall out. First, the 80/20 line: in a typical small fleet, two machines hold most of the pain, and the intuitive "worst machine" is often not either of them — the quiet leaker that stops for twelve minutes twice a week outranks the dramatic one. Second, the repair-or-replace threshold: when a rolling twelve months of downtime cost passes roughly a third of replacement cost — and the trend is not bending after PM and spares are in place — the machine goes on the capital list, and the annual budget gets a line item instead of a surprise. The uptime budget decides how much downtime you can afford; this roll-up shows where it actually went.

4. The lemon list — the annual walk with the trend line open

Once a year, rank the machines by downtime cost and read the trend, not just the total. Machines whose cost keeps climbing after preventive maintenance and spares are in place are lemons: the honest move is to plan the replacement, set the date, and stop feeding the ledger. The lemon list is also where you discover the opposite — the machine everyone complains about that costs almost nothing, which keeps its job and its reputation on the strength of a column of numbers.

The five traps

• Logging only the big outages. The dramatic four-hour failure gets written up because it was exciting; the fifteen-minute stops that happen twice a week are the ones quietly paying for nothing. The log catches every stop that ends, or it catches nothing.
• Blame entries. The column is who fixed it, never who broke it. A log that names culprits teaches the floor to log nothing, and the ledger goes blind precisely where the money leaks.
• Repair-hours only. Wrench time is what the invoice says; lost-production time is what the P&L says. Carry both, cost the second, or the roll-up will flatter the machines that hurt you most.
• The log nobody reads. Without the Friday triage the entries fossilise into a diary. The triage is the product; the logging is just its raw material.
• Shoebox history. A year of events scattered across texts, sticky notes, and one manager's memory cannot be rolled up, argued with, or handed over. One page per machine per quarter — a shared spreadsheet at minimum — is what makes the log survive the person who was keeping it in his head.

Worked example — the 40-seat restaurant and the $45 gasket

A forty-seat restaurant logged every kitchen equipment stop for a quarter. Q1 read: six downtime events, 19.5 lost-production hours, $1,150 in repairs and call-outs, and — once the missed covers were priced — about $7,300 of revenue walking out the door. The instinct had been to blame the worst day, the Saturday the combi oven threw an error and service came Monday. The roll-up said otherwise: four of the six events were the same walk-in cooler, same failure mode, compressor short-cycling on overload. The Friday triage finally caught the pattern when the second entry landed, but the habit stuck from the third.

The root cause was embarrassing and cheap: a torn door gasket letting humid air in, icing the coil, starving the compressor. A $45 gasket, a defrost-cycle check added to the weekly cold-chain walk, and a spare gasket on the shelf with the fiche in the drawer. Q2: one event, 2.5 hours, zero call-outs. The same roll-up put the twelve-year-old combi oven on the capital list — $2,900 a year in downtime and repairs against a replacement that suddenly had a business case, a date, and a budget line instead of a Friday-night failure and a panic quote. Nothing about the kitchen changed except that the breakdowns were being counted, and the counting did the arguing.

The log is not paperwork. It is the post-mortem habit applied at machine scale — every event asked once, in writing, what would have caught it — and the transfer to the generator during the outage, the switchover step in the generator checklist, is just another line: started, ended, what broke, what it cost, preventable next time?

Kits

Every page ships with a kit block — the paid tools behind the free advice:

• The First 30 Minutes — free incident quick-start checklist
• Ops Starter Kit — incident response for small teams — $14
• Ops Starter Kit Vol. 2 — advanced incident response & communications — $27
• Ops Mega Bundle — all 5 kits in one download — $49

Related: the preventive maintenance schedule is where the Friday triage sends its preventable events; the critical spare parts list is what the "what fixed it" column feeds; the uptime budget sets how much downtime you chose to allow; the cold chain failure checklist is the walk-in's bad day in full; and the supplier concentration map is the reason some of those lead times ran long. the maintenance work order is what a logged event becomes — the numbered ticket that carries the fix, the cost, and the preventable line to the schedule.; the refrigeration temperature log is the early-warning row that turns cold-chain drift into a Tuesday fix instead of a P1

Related: the shift handover log is the five-minute crossover sheet that keeps open issues from dying with the shift that found them — flags, absences and supplier problems written down while they are still cheap.

Related: log walk-in hardware faults from the cooler maintenance checklist in the downtime log — the pattern (third gasket this year, closer still slamming) is the budget case for the real fix.