How to Distribute Leads by ZIP Code & Radius

A contractor in Denver doesn't want inquiries from Miami. If you sell leads, you need to know how to carve up territories cleanly. This guide walks you through, step by step, how to distribute leads by ZIP code so every buyer only gets the region they can actually serve.

In short

Geo distribution means routing every incoming lead to the right buyer based on its location. The match is made using ZIP codes, a radius around a location, or city and state boundaries — and it decides whether a lead is even a fit for a given buyer in the first place.

Why location determines quality

A lead is only valuable if the buyer can actually serve it. A roofer with a 30-mile service area will dispute an inquiry from a neighboring state 200 miles away — and rightly so. Misrouted leads cost you money, trust, and ultimately entire customer relationships. That's why a clean territory definition is the starting point of any distribution that actually works.

Geographic routing is one of the most common filter rules in lead distribution. Before any other logic kicks in — like who's next in line or who pays the most — the system first checks which buyers are even eligible for the lead's location. Only from that pool does it then pick the recipient.

Three ways to define a territory

There's no single right method. Which one you use depends on how your buyers think and operate. In practice, you'll often combine several approaches.

1. Distribute leads by ZIP code

This is the most granular and controllable method. You assign each buyer a list of ZIP codes or ZIP ranges — for example 80201 to 80299 for the central Denver area. The big advantage: there are no gray zones. A lead either falls into an assigned ZIP code or it doesn't. That makes billing and disputes airtight.

Here's how to do it:

  • Ask each buyer for their actual service area, not their wish-list area.
  • Get the ZIP codes as a list or range (80000–80999) instead of city names.
  • Use shorter ZIP prefixes when a buyer covers a large area — 802* for the whole Denver metro saves hundreds of individual entries.
  • Document which ZIP code belongs to which buyer so you can spot overlaps instantly.

2. Radius around a location

Here you define a center point — usually the buyer's business address — and a radius in miles. Every lead inside that circle counts as a match. It's intuitive and mirrors how contractors and service providers think about their own service area: "I'll drive up to 25 miles out."

Technically, this calculates the distance between the lead's coordinates (derived from the ZIP code or address via geocoding) and the center point. Watch out for two things: first, straight-line distance is not driving distance — a 25-mile radius can mean 45 driving miles depending on the terrain. Second, overlapping radii automatically create overlaps you'll have to resolve (more on that in a moment).

3. City or state

The coarsest level. Handy for buyers who cover entire regions, or as a rough pre-filter. "All leads from California" is quick to set up but not very precise — a lead from San Diego and one from Sacramento are over 500 miles apart. Use this level for regional or national providers, or as a fallback, not as the main rule for local trade businesses.

Resolving overlaps between multiple buyers

As soon as you have more than one buyer per region, you get overlaps: two or more buyers lay claim to the same lead. That's not a bug, it's the normal case — you just need a clear rule for who wins. Three models have become standard.

  • Priority: You set a fixed ranking. Buyer A gets every matching lead first, Buyer B only gets one when A is maxed out or unavailable. Simple, but unfair to the lower ranks — good for premium buyers with an exclusivity claim.
  • Round robin: Leads are distributed evenly, in rotation, across all matching buyers. Whoever got the last lead goes to the back of the line. This keeps utilization fair. For how this works in detail, see the round robin entry.
  • Bidding: The buyer who pays the most for the lead wins. Common with exclusive, high-value leads and often combined with a ping post process, where buyers bid in real time on anonymized lead data before they receive the full contact details.

In practice, you'll mix the models: priority first for your top customers, then round robin for the rest of the pool. The only thing that matters is that the rule is deterministic — given the same conditions, the same buyer must always win, otherwise disputes become a matter of luck.

Daily limits and capacity caps

Geography alone isn't enough. A buyer might be responsible for all of Denver but only able to handle ten inquiries a day. Without a limit, you flood them, the leads go stale, and they pay for contacts they never call. So set the following per buyer:

  • Daily limit — the maximum number of leads per day (e.g. 15).
  • Weekly or monthly limit for the overall volume.
  • Time windows — some buyers only want leads during business hours, because fresh leads should be contacted right away.

