The facility manager's guide to smarter work orders

Almost every facility team already has a work order system. Very few have one their technicians use properly. The gap between those two facts is where most of the wasted effort in facilities management lives, and it is not a training problem.

Why systems get abandoned

A work order system is designed by the person who reads the reports and used by the person doing the job. Those two people want opposite things. The reader wants fields: category, sub-category, cause code, resolution code. The technician wants to finish and move to the next job.

Every field you add is a small tax on the person you most need to keep. Charge enough of it and they stop paying: work gets done and closed in a batch on Friday, from memory, with no photos. The system still produces reports. The reports are now fiction.

The six changes that actually work

These are in order of how much they change behaviour, based on what we see when teams move.

1. Remove every barrier to logging demand

If reporting a problem is harder than mentioning it to somebody in a corridor, it will be mentioned in a corridor. A QR code on the wall, a photo and a sentence is the bar. No account, no login, no category picker.

2. Put the procedure inside the work order

A work order that says "check the cooling tower" relies on the person knowing what checking it means. A work order that walks through the eight things to check produces the same result whoever is on shift, and produces a record as a side effect.

3. Capture evidence at the point of work

Photos taken in the app, at the step that asked for them, end up attached to the job. Photos taken on a personal phone end up in a camera roll with a picture of somebody’s dog either side of them. The difference is entirely about when you ask.

4. Make declining work a legitimate option

A technician who cannot record "I could not do this, and here is why" has two options: pretend it is done, or let it go red. Both are worse than the truth. Giving them a way to turn work back with a reason and a photo is the single change that most improves data quality, because it removes the incentive to lie.

5. Report how late, not just late

A queue where this morning’s slip and last March’s carry the same label trains everyone to discount the label, and the estate quietly develops a backlog nobody is arguing about. Ageing changes that: a job reported as five months late is a resourcing conversation, and "overdue" is not.

6. Close the loop with the reporter

The tenant who reported the leak does not know it was fixed unless somebody tells them. Nobody has time to tell them by hand, so nobody does, so the tenant reports it again. Automating that one message removes a surprising amount of noise.

What good looks like six months in

• •Anyone in the building can raise a job without an account
• •Duplicate reports merge rather than multiply
• •Finished work carries photos and times without anybody being asked
• •Late work is visible and specific
• •A technician can refuse a job honestly
• •You can produce the record of any job from a year ago in under a minute

None of this is exotic. It is a set of small decisions about who the system is for. Get them right and the reports become true, which is the only reason to have the system at all.