Stop sending trucks to jobs outside your real service area
Check every new job against your real service area before a technician is booked. Cut wasted drive time and out-of-area callouts for $49/month.
You get a call. Someone needs a furnace looked at, a drain cleared, a wasp nest gone by tomorrow morning. Your office books it in, hands it to a technician, and the truck rolls.
Forty minutes later the technician calls in: this address is nowhere near where they thought it was. It's on the far side of the county, past two other jobs, in a zone you don't normally cover. Now you're deciding whether to eat the drive time, push back the rest of the day's schedule, or call the customer back and apologise.
This happens more than most owners want to admit, and it's rarely because someone was careless. It's because "is this inside our service area" is usually answered by a mental map — a feel for which towns, zip codes, or neighbourhoods you cover — and mental maps have blind spots, especially when a new hire is taking the call, or the address is a bit unusual, or it's the fifth booking of a busy morning.
What a bad service-area call actually costs you
The obvious cost is the wasted trip. A technician and a truck, gone for half a day, on a job that should have been declined or handed to a subcontractor from the start. Fuel, wages, and a slot on tomorrow's schedule that a real customer could have had.
The less obvious cost is what it does to the rest of the day. Field service scheduling is tight — most small HVAC, plumbing, and pest control operations run four to eight jobs a technician a day, back to back, with maybe fifteen minutes of slack built in. One job that's thirty minutes further than expected doesn't just cost thirty minutes. It pushes every appointment after it, which means a customer waiting at home for a technician who's now running late, which means an apologetic phone call, which means a slightly annoyed customer leaving a slightly annoyed review.
And then there's the quiet cost: jobs you accept that you shouldn't have, at a price that assumed a fifteen-minute drive and turned into a fifty-minute one. If your pricing has any distance component — a trip charge, a mileage cutoff, a "we only travel this far for emergency calls" rule — and you're not actually checking distance before you quote, you're guessing. Sometimes the guess is generous to you. Often it isn't.
None of this is a training problem. It's a checking problem. Nobody looks up every new address on a map before they book it, because that's slow, and slow doesn't survive a busy phone line. So the checking gets skipped, and the service area lives in people's heads instead of on a screen.
The fix: know the location before you book, not after the truck leaves
The idea is simple. Before a job goes on the schedule, you find out where it actually is — not the town name someone said over the phone, not a rough guess, but the real coordinates for that address. Once you have that, comparing it to your service area is trivial: is this point inside the boundary you already cover, or is it outside?
The part that's usually missing for a small operation isn't the comparison — it's turning a written address into a precise location in the first place, reliably, for every job, without someone manually typing it into a map app one at a call at a time.
That's what a geocoding subscription does. You give it a list of addresses — the jobs on your books, new leads, whatever you need checked — and it hands back the exact coordinates for each one. From there, checking "inside or outside our zone" is a five-minute job even for someone with zero mapping background, because you're just looking at where a dot lands.
CSV2GEO runs this as a plain monthly subscription: you send a spreadsheet, you get a finished spreadsheet back with the location added to each row. No installed software, no technical setup, nothing that requires anyone on your team to understand mapping or programming.
For a business booking new jobs daily — an HVAC company, a plumbing outfit, a pest control route — the Starter plan at $49 a month covers up to 50,000 US rows. Realistically, most small field service operations use a small fraction of that each month, which leaves plenty of room to also run a monthly refresh of your whole customer list, or check a batch of leads before a marketing push, without upgrading.
How it works
Step 1: Pull your list of addresses
This can be tomorrow's job sheet, this week's new leads, or your entire customer database if you're doing a bigger cleanup. Export it from whatever you already use — a spreadsheet, your scheduling software, even a CRM export — as a plain spreadsheet file. One column needs to be the address.
Step 2: Upload the file
Log in to CSV2GEO and upload that spreadsheet. There's nothing to configure beyond confirming which column holds the address. You don't need to know anything about coordinates, boundaries, or mapping to do this step.
Step 3: Download your results
Within a short wait, you get back the same spreadsheet, with exact location coordinates added as new columns. Every address you sent gets one back — including a clear flag for any address that couldn't be matched, so you know which ones to check by hand rather than guessing.
Step 4: Compare against your service area
Now you can check each job against the zone you actually cover. If you have a defined service boundary — a set of zip codes, a radius from your shop, a drawn territory — you compare the coordinates against it. This can be done in a simple mapping tool, or your scheduling software if it supports drawing a coverage zone, or even just sorted by distance from your base if your area is roughly a radius.
Step 5: Flag or route the out-of-area jobs
Anything that lands outside the line gets handled the way you choose — declined, quoted with a trip surcharge, or handed to a subcontractor who covers that patch. The point is you're making that call before the job is booked, with the technician still in the shop, not after they've already driven there.
Step 6: Build it into your weekly routine
Once this is a five-minute habit — export, upload, download, check — you run it every time a batch of new bookings comes in, or once a week against your whole pipeline. It stops being a one-off cleanup and becomes part of how you take bookings.
Why this beats "we'll just ask on the phone"
Asking the customer where they are helps, but people describe their own location badly. They give you the town they think of as home, not the street they're actually on, especially near county lines or where towns blur into each other. A rural address might be genuinely 25 minutes from where the customer believes it is. None of that is anyone's fault — it's just how people talk about where they live. Coordinates don't have that problem. An address either sits inside your boundary or it doesn't, and a precise location settles the question instead of relying on someone's sense of geography.
It also removes the burden from whoever answers your phone. A new office hire, a temp covering for someone on leave, even you on a Saturday when you're the one picking up calls — none of them need to memorise which zip codes you cover. The check happens against the data, not against someone's memory.
FAQ
Is this hard to set up if I'm not techy at all? No. If you can attach a file to an email, you can use this. You upload a spreadsheet and download one back — there's no software to install and nothing to configure beyond telling it which column has the address.
What happens if an address is messy or incomplete — say, missing a zip code or spelled wrong? Most of these still get matched correctly, because the system is built to handle real-world address messiness. Anything it genuinely can't resolve gets flagged clearly in the results, so you know exactly which handful of rows need a manual look rather than guessing which ones might be wrong.
Do I need to already have a defined service area drawn out somewhere? It helps, but it's not required to start. Even a rough rule — "we don't go past 30 minutes from the shop" — becomes checkable once you have real coordinates for every job. You can tighten the boundary over time as you learn more about where jobs actually run long.
How much of my job list do I need to check each month? Whatever suits your volume. Some businesses check every new booking daily; others run it weekly against everything on the calendar. At $49 a month for up to 50,000 rows, most small HVAC, plumbing, and pest control operations have comfortable headroom either way.
Can I cancel if it's a slow month or I decide it's not for me? Yes. It's a monthly subscription with no lock-in — cancel any time and you're not billed again. There's no annual contract to break.
What happens to the addresses I upload — is this private? Your data is used only to produce your results and isn't shared or sold. It's the same list you already have; this just adds location information to it and hands it back.
Will this replace my scheduling software? No, and it isn't meant to. It sits alongside whatever you already use to book and dispatch jobs. It solves one specific problem — knowing exactly where a job is before you commit a truck to it — and leaves the rest of your workflow untouched.
Related articles
- Quoting jobs by real driving distance, not guesswork
- Building a daily stop order without fleet software
- Checking service area coverage for warranty claims
- Geocoding without engineers: an ops guide
- The real cost of running your own geocoder
--- *I.A. / CSV2GEO Creator*
Use our batch geocoding tool to convert thousands of addresses to coordinates in minutes. Start with 100 free addresses.
Try Batch Geocoding Free →