Dividing Territory Between Crews Without Creating Turf Wars

Why this matters

The day you run two crews, you have to decide who gets which work. Get it clean and both crews stay busy and out of each other's way. Get it fuzzy and you invite the two most expensive behaviors in a multi-crew shop: fighting over the good jobs and dodging the bad ones. A turf war does not just waste time, it leaks out to customers as missed calls and dropped balls in the gaps between territories. The fix is not more refereeing. It is a boundary so simple nobody has to argue about it.

Why turf wars start

Turf wars are not a character flaw, they are a design flaw. They start when two things overlap: an unclear boundary and an incentive to win. If a crew earns more by grabbing the easy job across the line, and the line is vague, they will grab it. Remove either half and the war stops. This article handles the boundary; keep the incentives shared so crossing the line to help never costs anyone money.

The three ways to divide

Pick one primary axis. Mixing all three at once creates the ambiguity you are trying to kill.

• By geography. Draw a map. Each crew owns an area (zip codes, a river, a highway, named neighborhoods). Best when drive time is your main cost and jobs are similar across crews. Simplest to dispatch and easiest for everyone to understand.
• By job type. One crew runs installs, another runs service; or one runs commercial, another residential. Best when the work needs different skills or gear and geography matters less than specialization. Crews build depth instead of stepping on each other.
• By account. Each crew owns certain customers or a customer tier and follows them wherever they are. Best when the relationship matters more than the route (recurring accounts, service agreements) and continuity is the selling point.

Most small shops start with geography because it is the most legible. Move to job-type or account splits only when the work truly calls for it.

Rules that keep the peace

The boundary is only half the job. Three rules handle the friction the boundary cannot:

• Make the boundary dumb-simple. A rule a dispatcher can apply in two seconds and a crew cannot argue with. "North of the highway is Crew A" beats a negotiated case-by-case call every time. Ambiguity is where fights live.
• Write the overflow rule in advance. When one crew's area floods past capacity, where does the extra go? Decide before it happens, and make sure the crew that catches overflow gets full credit for it. If absorbing another crew's spillover is a punishment, no one will do it and customers wait.
• Set a shared-lead credit rule. When a customer in Crew A's area asks Crew B for more work, or one crew's referral lands in the other's territory, decide up front how credit is shared. Otherwise every cross-boundary lead becomes a quiet grudge.

Handling the edges

The trouble is never the middle of a territory, it is the seam. Manage the seam on purpose:

• Name a tie-breaker. When a job sits right on the line or an address is genuinely ambiguous, one person (usually the dispatcher) decides, and the decision is final for that job. No relitigating in the yard.
• Do not split a single customer's property. If an account straddles the boundary, give the whole thing to one crew. A customer should never see two of your crews arguing over who does the back yard.
• Rotate genuinely contested zones. If a border area is a constant flashpoint, alternate it on a fixed schedule rather than fighting each occurrence. Predictable beats fair-in-the-moment.

When to redraw the map

A boundary is a living tool, not a monument. Redraw when the work shifts: one crew is consistently slammed while the other has open slots, a new area opens up, or you add a third crew. Redraw on a schedule (a set review, not a heat-of-the-moment reaction to one bad week), announce it before it takes effect, and explain the why. Crews accept a boundary that changes for a clear reason far better than one that seems to move based on who complained loudest.

The spine to keep

Divide the work on one clear axis, make the boundary too simple to argue with, and pay crews for shared outcomes so crossing the line to help never costs them. Turf wars are what you get when the line is fuzzy and the incentive is to win. Fix the line and the incentive, and the crews stop guarding turf and start covering the shop.

References

• U.S. Small Business Administration (SBA): dispatch and multi-crew operations management
• Trade-standard practice on service-territory design and drive-time routing
• See related: Two Crews Are Competing Instead of Cooperating (decision tree); What to Centralize and What to Leave to Each Location