Address to territory lookup

What each step means

Most routing tools answer with a name. This one answers with a name and the four questions it had to settle to get there, because when the answer is wrong those four questions are the only way to find out why.

Address

The address becomes a point on the map. Everything downstream is geometry, so this is where a wrong answer usually starts. The precision is reported as rooftop, street or centroid, because a decision made from a postcode centroid deserves less confidence than one made from a rooftop.

Territory

Which territories contain that point. Often more than one. Overlap is normal in a real business: a metro team and a specialist team can both cover the same street, and pretending otherwise is how routing software starts lying.

Priority

Which of them wins. A rule somebody wrote and can change, not a tie-break buried in a vendor’s code. This is the step that most often surprises people, and the reason it is worth showing.

Capability

Whether the winner can actually do the work. Covering an address and being able to serve it are different questions. An answer that ignores the second one sends a plumbing job to a team that only does HVAC.

Why territories overlap, and why that is fine

A business that has grown has overlapping coverage: a metro crew and a specialist crew both reach the same street, an acquired franchise kept its old boundary, a partner covers a corridor nobody else wants. Software that assumes one territory per address forces somebody to redraw the map to fit the tool.

The alternative is to let them overlap and to be explicit about which one wins. That is what the priority step is, and it is a rule someone at the company wrote and can change, not a tie-break inside a vendor’s code that nobody can see.