Guide · Facilities and maintenance
How to define maintenance request priority levels
Priority should describe consequence and response, not the emotion or job title of the person asking.
Published · Updated · 5 min read · By Servenzo Operations Team.
The short answer
Define maintenance priority from observable factors rather than from how urgent the request sounds: immediate safety risk, loss of an essential service, risk of escalating damage, the number and vulnerability of people affected, security exposure, and any legal or contractual response requirement. Give every level a response target, an escalation path and two or three examples, then hold the definitions in the same place you raise work orders.
A four-level scale that holds up in practice
| Criterion | What qualifies | What it commits you to |
|---|---|---|
| P1: Emergency | Immediate danger to people, major security breach, or total loss of an essential service | Attend now, out of hours if needed; escalate on the same call if you cannot resource it |
| P2: Urgent | Damage is escalating, a service is badly degraded, or a vulnerable occupant is affected | Attend same day or within the contract window; make safe if a full fix is not possible |
| P3: Routine | A fault with a safe workaround and no escalation risk | Schedule into normal capacity within days; group with other work at the site |
| P4: Planned | Cosmetic, deferrable, or best done alongside planned maintenance | Batch into a [planned maintenance](/solutions/preventive-maintenance-software) visit rather than a separate trip |
Bottom line: Four levels is usually the ceiling. Every level you add is another judgement call at intake, and scales with six or seven levels drift until P1 stops meaning emergency. Publish the examples alongside the definitions. People classify by analogy, not by criteria.
Keep the scale small and the examples concrete
The failure mode is not a missing level, it is inconsistent classification. Two coordinators reading the same request should reach the same priority, and the fastest way to achieve that is a short list of worked examples per level rather than a longer set of definitions.
Response and resolution are different promises
Most contracts commit you to attend within a window, not to fix within it. Recording both, time to attend and time to resolve, is what lets you defend performance later, and it is a distinction your service contract terms should already make.
Priority should change what actually happens next
A priority that does not change dispatch order, escalation or out-of-hours handling is decoration. Tie each level to a concrete operational consequence, so raising something to P1 visibly reorders the day for whoever is dispatching work.
A practical process
- List safety, service, damage, security and contract factors.
- Group them into a small number of clear priority levels.
- Set response, update and escalation expectations for each level.
- Train with real examples and review misclassified requests.
Sources and further reading
This article provides operational education, not legal, employment, accounting, safety or regulatory advice. Requirements vary by contract, industry and jurisdiction.
Questions about how to define maintenance request priority levels
What is a P1 maintenance request?
Many teams use P1 for the highest priority, but definitions vary. Publish the actual impact and response criteria instead of relying on the label alone.
Can priority decrease?
Yes. Once a safe temporary control reduces impact, the permanent repair may move to a lower response category. Preserve the change history and reason.
Should customers choose priority?
Customers should describe impact and urgency. The operations team should apply consistent rules, while allowing a documented escalation path.