ProxiMap

ProxiMap Guide

Your book on a map, in about five minutes.

No GIS background needed. If you can get a spreadsheet out of your CRM, you can build a territory map.

On this page

  1. The one idea to get first
  2. The five minute version
  3. Getting your file right
  4. Building areas from accounts
  5. The five tools
  6. The three select modes
  7. Groups: the layer above a territory
  8. Balancing the workload
  9. Anchors, coverage and drive time
  10. Scenarios: trying a shape before you commit
  11. Exports, PNGs and printing
  12. Saving, backing up, sharing
  13. When something looks wrong

1. The one idea to get first

Almost every confusing thing in ProxiMap comes from one distinction, and once you have it the rest is obvious.

An account is a dot. An area is ground. They are two different things and a territory can have one without the other.

An account is a row from your file. A hospital, a school, a customer. It has a ZIP, so it lands somewhere on the map as a dot.

An area is a piece of the country. A county, a ZIP code, or a state. It is a shape, and it is what actually gets colored in.

When you import a list with a territory column, ProxiMap knows which rep owns which account. It does not yet know which rep covers which ground. That is why a fresh import can look like a blank map even though every account came through fine. The dots are there. Nobody owns any ground yet.

Fixing that is one click, and it is the next section.

This also explains something that surprises people: a rep can own an account outside their own ground. That is not a bug. A system owned by one rep inside another rep's region is a real thing in the field, so the map shows coverage and the book shows ownership, and they are allowed to disagree.

2. The five minute version

If you only read one section, read this one.

1
Open ProxiMap and pick "Your own list." Paste your spreadsheet or choose the file. If you want to see how it works first, hit Load sample.
2
Click Next until you reach Open the map. The defaults are fine. If your file has a territory column we spot it and tell you so.
3
Nothing. It builds itself. If your list names territories, we hand every county to the territory whose accounts sit in it, fill the gaps, and clean up the borders. You land on a finished map. Undo puts it back to blank if you would rather draw it yourself.
4
Switch Tool to Lasso and fix what looks wrong. Pick a territory, draw a loop, approve it. Nothing commits until you say so, and Undo goes back ten steps.
5
Hit Lock plan. That makes this map the source of truth the rest of the suite measures against.

That is the whole workflow. Everything below is detail on one of those five steps.

3. Getting your file right

CSV or paste. One row per account. A header row helps but is not required.

ColumnNeededWhat we do with it
NameYesWhat the account is called. Anything with name, account, facility, hospital or org in the header.
ZIPYesWhere it goes on the map. Header with zip or postal.
SizeOptionalBeds, revenue, students, volume. This is what you balance on.
TerritoryOptionalIf it is there, we build your territories from it automatically. This saves the most time of anything in the product.
GroupOptionalYour region, district, area, zone or division. We build the groups from it and drop each territory into the right one. Header can say group, region, district, area, zone, division, SBU, segment, cluster or pod.
ScoreOptionalA ProxiScore exported from ProxiMed. We read it, we never invent one.

Things that bite people

4. Building areas from accounts

This is the step that does the heavy lifting, and if your list had a territory column it has already run by the time you see the map. It takes a map where territories own accounts and turns it into a map where territories own ground.

It runs in three passes:

  1. Seed. Any county holding your accounts goes to whichever territory has the most of them in it.
  2. Fill. Counties with no accounts go to the nearest territory that already works in that state, so nobody ends up covering an island they have never sold into. This is what gives you a map with no holes.
  3. Smooth. A county surrounded by one other territory joins it. Repeated until it settles. This is what turns speckle into clean borders.
Smoothing moves ground. It never moves your accounts. Your book is exactly as you uploaded it when this finishes. Only the coloring changes.

Everything it did is one Undo away, and the message afterwards tells you the numbers: how many came from your accounts, how many were filled in between, how many got tidied.

Territories are also recolored so no two that touch share a color. If you picked a color by hand, we leave it alone and color around it.

5. The five tools

The Tool dropdown decides what a click on the map does. This trips up more people than anything else, because the map opens in Move mode where clicks deliberately do nothing.

ToolWhat it does
Move mapDrag to pan. Clicks do not select. This is how the map opens, so a stray click cannot wreck your work.
PointClick one area at a time. Good for fixing a single county.
RectangleDrag a box. Fast for a block of the map.
LassoDraw a loop freehand. The one you will use most.
CircleDrag out from a middle point. Good for "everything within about this far."

Nothing commits the moment you draw. A selection is staged first, you see what it does to the balance, and then you approve it. Tick Keep this menu open at the bottom of the Tool dropdown if you are switching tools constantly.

6. The three select modes

Select decides what your tool is allowed to grab. It matters more than it looks.

ModeGrabsUse it when
NewOnly ground nobody holdsDrawing territories from scratch, so you cannot steal from yourself by accident.
ReplaceGround from whoever holds itAdjusting a finished map. This is what you want after Build areas.
RemoveHands ground back to unassignedCarving something out deliberately.
If your lasso says "0 picked up, N skipped, already in another territory," you are in New mode on a map where everything already has an owner. Switch to Replace. We now switch it for you after a build, but it is worth knowing.

