SLA compliance is usually treated as a field execution problem. It isn’t. Most of the time, the clock is running and nobody is working the job. The gap is in scheduling and preparation, not in the field.
Most operators think of SLA compliance as a field problem. The engineer is either on time or they aren’t. The installation either completes within the committed window or it doesn’t. If SLAs are being missed, the answer must be more engineers, or faster engineers, or better routing.
This is wrong. Or rather, it’s incomplete in a way that leads to expensive solutions for symptoms while the root cause continues untouched.
SLA time doesn’t start when the engineer leaves the exchange. It starts when the order is confirmed — sometimes days before an engineer is even assigned. Everything that happens in that gap is SLA time and most of it is invisible in the standard reporting that operators use to track their performance.
Where the time actually goes
Walk through a typical residential installation order and map when the SLA clock is running versus when anyone is actively working the job.
Order confirmed on Monday morning. The provisioning system validates it — a few minutes. The job goes into the scheduling queue — immediately. The scheduler picks it up on Tuesday afternoon and assigns an engineer for Thursday. That’s thirty hours of SLA time that passed while the job sat in a queue. Nobody missed a target. Nobody failed at anything. The job just waited.
Thursday morning. The engineer is briefed, collects equipment, drives to the address. Forty-five minutes of travel. Rings the bell. The customer isn’t home. Abortive visit. Job goes back into the queue. Rescheduled for Friday. Another twenty-four hours of SLA time. Another queue.
Friday. Engineer completes the job. SLA measured from Monday order confirmation to Friday completion: four days. SLA target: three working days. Miss.
How much of that four days was active work? Maybe three hours. The rest was queue time, scheduling lag and one abortive visit. The engineer wasn’t the problem. The preparation and scheduling were.
“SLA time doesn’t start when the engineer leaves the depot. It starts when the order is confirmed — and most of what happens in between is invisible in standard SLA reporting.”
The scheduling lag nobody measures
The time between an order being ready to schedule and an engineer being assigned is rarely tracked as a distinct metric. It gets absorbed into the overall SLA figure and reported as a field performance issue. This misattribution matters because it directs remediation at the wrong place.
When scheduling lag is the primary driver of SLA misses, the solutions are: faster scheduling decisions, more available engineer slots in the near-term horizon and automated scheduling that eliminates the queue entirely. None of these require more engineers. They require a scheduling system that acts immediately when an order is ready, not when someone gets to it.
The abortive visit multiplier
An abortive visit doesn’t just waste the time of the failed visit. It resets the scheduling clock. The job goes back into the queue. In a busy scheduling environment, “back into the queue” means available time slots that are now a day or two out, not the same afternoon. A single abortive visit commonly adds two to three days to a job’s completion time.
For operators missing SLA targets, calculating the proportion of misses that involved at least one abortive visit is usually instructive. The number is typically high enough to suggest that reducing abortive visits would have more impact on SLA compliance than any other single intervention.
Appointment reminders are the obvious first step. Less obvious but equally important is the question of why abortive visits happen when the customer was supposedly available. Often it’s because the appointment window communicated to the customer doesn’t match the slot in the scheduling system, because the communication came from a different system than the one that held the booking. Integration again.
What good SLA management looks like
The operators with the best SLA compliance rates tend to share a few characteristics that go beyond just having enough engineers.
They schedule automatically and immediately. When an order is validated and ready to schedule, the scheduling system assigns it without waiting for a human to pick it up. The queue time between “ready to schedule” and “engineer assigned” is minutes, not hours or days.
They track lag separately. Scheduling lag, customer-caused delays, and field execution time are measured independently. SLA misses can be attributed to their actual cause rather than being reported generically as field performance issues.
They manage the abortive visit as a metric. The abortive visit rate is tracked, reported and driven down actively — through appointment reminders, customer confirmation workflows and better job information that reduces the category of abortive visits caused by incorrect site data.