Sales territory maps in PowerPoint

A territory is a group of counties that has to fill as one region. That single requirement rules out both a picture and a chart, and it is why territory maps get rebuilt in a design tool instead of in the deck.

What a territory map has to show

A sales territory map answers one question at a glance: which areas belong to whom. It is not a visualization of revenue, and the moment it tries to be both it stops answering either. The readable version has a handful of territories, each one a solid fill, with the owner's name on it and nothing else.

That simplicity is exactly what is hard to produce, because a territory is rarely one shape. It is a list of counties, or a combination of states and postal codes, and the map has to fill all of them as one region.

Why the built-in chart struggles here

PowerPoint's map chart shades regions by value. That is the wrong model for territories twice over: a territory is a group rather than a value, and the chart's region levels stop at state and postal code, so a county-based territory has nothing to match against. The chart will shade California and Nevada in two colors, then refuse to do anything with the eleven counties that make up a Central Valley patch.

Building one from counties or states

Start from a map at the level the territories are defined at. If the CRM assigns counties, start from the state's county map.
Ungroup the map once. Every area is now a shape, listed by name in the Selection Pane.
Ctrl-click the areas that belong to one territory, then Group them and name the group after its owner.
Fill each group. Grouping first means the next edit moves a territory rather than a county.
Put the owner's name on the group, not on each county, and turn off the individual area labels.

Naming territories so a reader can find them

The labeled slides in a template name every area, which is right for a reference map and wrong for a territory map: 254 county names on one slide is noise. Hide the fine labels, name the territories, and keep the area names in the Selection Pane where they are useful — which is what makes the next territory change a two-minute job instead of a rebuild.

Keep a legend for the overlays. If one territory is split across two colors to show two products, say so. A map with four colors and no legend gets read as four territories.

Keeping it current

Territories change at the start of a year, and sometimes in the middle of one. Because the map is made of shapes, a change is a selection and a fill: move the counties that changed owner from one group to another. Nothing is re-exported, nothing is redrawn, and the deck that went to the board in January still matches the one in April.

Where the map goes next

The same slide usually appears three more times: in the quarterly business review, in the coverage slide of a hiring plan, and in the onboarding deck for a new rep. Keeping it as one file with three themes means the map can be restyled to whatever deck it lands in without being rebuilt.

$19.99 per template, one-time, with a refund window of 14 days. Browse county and state maps.

Questions

Can I build a sales territory map in PowerPoint?

Yes, if the areas are shapes. A territory is a group of counties, states or districts, so the work is selecting the member areas and filling them as one. A picture or a chart cannot make that selection, which is why territory maps are usually rebuilt in a design tool instead.

What is the smallest area a territory map should use?

Whatever the CRM assigns. Most teams assign counties or postal codes; some assign states. The map has to be at the level the quota is measured at, or the picture and the pipeline report describe different things.

How do I keep the map current when territories change?

Because the areas are shapes, a change is a fill rather than a rebuild: recolor the counties that moved and the map is current. Keeping each territory's areas grouped makes that a single selection.

Does the map connect to a CRM?

No. These are PowerPoint shapes with national codes carried on them, not a live data connection. The code is what lets you match the map to an export from the CRM: join on the code, not on the place name.