How do I know if my service area is too large?

Service area size is the most-undermanaged operational variable in field service businesses. The wrong answer (too large) silently destroys margin via drive time; too small leaves growth on the table.

Symptoms of a too-large service area:

1. Drive time exceeds 25-30% of total work time. Healthy residential service runs 15-25% drive time. Anything over 30% means you're paying for fuel and labor that doesn't generate revenue.

2. First-time fix rate drops on distant jobs. Techs can't carry every part for every system; longer drives correlate with "have to come back tomorrow with the right part" rates of 25%+ vs 10-15% on local jobs.

3. Route optimization can't get above 6-8 jobs per truck per day. Even with perfect routing, geographic spread limits density. If your average is 5 jobs/day with full routes, the area is too spread out.

4. Customer wait times exceed 5-7 days for routine work. A long backlog can mean you're successful — or it can mean you're spending so much time driving that you can't fit jobs.

5. You consistently say no to short-notice work outside a "core zone." That's a sign you have a real service zone and a fictional service zone, and the fictional one is hurting you.

Symptoms of a too-small service area:

1. You routinely turn away work because "that's outside our zone" but the work would be profitable at standard rates.

2. Calendar utilization is below 70% consistently (techs aren't fully booked).

3. Marketing spend reaches saturation in your zone (every targeted ad shows the same homes).

4. You're in a metro market under 250K population and trying to maintain 1-mile precision.

The "right" service area:

A healthy service area: - Allows 10-12 stops per truck per day during normal scheduling - Drive time stays under 25% of total tech time - Most customers reachable within 30 minutes of dispatch - Concentrated enough that emergency response can be 60-90 minutes for active customers

For most residential trade services in suburban metros: 15-mile radius from base, with concentrated customer density rather than evenly spread coverage.

The "zone density" model:

Don't think in radius — think in customer density. Divide your service area into zones, then prioritize zones with high customer count. A 30-mile arc covering 800 customers densely is operationally healthier than a 15-mile circle with 200 customers spread evenly.

The pricing-by-distance approach:

Some operators charge a "trip charge" or "extended service area" surcharge for jobs outside their core zone. Standard pricing within 12 miles, $25-$75 surcharge from 12-25 miles, custom quoting beyond 25 miles. This:

• Filters out unprofitable distant jobs
• Captures distant jobs at appropriate margin when they happen
• Sets clear expectations with customers

FSM software helps by:

• Visualizing customer density on the dispatch map
• Showing drive-time-as-percent-of-total-time as a metric
• Letting you set zone-based pricing rules
• Surfacing the patterns: which zones are actually generating revenue vs eating drive time