Deliveries and volunteer routes

Deliveries turns sign requests into optimized driving routes and hands each one to a volunteer. Open Deliveries under Field in the sidebar. The badge shows how many requests are approved and ready to route. A Requests / Routes switch at the top of the page flips between the incoming request pool and the routes you have already planned. The Plan routes button stays disabled until at least one request is approved and located. There is nothing to route before then.

Requests: approve what comes in

Every request is tied to a household, so its map location comes from the household’s address. The Readiness chip tells you the geocode state (Located, Locating…, or Address problem), and a request must be approved and located to be routed. Select rows and use Approve or Decline in the selection bar; the count is repeated on every button.

Plan routes (preview first)

1. 1Click Plan routes · N readySet the start address drivers leave from. Start typing and pick a suggested address. It’s remembered for next time.
2. 2Preview routesPreview is a pure calculation. It doesn’t save anything. You’ll see proposed routes, per-stop travel times, and an honest explanation of anything that couldn’t fit.
3. 3Create N routesOnly now is anything saved. All the routes are created together and you land on the routes list.

Assign and share

On a route, assign the volunteer first. The link is personal to them. Click Assign next to Volunteer, search by name or email, and pick the person (use Change or Remove volunteer to swap or clear them later). Then Copy volunteer link mints a private link and copies it to your clipboard. It expires after 30 days as a security safeguard, unless an administrator turns expiry off under Workspace → App (handy when routes run longer than a month). You can do all of this without opening the route: the Routes list has an inline Assign on any unassigned row, and each row’s ⋯ menu covers assign/change volunteer, copy the link, and cancel or delete the route. Like the Canvass Companion, the volunteer verifies a one-time code sent to their email or mobile on file, and a first-time volunteer needs a one-time admin approval on the Volunteer access page. Open in Google Maps launches turn-by-turn for the whole route. Reordering stops recomputes the estimate for you. Revoke or regenerate the link any time from the ⋯ menu.

Volunteers deliver

The volunteer opens the link on their phone and works one stop at a time: Mark delivered, Couldn’t deliver (with a reason), or Skip for now (moves the house to the end). The page shows first name and address only, never a constituent’s email or phone. Undo is available on any delivered or skipped stop, even after closing and reopening the page. A house reported undeliverable returns to your planning pool automatically, and when every stop is handled the route finishes itself.

Yard sign standing on profiles

You don’t have to open Deliveries to check a sign. Every household page carries a Yard sign card, and every person page shows the same control inside the Campaign standing card, right next to support level and voting status. It reads straight from the request pool for the campaign you are working in: None requested, Requested, Approved, Declined, or Delivered, with who asked, where it came from, and a link to the route it is riding on.

Flip the status yourself when reality happens outside the app. Pick Delivered if someone installed a sign by hand, or record a brand-new request for a household that asked in person. If the house is sitting on an active route when you mark it delivered, the route’s stop is marked delivered too, so volunteer progress stays truthful. The change lands in the household’s and requester’s activity history.