Anatomy of a Work Order

A technician arrives, finds the wrong problem, lacks the right part, and leaves. A second visit is scheduled. The cost has doubled and the equipment is still broken.

The cause is almost always the initial report, and the fix is a structured form rather than a free-text box.

What has to be captured

The asset, by tag number. Not "the walk-in" — the tag. A site with three coolers produces three ambiguities.

The symptom, in observable terms. Not "it is broken". What it does, what it does not do, when it started, whether it is intermittent.

Numbers where numbers exist. For refrigeration: what temperature does it hold, and what should it hold. This single field determines whether the call is urgent.

When it started and what changed. A failure that began after a delivery, a power event, or a cleaning is diagnostic information.

Whether it is currently in use. A cooler holding 45°F with product in it is a different call from one that is empty.

Photographs. Of the unit, the display, any error code, and any visible damage. Error codes photographed rather than transcribed avoid the transcription errors that send technicians with the wrong parts.

Site access details. Hours, who to ask for, parking, whether the roof is accessible, whether keys are needed. Technicians who cannot get in bill for the visit anyway.

Priority, from a defined scale rather than from the reporter's mood.

The priority scale worth using

Emergency. Food safety at risk, service stopped, or a safety hazard. Refrigeration out of temperature with product. Gas smell. Suppression system discharged. Response in hours.

Urgent. Service degraded but continuing. One fryer of three down. Ice machine failed. Response same or next day.

Routine. Working but faulty. A door seal, a light, a slow drain. Response within a week.

Scheduled. Preventive work.

Define these in writing and put them on the reporting form. Without a defined scale, everything becomes an emergency, emergency rates get paid for routine work, and genuine emergencies queue behind them.

Making site staff report well

The manager reporting the fault is not a technician and should not need to be.

Use a form with fields, not a free-text box. Structured prompts produce structured answers.

Ask for a photograph as a required field. This alone substantially improves first-visit resolution.

Provide asset tags they can scan or type. A code on the equipment removes the identification problem.

Give examples of good and bad descriptions in the training. "Walk-in freezer, tag 214, holding 18°F should be 0°F, started this morning, product moved to unit 3, ice buildup on evaporator, photo attached" is a report a dispatcher can act on.

Do not require them to diagnose. Asking a manager what is wrong invites a guess that misdirects the technician. Ask what it is doing.

Closing the order properly

The close is where the record's future value is created, and it is where most systems are weakest.

What was actually wrong. The fault, not the task.

What was done. Repair, part replaced, adjustment, cleaned.

Parts used, with numbers.

Labour time and rate.

Whether the fix is permanent or temporary. A temporary fix with no follow-up is how a small problem returns as a large one.

Photographs of the completed work, and of the failed part.

Recommendations. Anything the technician noticed that is not yet a fault. This is the highest-value field on the form and the most often blank; requiring it is worth a small argument with vendors.

Sign-off by site staff, confirming the equipment works.

Why the record matters later

Six months on, the question is whether to repair a unit again or replace it. That decision needs the history: how many visits, what faults, what total cost.

A work order history of "repaired refrigeration" tells you nothing. A history showing three compressor-related calls in eight months tells you the unit is finished.

The discipline of closing orders properly is dull, it is resisted by vendors, and it is the difference between a maintenance record and a pile of invoices.

A reporting form that fits on a phone

The form site staff use should be short enough to complete during service.

Asset tag — scanned or typed from the label.

What is it doing? A short list of common symptoms for that asset type, plus free text.

Numbers, where applicable. Current temperature, target temperature.

When did it start?

Is it in use? Yes, no, product at risk.

Photograph — required, not optional.

Anything else.

Seven fields, one screen, under ninety seconds. Anything longer will be bypassed by a phone call to a contractor, which is how work becomes invisible to the system.

Prefill everything you can: site, reporter, date, and the asset details once the tag is entered.