Priority inflates unless something resists it
Every work order system starts with sensible priority levels and drifts towards everything being urgent. The mechanism is not carelessness: whoever raises a ticket knows that urgent gets attention and normal does not, and each individual decision to mark something urgent is locally rational. Collectively they destroy the scale.
Once most of the queue is urgent, priority has stopped carrying information and maintenance falls back on choosing by whatever is loudest or most recent. The backlog is then genuinely unmanaged while looking fully managed, which is worse than having no priorities at all.
Four levels, defined by consequence
Define levels by what happens if the work waits, not by how annoyed the reporter is. Four is the right number — three cannot separate "guest is affected now" from "room cannot be sold", and five produces two adjacent levels nobody can tell apart.
| Level | Means | Target response | Examples |
|---|
| Emergency | Safety risk, or active damage getting worse | Immediate, interrupt current work | Active leak, no heat in winter, lock failure, gas or electrical fault, anything blocking egress |
| Urgent | Room cannot be sold, or a guest is affected right now | Same day | No hot water, AC failure in summer, toilet not flushing, TV dead in an occupied room |
| Standard | Guest-visible but the room is still sellable | 2 to 3 days | Slow drain, chipped paint, sticking drawer, one bulb out |
| Scheduled | No guest impact; do it when convenient | Next PM cycle | Touch-up painting, seal replacement, furniture tightening |
Anyone can raise; not everyone can escalate
The rule that actually holds the line is separating the two permissions. Anybody — attendant, front desk, maintenance, a guest complaint — can raise a work order at any level, and should be encouraged to, because the alternative is problems going unreported. But moving something *up* to Emergency or Urgent is a supervisor decision.
This costs very little. Genuine emergencies are recognised as emergencies by whoever is standing in front of them, and a supervisor confirms in seconds. What it prevents is the slow ratchet where the only way to get attention is to overstate, and it does so without ever telling a member of staff that their report did not matter.
Measure the backlog, not the throughput
Closed-tickets-per-week is a comfortable number that says almost nothing: it rises when many trivial jobs are done and falls during one large one. The figures that reveal the state of a property are the shape of what is still open.
Track the count of open orders by level, the age of the oldest open order at each level, and the proportion meeting their response target. An Emergency queue that is never empty is a staffing or contractor problem. A Standard queue whose oldest item is four months old means Standard has quietly become Never, and everyone raising tickets already knows it — which is precisely why the next one will be marked Urgent.
Let inspections raise the work
A large share of maintenance work is first noticed by housekeeping, because they are in every room every day and maintenance is not. If reporting it means remembering to tell someone at the end of a shift, most of it is lost.
The path from a failed inspection item to a work order should be immediate and carry the photograph with it. Without that link the same fault is recorded on three consecutive inspections and fixed after none of them, because noticing and fixing are separate systems that never speak to each other.
Common questions
What priority levels should hotel work orders use?
Four, defined by consequence rather than by the reporter's urgency: Emergency (safety risk or worsening damage, immediate), Urgent (room unsellable or guest affected now, same day), Standard (guest-visible but sellable, two to three days), and Scheduled (no guest impact, next PM cycle).
How do you stop every work order being marked urgent?
Attach a published response time to each level, and separate the permissions: anyone can raise a work order at any level, but escalating to Urgent or Emergency is a supervisor decision. Priority inflates because overstating is the only reliable way to get attention, so remove that incentive rather than blaming reporters.
What is a good work order response time for a hotel?
Immediate for emergencies, same day for anything making a room unsellable or affecting a current guest, two to three days for guest-visible issues in a sellable room, and the next PM cycle for cosmetic work. Set targets you can actually meet — a routinely missed target teaches staff to ignore the scale.
What work order metrics actually matter?
The shape of the open backlog rather than throughput. Track open orders by level, the age of the oldest open item at each level, and the share meeting their response target. Tickets closed per week rises with trivial work and falls during one big job, so it says very little.