Skills based scheduling means choosing who attends a job by what they can demonstrably do, not by their job title or who happens to be free. For a UK engineering or compliance business, that means every job carries its requirements (a gas appliance check, an EICR, a LOLER thorough examination) and the scheduler can only offer engineers whose recorded, in-date competence covers them. Done properly, it cuts wasted visits, protects you in an audit and stops the same two experienced people being sent everywhere.
This guide explains the idea, the data you need, how matching works in practice, and where UK rules make it more than a nice-to-have.
TL;DR
- Skills based scheduling assigns work using recorded skills, certifications and availability rather than job titles or habit.
- It only works if skill records carry evidence, an assessor and an expiry date, and someone owns keeping them current.
- In the UK, regulated work such as gas, electrical and lifting equipment makes competence a legal and audit issue, and working-time limits are a second constraint on any rota.
- Start small: a short skills list, a handful of hard rules, and a weekly review of failed or reassigned jobs.
- Curcle holds jobs, engineers, assets and compliance in one system, so the skills data and the schedule are not kept in separate places.
Table of Contents
- What skills based scheduling actually is
- Why scheduling is about more than filling a diary
- How matching works in field service and engineering
- What you need to record about each engineer
- Keeping skill records defensible
- A worked example
- Mistakes to avoid when introducing it
- Our perspective
- Where Curcle fits
- FAQ
- Sources
What skills based scheduling actually is
The general idea comes from workforce strategy. Deloitte describes skills-based models as using skills rather than jobs to decide who performs work, treating each worker as a portfolio of capabilities that can be deployed to matching work.
In field service the same principle gets very practical. "Engineer" is not one thing. Within a ten-person team you might have:
- two people qualified for commercial gas work,
- three who can sign off electrical periodic inspections,
- one with F-Gas certification,
- four who can do routine planned maintenance but nothing regulated,
- one apprentice who must be paired with someone.
Assigning by title ("send an engineer") ignores all of that. Assigning by skill filters the pool first, then lets you optimise on distance, priority, availability and workload among the people who can legitimately do the job.
How it differs from role-based and availability-based scheduling
| Approach | Question it answers | Typical failure |
|---|---|---|
| Role-based | Who has the right job title? | A title says nothing about specific certificates or experience |
| Availability-based | Who is free and nearby? | The nearest engineer arrives without the right qualification |
| Skills based | Who is competent, in date and free? | Fails only if skill records go stale |
The third approach does not replace the other two. Proximity and availability still matter; skills are the first gate they pass through.
Why scheduling is about more than filling a diary
Workforce scheduling is generally described as getting the right people to the right place at the right time while accounting for demand, compliance, availability and skills. UKG's UK white paper frames the purpose of labour scheduling in those terms, and it also argues that poor scheduling can reduce productivity, raise labour costs and contribute to staff leaving.
For a service business those costs show up as:
- Aborted visits. The engineer arrives, finds the job needs a certification they do not hold, and leaves.
- Repeat visits. A second attendance means a second travel cost and a customer who is already annoyed.
- Compliance exposure. Work done by someone who cannot show competence is hard to defend.
- Burnout and imbalance. If only a few people are "trusted" for certain jobs, they carry the load.
Scheduling software that enforces skills, certifications and working-time rules is a standard feature of workforce management tools. ADP notes that scheduling can use skills, certifications, experience and availability to staff efficiently and enforce rules such as maximum hours or minimum rest between shifts.
How matching works in field service and engineering
Good matching is a sequence of filters, not a single clever algorithm. Here is how it plays out for a typical job.
- The job declares what it needs. A boiler service at a commercial kitchen needs gas competence for commercial catering appliances. A fire alarm test needs a fire safety qualification. A lift-related inspection needs a competent person for lifting equipment. The requirement is attached to the job type or the asset, so a planner does not have to remember it.
- Hard rules remove ineligible engineers. No in-date certificate, no match. This is where legal requirements live. For example, registering with Gas Safe Register is a legal requirement for anyone carrying out gas work in the UK, so a gas job should never be offered to someone who is not registered.
- Availability and working time narrow the pool. Leave, existing jobs, travel time and working hours all apply. Acas explains that under the Working Time Regulations 1998 workers generally must not work more than 48 hours a week on average, usually calculated over 17 weeks. Emergency call-outs and overtime make this easy to breach quietly if nobody is counting.
- Soft preferences rank what is left. Proximity, familiarity with the site, parts already in the van, customer history and workload balance decide between the remaining candidates.
- Priority and SLA decide the order. If two jobs compete for the same engineer, the one with the tighter SLA wins. Our guide to priority based scheduling covers how to rank jobs so SLA breaches fall.
The point of the order is that a skills gap is never traded off against convenience. Distance can be a tiebreaker; competence cannot.
What you need to record about each engineer
The scheduling logic is only as good as the data behind it. The research on competence in UK industries points to a consistent shape.
The Building Engineering Services Association's competence guide for the Building Safety Act uses a framework called SKEB: skills, knowledge, experience and behaviours. BESA advises contractors to maintain evidence of those four things and to capture the competence requirements of each activity, so decisions about who is competent to do what can be supported. The government's Mandatory Technical Competence framework uses the same building blocks, adding continuing professional development.
Translated into a skills record for a field engineer:
- Qualifications and registrations: Gas Safe, electrical inspection and testing qualifications, F-Gas, LOLER, water hygiene and so on, with certificate numbers.
- Scope: what the qualification actually covers. "Gas Safe" is not one competence; categories of appliance differ.
- Experience: equipment types and sectors they have worked on, such as commercial catering or HVAC.
- Behaviours and working practices: whether they follow method statements, write accurate records and take safe-working steps. Skills England's engineering operative standard lists statutory, quality and health and safety compliance knowledge, diagnostics and maintenance to defined procedures among the capabilities expected of the role.
- Supervision status: whether they can work alone, and who can sign them off.
- Evidence and dates: when the skill was assessed, by whom, and when it expires.
Why "has a certificate" is not enough
BESA is explicit that qualifications alone do not give the full picture of whether someone can undertake particular work, and recommends a proportionate approach that records evidence, allocates work according to demonstrable competence and reviews it over time. A newly qualified engineer and a fifteen-year veteran may both hold the same certificate, yet you may reasonably want only one of them on a complex boiler house. That judgement belongs in the record, as a skill level or a sign-off, not in a planner's memory.
We go deeper on structuring this in our piece on an engineer competency matrix for field operations, including alerts ahead of expiry.
Keeping skill records defensible
The fastest way to make skills based scheduling useless is to let the records go stale. An out-of-date matrix gives false confidence, which is worse than no matrix.
The Office of Rail and Road is a useful benchmark here. Its guidance says competence records should identify the activity, the standard, the assessor and the expiry date, and be maintained so they can be verified and audited. Rail is a different sector, but the logic carries over to any compliance-led service business: a record that cannot say who assessed a skill, against what standard and until when is hard to rely on.
Practical habits that work:
- Give every skill an owner. Usually the service manager or compliance lead, not whoever last had a spare hour.
- Set expiry alerts at 90 and 30 days. Enough time to book renewal before the engineer drops out of the eligible pool.
- Block, don't warn. When a certificate lapses, the system should stop offering that engineer for the related jobs rather than flagging it for someone to notice.
- Capture evidence at source. Scans of certificates, assessment notes and supervised-job sign-offs go on the engineer's record, not in an inbox.
- Review after misses. Every aborted or reassigned job is a data point: was a requirement missing from the job, or a skill missing from the engineer?
- Keep an audit trail. Who changed a skill, when and why should be answerable. Our guide to embedding compliance in field service operations covers audit-ready practice in more depth.
A worked example
Imagine a 25-engineer mechanical and electrical contractor with a commercial catering client base. At 7:40am a walk-in freezer fault comes in with a four-hour SLA. The same morning, a planned gas safety check, an EICR and a fire alarm service are on the board.
Without skills data, the planner scans a spreadsheet and phone contacts, rings two engineers and finds one is on leave. With skills based scheduling:
- The freezer job requires refrigeration competence, with F-Gas certification as a hard rule.
- Six engineers hold it. Two are on leave and one is already past his weekly hours for the reference period, leaving three.
- Of those, one is 12 minutes away and finishing a job, one is across town, and one has the parts in the van from yesterday's visit.
- The system ranks them, the planner confirms, and the job is dispatched with the site history and asset record attached.
The planner has made one judgement call, not five lookups. The scenario is illustrative, but it is the daily reality the approach is meant to remove. Our engineer scheduling checklist walks through the planner side of this in detail.
Mistakes to avoid when introducing it
- Starting with 200 skills. Begin with the 15 to 25 that actually gate work: regulated qualifications and a few equipment categories.
- Treating skills as static. People gain experience and lose certificates. Build review into the calendar.
- No override trail. Sometimes a manager will override a rule in an emergency. Allow it, but record who did it and why.
- Ignoring working time. Skills-rich engineers are the ones most likely to be overloaded. Count hours against the 48-hour average limit, and check any opt-out arrangements with your HR adviser.
- Hiding the logic from engineers. If people understand why they are sent to certain jobs, and how to earn sign-off for more, the matrix becomes a development tool instead of a restriction. Competence frameworks such as the UK CAA's guidance on approved organisations stress planning staff availability, documented control of competence and recorded training for exactly this reason.
- Keeping skills in one tool and jobs in another. Anything that needs a manual re-key will drift.
Our perspective
We built Curcle out of a real UK service and engineering business, and the lesson that stuck is that scheduling problems are rarely scheduling problems. They are information problems. The engineer's certificate is in one folder, the asset history is in another, and the planner's knowledge of who is "good on boilers" is in their head.
So we do not think of skills based scheduling as a clever dispatch feature. We think of it as what happens when jobs, engineers, assets and compliance sit in one connected system. The job knows what it requires, the engineer's record knows what they can evidence, and the schedule simply respects both.
We also hold to two principles. Every click should earn its place, so a planner should not have to go hunting for competence information. And software should assist human judgement rather than replace it: it can rule out an engineer who is not in date, but a manager decides whether a newly qualified engineer is ready for a complex site.
— Luke Herridge
Where Curcle fits
If your skills, jobs and certificates currently live in a spreadsheet, a diary and a shared drive, Curcle brings them into one place. Engineers, assets, compliance records, scheduling, quoting and invoicing work from the same information, with a mobile app for the field and role-based dashboards for the office. You can see how it fits your trade on our field service management software page, or compare plans on the pricing page: Starter is from £99 per month, Professional from £249 per month and Business from £499 per month, with Enterprise on request.
FAQ
What is the difference between skills based and skill based scheduling?
None in practice. Both mean assigning work according to the capabilities people have rather than their job title or who is free. "Skills based" is the more common phrasing in UK writing, but the method is identical.
Does skills based scheduling slow dispatch down?
Not once the data is in place. The requirement is attached to the job, so the system filters the eligible engineers instantly and the planner picks from a short, ranked list. The slow part is the one-off effort of building the skills record, which is why we suggest starting with the skills that gate regulated work.
How often should engineer skill records be reviewed?
Certificates should be tracked against their expiry dates continuously, with alerts well ahead of renewal. Wider competence, such as experience level and supervision status, should be reviewed regularly and after any failed or reassigned job. Guidance from bodies such as BESA treats competence management as continuous and evidence-based, not a one-off exercise.
Is a qualification enough to prove an engineer can do a job?
For some regulated work a registration is a legal minimum, as with Gas Safe for gas work. But a qualification is only part of competence. Skills, knowledge, experience and behaviours all count, and your records should show the evidence for each.
Can small teams benefit, or is it only for large firms?
Small teams often benefit most, because competence sits in a few people's heads and holidays or sickness expose the gaps. A short skills list and a few hard rules is enough to start.
Sources
- Skills-based organizations, Deloitte Insights
- We Need to Talk About Labour Scheduling, UKG
- WFM Scheduling, ADP
- Registered Gas Engineer, regulated professions register
- Working Time Regulations, Acas
- Building Safety Act Competence Guide, BESA
- Mandatory technical competence framework, GOV.UK
- Engineering operative standard, Skills England
- Developing and maintaining staff competence, Office of Rail and Road
- AMC2 21.A.145(a) Approval Requirements, UK CAA