Work Order Priority Levels Explained (2026)
How to define maintenance work order priority levels, attach response times to each, and keep everything from being marked urgent.
Key Takeaways
- Priority is about consequence, not about who asked. Define each level by what happens if the work waits: risk to life and safety, risk to operations, inconvenience, or nothing much.
- Every level needs a target response time. Without a clock, a priority is just a color. With one, you can see what is late, which is the number that matters.
- Four or five levels is enough for most teams. DOE’s guide shows a six-level matrix from Emergency to Deferred; many teams collapse it to four in daily use.
- The requester suggests, the supervisor decides. Let requesters describe urgency, but have a planner or supervisor set the final priority so the scale stays consistent.
- Check the distribution every month. If more than a small share of work orders are top priority, your definitions or your intake need fixing.
Quick-Start Prioritization Framework
| Priority | Typical meaning | Example target response |
|---|---|---|
| 1 Emergency | Risk to life, health or safety, or the building cannot operate | Respond immediately, within about 1 hour |
| 2 Urgent | Continuous operation at risk; likely to become an emergency | Same day |
| 3 High / Priority | Affects people or deadlines but has a workaround | Within 2 to 3 business days |
| 4 Routine | Normal repairs, first come first served | Within 1 to 2 weeks |
| 5 Discretionary / Deferred | Desired but not essential; done when resources allow | Scheduled or batched |
Every maintenance team has priority levels. Far fewer have priority levels that mean anything. When half the backlog is marked High, the label stops helping anyone decide what to do next, and the loudest requester wins. A good priority scheme is short, defined in writing, tied to a response time, and assigned by someone who looks at the whole backlog. This guide explains the common schemes, including the six-level matrix the U.S. Department of Energy reproduces in its O&M Best Practices Guide, how to choose response times, and how to keep the system honest once it is running.
Why priority levels matter
A maintenance team always has more requests than hours. Priorities are how you decide, consistently, which requests get the hours first. They also set expectations: a tenant told “routine, within 10 days” is less likely to call three times than one told nothing.
Priorities also feed your metrics. If you track response time against target by priority, you can show that emergencies are handled within an hour while routine work is drifting to three weeks. That is a staffing conversation backed by data rather than anecdotes.
A reference scheme: DOE’s six-level priority matrix
DOE’s O&M Best Practices Guide (Release 3.0) includes a maintenance priority matrix, adapted from NASA, as part of its guidance on reliability centered maintenance. It is a useful starting point because each level is defined by consequence.
| Weight | Description | Application (as listed by DOE) |
|---|---|---|
| 1 | Emergency | Life, health, safety risk; mission criticality |
| 2 | Urgent | Continuous operation of facility at risk |
| 3 | Priority | Mission support or project deadlines |
| 4 | Routine | Prioritized first come, first served |
| 5 | Discretionary | Desired but not essential |
| 6 | Deferred | Accomplished only when resources allow |
How to read it
The first two levels are about protecting people and keeping the facility running. Level 3 is about supporting the organization’s work. Level 4 is the normal queue. Levels 5 and 6 are work you agree is worth doing but will not displace anything above it.
Collapsing it for daily use
Six levels can feel like too many choices on a phone screen. Many teams use four in practice: Emergency, Urgent, Routine and Planned, with Planned covering discretionary and deferred work. That works as long as the definitions are written down and applied the same way by everyone.
Writing definitions people apply the same way
The test of a definition is whether two supervisors, given the same request, would pick the same level. Use examples from your own buildings.
Emergency
Immediate risk to people or property, or loss of a critical system. Examples: gas smell, active water leak into occupied space or electrical equipment, no heat in freezing weather, fire alarm or sprinkler impairment, elevator entrapment, sewage backup, a door that cannot be secured. Emergencies get a phone call, not just a ticket.
Urgent
Will become an emergency or significant loss if left more than a day. Examples: a refrigeration unit running warm, a failed pump in a duplex set where the backup is now carrying the load, a roof leak into an unoccupied area, a single restroom out of service in a building with one restroom.
Routine
Real problems with a workaround: a dripping faucet, a ceiling tile stain, a door closer slamming, a light out in a corridor with other working fixtures. This should be the largest share of your reactive work.
Planned or deferred
Improvements, cosmetic work and anything you will batch: repainting, replacing worn but functional fixtures, adding shelving. These wait for slack time or a project budget.
Setting response and completion targets
Attach two clocks to each priority if you can: response time (someone acknowledges and assesses) and completion time (the work is done or made safe). A response target alone hides jobs that were looked at and then sat for a month.
Base targets on what you can actually do
A one-hour emergency response is only real if someone is on call after hours. If nobody is, say so and set the target you can meet, then use the gap as evidence for an on-call rota.
Use business hours or calendar hours deliberately
Emergency and urgent targets should run on the clock regardless of weekends. Routine targets usually run on business days. Write which one applies so “within 3 days” is not argued later.
Residential properties have legal timelines too
In housing, priorities interact with landlord repair duties. California’s Department of Real Estate says the law usually considers 30 days a reasonable time for repairs, but a shorter period may apply, and gives one to two days for a broken furnace in cold weather as an example. Rules differ by state and city; this is general information, not legal advice. Our guide to tenant maintenance requests covers this in more detail.
Who sets the priority
The person reporting a problem is the right person to describe it and the wrong person to rank it against everything else.
Requester urgency versus work order priority
Give the request form a plain question such as “Is anyone at risk, or is something leaking or without power right now?” with a yes/no answer, and a free text description. Use the answer to flag possible emergencies for immediate review. The supervisor or planner then sets the actual priority.
Emergencies bypass the queue
Publish a phone number for emergencies and make the request form say so at the top. A ticket submitted at 6 p.m. Friday about a gas smell should never wait for someone to open the inbox Monday.
Asset criticality as a tiebreaker
Some teams calculate priority from two inputs: the criticality of the asset (from the asset register) and the severity of the problem. A minor fault on a critical asset can outrank a moderate fault on a non-critical one. Keep the formula simple enough that technicians understand it.
Keeping priorities honest over time
Priority inflation is natural: every requester wants to be first, and every supervisor wants to avoid complaints. It needs a monthly check.
Watch the distribution
Count work orders by priority each month. DOE’s table of industry benchmarks gives emergency maintenance percentage (hours on emergency jobs divided by total hours worked) a benchmark below 10%. If your emergency share is far higher, either your PM program is not preventing failures or work is being mislabeled.
Re-prioritize aging work
A routine job that has sat for 30 days may have become urgent, or may no longer be needed. Review the oldest 10 open work orders weekly and either escalate, schedule or close them.
Record downgrades and upgrades
When a supervisor changes a priority, note why. Over time those notes show whether your definitions need adjusting.
Where preventive maintenance fits
PM work orders do not compete in the same queue as reactive requests in most teams. They are scheduled, with their own due date and completion target, and tracked with a separate metric: PM completion percentage, which DOE benchmarks at above 90%.
The risk is that PM is always the first thing deferred when an emergency appears. Give PM on critical equipment a priority equal to urgent work, and require a reason when a PM is deferred so you can see how often reactive work is eating your preventive program.
Common mistakes
Most priority systems fail in one of these ways.
- Too many levels, so people pick at random between adjacent ones.
- Letting requesters set the final priority.
- No response time attached, so nothing is ever late.
- Calling everything High to get it done, until High means nothing.
- No after-hours path for emergencies.
- Never reviewing old work orders, so the backlog fills with jobs nobody will do.
- Ignoring asset criticality, so a squeaky door outranks a warning on the fire pump.
Putting it into your system
Any CMMS lets you define priority values; check that it also lets you attach target times and report on lateness. A spreadsheet can hold priorities but will not alert anyone when an emergency ticket is still unassigned after 30 minutes.
If you’d rather not do this in an off-the-shelf tool, Floot, an AI app builder, can build a work order app from a plain-English description with your own priority definitions, response targets and push notifications for new emergencies. It is free to start.
Frequently Asked Questions
How many work order priority levels should we have?
Four or five is enough for most teams. DOE’s O&M guide shows a six-level matrix from Emergency to Deferred, and many teams merge the bottom levels into one planned category for daily use.
What counts as an emergency work order?
Anything with an immediate risk to life, health or safety, or the loss of a critical system: gas leaks, active water leaks, no heat in freezing weather, fire protection impairments, elevator entrapments and sewage backups are common examples.
What is a reasonable response time for routine maintenance?
Many teams target a response within a few business days and completion within one to two weeks. Set targets you can meet with your staffing, and in residential property check the legal timelines where you operate.
Who should assign work order priority?
A supervisor or planner who sees the whole backlog. Requesters should describe the problem and flag possible emergencies, but final priority should be set consistently by one role.
What percentage of maintenance should be emergency work?
DOE’s O&M Best Practices Guide lists a benchmark of less than 10% of total maintenance hours spent on emergency jobs.
Should preventive maintenance have a priority?
Yes. Give PM on critical equipment a priority on par with urgent work and track PM completion separately, so preventive work is not silently deferred whenever reactive work spikes.
Sources
- U.S. Department of Energy, FEMP, Operations & Maintenance Best Practices: A Guide to Achieving Operational Efficiency, Release 3.0, 2010 https://www.energy.gov/sites/default/files/2020/04/f74/omguide_complete_w-eo-disclaimer.pdf
- U.S. Department of Energy, FEMP, O&M Best Practices Guide overview page, 2010 https://www.energy.gov/eere/femp/articles/operations-and-maintenance-best-practices-guide-achieving-operational-efficiency
- IBM, What is a CMMS?, 2026 https://www.ibm.com/think/topics/what-is-a-cmms
- California Department of Real Estate, Landlords’ and Tenants’ Rights Guide: Dealing With Problems, 2026 https://www.dre.ca.gov/publications/ResourceGuidebook/gb09_dealingwith.html