How to Build a Walk List That Saves Canvassers Hours

By noon the rep has given up on the route. He's been driving six blocks between doors all morning because the list came straight out of a database, sorted by nothing that matters on foot, and following it honestly means zig-zagging across the whole neighborhood. So he stops following it, starts freelancing, and by the end of the day nobody — not him, not his manager — can say which doors got worked. He wasn't lazy. His walk list was built backwards.

A good walk list does the opposite: it clusters addresses geographically, filters out the doors that can't convert, orders the stops so the canvasser never backtracks, and drops cleanly into a mobile app. It costs the same to generate as the bad one and adds four to six real doors an hour. This guide builds one from scratch — whether you're running a campaign, a solar team, or a roofing blitz.

What a walk list actually is

A walk list is the ordered sequence of doors a canvasser works in a single shift. It's three things stacked: a contact list (who to see), a filter (which doors matter), and a route (the order that minimizes travel). Get all three wrong at once and you get the morning above — low-value contacts, no geographic logic, a rep zig-zagging. Get them right and the same raw data becomes a shift a person can actually finish. The term goes by "door list," "knock list," or "turf sheet" depending on the industry; here they all mean the same thing.

Step 1: Start with the right source data

Your list is only as good as the data feeding it — garbage in, garbage means wasted doors. For campaigns that's the state voter file, third-party enriched voter data, and prior canvass results; for sales teams it's homeowner data with property attributes (year built, roof age, square footage), permit data, and storm overlays. Every row needs, at minimum, a full verified address, a first and last name, and a status field you can update in the field. Addresses without coordinates can't be routed — if your vendor doesn't include lat/lng, geocode before you build. WalkLists handles geocoding automatically when you import homeowner or voter data.

Step 2: Filter down to your real target universe

This is where most programs leave efficiency on the table. Knocking every address in a zip is for amateurs — define exactly who you want to reach and make everyone else invisible to the canvasser. Political lists filter on registration, support score, age, and vote history; roofing and solar on owner-occupied, square footage, year built, and storm-damage overlays; insurance on income band and structure age. A typical campaign might cut a 10,000-contact universe to 2,000 targeted households. That's not waste, it's the opposite — every door a filter removes is time spent on a door that can actually convert. When you're targeting after a storm, filtering on storm and hail data first is one of the highest-leverage moves in the whole process.

Step 3: Define your turf

Turf is the geographic boundary one canvasser or team will work, and defining it before you build individual lists keeps reps out of each other's way and guarantees coverage without overlap. Two approaches: manual cutting, where a manager draws polygons and assigns each to a canvasser (precise control, good for dense neighborhoods), and auto-routing, where the software clusters nearby addresses automatically (faster for large deployments). Aim for roughly 60–90 doors per canvasser per shift — over 100 and they rush, under 50 and you're underusing labor.

Step 4: Route the addresses in walk order

Lists sorted by street name or house number produce inefficient routes — sometimes a mile of driving between consecutive entries. Walk order means the canvasser starts at one end of a block, works both sides, and moves on without backtracking. Two principles do the heavy lifting: compact clustering (group addresses close enough to walk between, not drive) and logical block progression (work one side, cross, work back — never split a block across the middle of the list). Modern platforms handle this with TSP-variant algorithms — WalkLists' route optimization engine accounts for one-way streets, gated communities, and multi-unit buildings. Building by hand in a spreadsheet? Sort by zip → street → odd/even house number as a rough approximation that at least kills the worst inefficiencies.

Step 5: Add canvasser context to each door

A list without context forces the rep to improvise. Give each door as much as the canvasser needs — and no more:

Five to eight well-chosen fields is the ceiling. Past that, the canvasser stops reading.

Step 6: Export to something canvassers can actually use

A spreadsheet is fine for one or two canvassers. For anything larger you need a mobile app that shows the route on a map with numbered pins, records dispositions in the field, handles offline dead zones, and syncs back in real time. Exporting a CSV and asking reps to open it in Google Sheets on a phone introduces transcription errors, delays sync, and makes live tracking impossible — past about five canvassers, paper or spreadsheet lists cost more in data-quality losses than software saves. WalkLists exports straight to a mobile interface with map view, disposition logging, and offline capability; canvassers tap through the list while supervisors watch progress on a live dashboard.

Step 7: Validate before you deploy

Build one list, walk the first 15 doors yourself, and catch the problems that only surface in the field before they multiply across a team: gated communities that look walkable but aren't, apartments listed as single-family, duplicate entries for one household, vacant lots that still show as active, business addresses in a residential list. Catching five errors on a test run saves you from multiplying them across 20 canvassers.

Step 8: Capture dispositions and update the list

A walk list is a living document. Every knock generates data — answered or not, yes or no, callback requested — and all of it feeds the next list. Standard disposition categories: completed/converted, not home (door hanger left), not home (no contact), refused, moved/wrong address, callback requested, do not contact. At shift's end the completed list should sync back so those doors don't reappear tomorrow — unless they need a follow-up. This is exactly where manual systems collapse: a canvasser returning paper sheets at 9pm can't update a shared spreadsheet before the next team deploys at 7am.

Tips for better walk lists

1. Update your data before each deployment — a two-week-old list already has stale addresses and answered doors.
2. Weight by priority — put high-score contacts in the first 40% of the route so reps hit the best doors even if they run out of time.
3. Include a 10–15% buffer of extra doors so dead addresses and no-answers don't leave a rep idle.
4. Use geographic tightness as a quality metric — average distance over half a mile between consecutive doors means the route needs resequencing.
5. Suppress converted contacts immediately — don't knock a door twice in a cycle; it annoys residents and wastes time.

WalkLists vs. building your own

If your team is small — under five canvassers, single city, single campaign — a spreadsheet is manageable. Once you cross any of these lines, it breaks:

The WalkLists platform handles import, filtering, routing, mobile access, offline sync, and supervisor dashboards in one workflow — build the list once, the platform handles the rest.

Frequently Asked Questions

How many doors should a canvasser cover in one shift?

A well-routed list in a walkable neighborhood typically produces 60–80 knocks per 4-hour shift, or 15–20 an hour; suburban areas with longer blocks run 40–60. If canvassers are consistently under 10 an hour, the route density or geographic clustering is the problem — not the canvassers.

What's the difference between a walk list and a call list?

A walk list is ordered geographically — it's a physical route. A call list is sorted by priority or phone number with no geographic constraint. Many campaigns run both: canvassers work walk lists in the field while phone bankers work call lists at HQ. Walk lists usually convert higher because in-person contact is more persuasive; call lists cover more contacts per hour.

Can I build a walk list from an existing voter file?

Yes. Most state voter files include address data that can be geocoded and routed — filter to your target universe first (party, score, geography), geocode to get coordinates, then run a routing algorithm. WalkLists imports voter-file exports from most state formats and handles the geocoding and routing automatically.

How often should I rebuild the list during a campaign?

At minimum before each deployment day. In a fast-moving stretch — the final two weeks before an election, or a storm-chase roofing blitz — rebuild every 24–48 hours, folding in prior-day dispositions so canvassers aren't re-knocking answered doors.

Ready to build your first walk list without a spreadsheet? Start free with WalkLists — import your data, set your filters, and have a routed, mobile-ready list in under ten minutes.