The Maintenance Work Order: The One-Page Ticket That Turns “It’s Making a Noise” Into “Fixed, Costed, Prevented”

One page per job: a number, the asset, the operator’s own words, a priority set by downtime cost instead of loudness, a named tech, the parts reserved against the ticket, and a close-out that isn’t done until the downtime log, the spare-parts shelf and the maintenance schedule all agree. The work order is what a logged breakdown becomes — the ledger finds the pain; the ticket is what actually fixes it, on the record.

The equipment downtime log counts what broke and what it cost. The preventive maintenance schedule books what should happen next. The work order is the piece between them that most small operations never write down: the actual job. Not a text message, not a shout across the floor, not “I’ll get Dave to look at it” — a numbered, one-page ticket that says who owns it, what it will take, and whether it ended. The difference is not bureaucracy. It is the difference between a $45 gasket and a $7,300 quarter, because the gasket job that gets a ticket gets a close-out, and the close-out is where the prevention lives.

1. The eight fields — written at hand-off, not from memory

A work order filled in on Friday about something that happened on Tuesday is a short story. The eight fields take eight minutes while the job is still warm:

1. Number and date. Every ticket gets a number, even the fifteen-minute ones. The number is what the invoice, the part, and the downtime log line all reference — without it the paper trail forks.
2. Asset and number. The machine and its asset ID, in the same words the downtime log uses. “The walk-in” is not an asset; “Walk-in cooler #2, 2019 Beck” is.
3. The complaint in the operator’s own words. “It’s making a noise again” is data — it is the symptom the tech actually gets. Quote it; do not translate it into jargon until the diagnosis line is written.
4. Priority. P1, P2 or P3, set by downtime cost. Not by loudness, not by rank, not by who is standing closest.
5. Assigned tech and parts. A named person — “whoever’s free” is nobody — and the parts reserved from the critical spares list against this ticket number, so the shelf answers the ticket instead of the loudest shout.
6. Work performed. What was actually done, in words the next tech could repeat without calling you: replaced, torqued, tested, observed for one full cycle.
7. Downtime hours and cost. Both clocks — lost production and wrench time — matching the downtime log line, so the monthly roll-up doesn’t have to reconcile two truths.
8. Preventable, Y/N, plus one line. The sentence that feeds the schedule: “torn door gasket — add weekly gasket + defrost check”. If the line is blank, the ticket closed a job but taught nothing.

2. Priority is arithmetic, not volume

• P1 — down now, or about to be. Production stopped, a safety issue, or the cold chain at risk. Everything drops, parts come off the shelf, and the downtime log line opens the same hour.
• P2 — inside 48 hours. Degraded, intermittent, or the failure mode that ended another machine last quarter. Scheduled within 48 hours, parts ordered, the shift lead told.
• P3 — the schedule’s next slot. Cosmetic, noisy but running, or pure prevention. It goes on the PM schedule and stops occupying anyone’s head.

The rule that makes the three levels real: the downtime log’s cost column decides, not the loudest voice in the room. A P1 that gets called for a squeaky fan while the cold chain quietly drifts is priority inflation — and it costs the same as having no priorities at all.

3. Close-out — the machine running is not the job done

A work order is finished when four things are true, and not before:

• the downtime log line is closed with hours and cost;
• the parts used are off the shelf, the reorder placed, and the fiche back in the drawer;
• the preventable line has become a task on the PM schedule;
• the invoice is attached to the ticket number.

No close-out, no ticket — an open ticket with a running machine is a lie the backlog tells, and it is how December arrives with forty tickets “still open” and nobody able to say which ones are real.

The five traps

• Verbal work orders. “Just tell Dave” is how a repeat failure stays invisible: no ticket, no number, no line in the ledger, no prevention. If it isn’t on a page it didn’t happen — and it will happen again on a Saturday.
• The ticket without a close-out. Half the tickets open in December are finished jobs nobody closed. The close-out is the product; the repair is just its middle.
• Priority inflation. When everything is P1, the word stops meaning “drop everything” and the genuinely-down machine waits behind a squeaky fan. Three levels, arithmetic, done.
• One giant ticket. “Fix the kitchen” is not a work order; it is a wish. One page per job, per asset — otherwise nothing can be costed, assigned, or closed.
• The invisible backlog. Tickets scattered across a whiteboard, three texts and someone’s notebook can’t be triaged, because no one can see them in one place. One numbered list — a spreadsheet is fine — or the uptime budget is being spent by whoever shouts first.

Worked example — the 40-seat restaurant’s third “just tell Dave”

The walk-in cooler has stopped three times in six weeks; the Friday triage has already flagged it as a repeat offender. Monday, 07:10: the prep cook logs “compressor short-cycling again, food temp creeping.” Work order #0142, priority P1 — cold chain at risk, not because the cook shouted. 07:20 it is assigned to Dave by name, with the spare gasket reserved from the critical spares shelf against ticket #0142. 08:00 the door gasket is off, torn along the hinge edge — the same failure mode as last time, now undeniable. New gasket on, door seal tested with the dollar-bill test, one full defrost cycle observed. 10:30 close-out: downtime log line closed at 2.5 lost-production hours (brunch service moved to ice chests, 40 covers saved), $45 part plus 90 minutes of Dave, invoice stapled to #0142, and the line that pays for the whole page: preventable Y — add weekly door-gasket and defrost check to the cold-chain walk; reorder spare gasket (bin empty).

Total paperwork: one page, eight minutes. The alternative — the third “just tell Dave” with no ticket — is exactly how the first quarter became six events and $7,300 of lost revenue with nobody able to prove the pattern. The ticket didn’t fix the cooler; the gasket did. The ticket is why the schedule learned, the shelf got refilled, and the downtime budget shows where the money went.

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 pest control service log is where the exclusion fix comes from — a flagged activity becomes a $12 door sweep on a work order instead of a tenting week; the equipment downtime log is where every P1 starts and ends — the work order carries its event; the preventive maintenance schedule is what the close-out’s preventable line becomes — each scheduled task runs as its own work order; the critical spare parts list is what gets reserved against the ticket number — the shelf answers tickets, not shouts; the uptime budget is the pot every P1 spends from; and the generator transfer checklist rides on a P1 work order so the switchgear leaves a paper trail too.; the refrigeration temperature log is where the symptom history comes from — two days of readings stapled to the ticket beat one shrug

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: Sunday findings from the walk-in cooler maintenance checklist become Thursday parts orders here — a dollar bill that pulls free at point 4 is work order language, not a feeling.