Field Revisit Normalization:
When Repeat Truck Rolls Become “Normal”
Field Revisit Normalization is the pattern where repeat field service visits become so common that the organization stops treating them as failures. The cost is enormous.
What Is Field Revisit Normalization?
Field Revisit Normalization is the pattern where repeat field service visits become so common that the organization stops treating them as failures and starts treating them as normal operations.
A technician visits a site. The issue is not resolved. A second visit is scheduled. Sometimes a third. Each visit costs $150–$400 in direct labor, truck roll, parts, and scheduling overhead. But because revisits have always happened at a certain rate, nobody flags them as structural waste. They are “just how field service works.”
They are not how field service works. They are how field service fails — and the cost is enormous.
The Economics of a Revisit
The canonical example from our diagnostic work:
A 7-minute interaction became 47 minutes of total operational capacity consumed, plus a $180 truck roll. The customer’s issue was a wiring configuration that could have been diagnosed remotely with the right troubleshooting tree. Instead, the contact center dispatched a technician on the first call because the agent lacked the authority and the tools to attempt remote resolution.
That single revisit cost the operation $240. Multiply by the field service revisit rate — typically 15–25% of all dispatches — and you are looking at $1.2M–$3.6M per year for a mid-size field service operation with 50 daily dispatches.
Why Revisits Get Normalized
1. First-visit resolution is measured at the visit level, not the issue level. If a technician arrives, performs work, and closes the ticket, the visit is coded as “completed.” When the customer calls back three days later with the same problem, it generates a new ticket. The revisit is invisible to first-visit resolution metrics.
2. Revisit costs are absorbed into general operating expense. Each truck roll is logged as a standard dispatch. The incremental cost of the revisit — the wasted first visit, the scheduling overhead, the customer downtime — is never attributed to the original failure. It vanishes into the average cost per dispatch.
3. Contact center and field service operate on separate dashboards. The contact center sees a “dispatch request.” Field service sees a “work order.” Neither one tracks whether the dispatch was caused by an incomplete remote troubleshooting attempt. The hand-off between the two systems is where the revisit pattern hides.
How to Detect It
Step 1: Link dispatch records to the originating contact center interaction. If a dispatch was triggered by a call, the two records must be joined.
Step 2: Track issue-level resolution, not visit-level completion. A “completed” visit that generates a callback within 7 days for the same address or account is a revisit, not a new issue.
Step 3: Calculate the Field Revisit Rate: (Dispatches followed by a related dispatch within 14 days) / (Total dispatches)
Step 4: Calculate the Revisit Cost Exposure: Field Revisit Rate × Average Dispatch Cost × Annual Dispatch Volume
Step 5: Segment by failure reason. “Wrong part ordered” has a different fix than “could have been resolved remotely.” The segmentation drives the intervention.
The Three Root Causes
Dispatch Authority Gap: Contact center agents dispatch technicians because they lack the authority or the tools to attempt remote resolution. Expanding remote resolution authority for the top 5 dispatch reasons eliminates 20–30% of unnecessary dispatches.
Diagnostic Incompleteness: The technician arrives without the right information. The contact center collected the symptom but not the equipment model, the configuration history, or the prior service record. The technician diagnoses on-site what could have been diagnosed remotely.
Parts and Scheduling Mismatch: The technician arrives with the wrong part or without the access required to complete the work. A second visit is scheduled. The root cause is upstream — in the intake process that failed to capture the right information.
What Healthy Looks Like
| Metric | Healthy | Warning | Critical |
|---|---|---|---|
| Field Revisit Rate | <10% | 10–20% | >20% |
| Remote Resolution Attempt Rate | >60% | 40–60% | <40% |
| Annual exposure per 50 daily dispatches | <$500K | $500K–$1.5M | >$1.5M |
Why This Matters for Insurance and Telecom
Insurance claims: Property inspections that require a second visit because the adjuster lacked photos, prior claim history, or coverage verification from the first notice of loss call. Each revisit adds 3–5 days to claim cycle time and $200–$400 in direct cost.
Telecom: Technician dispatches for issues that could have been resolved remotely through guided troubleshooting. The 7-minute call that becomes a $180 truck roll is the signature pattern of Field Revisit Normalization in telecom operations.
If revisits are “normal” in your operation, they are normalized waste. The first step is measuring them as failures, not as routine.
We do not guess. We map.
Brandon Burdin is the founder of MarginSignal OS, a forensic margin diagnostic for contact center and field service operations. More at marginsignalos.com.