Back to blogCounty vs ZIP Code Territories for Plumbing Companies: Which Works Better?
territory managementplumbingfield service schedulingdispatchservice areasrouting

County vs ZIP Code Territories for Plumbing Companies: Which Works Better?

Kyle Strouse·

For most plumbing companies, ZIP code territories outperform county boundaries because ZIP codes are smaller, denser, and map more closely to where jobs actually cluster. Counties are too large for 3–15-tech teams — one tech can easily cover a quarter-county and still spend 40 minutes between jobs. ZIP codes let you assign coverage precisely and adjust a single zone without redrawing the whole map.

ZIP code territories work better for most plumbing companies because they match real job density and let you assign or adjust one zone at a time without overhauling every tech's coverage.

Why the boundary type matters more than you think

Your territory boundary is not just a line on a map. It is the rule that decides which tech gets booked when a customer in a given address submits a job request. Get it wrong and two techs end up driving past each other's jobs on the same street — or worse, a customer in an uncovered pocket simply cannot book at all.

The stakes are real: a 10-tech plumbing company running unstructured dispatch can easily burn 60–90 minutes of windshield time per tech per day. At a fully loaded cost of $40–$60 per tech-hour, that is $2,400–$5,400 in wasted labor every single day, before you count the jobs that didn't get done. Choosing the right territory granularity is one of the highest-leverage decisions an owner makes — and it rarely gets the attention it deserves.

If you are still routing manually or relying on a dispatch board with no geographic logic, the territory routing without a dispatcher guide is worth reading alongside this one.

How county territories work — and where they break down

County-based territories are intuitive. Every address in the United States belongs to exactly one county, the data is clean, and there is no ambiguity. For a company with one or two techs covering a rural market, assigning "Tech A owns Jefferson County, Tech B owns Madison County" is perfectly sensible.

The problems start when your team grows or your market gets denser:

  • Counties are too large for urban and suburban markets. A single county in the Chicago metro or the Dallas–Fort Worth sprawl can contain 800,000+ residents and hundreds of competing plumbing jobs per week. One tech cannot cover that, and splitting a county arbitrarily creates the overlap you were trying to prevent.
  • Irregular shapes create dead zones. County lines follow historical boundaries — rivers, old railroad lines, political compromises — not drive-time logic. A tech assigned to a long, thin county may be 55 minutes from one end to the other.
  • Adjusting one territory means re-drawing everything. If Tech C leaves and you need to redistribute her county, every adjacent tech's map changes. With five or more techs, this becomes a quarterly headache.

How ZIP code territories work — and where they shine

ZIP codes were designed around mail delivery density, which happens to correlate well with residential job density. A typical suburban ZIP covers 20,000–40,000 residents in a reasonably compact area. For a 5–15 tech plumbing company, that granularity is close to ideal.

The practical advantages:

  • Each tech owns 3–8 ZIPs, not a vague region. A tech based in the northeast corner of your market gets ZIP codes 60601–60614, full stop. When a customer in 60608 books a drain inspection, the system routes it to that tech automatically — no dispatcher judgment call required.
  • You can tune one zone without touching others. If Tech D is consistently overloaded in ZIP 30306, move one ZIP to a neighboring tech. Three ZIP reassignments later, workloads balance. No county redraws.
  • Route density is easier to build. Batching service calls by neighborhood works naturally when your tech's entire workday is already in adjacent ZIP codes. County boundaries rarely support that kind of clustering.
  • Gaps are visible and fixable. If no tech covers ZIP 85032, you see it immediately. With county assignments, gap ZIPs hide inside a county boundary that looks covered on paper.

When county territories are the right call

ZIP codes are not always the answer. County-level territories make sense when:

  • You operate in rural or semi-rural markets where a county contains only 15,000–30,000 people and one tech can realistically cover it.
  • Your team has one tech per major metro area and you need a clean, non-overlapping division across a wide geography.
  • You sell or acquire plumbing businesses by county franchise area and the legal boundary matters more than drive-time logic.

In these cases, county assignment gives you clean data and zero ambiguity. The key is that each county maps to roughly one tech's realistic capacity — not a legacy of how the map used to look.

The hybrid approach: counties for regions, ZIPs for metro cores

