How to draw and assign knocking territories the right way

Why most territory plans fail

Most territory plans fail for the same reasons: they were drawn once, in a hurry, on a desktop, without the reps in the room. Then they stayed frozen while the crew, the market, and the season changed underneath them.

A good territory plan is a living thing. Density changes, reps come and go, certain neighborhoods get saturated. The territory map should be re-drawable in five minutes, not a quarterly project.

Polygon vs pin-drop vs zip code

Three common ways to define a territory:

• Polygon. Sketch a boundary on the map, every house inside is part of the territory. Best for new neighborhoods because the system populates the houses for you.
• Pin-drop / lead list. Hand-pick specific addresses (or upload a CSV). Best for re-knock campaigns or qualified-leads-only motions, terrible for fresh canvassing.
• Zip code or census tract. Coarse, shape doesn't match how reps actually walk. Useful for revenue analytics, bad for assignment.

Default to polygons. Use pin-drop only when you genuinely have a curated list. Avoid zip-based assignments.

Density-based vs revenue-based carving

Two ways to size a territory:

• Density-based: "300 doors per rep per day." Simpler, doesn't account for income or qualification differences.
• Revenue-based: "$X expected revenue per rep per week." More accurate but harder to predict for new neighborhoods.

For new crews, start density-based and switch to revenue-based once you have two or three weeks of actual results to model on. Trying to predict revenue from a cold map is a great way to overthink the decision.

Reassigning when reps quit

Rep turnover is constant in D2D. The territory tool's job is to make the handoff zero-friction:

1. Reassign the polygon to another rep with one tap.
2. The new rep sees the full status history per house — who was knocked, who said come back tomorrow, who's a warm lead waiting on a callback.
3. The departed rep's notes are still attached to each house.

If your tool requires you to "transfer leads" rep-to-rep manually, you'll lose information every single time. The data should live with the house, not the rep.

Tools that do it well

For polygon-based assignment with auto-populated houses and per-house history, the cleanest options are RepGrid (mobile-native, clear field-team tiers), SPOTIO (web-first, more configurable), and SalesRabbit (enterprise depth). For very small teams or specialized verticals like real estate, Knockwise and similar tools have more focused overlays.

Saturation and re-knock cadence

Every territory eventually saturates. A neighborhood that converted at 4% on the first sweep might convert at 1.2% on the second sweep three months later, and 0.4% on the third. The right re-knock cadence depends on the product and the season — solar crews often re-knock every 90–120 days through summer, pest control re-knocks quarterly to match the treatment cycle, roofers usually only re-knock after a storm event. The CRM should make saturation visible (per-territory percent-knocked, percent-converted) so you can see when it's time to retire a polygon and draw a new one.

Without that visibility, crews tend to over-knock a few favorite neighborhoods and never expand. The owner notices when revenue plateaus and the crew is still putting in full hours.

Multi-rep coverage and overlap rules

For larger crews, the question becomes whether multiple reps can knock the same house in sequence (e.g., a junior rep knocks first and a closer comes back for warm leads). Three common patterns:

• One-rep-per-house, hard lock. Once a house has any status other than Not Knocked, only the assigned rep can update it. Simplest; works for most crews.
• Tier-based handoff. Junior reps qualify, then a senior closer is invited to specific warm leads. Requires the CRM to support a re-assignment workflow without losing history.
• Time-based reset. A house auto-returns to the pool after N days of inactivity. Use cautiously — it can punish reps for working slow leads.

Whichever model you pick, write it down and make sure the CRM enforces it. Tribal knowledge about "who knocks what" creates commission disputes within weeks.

A practical territory checklist

• Polygon, not pin-drop, for fresh neighborhoods.
• Natural boundaries (roads, parks) over arbitrary cuts.
• 200–400 doors per rep per day as a starting point.
• Reps see only their own territory by default.
• Status history lives with the house, survives rep turnover.
• Re-draw monthly based on actual saturation, not on the original plan.