Canvassing Route Optimization: Cut Walk Time 30%

Two canvassers work the same 60 doors on the same afternoon. One walks eight miles and drags in exhausted at four o'clock with half the turf undone. The other walks four, finishes early, and asks for a second list. Neither is faster or fitter than the other. One of them got a *route*; the other got a *list*, and the list sent her backwards up one street and down another two blocks over, all day long.

That's the entire case for route optimization: a canvasser who's walking isn't knocking. Optimization is just the work of reordering the same addresses so your team spends its hours at doors instead of between them. This guide covers the three routing strategies field directors actually use, how the algorithm works, how to set it up in WalkLists, and the configuration mistakes that waste doors even with good software.

What canvassing route optimization is

Route optimization resequences a list of target addresses so a canvasser covers them in the shortest total walking distance. The point isn't raw speed — it's knock density: answered doors per hour on the street.

A raw voter file or prospect list knows nothing about geography. Pull 200 addresses from a database and they'll scatter a canvasser across three zip codes, up one side of a street and back two blocks over. Optimization reorders those same addresses into a path that respects block structure, kills backtracking, and keeps the canvasser moving forward. Underneath, it's a variant of the Traveling Salesman Problem — expensive to solve perfectly at scale, so canvassing software uses fast approximations (nearest-neighbor, two-opt swaps, cluster-first) that get close enough that the last few percent don't matter on the ground.

A real router also has to respect the things a straight line ignores: one-way streets and legal crossings, block face (finish one side before crossing), apartment buildings (vertical density needs its own handling), the canvasser's start and end point, and suppression zones like gates and no-knock lists.

Why walk order decides the day

Go back to the two canvassers. The one on the unoptimized list wasn't slow — the list walked her eight miles to knock what four miles would have covered. That extra four miles is pure waste, and it compounds in a way that decides campaigns. One wasted mile per canvasser, across a team of 20, across a 60-day campaign, is 1,200 person-miles burned on transit — thousands of doors that never got knocked. In a close race, that's the margin.

For commission teams — roofing, solar, pest control — it hits the paycheck directly. A rep who knocks 22 doors instead of 35 because the route sent him wandering doesn't just lose contacts, he loses closings. Routing isn't an operations detail; it's a revenue variable.

Three routing strategies, and when each wins

Not every campaign needs the same approach:

For campaigns working precinct-sized turf, the turf cutting vs. auto-routing choice is real — each handles multi-canvasser coordination differently, and the wrong pick creates overlap and double-knocking. For a solo sales rep who controls their own list, pure auto-routing usually wins. And the fourth option, hand-sequencing by street name, is what teams default to without software — better than random, far worse than any algorithm on non-grid streets.

How auto-routing actually works

Most canvassing apps run a variant of the two-opt algorithm:

1. Generate an initial route (usually nearest-neighbor).
2. Pick two edges in the route and reverse the segment between them.
3. Keep the change if the total distance dropped; discard it if not.
4. Repeat until no swap improves the total.

Two-opt runs fast enough to compute server-side before routes hit devices, and lands within a few percent of optimal on residential layouts — a gap worth at most an extra block, nothing next to eliminating backtracking entirely. Better engines layer in real road-network data — one-way streets, turn restrictions, actual pedestrian paths — which matters in dense grids where the straight line between two doors crosses a highway.

WalkLists computes routes server-side and fixes them before the canvasser starts, on purpose: live rerouting on the phone burns battery and causes decision fatigue. Canvassers can still skip or reorder by hand, and the app recomputes the remaining sequence from wherever they're standing.

How to set up optimized routes in WalkLists

Four steps, and the choices here directly set your walk time.

Step 1: Upload and clean the list

Route quality can't beat geocoding quality — an address that lands on the wrong block face or the center of a big parcel creates a small detour that compounds across the whole route. Upload your CSV or sync from your CRM, and apply every filter *before* routing: target universe, suppression, prior-contact exclusions. The optimizer works with whatever it's handed, so clean input is clean output.

Step 2: Set turf boundaries for multi-canvasser runs

