✦ Sector
Field service scheduling: what off-the-shelf tools get wrong
Field service scheduling software has to match the right engineer to the right job by skill, certification and location, hold that against an SLA, and cope when a job runs long or an emergency call comes in. Most off-the-shelf tools handle the calendar view well and the constraints badly.
Haystak · 11 August 2026 · Updated 11 August 2026 · 8 min read

Field service scheduling software assigns jobs to engineers based on their skills, certifications, location and availability, then keeps that plan workable as the day changes. It's a harder problem than a shared calendar, because a schedule that looks fine at 8am can be wrong by 9:15 when a job overruns or an emergency comes in.
The gap between what field service tools promise and what they actually deliver is usually in the constraints: skills matching, travel time, SLA priority and reallocation. Get those wrong and the software becomes a very expensive calendar.
Skills and certification matching
Not every engineer can do every job. Gas work needs a Gas Safe registration, electrical work needs specific qualifications, and some equipment needs manufacturer-specific training. A scheduler that only checks 'is this engineer free' rather than 'is this engineer qualified and free' will happily book the wrong person.
- Hard constraints - legal certifications (Gas Safe, electrical qualifications) that must never be overridden by the software.
- Soft constraints - preferred skills, like an engineer who's done that model of boiler before, which should influence but not block a booking.
- Expiry tracking - certifications lapse, and a scheduler that doesn't track expiry dates will keep offering an engineer who's no longer qualified.
This is one of the areas generic scheduling tools handle worst, because certifications and skill categories are specific to your trade and your compliance obligations, not a generic concept the software vendor modelled.
Travel time is not a rounding error
Many schedulers treat travel as a fixed buffer between jobs rather than something that varies by actual distance, traffic and time of day. In a rural patch or a city with predictable congestion, that difference is the gap between a realistic day and one that quietly falls behind by lunchtime.
| Approach | How it treats travel | Where it fails |
|---|---|---|
| Fixed buffer per job | Same gap regardless of distance | Overbooks engineers with spread-out patches |
| Straight-line distance estimate | Rough calculation, no road network | Underestimates rural or river-crossing routes |
| Live routing with traffic | Realistic drive time by time of day | Needs a mapping API and good address data |
SLAs and priority, not just first-come-first-served
Many field service contracts carry service level agreements - a four-hour response for a priority fault, next-day for routine work. A scheduler needs to know which jobs are against an SLA, what the clock is measured against, and to surface breaches before they happen rather than after.
Off-the-shelf tools often support a generic 'priority' flag but not a proper SLA clock tied to contract terms, which means someone still has to watch a spreadsheet to catch a breach in time to act on it.
Emergency reallocation
A schedule is a plan for a day that hasn't happened yet, and something always changes it - a job overruns, an engineer calls in sick, an emergency job lands. Good field service scheduling software reallocates the knock-on effects automatically or semi-automatically, rather than leaving a controller to manually re-sequence everyone by hand.
- 01Flag the change (overrun, cancellation, new urgent job) as soon as it's known.
- 02Recalculate affected engineers' remaining day against skills, SLA and travel constraints.
- 03Surface the proposed changes for a controller to confirm rather than silently rebooking customers.
- 04Notify affected customers automatically once confirmed, rather than leaving that to a phone call.
Parts on the van
A job can't be completed if the part isn't on the engineer's van, and a scheduler that ignores van stock will send the right engineer to the right job without the right part. This links scheduling to stock control - see our guide to stock control software for how multi-location stock, including mobile van stock, should be tracked as its own location rather than an afterthought.
Offline working
Engineers work in basements, rural areas and buildings with poor signal. A scheduling app that requires a live connection to show the day's jobs, log completion or update parts used will fail exactly where it matters - mid-job, out of signal, with a customer waiting.
A field service app worth using has to work offline and sync when signal returns, without losing or duplicating updates in the process. This is a genuinely hard engineering problem, and it's one of the areas where cheaper products cut corners.
Buy or build for field service scheduling
Off-the-shelf field service management products are a sound starting point for straightforward call-out work with simple skills and no complex SLAs. Where they fall short - certification-heavy trades, tight SLA contracts, or scheduling that has to account for van stock and offline working together - is where our field service software work tends to start.
If you're not sure which side of that line you're on, our guide to custom software vs off-the-shelf sets out the general trade-offs. Otherwise, get in touch with what your scheduling day actually looks like when something goes wrong.
✦ Where this fits
More on this from us: our work in field service software.