A job priority matrix is a grid that ranks work against two criteria, so you can see what to do first, what to schedule, what to hand on and what to drop. The two most common versions compare urgency with importance, or impact with effort. For a service business, the best version adds a third question the textbooks skip: what happens if this job is late, legally or contractually?
This guide explains both standard models, shows how to build a matrix in six steps, and then adapts it to engineers, SLAs and compliance work, where a wrong call costs more than a missed to-do item.
TL;DR
- A job priority matrix plots each task against two criteria. Urgency and importance tells you what to do now. Impact and effort tells you which work is worth the resource.
- Urgent is not the same as important. Pressure from outside is not proof that a job matters.
- For field service, replace generic axes with ones that reflect your reality: safety or compliance risk, SLA clock, and customer or asset criticality.
- Agree the criteria with the people who deliver the work, and review the ranking regularly, because a matrix is only as good as its last update.
- A matrix helps most when the same scoring runs inside your scheduling and dispatch, not on a separate sheet.
Table of Contents
- What a job priority matrix is and what it is for
- The two matrices most people mean
- How to build a job priority matrix in six steps
- A worked example for a service team
- Why a generic matrix falls short for field service
- A field service version you can adopt
- Common mistakes and how to avoid them
- Our perspective: a matrix should live where the work lives
- Putting your matrix into a system
- FAQ
- Sources
What a job priority matrix is and what it is for
A priority matrix is a visual chart that ranks tasks or projects against criteria you choose. Smartsheet's guide to priority matrices describes them as a way to rank upcoming work, support project selection, delegation and planning, and create a shareable record that improves visibility for stakeholders and helps them reach consensus.
That last point matters more than it first seems. The chart itself is simple. Its real value is that a decision which used to live in one manager's head is now visible, so the team can challenge it, understand it and repeat it.
Matrices come in different sizes. Asana's guide notes that a matrix can be a simple four-quadrant grid or a complex grid with 20 or more rows and columns. Complex grids give more precision, simple ones are faster. For most service teams, the simple grid wins until you have a clear reason to add detail.
The two matrices most people mean
When people search for a job priority matrix, they usually want one of two models. They answer different questions, so it helps to know which you need.
The Eisenhower matrix: urgency and importance
The University of Hull's guide to priority matrices defines importance as direct contribution to your goals, and urgency as the need for immediate attention, often driven by external pressure and immediate consequences. Crossing the two gives four quadrants:
| Urgent | Not urgent | |
|---|---|---|
| Important | Do first | Schedule |
| Not important | Delegate or delay | Ignore or remove |
The central warning in the Hull guide is not to confuse immediate pressure with genuine importance. A customer chasing by phone feels urgent. Whether the job matters is a separate question.
The Local Government Association's time-management factsheet makes a practical point about the top-right box: concentrating on important but non-urgent work reduces the chance that tasks later become both urgent and important. It also says that a diet of constant urgent work, or leaving tasks until the last minute, is stressful. In field service terms, planned preventive maintenance is the important but non-urgent work. Skip it, and it returns as an emergency call-out.
The action-priority matrix: impact and effort
The second model compares expected impact with the effort required. According to a comparison of the two approaches, the Eisenhower matrix triages time-sensitive work, while the action-priority matrix selects valuable work using expected impact and required effort. In other words, one decides what to do now, the other decides what is worth doing with limited resource.
The Hull guide gives the four boxes names that travel well:
- Quick wins: high impact, low effort. A short job, or a sub-task of a bigger one.
- Major projects: high impact, high effort. Worth doing, but they need planning.
- Fill-ins: low impact, low effort. Housekeeping or preparatory tasks for slack moments.
- Thankless tasks: low impact, high effort. Candidates to drop.
Use urgency and importance when the question is sequence: what do we do today? Use impact and effort when the question is selection: which of these improvement projects, contract bids or backlog items deserves our limited time?
How to build a job priority matrix in six steps
The method is consistent across the guidance. Asana's version is to list the work, choose two variables, label the axes, score or place each task, and then turn the result into an action plan with goals, resources, deadlines, milestones and regular review. Here is that process made concrete.
- List everything in one place. Include the awkward items: the quote nobody has chased, the recurring inspection, the stock reorder. If a job is not on the list, it cannot be ranked.
- Compare like with like. A team prioritisation guide from Atlassian recommends comparing work at a similar scale, tasks with tasks and projects with projects. Ranking a ten-minute callback against a depot refit on one grid produces nonsense.
- Pick two criteria tied to your goals. Nielsen Norman Group's guidance on prioritisation matrices says criteria should derive from the overall goals and business needs of the project. For a service firm, that means your SLA commitments, safety duties and margin, not generic labels.
- Score on a simple scale. The Hull instructions use 0 to 10 for impact and for effort, with 0 meaning none and 10 meaning maximum. Asana's example uses a five-level scale and multiplies the levels: required urgency (5) and medium effort (3) gives a priority score of 15. Either works. Qualitative or numeric scales are both fine, as the NN/g guidance notes.
- Place the jobs and argue about them. The prioritisation play from Atlassian asks teams to place work on the grid relative to a shared goal, then discuss and move items until the group agrees on the distribution. This discussion is where the value is. NN/g makes the same point: the conversation behind each placement helps balance time and resource against user needs.
- Draw the line and say what you will not do. Atlassian's perspective is that a matrix fails when everything lands in the top quadrant. Agree explicitly what gets delayed or dropped. Its guide suggests limiting must-have work to about 40% of team capacity and nice-to-have work to about 30%, leaving room for requests and unexpected work. Treat those percentages as a starting point to test, not a rule.
A worked example for a service team
The example below is an illustration of the method, not data from a real business. A maintenance office has seven open jobs on a Monday morning. It scores urgency from 1 to 5 and effort from 1 to 5, then sorts by urgency score, using effort to break ties in favour of quick work.
| Job | Urgency (1-5) | Importance | Effort (1-5) | Quadrant | Decision |
|---|---|---|---|---|---|
| No heating at a care home | 5 | High | 3 | Urgent and important | Dispatch now |
| Annual inspection due in 10 days | 3 | High | 2 | Important, not urgent | Book into this week |
| Customer chasing a minor quote | 4 | Low | 1 | Urgent, not important | Office replies today |
| Replace worn door closer | 2 | Medium | 2 | Important, not urgent | Add to planned route |
| Reorganise van stock labels | 1 | Low | 2 | Neither | Fill-in |
| Repaint plant room signage | 1 | Low | 4 | Neither | Drop for now |
| Fault found on a lift check | 5 | High | 4 | Urgent and important | Escalate, plan parts |
Three things stand out. The customer chasing the quote feels urgent but is not important, so the office handles it without pulling an engineer. The inspection is not urgent today but has a legal deadline approaching, so it is scheduled before it becomes a crisis. And the signage job, high effort for little gain, drops out entirely.
Why a generic matrix falls short for field service
The textbook matrices were written for personal to-do lists and project teams. They are a sound starting point, but a service business has constraints they ignore.
Some deadlines are not negotiable. A certificate expiry, a statutory inspection interval or a contractual response time is not just urgent, it carries legal or financial consequences. If your scoring treats these as one factor among many, a strong score elsewhere can bury them.
Effort is not one number. The same job takes different effort depending on whether the right engineer, with the right competence, is nearby with the right part in the van. Effort in field service depends on skills, location and stock. Our guide to an engineer competency matrix covers the skills side.
The clock keeps running. Priorities shift hourly. An emergency lands at 10:15 and the whole day's ranking changes. A matrix on a spreadsheet goes stale the moment it is saved.
Too much method is a cost. The AABB quality-tool guide lists two limitations worth remembering: a matrix can take too long for simple projects, and building one gets more complex as the number of options grows. If you are ranking three jobs, use your judgement. Use the matrix for the backlog, not for every phone call.
A field service version you can adopt
Keep the four-box shape, but change the axes and add a hard override.
Step one: set override rules first
Before any scoring, decide which jobs bypass the matrix. Typical candidates are risk to life or safety, an asset that is unsafe to use, and a job about to breach a contractual SLA. These go straight to dispatch. Write the rules down so everyone applies them the same way.
Step two: score the rest on consequence and time
For everything else, use two axes that mean something in your business:
- Consequence of delay: compliance exposure, SLA penalty, customer or site criticality, and the chance the fault gets worse.
- Time to act: how long until the deadline, the SLA clock or the next planned visit.
Plot jobs the same way as an Eisenhower grid. High consequence and short time to act go first. High consequence and long time to act get booked into planned routes. Low consequence and short time to act go to the office or a quick remote fix. Low on both gets batched.
Step three: add effort when you allocate, not when you rank
Once the order is clear, use effort, skills and location to assign. This is where scheduling and dispatch come in. Our walkthroughs of work order prioritisation and priority-based scheduling show how to turn a ranked list into routes, and the engineer scheduling checklist covers the planner's side.
Step four: review on a rhythm
The Government Digital Service's guidance on deciding priorities suggests regular review, for example weekly for a sprint backlog or quarterly for a roadmap, drawing on performance analysis, user research and stakeholder input. For a service team, a daily check of the live list, a weekly look at the backlog and a quarterly look at your criteria is a sensible rhythm. The same guidance says no single method suits every situation, and teams may need to try several. Your matrix should change when your contracts or capacity do.
Common mistakes and how to avoid them
- Letting the loudest customer set the order. Pressure is not importance. Score against agreed criteria, not volume.
- Putting everything in the top box. If most jobs are urgent and important, the criteria are too loose. Tighten the definition until the top box is small.
- Building it alone. The UK government's prioritisation guidance says prioritisation should balance value, user needs, risks, dependencies and organisational alignment, and should be an evidence-based decision rather than a ranking exercise. Involve the engineers and supervisors who know how long jobs really take.
- Over-engineering the estimate. The same guidance says estimation effort should be proportional to the size of the task. A five-minute job does not need a five-minute debate.
- Never revisiting it. A stale matrix is worse than none, because it looks authoritative.
- Ignoring the important-but-not-urgent box. This is where preventive maintenance and compliance renewals live. Neglect it and it feeds the urgent box next month.
Our perspective: a matrix should live where the work lives
Curcle was born inside a real UK service and engineering business, and the pattern we saw there was consistent. The ranking was usually sound. The trouble was that it lived in someone's head, or on a sheet, while the jobs, assets, certificates and engineers lived in four other places.
So we hold three views. First, compliance cannot be one score among many. It belongs in the backbone, so an expiring certificate or an SLA clock surfaces without anyone remembering to look. Second, software should help a business see what needs attention, not just record what has already happened. Third, AI should assist and not replace human judgement: a system can flag that a job is about to breach, but a dispatcher who knows the site decides what to do.
A matrix is a good thinking tool. It becomes a good operating tool when the scoring, the schedule and the evidence trail share one source of truth.
— Luke Herridge
Putting your matrix into a system
If your team already ranks jobs this way, the next step is removing the manual copying. Curcle brings jobs, customers, engineers, assets, compliance, stock, quoting and invoicing into one connected system, with an offline-capable mobile app for engineers and role-based dashboards for the office. You can see how the pieces fit on the product page, and the Operations Room shows how live service decisions are surfaced.
Plans start from £99 a month for Starter, £249 a month for Professional and £499 a month for Business, with Enterprise priced on request. Full details are on the pricing page. If you want to estimate what better prioritisation could be worth to you, try the field service savings calculator.
FAQ
What are the main types of job priority matrix?
The two most common are the Eisenhower matrix, which compares urgency and importance, and the action-priority matrix, which compares impact and effort. Use the first to decide what to do today and the second to choose which projects or improvements deserve limited resource. Larger grids with many rows and columns exist, but they take longer to build and maintain.
What is a good example of a priority matrix?
A simple one is a four-box grid for an inspection backlog: a gas leak call goes in urgent and important, a certificate due next month goes in important but not urgent, a chasing email goes in urgent but not important, and tidying the stores goes in neither. In the action-priority model, a short sub-task of a larger job is a quick win, while a high-effort, low-impact job is a thankless task you may drop.
How often should I review my priorities?
Match the review to how fast your work changes. Government guidance suggests weekly for a sprint backlog and quarterly for a roadmap. For a service team, check the live job list daily, the backlog weekly and the scoring criteria quarterly, or whenever a major contract or capacity change arrives.
Is a priority matrix too slow for emergency work?
Yes, if you use it on every call. Set override rules in advance for safety risks and imminent SLA breaches, so those jobs go straight to dispatch. Use the matrix for everything else, where a few minutes of structured ranking saves rework later.
Sources
- Priority matrices, Introduction to university study (University of Hull)
- Deciding on priorities, GOV.UK Service Manual
- Principle 4: Prioritise with your roadmap, Deliver Good Services
- Time management factsheet, Local Government Association
- Using prioritization matrices to inform UX decisions, Nielsen Norman Group
- Quality tool: prioritization matrix, AABB
- How to use priority matrices
- Priority matrix: prioritise tasks by impact and effort
- Action priority matrix vs Eisenhower matrix
- Prioritization matrix team play