How to Prioritise Maintenance Jobs: A Practical Guide
- Trefnus
- Jul 30
- 13 min read
Published: 27 July 2026 | Last reviewed: 27 July 2026
Every maintenance team faces the same question each morning: what gets done first? A pump is making a noise, a fire door will not close properly, three planned services are overdue, and the warehouse manager wants a shelving unit refitted today. Knowing how to prioritise maintenance jobs is what separates a team that stays in control from one that spends every week firefighting.
This guide sets out a practical method for ranking maintenance work in a UK small or medium business. It covers assessing asset criticality, scoring consequence against urgency, protecting statutory compliance tasks from the daily scramble, and clearing an existing backlog without letting the same problem build up again.
Why Prioritising Maintenance Jobs Matters
Where there is no agreed method, priority defaults to whoever asks most persistently. That is not a system. It is a queue shaped by personality, and it produces three predictable problems.
First, planned work slips. Preventive tasks are easy to defer because nothing visibly breaks when you postpone them. The consequence arrives later, as a failure that could have been avoided, which in turn generates more reactive work and squeezes the planned schedule further. This is the reactive spiral, and it is self reinforcing.
Second, statutory obligations get treated like ordinary requests. A thorough examination that is legally due gets bumped by a job that feels more urgent because someone is standing in front of you asking about it. The legal exposure does not care how busy the week was.
Third, trust erodes. When departments learn that escalation is the only thing that works, everyone escalates. Every request becomes urgent, and the word stops meaning anything.
The purpose of a prioritisation method is not to get everything done. It is to make sure the right things get done first, and to be able to explain afterwards why the work was ordered the way it was.
Start With Asset Criticality, Not the Job in Front of You
The single biggest improvement most teams can make is to rank their assets before they start ranking jobs. Without that, every prioritisation decision starts from scratch, based on how the request was worded and who sent it.
What asset criticality actually measures
Criticality is a measure of the consequence of an asset failing. It is not a measure of how likely that failure is. A boiler that has never given trouble in ten years is still highly critical if its failure would close the building tomorrow.
Separating consequence from likelihood matters, because likelihood changes with condition and age while consequence is largely fixed by the role the asset plays. Criticality gives you a stable baseline that you are not re-arguing every week.
Five factors to score
Score each asset from one to five against the factors below. Keep the scale coarse. Precision here is false comfort, and a three point scale that people actually use beats a ten point scale that they argue about.
Factor | Low (score 1) | Medium (score 3) | High (score 5) |
Safety and legal consequence | No safety or legal implication | Indirect safety implication | Direct injury risk or a statutory duty attaches |
Operational impact | Minor inconvenience only | Slows one team or process | Stops production, trading or a critical service |
Redundancy | Duplicate asset available | Partial cover or manual workaround | Single point of failure, no alternative |
Repair or replacement lead time | Same day, parts held | Days, parts obtainable | Weeks or months, bespoke or imported parts |
Financial consequence of failure | Low repair cost, no knock on effect | Moderate cost or short disruption | High repair cost, lost revenue or penalties |
Add the five scores together for a total between 5 and 25, then band the results:
Class A, critical: 19 to 25. Failure has serious safety, legal or operational consequences. These assets get planned maintenance, spares held where sensible, and fast response.
Class B, important: 12 to 18. Failure is disruptive but manageable. Planned maintenance at a sensible interval, standard response.
Class C, routine: 5 to 11. Run to failure is often the rational choice. Fix when convenient, batch the work.
Being explicit that some assets are run to failure is not negligence. It is a deliberate decision to spend attention where it changes an outcome. What matters is that the decision is recorded rather than accidental.
Keep the exercise proportionate
Do not attempt to score four hundred assets in one sitting. Start with the twenty or thirty whose failure would hurt most, agree their classification, and extend from there. Review the classifications once a year, or whenever the business changes what an asset is used for.
How to Prioritise Maintenance Jobs Using a Simple Scoring System
Once assets are classified, individual jobs become far easier to rank. For any incoming job, ask two questions:
What happens if we do nothing? This is the consequence, and asset criticality already tells you most of the answer.
How soon does that consequence arrive? This is the urgency, and it is a separate question entirely.
A high consequence job with a long fuse is not the same as a low consequence job that is already causing a problem. Combining the two produces four practical priority bands.
Priority | When it applies | Typical response target | Examples |
P1 Emergency | Immediate danger to people, or a critical service has already stopped | Attend immediately, same day | Failed fire alarm panel, lift entrapment, gas smell, loss of heating in a care setting |
P2 Urgent | Serious safety, compliance or operational consequence if not resolved quickly | Within 24 hours | Critical asset running with no redundancy, failed emergency light, active water ingress |
P3 Routine | A genuine fault, but there is no immediate consequence and a workaround exists | Within 5 to 10 working days | Non critical equipment fault, minor contained leak, door closer needs adjusting |
P4 Scheduled | Deferrable work with no current consequence, best done in a planned window | Next planned window or shutdown | Redecoration, opportunistic improvement work, non urgent upgrades |
Set the response targets to match your own resourcing rather than copying someone else's. A target you consistently miss is worse than no target, because it teaches everyone to ignore the system.
A worked example
Three jobs are reported on a Monday morning and there is one available engineer.
An emergency light on a protected escape route fails its monthly functional test. The fitting is part of the building's fire safety measures, and in this scenario the failure leaves an escape route without adequate emergency lighting. This is a P1 job and requires immediate attention because it affects a statutory fire safety measure.
The extraction fan serving a spray booth has become noticeably noisier and is vibrating. The spray booth is a Class A asset with no redundancy. If the fan fails, production stops and employees could be exposed to airborne contaminants. This is a P2 urgent job. The engineer should inspect the fan to identify the underlying fault rather than simply restoring it to service.
A ceiling light has failed in a stockroom, but three other fittings provide adequate lighting and staff can continue working safely. The lighting circuit is a Class C asset, there is a straightforward workaround and there is no immediate operational consequence. This is a P3 routine job and can be completed once higher priority work has been dealt with.
The order is therefore clear. The emergency light comes first because it affects a statutory fire safety measure. The spray booth fan comes next because failure would have significant operational and safety consequences. The stockroom light is repaired afterwards because the consequence of waiting is low and an acceptable workaround already exists.
Without an agreed method, the order could easily be influenced by who reported the problem first or who asks most often for an update. A written prioritisation system keeps decisions consistent by basing them on consequence, urgency and compliance rather than personal judgement.
Do not let quick masquerade as important
Short jobs get done because they are satisfying, not because they matter. The fix is to batch them. Reserve a fixed slot, perhaps a Friday afternoon or one morning a fortnight, and run the P4 list in geographical order. The work still gets done, and it stops leaking into time reserved for critical assets.
Where Statutory and Compliance Work Sits
Some maintenance is not a candidate for prioritisation at all. It is a legal duty with a defined frequency, and the correct treatment is to ring-fence it before discretionary work is allocated, rather than ranking it against everything else.
Examples that apply to many UK workplaces include the following, though the detail depends on your sector, equipment and premises:
Work equipment: The Provision and Use of Work Equipment Regulations 1998 require work equipment to be maintained in an efficient state, in efficient working order and in good repair, with inspection where safety depends on installation conditions or the equipment is exposed to deteriorating conditions.
Lifting equipment: The Lifting Operations and Lifting Equipment Regulations 1998 require thorough examination by a competent person at intervals set in the Regulations or under an examination scheme.
Pressure systems: The Pressure Systems Safety Regulations 2000 require a written scheme of examination to be in place before a qualifying system is operated, and examinations to be carried out in accordance with it.
Electrical systems: The Electricity at Work Regulations 1989 require electrical systems to be maintained so as to prevent danger, so far as is reasonably practicable.
Fire safety: The Regulatory Reform (Fire Safety) Order 2005 places duties on the responsible person in England and Wales, including maintaining fire safety measures. Scotland and Northern Ireland have their own equivalent regimes.
Distinguish the four kinds of obligation
Teams get into difficulty when they treat every requirement as though it carried the same weight. In practice there are four distinct categories, and they behave differently when you are deciding what can be deferred:
Statutory duties. Set out in legislation. These are not optional. Note that many health and safety duties are qualified by phrases such as "so far as is reasonably practicable", which qualifies the extent of the measures required, not whether the duty applies.
Approved Codes of Practice. Documents such as the HSE Approved Codes supporting PUWER and LOLER have a special legal status. Following them means you will normally be doing enough to comply. Departing from them means being able to demonstrate you have complied in another way.
Industry standards and best practice. Maintenance specifications such as SFG20 and the relevant British Standards are not law, but following a recognised standard is strong evidence of a reasonable approach.
Insurer and contract conditions. Policy conditions and lease obligations are commercial rather than statutory, but breaching them can invalidate cover or trigger a liability. Treat them as fixed commitments and diarise them alongside statutory tasks.
The practical rule is simple: statutory and contractual tasks get a slot in the schedule before anything discretionary is allocated. Everything else competes for what is left.
Handling the Backlog You Already Have
A prioritisation method applied to new work does nothing about the two hundred open jobs already sitting in the system. That list needs a separate, one off exercise.
Measure it properly. Count outstanding labour hours, not the number of open jobs. Divide by the labour hours you have available in a normal week to express the backlog in weeks of work. A backlog of a few weeks per trade is often treated as healthy, since it allows work to be planned rather than scrambled, but treat that as a working rule of thumb rather than a standard.
Triage the whole list once. Assign every open job a priority band using the same method you apply to new work. This is tedious and it is worth doing properly, because a list nobody trusts gets ignored regardless of what is on it.
Be willing to close jobs. Duplicates, requests against assets that have since been removed, and cosmetic items that will never be funded should be closed with a reason recorded. Carrying dead work inflates the backlog and hides the real position.
Set explicit deferral rules. If a job is deferred it should have a named approver and a review date. Open ended deferral is how compliance tasks quietly disappear.
Protect planned capacity. Reserve a fixed proportion of available hours for planned maintenance and defend it. If reactive work is allowed to consume everything, the backlog will keep growing no matter how well it is ranked.
It is worth being honest at this stage if the backlog is simply larger than the resource available. A ranked list makes that visible, and it turns a vague complaint about being overstretched into a specific and defensible case for more capacity or fewer commitments.
Common Mistakes When Prioritising Maintenance Jobs
Priority inflation. When everything is marked urgent, nothing is. Cap the proportion of jobs that can be raised as P1, and review the ones that were.
Confusing urgency with importance. A job can be genuinely urgent and still low consequence. Score both separately or the loudest problem will always win.
Ranking by requester. If a request from a director outranks one from a warehouse operative by default, the system is recording seniority rather than risk.
Never re-prioritising. Priority assigned on day one is a snapshot. Build in ageing rules so a P3 that has sat untouched for a month gets reviewed rather than forgotten.
Ignoring the pattern. The same job appearing repeatedly on one asset is not a prioritisation problem, it is a root cause problem. Faster response will not fix it.
Keeping the method in one person's head. If the reasoning is not written down, it cannot be audited, handed over or defended. It also disappears when that person leaves.
Making the System Stick
Most prioritisation schemes fail not because the logic is wrong but because nobody maintains them. A few things make the difference.
Write it down on one page. Criticality bands, priority definitions, response targets and who decides. If it does not fit on a page, it will not be used.
Name the decision maker. One person should own priority assignment, with a clear route for challenging a decision. Prioritisation by committee produces P1 inflation.
Hold a short weekly review. Fifteen minutes to check what came in, what slipped and what needs re-ranking is usually enough.
Measure a small number of things. Planned maintenance completed on time as a percentage, the ratio of planned to reactive hours, backlog in weeks, P1 response time, and overdue statutory tasks. The last of those should be zero.
Review asset criticality annually, and whenever the business changes what an asset is used for.
You may also see the planned to reactive ratio quoted as a target, commonly in the region of eighty per cent planned. Treat that as a heuristic rather than a benchmark, since the right balance depends heavily on your asset base and sector. What matters more is the direction of travel over time.
Keeping priorities visible once the list gets long A prioritisation method only works if everyone can see the same list. Once jobs are spread across a wall planner, an inbox and a WhatsApp group, priority quietly reverts to whoever asked last. That is the point at which most teams outgrow a spreadsheet. Trefnus CMMS is built for exactly this. It holds your asset register with condition and location, links defects and completion records to the asset that generated them, and separates recurring planned activities from reactive jobs so compliance work is not competing for attention with everything else. Defects carry severity levels from critical down to low, and the dashboard flags overdue activities and critical defects before they become a problem. It is an offline first progressive web app, so it keeps working in a plant room or on a site with no signal. It is a one time purchase covering up to five devices, with no monthly subscription. You can see how it works at: |
Frequently Asked Questions
How do you decide which maintenance job to do first?
Decide by consequence and urgency rather than by who asked. First establish how critical the asset is, based on safety and legal implications, operational impact, redundancy, repair lead time and financial consequence of failure. Then ask how quickly the consequence of inaction will arrive. Work that carries a statutory duty, such as a legally due thorough examination or a fire safety measure, should be scheduled first and separately, before discretionary work is allocated capacity.
What is asset criticality analysis?
Asset criticality analysis ranks equipment by the consequence of its failure rather than the likelihood of failure. Each asset is scored against factors such as safety and legal exposure, operational impact, whether a backup exists, how long a repair would take and the financial cost of downtime. The scores are banded into classes, typically critical, important and routine. The classification then drives maintenance strategy, deciding which assets get planned maintenance and held spares, and which can reasonably run to failure.
Should planned maintenance ever be delayed to deal with a breakdown?
Sometimes, but it should be a recorded decision rather than a default. A genuine emergency on a critical asset outranks a routine service on a low criticality one. The risk is that this becomes habitual, and deferred preventive work generates further failures that consume more time again. Protect a fixed proportion of weekly capacity for planned work, require a named approver for any deferral, and set a review date so the task does not simply disappear from the schedule.
How big should a maintenance backlog be?
A backlog is not automatically a failure. Some backlog is necessary to allow work to be planned, batched and resourced rather than done reactively. Measure it in weeks of work by dividing outstanding labour hours by the labour hours available in a normal week. A few weeks per trade is commonly treated as workable, though this is a rule of thumb rather than a standard. What matters more is whether it is growing, and whether statutory tasks are sitting inside it.
What is the difference between urgent and important maintenance work?
Urgency is about how soon a consequence arrives. Importance is about how serious that consequence is. A blocked sink is urgent to the person who reported it but rarely important. A corroding support bracket on a critical asset is important but may not be urgent this week. Prioritisation goes wrong when the two are collapsed into a single judgement, because visible and immediate problems then consistently displace serious ones that have not yet surfaced.
Do small businesses need a formal prioritisation system?
The formality should match the scale, but the principle applies at any size. A business with thirty assets and one maintenance person does not need a weighted scoring matrix, though it does need an agreed view of which assets matter most and which tasks are legally required. A single page setting out criticality bands, priority definitions and response targets is usually enough, and it becomes valuable the moment the person holding it all in their head is unavailable.
Conclusion
Knowing how to prioritise maintenance jobs comes down to a handful of disciplines rather than a complicated system. Rank assets by the consequence of their failure before you start ranking individual jobs. Separate urgency from importance so that visible problems do not automatically displace serious ones. Ring-fence statutory and contractual work rather than letting it compete with discretionary requests. Deal with the existing backlog as a one off exercise, then protect planned capacity so it does not rebuild.
Above all, write the method down and give one person responsibility for applying it. A prioritisation scheme that exists only as shared instinct cannot be handed over, challenged or defended when something goes wrong. If your current approach relies on memory, spreadsheets and persistence, it may be worth looking at how maintenance management software could give the whole team a single, visible view of what matters most.
Further Reading and Official Guidance
The following sources provide authoritative UK guidance on the legal duties referred to in this article. Requirements vary by sector, equipment and premises, so check what applies to your own circumstances.
Disclaimer
The information in this article is intended for general guidance only and does not constitute professional legal, financial, or regulatory advice. Always consult a qualified professional for advice specific to your circumstances.
