πŸ—Ί Leaflet Route Builder

Turn a ward's road data into printable, walkable leaflet-delivery routes -- no installation needed, works from any Google Sheet.

1Load your road data

βš™ My area isn't listed, or I have my own tracker link
The address of the ward's live leaflet-map site. Reads its data source, backend, and title automatically -- nothing else on this page needs filling in by hand.
βš™ Load from a plain Google Sheet instead
In your Sheet: File β†’ Share β†’ Publish to web β†’ select the right tab β†’ format CSV β†’ Publish. Paste the link it gives you.

2Choose ward and route size

~90 minutes of leafleting at ~100 homes/hour, calibrated for a typical housing estate. A route covering the same target will be a much smaller area in a dense town centre, and a much longer walk or drive on spread-out rural roads -- the target is a residence count, not a distance.

Residence counts come from UPRN records (unique property references), which tend to run a little high compared to how many doors you'll actually knock on -- treat every figure on this page as an estimate, not an exact count.
By default a route can grow to two or three times the target when leftover streets are folded in. With this on, routes stay within about ±25% of the target (unless Min/Max are set under Advanced), and a single street too big for one route is split between routes. You'll get more routes, and a few isolated spots may still come out small.
βš™ Advanced options

3Review

4Live tracker connection

From the live leaflet-map site's own config (MAP_CONFIG.APPS_SCRIPT_URL in its index.html). In-app progress reports write straight to that ward's own Data sheet -- authorised editors write directly, everyone else's taps go to that site's normal pending-review queue. Leave blank to generate a read-only app with no reporting.

5Get your deliverables

A fresh route plan should be generated close to the actual event day so it reflects the latest leafleted roads -- publishing here auto-deletes any previously published page over 14 days old, and tells you what it removed.
How route access works: each route gets its own secret word baked into its QR code and printed link (e.g. #Arbor). Only someone who scans or opens that specific route's code can report progress on it -- everyone else can still browse the map, but reporting stays locked to a read-only view. This needs the printed sheets (or their links) to actually reach volunteers.
For a branch that can't get printed sheets or QR codes to people. With this on, whoever opens the app can pick and report on any route directly, no scanning needed.
βš™ I'll host it myself instead
Used for the QR codes on the route sheets and printed above -- re-download the sheets after filling this in if you already downloaded them.

πŸ“ Tap the map to set your start point

Grey lines are this ward's roads, for reference. Tap/click anywhere to drop the pin -- drag it afterwards to fine-tune.