The work order lifecycle: from report to sign-off

A work order looks simple from the outside — something's reported, someone fixes it, it's closed. In practice, most of the risk in reactive maintenance sits in the gaps between those three stages, not in any one of them individually. A facilities team that's genuinely good at the middle stage but loose about the first and last is still exposed, just in a way that's harder to notice.

Report: capturing enough to act on

The report stage is where most of the useful context either gets captured or gets lost permanently. A vague report — "something wrong with the heating" — forces whoever picks it up to spend time diagnosing before they can even start fixing, which is time better spent the first time around if the original report had captured location, symptom and urgency clearly. Getting this right is mostly about triage at the point of intake, not the technical work itself.

Assign: matching the job to the right person, quickly

A job that sits unassigned for a day because nobody's clearly responsible for picking it up is functionally the same as a job nobody's heard about yet, from the reporter's point of view. Clear ownership — a named person or a specific contractor, not a general queue everyone assumes someone else is watching — is what keeps this stage short.

Fix: the part everyone assumes is the whole job

This is the stage most conversations about maintenance focus on, and it's genuinely important, but it's not actually where lifecycle failures cluster. Engineers doing the physical work tend to do it competently; the risk is what happens immediately before and after this stage, not during it.

• –A report with enough detail — location, symptom, urgency — to act on without a follow-up call first
• –Clear, immediate ownership once a job is logged, rather than a queue everyone assumes someone else is handling
• –A record of what was actually done, not just that the job status changed to closed
• –Confirmation the fix worked, ideally from someone other than the person who did the work
• –A closed job that's genuinely closed — not reopened a week later because the underlying issue was never fully resolved

Sign-off: the stage most often skipped entirely

Sign-off means confirming the fix actually worked, ideally by someone other than whoever did the repair — a second pair of eyes, or feedback from whoever reported the original issue. Skipping this stage and marking a job closed the moment the engineer says they're done is how the same fault ends up being reported again a month later, except now it looks like a new problem rather than a recurrence of one that was never properly verified.

This full lifecycle discipline matters just as much for statutory findings as it does for routine reactive work — what should happen when an inspection turns up a defect follows exactly the same shape, report through to a genuinely confirmed close.