Field service work scheduling for reactive and planned work

Every field service team runs two businesses at once. One is planned: servicing contracts, inspections, maintenance programmes and installations booked days or weeks ahead. The other is reactive: breakdowns, leaks, faults and urgent callouts that arrive whenever they like. Both need the same engineers, the same vans and the same hours in the day. 

Most of the friction in field service work scheduling comes from trying to keep those two worlds apart. This sector guide looks at each type of work on its own terms, explains why splitting them causes so many problems and sets out the principles, setup steps and measures that let reactive and planned work share one schedule without either one losing out. 

Key takeaways 

• Reactive and planned work competes for the same capacity, so managing them in separate diaries creates clashes, idle time and missed SLAs. 
• One schedule beats two. When both types of work sit together, planned jobs can flex around urgent ones in a controlled way. 
• Not all work is equally flexible. Good field service work scheduling knows which jobs can move, which cannot and by how much. 
• Real-time re-planning is what makes it work. A plan built once at 7am cannot cope with the callouts that arrive at 10am. 
• Keep your existing systems. A scheduling engine can sit alongside your job management platform rather than replace it. 

Know your work: a quick field guide 

Before deciding how to schedule anything, it helps to be clear about what each type of work actually needs. Field service work scheduling gets much easier once these are clear. Most field service and maintenance teams handle some mix of the six below, and each behaves differently when the day gets busy. 

Reactive work 

Breakdowns, faults and emergencies with little or no notice. Priority and SLA deadlines matter most, and the right skills need to arrive quickly. Reactive work is the least predictable part of the day and the most likely to disrupt everything else. 

Appointed work 

Visits booked with a customer for an agreed window. The promise to the customer is the fixed point, so the schedule has to protect the slot even when other work moves. How those windows are configured makes a real difference to cost, as MoreIQ’s analysis of optimised appointments shows. 

Planned maintenance 

Routine servicing and maintenance agreed in advance, often under contract. It usually has a window of days or weeks rather than hours, which makes it the natural buffer when reactive demand spikes. 

Preventative and cyclical work 

Recurring inspections, safety checks and statutory testing that must happen within set intervals. There is some flexibility on the exact day, but hard compliance deadlines sit behind it. 

Project work 

Larger jobs that run over several days or need several trades in sequence. Dependencies matter here: the second trade cannot start until the first has finished. 

Follow-on visits 

Return trips for parts, second opinions or work that could not be finished first time. They are often avoidable, and each one takes capacity away from new work. 

MoreIQ supports all of these work types in one place. You can see how on its field service scheduling software page. 

Why separate diaries cause so many problems 

Many teams split reactive and planned field work into separate diaries, separate teams or even separate systems. It feels tidy. In practice, it creates a constant tug of war, and it is the single biggest reason field service work scheduling feels harder than it should. 

Double booking the same people 

When the reactive desk and the planned maintenance team both book the same engineer, someone loses. Usually it is the planned visit, which gets cancelled at short notice and has to be rebooked, often more than once. 

Ring-fenced teams that sit idle 

Some organisations dedicate engineers to reactive work only. On a quiet day those engineers have little to do. On a busy day there are not enough of them, and planned engineers get pulled across anyway. 

Travel that makes no sense 

Two engineers from two diaries can end up working on the same street at the same time, or one can drive across the patch to an emergency while a colleague doing planned work is five minutes away. 

SLAs that depend on luck 

When nobody can see the whole picture, SLA performance comes down to how busy the reactive desk happens to be that day. Housing providers face exactly the same challenge, as this piece on managing reactive and planned repairs in a single schedule explains. 

Five principles for one schedule that works 

Bringing reactive and planned field work together is not just about putting every job in the same list. It needs a few clear rules so the schedule knows how to balance competing demands. These five principles sit behind most successful setups. 

1. Give every job a clear priority and a real deadline 

A boiler breakdown for a vulnerable customer and a routine annual service are both jobs, but they are not equal. Each job should carry a priority and an SLA or compliance deadline the schedule can see and respect. 

2. Decide how much each job can flex 

Some work can move by a week without anyone noticing. Some can move by a few hours. Some cannot move at all. Recording that flexibility is what allows planned work to make room for emergencies without breaching its own deadlines. 

3. Optimise across the whole team, not each diary 

When jobs can move between engineers, the schedule can find the best person for an urgent callout rather than whoever is free. In one example from MoreIQ’s review of route optimisation versus global optimisation, average travel between jobs fell from 1 hour 4 minutes to 33 minutes per technician once work could be reassigned across the team. 

4. Re-plan continuously, not once a day 

