Every property maintenance team eventually learns this the hard way: a burst pipe sat behind a cabinet-hinge request for three hours because the hinge request came in first, and nobody had a system that forced the pipe to jump the line. Priority isn't a nice-to-have — it's the difference between a minor inconvenience and a five-figure water damage claim.
Here's a framework that holds up in practice, not just on paper.
The four tiers that actually matter
Most teams over-complicate priority with five or six levels that nobody can consistently tell apart. Four is enough:
- Emergency — active damage, safety risk, or something getting worse by the minute. Burst pipes, no heat in freezing weather, gas smell, electrical sparking, lockouts with a safety concern.
- High — seriously impacts livability but isn't actively causing damage right now. No hot water, AC failure in extreme heat, a broken exterior door lock.
- Normal — a real problem that should be fixed this week, but waiting a few days won't make it worse. A dripping faucet, a slow drain, a flickering light.
- Low — cosmetic or convenience issues with no urgency. A loose cabinet hinge, a squeaky door, a scuff on the wall.
The test that cuts through most disagreements
When a request doesn't obviously fit a tier, ask one question: if nobody touches this for 48 hours, does the situation get worse, or does it stay exactly the same?
If it gets worse (water spreading, mold starting, a security gap staying open), it's Emergency or High. If it stays the same regardless of when someone gets to it, it's Normal or Low. This single question resolves the vast majority of "is this really urgent?" arguments.
Priority has to be visible, not just assigned
Tagging a request "emergency" does nothing if it looks identical to every other item on the list. Emergency work needs to be impossible to miss — visually distinct, sorted to the top automatically, not something a technician has to notice by reading every line carefully. If your system (or your whiteboard, or your group chat) doesn't make emergency work visually jump out, priority tagging is just decoration.
Don't let priority get inflated
The other failure mode: everything becomes "high priority" because residents (understandably) want their issue treated as urgent, and staff don't want to argue about it. Once that happens, priority stops meaning anything — if everything is high, nothing is.
This is a policy problem, not a technology problem, but the systems that make priority visible and consistent make it much easier to hold the line, because a manager can look at the board and immediately ask "why are twelve things marked emergency" instead of discovering it three weeks later during a review.
Auto-sort, don't manually re-order
If a dispatcher has to manually drag items around to keep the urgent ones on top, priority will drift the moment that person is out sick or slammed. The list should sort itself: emergency first, then high, then normal, then low, automatically, every time a new item comes in. Manual sorting is where good intentions quietly fail under real workload.
The short version
Four tiers, not six. Use the "does it get worse if ignored" test for anything ambiguous. Make emergency work visually impossible to miss. Watch for priority inflation. Let the system sort automatically instead of relying on someone to remember to reorder the list by hand.
Priority that sorts itself
MaintenanceHub ranks every work order automatically — emergency always floats to the top.