The most effective setup for companies with mixed rural and urban coverage uses both. Assign outlying rural counties as single-tech territories. Inside your metro core, switch to ZIP-level assignment for each tech. This way your rural techs have clear, uncomplicated ownership, and your high-volume urban techs have precise, density-matched zones.

In Cartoply's plumbing scheduling software, you can build each tech's territory as a mix of boundary types — ZIP codes in the urban core, a county or two appended for rural coverage — all within a single organisation booking page. A customer enters their address, the system checks which territory it falls in, and books the matching tech automatically.

How to set up ZIP code territories in Cartoply — step by step

This assumes you already have your techs added as team members in your Cartoply organisation.

  1. Open your organisation's territory settings and select a tech.
  2. Choose "ZIP code" as the boundary type for that tech's service area.
  3. Enter or paste the list of ZIP codes this tech covers — you can add them one at a time or in bulk.
  4. Repeat for every tech, making sure no ZIP appears in two techs' lists unless you intend shared coverage.
  5. Publish the updated territories and test with three real addresses — one per tech's zone — to confirm routing.
  6. Set a deposit amount on your organisation booking page so the booking only confirms once payment is authorised.

Collecting a deposit at the point of booking is worth doing alongside your territory setup. A $49–$75 service-call fee authorised at booking eliminates most no-shows and cancellations — the driving costs plumbing companies absorb most painfully. See the full case for it in how a deposit cuts home service no-shows by 40–60%.

Note: payment collection and territory routing both require an organisation booking page in Cartoply, not a personal one. A solo plumber sets up a one-member organisation — that is fully supported, and the Stripe or PayPal payout goes directly to their own account.

person holding black samsung android smartphone
person holding black samsung android smartphone — Photo by Tech Daily on Unsplash

Benchmarks: what good territory sizing looks like for plumbing

  • Jobs per day per tech: 4–6 is a healthy target. More than 7 with no buffer time is a recipe for late arrivals and callbacks.
  • Drive time between consecutive jobs: under 20 minutes is the goal; over 30 minutes is a territory design problem.
  • ZIP codes per tech (suburban market): 3–6 ZIPs is typical for a tech doing 4–6 jobs per day. Rural techs may own 8–12 ZIPs covering similar job volume.
  • Territory review cadence: quarterly is right for most teams. After a tech hire or departure, review within two weeks.

Ready to stop your techs driving past each other's jobs?

14-day free trial — no credit card required. $7/seat/month after that.

Start free trial →

Frequently asked questions

Can a plumbing company use both ZIP codes and counties in the same territory setup?

Yes. A hybrid approach works well for companies that serve both urban and rural markets. Assign ZIP codes in high-density metro areas where job clustering matters, and assign full counties in rural coverage zones where one tech can realistically cover the whole area. The two boundary types can coexist in the same system as long as no address falls into two different techs' territories simultaneously.

What happens if a customer's address is in a ZIP code not assigned to any tech?

In Cartoply, the booking form will not route the job if no territory covers that address, which prevents a customer from booking a tech who cannot realistically serve them. That is a feature, not a bug — it surfaces gaps in your coverage so you can decide whether to extend a territory, add a tech, or explicitly exclude that area. Review unmatched addresses monthly to catch gaps before they cost you jobs.

How many ZIP codes should each plumbing tech own?

In a typical suburban market, 3–6 ZIP codes per tech supports a 4–6 job-per-day schedule with drive times under 20 minutes between stops. Rural techs can own 8–12 ZIPs covering similar job volume because residential density is lower. If a tech is consistently over 30 minutes between jobs, the territory is too large or shaped poorly — usually an elongated zone rather than a compact cluster.

Do ZIP code territories work for emergency plumbing calls?

ZIP code territories set which tech is automatically booked for a given address. For true emergency dispatch — a burst pipe at 2 a.m. — you still need a human deciding who is closest and available. Territory routing is most valuable for scheduled jobs and new-customer bookings flowing through your online booking link. For emergencies, territory routing tells you who should own that job once the crisis is contained and a return visit needs to be booked.

Get field service tips in your inbox

Scheduling, dispatch, and territory strategy for home service teams. No spam, unsubscribe anytime.

By subscribing you agree to receive emails from Cartoply. Unsubscribe anytime. See our Privacy Policy.