7. Groups: the layer above a territory

Most sales orgs have more than one level. Region over district over rep is the normal shape, and if your territory names look like "SBU1 - Chicago" you are already doing this by hand inside a text column.

A group is a named bag of territories. Call it a region, a district, an area, a pod, a vertical, whatever you actually say out loud. Rename them to match your org.

A group owns no ground of its own. Ground belongs to exactly one territory, always. A group's coverage is simply the sum of its members. That is what keeps it safe: there is no way to end up with two things claiming the same county.

What a group gives you:

The easy way: put it in your file

Add a column called Group, Region, District, Area, Zone or Division. We read it at import, build the groups, and drop each territory into the right one. Nothing to click.

The other way: set them up in the panel

  1. Open the Groups tab in the panel.
  2. Hit New group and rename it.
  3. Scroll to "Which group is each territory in?" and set the dropdown for each one.
Balance still lives at the territory level. It does not help that your regions look even if the rep territories inside them are not. Groups are for reporting and navigation. Balance the territories.

Groups and your team

If you are on a Team plan there are three views of the same map, and groups are the middle one:

A manager or rep who is not building the map does not get the builder. They get a read-only view of their own patch: a header with their totals, buttons to zoom, save a picture and export their accounts, and the map. No wizard, no tools, nothing they cannot use.

Scoping happens on the server, not in the browser. A rep is not shown the whole book with the other rows hidden; the other rows never leave the server.

One level, on purpose. Two tiers covers almost every small and mid-size sales org. If you need region over district over territory, use groups for the top level and put the district in the territory name.

8. Balancing the workload

The Balance panel is the point of the whole exercise. Pick what you are balancing on in the dropdown: counties, accounts, size from your file, a ProxiScore, or federal data underneath the map.

Balance on the thing that actually drives a rep's week. Account count is a fine start. Beds, revenue or a ProxiScore is usually closer to the truth, because forty small accounts and forty large ones are not the same job.

The Report tab turns all of this into a page you can hand to somebody: a balance grade, a workload table, and where the outliers are.

9. Anchors, coverage and drive time

Every distance in ProxiSuite measures from a territory's anchor. It is worked out in this order:

  1. A home ZIP you typed in the Settings tab. Always wins, because it is a person stating a fact.
  2. The middle of that territory's accounts. Territories built from a list get this automatically.
  3. The middle of its ground, for a territory that has been drawn but is still empty.
We anchor on the work, not on the geometric middle of the shape. Reps are productive when they sit near their accounts, and the empty ground between them is not where anybody drives.

Coverage draws rings from each anchor by drive time or distance, so you can see what a rep can realistically reach. Set the two ring sizes and hit Draw.

10. Scenarios: trying a shape before you commit

Realignment is an argument, not a decision. "Is the new shape actually better than the old one" is what it always comes down to, and the honest answer needs both numbers side by side.

Save the shape of the map before you start changing it. Then change it. Then look at the Report.

A scenario is a shape, not a copy of your book. It stores the territories, the groups and who owns which ground. It never copies your accounts, because your accounts are the same in every scenario. That is exactly what makes the rows comparable, and it means a scenario costs about a twentieth of a full plan to keep.

Restoring moves ground only. Your accounts stay where they are and Undo puts it back. If a territory in the scenario has since been deleted, its ground comes back unassigned rather than resurrecting a rep who is gone, and the message tells you how many.

A grade measured on Accounts and a grade measured on Counties are not comparable numbers. If you switch what Balance is measuring between scenarios, the table says so rather than putting two different things in one column.

11. Exports, PNGs and printing

Everything lives under Actions in the toolbar.

Turn off the account dots before exporting a territory picture. A clean colored map reads better in a deck than the same map with three thousand dots on it.

12. Saving, backing up, sharing

A big book uses a lot of browser storage. If you see a bar telling you this browser is out of storage, use Back up to my account or Save a copy to this device. Both work even when the browser cannot save any more.

13. When something looks wrong

What you seeWhat it means
Blank map after importOnly happens when your list had no territory column. Draw the territories, or run Build areas from accounts once your accounts are in them.
Clicking does nothingYou are in Move map mode. Change Tool to Point or Lasso.
Lasso grabs nothingSelect is on New and everything already has an owner. Switch to Replace.
Every territory reads 0 countiesSame as the blank map. No ground assigned yet.
Ideal 0 eachNothing to count yet. It fills in as soon as there is.
Rows we could not placeBlank, N/A or non US postal codes. They are listed under the map and stay in your plan.
A territory in several piecesUsually real, from islands or a split book. Lasso the stray bits into a neighbor if you would rather they were joined.
Undo did not put everything backFixed in August 2026. Undo restored the ground but not the accounts, on every operation that moved them. If you are on an older build, check your account counts after undoing.
Colors repeatTen colors, more territories than that. No two touching territories ever share one, which is what matters on a map.
ProxiField ProxiMed ProxiMatch ProxiMap How It Works Pricing Proximity Report Contact Support Sign In