Forty signs in a trunk. Addresses in a text thread.
Every campaign has lived it: the requests live in three inboxes, the driver gets a screenshot of a list, and two weeks later somebody asks why the Chens on Alder Street never got their sign.
pplCRM keeps one queue of requests and sends the approved ones out as delivery outings — batches of doors in driving order, delivered from the same phone app your canvassers already use.
A request has one home and four states.
One open request per household per kind — a sign request and a flyer request can coexist, two of the same cannot. Asked for at the door, approved at a desk, delivered from a car. No step happens in a spreadsheet.
A canvasser taps “wants a yard sign” in the companion, a supporter checks the box on your web form, or a teammate records it in the CRM. Either way it lands in one queue — nothing lives in a text thread.
You approve each request, and a readiness chip shows whether the address is placed on the map yet. A request with an address problem links straight to the household to fix it.
Cutting a delivery outing claims its requests, so two outings can never be sent to the same lawn. Each request’s row names the outing carrying it; retire the outing and its undelivered requests return to the pool.
Marked by the volunteer at the door, by a canvasser planting the sign mid-walk, or by a teammate in the CRM. All three flip the same request.
“Can you take one outing tonight?”
One button turns the approved pile into outings a volunteer can actually say yes to: you pick what they carry and how many doors, and the doors arrive in driving order. Cutting claims the requests, so nothing is handed out twice.
Press “Cut into outings” on the Requests tab and the wizard opens with delivery already chosen: pick signs, flyers or both, pick how many doors per outing, and the approved pile becomes batches a volunteer can say yes to. Anything without a map position is named, not hidden.
A delivery outing’s doors are ordered for a car, not a walker’s street sweep. The math is deterministic and runs on our servers — no third-party routing service ever sees your addresses.
On the volunteer’s phone, every stop has a Navigate button, and one tap opens the next stretch of stops in Google Maps as a waypoint chain, for the driver who wants voice directions.
One stop at a time, honestly.
Assigning a volunteer sends their personal link by email and text in the same moment. No install, no account — re-assigning rotates the link, and every volunteer verifies a one-time code and is approved once by an admin.
The outing is a numbered stop list with the next undone door ringed, and two honest buttons on every row: Delivered, and Couldn’t deliver — which asks for a reason your office sees on the request.
It is the same offline-first companion canvassers use: taps queue on the phone and sync back when signal returns, and Undo is right there for the fat-fingered “Delivered” at a red light.
The volunteer sees what the doorstep needs — who lives there, the address, and what happened at the door before. Never an email, a phone number or a donation history. A lost phone leaks a door list, not your voter file.
Mark a door “couldn’t deliver” and the request stays with the outing for a retry, reason attached. Retire the outing and every undelivered request returns to the pool on its own. Nobody keeps a list of leftovers in their head.
The field and the office stop disagreeing.
“Out for delivery” is one claim on the request itself — taken when an outing is cut, released when it retires — so the canvassing crew, the delivery volunteers and the office are always looking at the same truth, and no house is ever handed to two people.
Every household page — and the campaign card on every person — shows where the sign request stands: none, requested, approved, declined or delivered, with who asked and a link to the outing carrying it.
A canvasser carrying signs can mark one delivered right at the door. The request flips everywhere at once — including on a delivery outing that was carrying it, where the door shows as already served.
The limits, from us, before you ask.
A request joins an outing once its address is placed on the map. Address lookups run on the Movement plan, spread over a daily budget, and a request that cannot be placed says so on its row — with a link to fix the address — rather than being silently skipped.
The driving order is computed from distances between houses on our servers — it does not know about one-way streets or bridges. That is why every stop hands you to Google Maps for the actual roads, and why we don’t promise per-stop minutes.
Requests, delivery outings and the volunteer app are on the Movement plan. Every new workspace’s demo data unlocks all of it, so you can send out demo outings before paying anything.
Send out an outing over sample data tonight.
Your free workspace opens with sample households and sign requests already waiting. Approve a few, cut them into outings, and open one on your own phone. No card, no time limit.