Running more than one canvasser? Draw turf boundaries before routing and assign each person a zone, or you'll get overlapping routes, double-knocked doors, and frustrated volunteers. The router keeps each canvasser's addresses inside their area. Solo canvassers skip this and go straight to parameters.

Step 3: Configure the parameters that matter

Three settings move walk time the most:

• Start and end point. Set the actual parking spot or drop-off; a route optimized from the wrong origin adds needless walking to the front of every shift.
• Block-face preference. Finish one side of a street before crossing. It costs a small detour at intersections but means a new canvasser never has to think about which side they're on.
• Density clustering. For blocks with apartments mixed in, cluster a building's units so the canvasser clears the whole building before moving on, instead of interleaving 3B, a house two blocks away, then 3D.

Step 4: Push routes to devices

When the route computes, push it to the WalkLists app. The canvasser sees a numbered list, each finished door showing its logged disposition, with the next address surfacing automatically after every knock — no scrolling, no navigation. Push the night before and canvassers start the moment they arrive instead of waiting on a manager to queue lists.

Configuration mistakes that quietly cost doors

Even with good software, these come up constantly:

• Over-large routes. Assign 200 doors to one canvasser and they'll finish 60–80 and carry the rest — and the unreached doors log as "not attempted," which corrupts follow-up. Build 80–100-door routes and let fast finishers extend.
• Wrong start point. A route optimized from the center of the turf instead of the parking spot adds walking to the front of every single shift.
• Ignoring apartments. Without density clustering, an auto-router interleaves 3B, a street address two blocks off, then 3D. Enable it for any list with buildings.
• Last-minute routing. Pull lists and route the morning of, and canvassers stand around while it computes. Route the night before.
• Never reviewing the GPS trace. A route that looked clean can hide a locked gate or a construction closure the algorithm didn't know about. Check the actual GPS path after the first pass through new turf and update suppression zones.

Tips for maximum doors per hour

Optimization is the floor; these raise the ceiling:

1. Start knocking around 10am on weekdays — people are home and not rushing out.
2. Hit the apartment buildings first in mixed routes — predictable, high-yield, and better while energy's up.
3. Cap new canvassers at 60 doors for their first few shifts; an 80-door route that takes a veteran six hours takes a rookie eight.
4. Never re-knock in the same shift — mark "not home," move on, and put return visits on a dedicated follow-up route.
5. Brief the next address while still at the current door — the 30-second reset between conversations gets faster when they already know where they're going.

For political canvassing teams, add one more: sort the universe by likelihood score before routing. Routing decides the order; targeting decides who's on the list — combining both is where contact rates climb most.

Frequently Asked Questions

How many doors can one canvasser realistically knock in a day?

Experienced canvassers on well-optimized residential turf usually knock 60–100 doors in a six-to-eight-hour shift, depending on answer rate, conversation length, and how tightly the doors sit. Apartment-heavy routes can top 100 because vertical movement replaces street walking; rural routes rarely clear 50 because the gaps between doors mean driving, not walking.

Does optimization still matter for small lists under 50 addresses?

Yes, but the payoff shrinks. For 50 walkable doors in a tight neighborhood, optimized versus not might be 20–30 minutes of walking. The gains explode at scale — 200-plus addresses across irregular geography with multiple canvassers — where routing often decides whether the team finishes or carries a big chunk to tomorrow.

Can canvassers change the route order on the fly?

In WalkLists, yes — skip or reorder, and the app recomputes the remaining sequence from the current position. But frequent manual changes usually mean the original route had a problem: a bad start point, an apartment block that wasn't flagged for density clustering, or a gated community missing from suppression. Treat manual overrides as a signal to fix the setup, not a habit to lean on.

What's the difference between turf cutting and auto-routing for teams?

Turf cutting assigns geographic zones first, then sequences within each — easy to manage visually and naturally overlap-proof. Auto-routing optimizes the full set algorithmically for more efficient individual paths, but needs turf enforcement as a separate step. The full breakdown compares them directly.

Route efficiency compounds across every shift, every canvasser, every day of a campaign. Compare WalkLists features to see where routing fits in the platform, or register free and run your first optimized route in under a minute — then hand your team the four-mile day instead of the eight.