How one no-access stop becomes a route-margin problem
Follow one unavailable pest control stop from route departure to rebooking, then learn which records turn a missed visit into useful evidence for the GM.
The route leaves on time — and still loses a stop
A no-access service stop can look harmless on the route board: one small exception tucked between completed calls. Then it reaches payroll, rebooking, and the monthly forecast, where it turns out to have brought friends.
Here is one representative, illustrative quarterly-service incident, not company data. The technician leaves the depot at 9:42 on a residential route. The plan assigns this stop a 10:00–10:30 window and a $95 service value. At 10:12, the technician finds a locked gate; at 10:16, the customer does not answer a call. The technician records no access and leaves at 10:18 for the next stop.
At 10:23, the exception reaches the CSR queue. The CSR reaches the customer at 10:31, learns that a gate code is required, and rebooks the service for Tuesday, 10:00–10:30, with the code noted on the appointment. The work was not completed Monday, but technician time and vehicle use were real. That is where route profitability gets fuzzy if each role keeps only its own slice of the story.
Illustrative trail: 9:42 route departure → 10:12 arrival → 10:16 unanswered call → 10:18 departure → 10:31 customer contact → Tuesday 10:00–10:30 rebook → payroll inputs → GM forecast review.
The GM does not need dispatch to become accountants, or AP to play dispatcher. They need records that can meet in the middle.
At the doorstep, capture the failed stop
The technician records: “10:12 arrival; gate locked; called at 10:16, no answer; no safe alternate entry; 10:18 departure.” The outcome code is no access—gate code required. Arrival, departure, drive/wait time, and the $95 scheduled value stay tied to the stop even though Monday’s completed-service value is zero. Accurate records of actual hours and schedule deviations support payroll review (DOL recordkeeping guidance).
At the CSR desk, close the recovery loop
The CSR matches the 10:23 exception with the reminder, on-the-way notice, 10:16 call attempt, and the 10:31 conversation. The customer confirms that a gate code is needed. The CSR records the code, owns the recovery, and promises Tuesday, 10:00–10:30.
| Record | What it establishes in this incident |
|---|---|
| Notice and call timestamps | The customer received notice and did not answer at 10:16 |
| Field note and outcome code | Locked gate, no safe entry, and 10:12–10:18 time at the stop |
| CSR contact and rebook note | Gate-code requirement, owner, and Tuesday 10:00–10:30 promise |
A calendar date alone is not recovery. The access need, owner, and promised window must travel with the rebook.
At payroll review, separate cost from recovery
Finance reconciles the same trail: the technician’s paid time, route GPS or mileage, the outcome code, and Tuesday’s appointment. It charges Monday’s direct travel and wait time using the company’s normal labor and vehicle-cost method; it does not count the $95 as Monday service revenue. Any later-route delay or overtime is reviewed separately from the direct incident cost.
| Evidence | Review or calculation | Keep separate from |
|---|---|---|
| 10:12 arrival and 10:18 departure | Paid travel and wait time for the failed stop | Productive service time |
| GPS/mileage record | Added vehicle cost using the company method | A guessed per-stop charge |
| $95 scheduled value and Tuesday rebook | Revenue deferred from Monday to Tuesday | Incident cost |
| Later-route timestamps | Any delay or overtime | The direct no-access cost |
Use consistent treatment for like costs and a reasonable relationship between pooled costs and the work that caused them (Cost Accounting Standards). The IRS optional mileage rate can be a reference basis, not a substitute for the company’s actual vehicle-cost method (IRS explanation).
At reforecast, give the GM the decision
The forecast moves $95 of expected service revenue from Monday’s week to Tuesday’s week and retains Monday’s incremental labor and vehicle cost. Because the Tuesday slot is already available, the GM treats this as a timing shift, not lost revenue or added route capacity. The GM asks the CSR lead to add gate-code confirmation to reminders for gated accounts, reviews the no-access—gate-code-required rate in 30 days, and keeps the evidence trail as the reusable review lens.
That follows sound forecast practice: compare actuals with budget and forecast, decide whether a variance is one-off or persistent, and revise as conditions change (Business Queensland guidance). One stop does not prove a route problem; the 30-day rate will show whether this fix is warranted.