A plan built overnight is out of date by mid-morning. Field service work scheduling has to keep reworking the day as callouts land, jobs overrun and customers cancel. That means real-time reactiveness rather than a batch run. 

5. Keep planners in control 

Automation should handle the thousands of small decisions. Planners should still be able to lock jobs, override choices and see why the system did what it did. Trust in the schedule depends on it. 

What happens when an emergency lands 

It is worth walking through how a unified schedule handles the moment that causes most of the stress: an urgent job arriving in the middle of a busy day. 

• The job is raised in your job management system or the contact centre, with priority and SLA attached. 
• The engine looks at the whole team, checking skills, location, current progress and what each engineer has left to do. 
• It finds the best fit. Often that is the nearest qualified engineer finishing a planned visit nearby. 
• Planned work flexes where it safely can. A routine service with a two-week window might move to tomorrow. An appointment with a customer waiting stays put. 
• Everyone is updated in real time. Engineers see their revised day, and any customer whose visit has moved is notified straight away. 

This is mobile field service scheduling at its most useful. The whole process takes moments rather than a string of phone calls. MoreIQ’s explainer on dynamic resource scheduling describes the capabilities behind it, from continuous background optimisation to support for dependencies and multi-day jobs. 

Common mistakes to avoid 

Even with the right tools, a few habits can undermine field service work scheduling. These are the ones that crop up most often. 

• Treating every job as urgent. If everything is a top priority, nothing is. Be honest about which work genuinely cannot wait. 
• Leaving no room for reactive demand. Booking planned work into every available minute guarantees cancellations later. Good optimisation fills gaps intelligently rather than leaving them empty or overfilling the day. 
• Ignoring travel when choosing who goes. The first free engineer is rarely the best choice if they are on the other side of the patch. This guide to reducing field service travel time explains why sequencing matters so much. 
• Letting skills and parts data go stale. The schedule can only send the right person if it knows who has which certifications and what is on each van. 
• Measuring reactive and planned performance separately. Look at both together, or you will miss the trade-offs between them. 

Where this matters most 

Almost every field team runs some mix of reactive and planned field work, but the pressure shows up differently from sector to sector. 

Maintenance and facilities contractors 

Contracts usually come with tight reactive SLAs alongside planned preventative maintenance schedules. Good field service work scheduling protects both, and gives contract managers the evidence they need at review time. 

Installers and service engineers 

Customer appointments for installations and servicing sit alongside breakdown callouts. Keeping appointed visits on time while absorbing faults is the daily balancing act. 

Housing and property teams 

Responsive repairs, voids, servicing, compliance checks and capital works all draw on the same trades. MoreIQ’s housing and property solution covers that side in more detail. 

Setting it up: a practical checklist 

You do not need to transform everything at once. Most teams get the best results by starting small and expanding once the approach is proven. 

Before you start 

• Agree priority levels and SLA deadlines for each work type. 
• Record how far each type of planned work can flex. 
• Clean up skills, certification and territory data for every engineer. 
• Capture a baseline for SLA performance, travel time and jobs completed per engineer. 

During the pilot 

• Choose one region or contract where reactive and planned work regularly clash. 
• Bring both types of work into a single field service scheduling engine built for mobile field service scheduling. 
• Connect it to your existing job management system through APIs, so engineers keep the apps they know. 
• Check in weekly with planners and engineers to fine-tune the rules. 

After the pilot 

• Compare results against your baseline and share them openly. 
• Roll out region by region, adjusting rules for local needs. 
• Review priorities and flexibility rules every few months as contracts change, so your field service work scheduling keeps pace with the business. 

Measuring success across both types of work 

The point of unified field service work scheduling is better performance across reactive and planned work, not one at the expense of the other. These measures help you see whether it is working. 

• SLA performance for reactive work, especially on the busiest days. 
• Planned work is completed on time, and how often it has to be rebooked. 
• Travel time per job across the whole team. 
• Jobs completed per engineer per day. 
• Backlog size and average completion time. 
• Customer satisfaction with both repair speed and appointment reliability. 

Raven Housing Trust gives a sense of what is possible. As the Raven Housing case study sets out, completed works orders rose by 26%, absorbing 16% more demand without extra staff. Average job completion time fell from 27 to 15 days and the backlog came down from 2,500 to around 1,500 jobs. 

Bring reactive and planned work into one schedule 

If your reactive and planned teams are still pulling against each other, there is a better way. MoreIQ’s real-time scheduling engine brings every type of field work into one schedule and works alongside the systems you already use. 

Book a call with MoreIQ and let’s discuss how one schedule could protect your SLAs across reactive and planned work.