Running a doorknock weekend
A weekend of canvassing is won or lost in the week before it. This is the sequence that gets twenty volunteers onto the right doors with the right script and gets the data back clean.
Before the weekend
Cut the turf first, not last. Turf is the constraint everything else hangs off – how many volunteers you need, how long a shift runs, which suburbs get covered. Cut it from the map or straight from geographic areas, and watch the live address-count estimate as you draw. A turf of 120–150 doors is roughly a three-hour shift for a pair who stop and talk.
Decide what a good conversation looks like. Build or pick the survey before you recruit, because the survey defines what you will know on Monday. Keep it to three or four questions – a doorstep is not a focus group. See Building a branching survey.
Check your dispositions. Your outcome codes should be the words your volunteers will actually use. If half the team says "not home" and the system says "no contact", you will lose a fortnight to reconciliation. See Reading your results.
Set the shift, then invite. A named shift is a kept commitment far more often than a general call-out. Put the shifts in the calendar first so the invitation points at something concrete.
The morning of
Run the briefing to a clock. Fifteen minutes, standing up:
- Why this turf. One sentence on what the data says about these streets.
- The ask. What you want each conversation to end with.
- The app. Everyone installs it before they leave the room, not on the footpath.
- Pairs and turf. Assign on the spot; reassign as people arrive late.
- When to come back. A hard time, a named meeting point.
Have volunteers install the canvasser app to their home screen in the room, where there is wi-fi and someone to help. It takes a minute and removes the single most common reason a first-timer never records a door.
During the shift
Watch the action room rather than ringing round. It refreshes your active canvassers roughly every ten seconds, so you can see who has started, who has stalled, and which turf is moving slowly.
Use broadcast push sparingly and for real things – a weather call, a target bump, a change of meeting point. A channel that only carries signal keeps getting read.
Do not chase data during the shift. Volunteers in a basement block are not offline by mistake; the app queues every knock on the device and flushes it when signal returns. Missing numbers mid-shift are almost always a sync that hasn't happened yet, not a knock that was lost.
Straight after
Debrief while people are still in the room. Ask two questions: what surprised you, and what did you not have an answer for? The second one becomes next week's talking points.
Then look at the numbers the same day:
- Contact rate. Doors knocked versus conversations had. If it collapsed, the problem is timing or turf, not the script.
- Support distribution. Where the conversations actually landed on the five-point scale.
- Pace against target. Whether this weekend's rate gets you to the number by the date that matters.
The following week
Feed it back. Roll the strong supporters into an audience for the next event, put the persuadables into a follow-up list, and stop spending volunteer hours on streets that came back solidly opposed. That is the loop – see Reading your results and Turf and walk lists.
Common failure modes
- Turf cut too big. Volunteers finish a third of it, and your coverage data is a lie by omission.
- No named shift. "Sometime Saturday" produces about half the people that "10am Saturday" does.
- Survey too long. Question five is where the conversation dies and the disposition gets guessed.
- No debrief. The most valuable thing you collected all day walks out of the room in people's heads.