Setting Service Areas So the Schedule Stops Breaking

A service area is a commercial decision rather than a radius, and most are drawn by accident: 1 customer at a time, each of whom seemed worth having. 3 methods draw it deliberately, and the honest test is what an outlying site costs on the day it calls.

The short version

Almost nobody in this trade decides their service area. It accumulates, because a good customer asks whether you cover them and the answer is yes.

Ten of those over four years produces a map with no shape, a schedule that breaks whenever two distant sites call on the same morning, and a set of customers who cannot be served profitably and cannot be dropped without an awkward conversation.

This is about drawing the boundary rather than routing inside it. Where the line sits decides which work is possible, and getting it wrong is a slow problem that never announces itself.

What an outlying customer actually costs

Cost	Why it is larger than it appears
The travel itself	Paid hours producing nothing
The displaced job	A half day is a job that cannot happen
Schedule fragility	One distant emergency breaks the whole day
Response commitments	You cannot honor four hours ninety minutes away

The third and fourth are the ones that matter beyond that customer. A distant site does not only cost its own travel, it makes the day unreliable for everybody else on it.

3 ways to draw the line

And travel time beats distance in every one of them.

By drive time from your base, which is the simplest and works for a single-depot business. Forty minutes and ninety minutes are different businesses and the map is misleading about which is which.

By density, meaning the areas where you already have enough customers to fill a day without long drives between them. This is usually the most profitable version and it produces an irregular shape rather than a circle.

By response commitment, working backwards from what you have promised. If you sell a four hour response, your area is wherever you can reach in that time on a bad afternoon, not on a good morning.

Most service companies end up with two lines rather than one: a core area with full commitments, and an outer band served on planned work only.

The two-tier area is the answer most books need

Because a single boundary is either too tight or unaffordable.

Inside the core: reactive work, emergency cover, contracted response windows, everything.

In the outer band: planned maintenance and scheduled repairs, batched onto specific days, with no response commitment and a rate that reflects the travel.

That structure lets you keep good customers who happen to be far away without pretending you can reach them in four hours, and it is honest in a way a quiet inability to attend is not.

State it in writing at the start of the relationship. Customers accept a stated limitation and resent discovering one during a breakdown.

Measure your own map before redrawing it

Two figures per site, from last year.

Visits, and average travel time. Plotting those together produces the picture immediately: a dense middle, a thinner ring, and a small number of sites consuming a disproportionate share of the driving.

Roopairs holds jobs against equipment records per site, which is what makes attendance counts per site retrievable rather than something somebody estimates.

What usually appears is that a handful of customers account for most of the long journeys, and that several of them are near each other, which changes the decision from dropping them to batching them.

The exceptions worth keeping

Because a rule with no exceptions is a rule that loses good work.

A distant site belonging to a customer whose other sites are central. Serving it is part of holding the account, and it should be priced into that relationship rather than judged alone.

A cluster of outlying customers who can share a day. Three sites in one distant town is a route, and the arithmetic is completely different from one site alone.

And equipment nobody else covers, where the journey buys a specialty that is billable elsewhere.

Each of those is a decision made deliberately, which is the difference between an exception and a drift.

How to withdraw from an area without damage

1. Give real notice, measured in months rather than weeks, and in writing
2. Name a successor where you can, because a customer left with nobody remembers it
3. Send their equipment records, which is theirs and makes the handover work
4. Finish the open work rather than leaving a piece of equipment mid-repair

Restaurant operators talk to each other, and how you leave is remembered longer than how you served them. A clean withdrawal occasionally produces a referral inside your own area.

Review the boundary annually

Because the map moves without anybody moving it.

Customers open and close sites, your own density changes as you win work, and a band that was uneconomic two years ago may now contain six customers.

Which means the outer band is not permanent. It is where you serve on planned work until the density justifies more, and that is a threshold worth naming rather than a judgment made each time.

Name the threshold in customers rather than in revenue. Enough sites in one direction to fill a technician's day is what makes the area work, and a single large customer at the same distance does not achieve it.

The pain starts around your third or fourth technician, which is where a day can no longer be rearranged around one long journey and the boundary starts governing whether commitments are met.

Roopairs runs a product tour where you can see per-site equipment records and the job history behind each customer.

What service companies in the trade say

“When our initial data export wasn't as clean as it should have been, they paused the onboarding process to meticulously clean and perfect it before we went live.” — Korey Austin

Also worth reading

• Routing Technicians Across a Metro Area
• Coverage Maps: Saying No to the Distant Job
• Is equipment leasing worth it

Frequently asked questions

How should a service area be decided?

Deliberately, by drive time, by density, or by working backwards from your response commitments. Most areas in this trade accumulate one customer at a time and end up with no shape.

What does an outlying customer cost?

Four things: the travel, the job displaced by a half day, the fragility one distant emergency introduces into the whole day, and the response commitment you cannot honor ninety minutes away.

Should there be one boundary or two?

Usually two. A core area with full commitments and reactive cover, and an outer band served on planned work only, batched onto specific days, at a rate reflecting the travel.

How do you measure your current map?

Visits and average travel time per site from last year, plotted together. A handful of customers usually account for most of the long journeys, and some of them are near each other.

Which distant customers are worth keeping?

A site belonging to a customer whose other locations are central, a cluster that can share a day, and equipment nobody else covers where the journey buys a billable specialty.

How do you withdraw from an area?

Months of written notice, a named successor where possible, their equipment records handed over, and the open work finished. How you leave is remembered longer than how you served them.