Once a buyer hits their limit, they drop out of the pool and the lead goes to the next matching buyer. That keeps distribution moving instead of stalling at a daily cap.

Sample setup: solar leads in the Denver area

Say you're distributing solar inquiries to three installers. Buyer A (central Denver) gets ZIP codes 80201–80299 with 12 leads/day and top priority. Buyer B (Aurora) covers a 20-mile radius around their location, 8 leads/day. Buyer C (large provider) takes all of Colorado as a fallback, no limit. A lead from ZIP 80246 goes to A first. If A has hit their daily limit, the system checks B: is 80246 within the 20-mile radius? Yes → B gets it. If B is out, the lead lands with C. In the overlapping area between A and B, when both are available and ranked equally, round robin decides. This is a constructed example to illustrate the logic.

Common mistakes in territory definition

Most problems don't come from the software — they come from the setup. These pitfalls show up again and again:

  • Gaps in the ZIP coverage: If no assigned ZIP code covers a lead, it slips through the cracks — no buyer, no revenue. Check regularly for "white spots" in your service area.
  • Double assignment without a tie-breaker: Two buyers in the same territory with no clear resolution rule lead to random or duplicate delivery. Always define who wins in a tie.
  • Confusing straight-line distance with driving distance: A 30-mile radius sounds generous, but in a region with rivers, mountains, or poor connections it's often too large. Ask buyers about their real drive time.
  • Wish-list area instead of service area: Buyers like to claim generous territories to get more leads, then fail to serve them — and dispute. Hold them to a realistic footprint.
  • Outdated limits: A buyer scales their team, but the daily limit stays at the old level. Review limits at regular intervals.
  • No fallback rule: When every matching buyer has hit their limit, you need a catch-all buyer or a queue, otherwise the lead goes to waste.

Step by step to a clean setup

When you're building a new service area, work in this order:

  • Capture each buyer's real service area — ideally as a ZIP code list.
  • For each region, decide which resolution model applies: priority, round robin, or bidding.
  • Set realistic daily and volume limits.
  • Define a fallback for maxed-out or invalid territories.
  • Test with real sample addresses from edge and overlap zones before you go live.
  • Watch disputes and gaps during the first few days and fine-tune.

Modern lead distribution software like Leadfy takes the number-crunching off your plate: it geocodes incoming leads, checks the configured territories and limits, and applies the resolution rule automatically. Your job stays the territory strategy — the mechanics run in the background.

Frequently asked questions

What's more precise — ZIP code or radius?

ZIP codes are clearer and better for billing and disputes, because a lead is plainly in or out. A radius more naturally reflects actual driving behavior. Many people combine the two: ZIP code as the hard boundary, radius for fine-tuning.

What happens when two buyers cover the same area?

Then you need a resolution rule. The common ones are priority (fixed ranking), round robin (rotation), or bidding (highest price wins). Without a clear rule, the assignment becomes random and dispute-prone.

Should I use entire states as a territory?

Only for regional or national providers, or as a fallback. For local trade businesses the level is too coarse, because there can be hundreds of miles within a single state. There, go with ZIP code or radius instead.

How do I keep a buyer from getting overloaded?

Set daily, weekly, or monthly limits per buyer, and optionally time windows. Once the limit is reached, the buyer drops out of the pool and the lead goes to the next matching buyer.

Why did a lead end up with no buyer at all?

Usually there's a gap in the territory coverage — no assigned ZIP code or radius covers the location — or every matching buyer has hit their limit. A fallback rule or queue catches leads like these.

Does straight-line distance or driving distance matter?

Radius calculations typically use the straight-line distance between coordinates. Since the real driving distance is longer, you should set the radius conservatively and ask buyers about their actual drive time.

Geo distribution without the manual work

See how Leadfy automatically routes leads by ZIP code, radius, and limit to the right buyers.