Open your territory map and look closely. Somewhere in there, odds are, sits a little island: a ZIP code assigned to Territory 9 but completely surrounded by Territory 4. The rep who owns it drives through a colleague’s patch to reach it, and the rep who surrounds it wonders why the account inside keeps getting someone else’s mailers.
That island is a non-contiguous territory, one whose area is broken into disconnected pieces, and it’s among the most common defects in territory design. Most are accidents. A few are deliberate and perfectly sensible. A good territory review finds every one, sorts the accidents from the intentions, and fixes the accidents.
What “Contiguous” Means in Territory Design
A territory is contiguous when you can travel from any part of it to any other part without leaving it. One connected shape. A non-contiguous territory has satellites: fragments, often a single ZIP code, cut off from the main body and stranded inside another rep’s ground.
Contiguity is one of the core principles of sound territory design, right alongside balance and compactness, and disconnected territories carry three real costs. They waste drive time, because the owning rep crosses someone else’s territory to serve a scrap of their own. They blur ownership, so accounts near the satellite get claimed by the wrong rep, skipped by both, or double-covered. And they erode trust: when reps spot obvious map defects, they stop believing the plan was drawn fairly and start lobbying for exceptions. A clean map defends itself.
How Non-Contiguous Territories Happen
The big one is realignment side effects. During a redraw, ZIP codes get traded at the edges, and a chain of individually sensible swaps leaves one ZIP orphaned. Nobody notices, because each move looked fine on its own.
Data-entry errors do it too. A single wrong digit in a ZIP-to-territory spreadsheet drops a ZIP hundreds of miles from where it belongs, and name-based county imports (instead of FIPS-code imports) are notorious for it. Then there are legacy carve-outs: “Sarah’s covered that hospital for ten years, leave it with her.” The carve-out was intentional, but after Sarah’s territory shifts twice more, the fragment lingers with nobody remembering why. And sometimes geography itself is the cause. Islands, peninsulas, and ZIPs split by a bay can make a technically non-contiguous territory the right answer, when the drive between two “connected” areas runs longer than the ferry to a “disconnected” one.
Not Every Satellite Is a Mistake
Before you fix anything, sort each fragment. Keep it if it’s a deliberate account override, a named account intentionally assigned outside its geography (a national account, a specialist relationship, a house account). The trick there is to leave the geographic assignment alone and handle the exception as an account-level override, so the anomaly stays documented, reportable, and survives the next realignment. Keep it, too, if geography justifies it: the satellite really is faster to reach from its assigned territory than from the one around it. Fix everything else. If nobody can say why a fragment exists, it’s an error, usually years old.
Finding Them: Don’t Trust Your Eyes
On a national map, a stranded ZIP is a few pixels. Manual inspection misses them constantly, especially in dense metros, so you need a systematic check. In AlignMix, the territory integrity tools locate non-contiguous territories for you: the software scans every territory for disconnected fragments and jumps you to each one, turning a full national audit into minutes instead of days. Run it after every import and at the end of every design session. In a GIS or spreadsheet workflow you’d have to run a spatial adjacency analysis per territory, which is exactly the kind of chore that justifies purpose-built territory software.
Fixing Them: A Simple Decision Rule
For each accidental fragment, pick the cheaper of two moves. Absorb it: reassign the satellite to the territory that surrounds it. That’s the right call about nine times in ten, killing drive time and ambiguity for a small shift in balance. Or bridge it: reassign the ZIP codes between the satellite and its main body to connect them, which makes sense when the satellite holds accounts that truly must stay with the current rep and the corridor between is thin. After either fix, re-check balance (a swap of comparable-value ZIPs usually restores it) and confirm you haven’t broken other rules like state boundaries. Because fixes ripple, do this on the map with live totals rather than in a batch.
Watch: Finding and Fixing a Non-Contiguous Territory
Frequently Asked Questions
What is a non-contiguous sales territory?
A territory whose assigned area is split into disconnected pieces, typically a main body plus one or more isolated ZIP codes stranded inside other territories.
Are non-contiguous territories ever acceptable?
Yes. Deliberate named-account carve-outs (better handled as account overrides) and geography-driven cases like islands, where the disconnected assignment is actually the shortest way to serve the customer.
How do I check if my territories are contiguous?
Don’t rely on the naked eye at scale. Use territory mapping software with an integrity check; AlignMix scans every territory and jumps you to each disconnected fragment.
What causes territories to become fragmented?
Mostly realignment edge-swaps that orphan a ZIP, import errors like wrong ZIP digits or name-based county matching, and legacy carve-outs that outlive their reason.
Audit your alignment for free. Import your territories into AlignMix and run the contiguity check, or book a demo and we’ll walk your map with you.