When your customers spread across big, thinly-covered areas, think agricultural equipment, industrial distribution, or medical devices in rural health systems, building territories from ZIP codes is overkill. There are more than 40,000 ZIP codes in the US but only about 3,100 counties, which makes counties the natural building block for large-area design: big enough to keep assignments manageable, small enough to balance workload fairly.
This guide covers when counties beat ZIP codes, the one technical detail that makes or breaks a county-based alignment, and how to build county territories in AlignMix.
When Counties Beat ZIP Codes
Choosing a base geography is the first pillar of territory design, and the answer comes down to customer density. Reach for counties when your reps cover large, low-density areas, when a single territory would otherwise swallow hundreds of ZIP codes, when your market data (agriculture, healthcare, government) is published by county, or when reviews happen at a regional level rather than street by street. Stick with ZIP codes for dense metros, for balancing many territories finely, or for account lists where one county holds several reps’ worth of business (see what a ZIP code boundary really is for how that works). You can also blend the two, counties in the countryside and ZIPs in the cities, in a single alignment.
The Detail That Makes or Breaks It: FIPS Codes
Here’s where most county projects go sideways. County names aren’t unique. There’s an Orange County in eight different states, roughly half the states have a Jefferson County, and thirty have a Washington County. Tell any mapping tool “Washington County to Territory 7” and it has no way to know which of the thirty you mean.
The fix is the FIPS code, the federal identifier assigned to every county. It’s five digits: the first two are the state (12 for Florida, 06 for California, 48 for Texas) and the last three are the county within it (12117 is Seminole County, Florida; 06059 is Orange County, California). Because every county’s FIPS code is unique nationwide, a file keyed on FIPS imports perfectly every time. No ambiguity, no misplaced counties, no cleanup.
One spreadsheet trap to watch: Excel loves to strip leading zeros, turning Alabama’s 01001 into 1001. Format the FIPS column as text, or re-pad it to five digits, before you import. That single step prevents the most common county-import failure. As for where to get the codes, the Census Bureau publishes the full list, most vendors include FIPS in county datasets, and AlignMix ships with every US county and its FIPS code built in, so you can export the master list and key your data to it.
Building County-Based Territories, Step by Step
Prepare your data. At minimum you need two columns: the county FIPS code and the territory assignment. Add whatever you want to balance on, revenue, accounts, potential, workload, as extra columns. No existing assignments? Just import the metrics and build from scratch on the map.
Import into AlignMix. Choose county (FIPS) as your base geography and load the file. Every county appears with your data attached, and a clean FIPS-keyed file loads in under a minute.
Design on the map. Use Touch Align to drag counties between territories. Totals for revenue, accounts, and workload update as you go, so you watch balance improve in real time, and thematic maps shade counties by any metric to show where the opportunity sits.
Check integrity. Keep territories contiguous and drivable, watch for a lone county stranded inside another rep’s patch (see finding and fixing non-contiguous territories), and respect state lines if your business needs it (keeping territories within state boundaries).
Export and deploy. Push the finished county-to-territory list back to Excel or your CRM. Because it’s keyed on FIPS, it’s unambiguous for every downstream system.
Best Practices
Balance on opportunity, not acreage. A visually enormous plains territory may hold less business than three counties in Ohio, so use market potential per county, not square miles. Mind the outliers: a single county like Los Angeles or Harris can outweigh whole states, and it’s fine for one county to be a territory by itself, or to switch that metro to ZIP resolution. When you realign, minimize disruption by moving the fewest counties that restore balance. And document intentional exceptions, handling a national account inside a county as an override rather than distorting the county assignment.
Watch It Done in Under 3 Minutes
Frequently Asked Questions
What is a county FIPS code?
A unique five-digit federal identifier for every US county: two digits for the state, three for the county. Because names repeat across states, FIPS codes are the only reliable key for county data.
How many counties are there in the United States?
About 3,100 counties and county-equivalents (Louisiana parishes, Alaska boroughs and census areas, Virginia’s independent cities). All carry FIPS codes and all are mappable in AlignMix.
Can I mix county-based and ZIP-based territories?
Yes. A common pattern is counties in rural regions and ZIP codes in dense metros, managed in one alignment.
My county import isn’t matching. What’s wrong?
Nine times out of ten it’s leading zeros: Excel turned 01001 into 1001. Format the FIPS column as text and re-import. The next most common cause is using county names instead of FIPS codes.
Does AlignMix include county boundaries?
Yes, current boundaries for every US county ship with the software, along with ZIP codes, states, and international geographies.
Design county-based territories in an afternoon, not a quarter. Try AlignMix free or book a demo.