
Draw the boundary in drive time, not miles, and draw it twice: 1 line for scheduled work and a tighter one for emergency response. A service company with a single radius on a map is agreeing to windows it cannot meet at the edge.
Every service company has a service area and most have never written it down. It exists as an instinct in a dispatcher's head, applied inconsistently, and negotiated away whenever a customer asks nicely.
Two things make it a real boundary rather than a preference:
The second is the one service companies miss, and it is why so many SLA misses cluster at the edge of the map.
Forty miles is an hour in one direction and two and a half in another at 8am.
A circle on a map treats those as equivalent. Your technician does not, and neither does a four hour response window.
What to do instead, and it takes an afternoon:
The fourth point catches service companies out. A site reachable in fifty minutes outbound at 7am can be ninety minutes back at 4pm, which is unbillable time somebody is paying for.
| Cost | Why it is larger than it looks |
|---|---|
| Unbillable travel | Both directions, at loaded cost, and often unbillable entirely on portal work |
| The displaced jobs | A four hour round trip removes two or three local visits from the day |
| Second visit risk | A missing part at the edge costs the whole trip again, not an hour |
| Response window exposure | Accepting an SLA you cannot reliably meet damages the scorecard on every occurrence |
The third row is the one that changes the calculation. First-time fix matters everywhere and it matters most at distance, which means a distant site needs the van stocked better than a local one to be worth serving at all.
That connects the boundary decision to the parts chain rather than to the map. A service company with weak van stock has a smaller viable service area than one with good stock, using the same vehicles.
Scheduled work and emergency response have different economics and should have different edges.
The scheduled boundary is wider. Planned maintenance can be clustered, routed and done on a day of your choosing. A site ninety minutes out is viable when you visit it with three others on the same trip.
The emergency boundary is tighter. A four hour window from an unpredictable start point, on a day already scheduled, is a different commitment. Sites that work for PM often do not work for break-fix.
Saying that out loud to an account is not a weakness. Offering scheduled coverage across a wide area and emergency coverage across a narrower one is a normal arrangement, and it is far better than accepting both and missing one.
Programs and customers respond badly to unreliability and well to clarity.
What works, in order:
The second point is the one service companies find hardest and it is the most effective. Facilities managers are managing coverage gaps constantly and they would rather know where yours are than discover them.
A boundary nobody ever crosses is a boundary set too tight, and there are three legitimate exceptions.
Density is coming. A single distant site is expensive. Three in the same town changes the arithmetic, and taking the first one is sometimes how you get the other two.
An existing customer expanded. Declining a new site for a customer you already serve well costs more than the drive, because it invites them to find somebody who covers both.
The work is high value and plannable. A large scheduled job at distance can carry its travel comfortably. A break-fix call at the same site cannot.
What matters is that these are decisions rather than drift. An exception granted with a reason is a strategy. Three exceptions granted because somebody asked is a service area that has quietly moved.
The boundary only works if the person answering the phone knows it.
One page: the drive-time bands, which sites fall in each, the scheduled boundary, the emergency boundary, and who can approve an exception. Give it to the dispatcher and whoever takes calls.
Then review it twice a year against where your customers actually are. Service areas drift with the customer base, and a boundary drawn three years ago describes a business you no longer run.
Where portal work is involved, tell each program which of their sites fall inside your emergency boundary. Most will adjust assignment rather than lose a vendor, and the conversation is much easier before the first miss than after the third.
Roopairs runs a product tour where you can see scheduling, equipment records and parts against the jobs that decide whether a distant site is viable.
“Given that 75% of our business involves handling urgent 'fires', figuring out what the biggest fire is at the moment and who is available to handle it. The ability to manage and schedule on the fly is crucial, and Roopairs let's us to do this easily.” — Korey Austin
In drive time from your base at the hours you actually dispatch, rather than in miles on a map. Then set two boundaries: a wider one for scheduled work that can be clustered, and a tighter one for emergency response with a window to meet.
Because forty miles is an hour in one direction and considerably more in another at peak times, and routes are frequently asymmetric. A circle on a map treats sites as equivalent when the technician and the response window do not.
Unbillable travel both ways, the local jobs it displaces, a much higher cost if a second visit is needed, and exposure on any response window you agreed. The second visit risk is the one that changes the arithmetic, which ties the boundary to your van stock.
Decline quickly, decline the site rather than the account, and say what you can offer instead. Naming the sites you cover reliably and the ones you do not is a partnership conversation. Facilities managers manage coverage gaps constantly and prefer knowing where yours are.
Yes, for density that is coming, for an existing customer's new site, or for high-value plannable work. What matters is that those are decisions with reasons rather than three exceptions granted because somebody asked.
Twice a year against where your customers actually are. A service area drifts with the customer base, and a boundary drawn three years ago describes a business you are no longer running.
The all-in-one platform built for commercial kitchen service companies. Dispatch, invoicing, parts ordering — all in one place.
Book a product tour →