How Door-to-Door Sales Teams Use Territory Mapping to Close More Deals

If you've managed a door-to-door sales crew for more than a week, you've already run into the re-knock problem. Two reps work the same block, hit the same houses, annoy the same homeowners, and blame each other in the group chat. It's not a people problem — it's a territory problem. And fixing it with better mapping is one of the fastest ways to increase productivity without hiring a single new rep.

Territory mapping is the practice of dividing your service area into clearly defined zones, assigning each zone to a specific rep or team, and tracking results at the zone level. Done right, it eliminates overlap, reduces drive time, and gives managers a clear picture of which areas have been worked and which haven't.

Why territory mapping directly affects close rates

Most D2D sales managers think about territory mapping as a logistics problem — how do we divide up the map so everyone has enough houses to knock? That's part of it. But the deeper reason territory mapping boosts close rates is trust.

When a homeowner gets knocked twice in three days by different reps from the same company, they don't think "this company is thorough." They think "this company is disorganized, and if they can't run their own operation, why would I trust them with my roof?" One re-knock can kill a sale that was already warm.

On the other side, a rep who knows their territory owns it. They're not racing to beat a coworker to a street. They can pace themselves, note which houses are a re-visit in the afternoon, and build a mental model of their area. That confidence comes through at the door.

The three territory-drawing methods (and when to use each)

There are three common ways D2D teams carve up their areas. Each has trade-offs.

Zip code-based territories are the easiest to explain and assign. "You've got 90210, she's got 90211." The problem is zip codes aren't drawn for sales density. One zip might have 200 houses; the next might have 4,000. You end up with wildly uneven workloads and reps who feel like they got cheated.

Pin-drop territories are more granular — a manager drops a pin on the map and draws a rough radius. Better than zips, but most tools don't tell you how many houses are inside that radius until your rep is already in the field.

Polygon territories give you the most control. You trace a shape on the map — a few blocks, a subdivision, a neighborhood — and the tool fills in the actual residential addresses inside that polygon. You know exactly how many doors you're assigning before your rep drives out there. RepGrid uses polygon drawing with auto-populated houses from OpenStreetMap, so managers can size territories accurately without any manual counting.

How to set territory size for your team

A common mistake is drawing territories that are either too big (rep spends more time driving than knocking) or too small (rep runs out of doors before end of shift). The right size depends on your product, pitch length, and target close rate.

A good starting heuristic for a full-day territory: figure out how many doors your average rep can reasonably knock in a shift (accounting for travel between houses, pitch time, follow-up notes, and breaks), then add 20% buffer. In dense suburban areas, a typical D2D solar rep might knock 80–120 doors in a solid 8-hour day. A roofing canvasser doing longer pitches might cover 40–60.

Don't forget to account for not-home rates. In most residential areas, 40–60% of households won't answer. Your rep needs enough raw doors to hit their contact goal even accounting for no-answers.

Assigning territories without creating conflict

The two biggest causes of territory disputes are ambiguous boundaries and unclear ownership. Both are solved by software.

Ambiguous boundaries happen when territories are described in plain English ("the east side of town") rather than drawn on a map. Get your territories into a digital tool where the lines are visible to everyone. When a rep asks "is this street mine?", the answer should take three seconds to verify, not a phone call to the manager.

Unclear ownership happens when territories are reassigned without updating the records. Rep A quits on a Wednesday, and by Thursday, Rep B and Rep C are both working the same houses because nobody updated the system. A good CRM lets you reassign a territory in one tap, and every rep sees their own map immediately.

Status tracking makes territory data useful

Territory mapping only pays off if you're tracking status at the house level. If your rep marks a house as "Warm Lead" on Monday, and their replacement knocks the same house cold on Friday, you've lost that lead. The status needs to follow the house, not the rep.

This is why territory mapping and status tracking need to be in the same tool. Spreadsheets fail here — status info lives in someone's personal file, and when they quit, it goes with them. A purpose-built field CRM like RepGrid attaches status history to each address permanently, so managers can see the full knocking history of any house regardless of which rep visited it.

Measuring territory performance over time

Once your territories are drawn and being worked, you have the data to actually optimize them. Look at:

• Contact rate by territory — some neighborhoods have higher not-home rates at certain times of day. This tells you when to schedule those areas.
• Close rate by territory — if one zone consistently closes at 3x the rate of another, that's a signal about demographics, competition, or product fit in that area.
• Revenue per door knocked — the single most useful efficiency metric. Divide total revenue from a territory by total doors knocked to get a number you can compare across zones and reps.
• Re-visit conversion rate — how often does a "Re-visit AM" or "Re-visit PM" status actually turn into a booked job? If it's low, your reps aren't following through on callbacks.

Getting your team to actually use the system

The biggest adoption killer is friction. If logging a status update takes 4 taps and a text field, reps will skip it and do it later (they won't). If it takes one tap from the same screen where they see their territory map, they'll do it at the door.

Build the habit in the first week. New reps should only ever open one app in the field. If they're switching between a map app, a note-taking app, and a spreadsheet, the system is too fragmented and it will collapse. The status update, the territory view, the timer, and the team chat should all live in one place.

RepGrid is built around this constraint — every D2D workflow lives on one screen so reps don't have to context-switch while standing on a porch. You can read more about how to draw and assign territories or what offline support really means in a field app in the RepGrid library.