Home / Guide / Operations
Dispatch: Report to Technician
The half hour between a manager noticing a problem and a technician being assigned determines cost, response and whether the visit works.
- Section
- Operations
- Document type
- Procedure
- Applies to
- Multi-site operators
Dispatch is where a report becomes work. Done badly it produces the wrong technician, the wrong priority, and a second visit.
The steps
Receive, through a single defined route. Multiple routes — some calls, some messages, some direct to vendors — produce work nobody sees.
Triage. Is the report complete? Is the priority right? Is it actually a maintenance issue?
Check warranty and ownership. Before dispatching anything.
Check history. Has this asset failed recently? A repeat within the warranty period of the vendor's own work should go back to them at no charge.
Assign, to the right trade and the right vendor.
Communicate, to the site: who is coming, when, and what to do meanwhile.
Track to completion.
Close with the record.
Triage catches more than people expect
A meaningful share of reports are not equipment failures.
Operator error. A unit switched off, a control adjusted, a door left open, a breaker tripped by something else.
Consumables. A filter, a bulb, a seal that site staff can replace.
Not our equipment. Supplier-owned beverage or ice equipment, or a landlord responsibility.
Already reported. Duplicates from different shifts.
Wrong trade, which sends the wrong technician and produces a wasted call-out.
A five-minute triage conversation — is it powered, is the breaker on, what does the display say, send a photograph — resolves a real proportion of reports without dispatch. The saving is substantial and it requires someone competent taking the call rather than a form auto-forwarding to a vendor.
Batching
Not everything needs to go immediately.
P3 work should queue. Three routine items at one site done in one visit cost far less than three call-outs, and the difference is entirely in the willingness to wait a few days.
Combine with scheduled visits where possible. A preventive visit is an opportunity to clear the routine queue at that site.
Communicate the queue to the site so the manager knows the item is not lost. Reports that appear to vanish stop being made.
Assigning correctly
By trade, which requires knowing what kind of fault it is. This is where a good report matters.
By geography, minimising travel.
By history, preferring the technician who has been to that site.
By capacity, which requires knowing what the vendor is carrying.
By warranty, which may mandate a specific servicer.
Communicating with the site
The most neglected step and the source of most friction between sites and the central function.
Confirm receipt immediately. A report acknowledged is a report the manager stops chasing.
Give a time window and a name.
Tell them the interim measure — move product, adjust the menu, use the other unit.
Notify of delays before the window passes rather than after.
Confirm closure and ask whether it is fixed. A work order closed by a vendor and not verified by the site is closed on the vendor's word.
After hours
A defined route — a number, a form, an on-call person. Not the maintenance manager's personal phone, which fails on holiday.
A defined authority. What the site manager may authorise without approval, and what requires a call.
A defined list of genuine emergencies, which is the same list from the priority scale.
A written interim procedure for each emergency type, available on site.
Reviewed the next morning, because after-hours decisions made under pressure need checking.
Tracking
Open work orders, by age. The single most useful operational view. Anything ageing past its priority commitment needs a call.
By site, so a manager with a growing queue is visible.
By vendor, so a vendor accumulating open items is visible.
Weekly review of anything older than its commitment. Fifteen minutes, and it catches the work orders that would otherwise sit for a month because everyone assumed someone else was handling it.
The triage script
A short set of questions for whoever takes the report, which resolves a meaningful share without dispatch.
Which asset — what is the tag number?
Is it powered? Check the switch, the plug and the breaker panel.
Has anyone changed a setting?
Is anything blocking airflow — product against the evaporator, boxes against the condenser, a blocked intake?
Is there an error code? Photograph it.
Is a filter obviously blocked?
Is the door closing and sealing?
What is it reading, and what should it read?
When did it start and what changed?
Five minutes. It resolves operator error, tripped breakers, blocked airflow and adjusted controls, which together are a substantial share of reports. It also produces a much better work order for the ones that do need dispatch.