How it works
Volunteer scheduling software that runs a field program, start to finish
Six steps take a campaign from a messy spreadsheet to a fully scheduled field program with a daily coverage report. The first campaign we loaded went from three workbooks to 700+ scheduled shifts, end to end.
Setup takes ten minutes
The onboarding wizard walks through election dates, wards, locations, and shift templates, then generates the full shift grid. A DC campaign starts from the built-in vote-center pack: 74 election-day centers and 25 early-voting sites, ready to schedule. Other jurisdictions enter their locations once and reuse them every cycle.
Import survives real spreadsheets
Upload xlsx or csv from your own tracking sheet, the party's export, or the QR signup pool. The importer auto-maps columns, splits full names, normalizes phones and emails, and reconciles ward drift like Ward 4, 4.0, and 4 into one value. Deduplication runs exact match first, then phone, then fuzzy.
It was built against real DC council campaign workbooks, so it handles sci-notation phone numbers, multi-value cells, free-text shift entries, and the all-caps banner rows that break every other import.
Schedule on a live grid
The grid shows every center grouped by ward, every shift, and every assignment. It syncs live over WebSocket, so three organizers scheduling at once see each other's changes as they happen, with no refresh and no version conflicts.
Conflicts surface the moment they happen
Overlapping shifts, travel-time conflicts between centers, assignments against stated unavailability, and duplicate bookings all flag in place. The system warns and never blocks, because election day sometimes requires judgment calls, and every override is logged with who made it.
Gaps fill from ranked candidates
The gap panel lists every uncovered shift and ranks fill candidates by who lives in the ward, who has covered this center before, reliability history, and stated availability. One click assigns. A toggle widens the search to adjacent wards when the home ward runs dry.
The report lands at 7am
Every morning the executive coverage report emails the field director: coverage by ward, open gaps, no-shows from yesterday, and the day ahead. It also exports as PDF and CSV whenever anyone needs it. See the 7am report.
Under the workflow, a volunteer CRM built for campaigns
Cross-campaign history
Volunteers carry their shift history and reliability counts across campaigns, so 2026's flakes and stars are both known in 2028.
Interaction logging
Calls, texts, emails, and in-person contacts log with attribution, and the follow-ups-due queue keeps recruitment moving.
The AI assistant
Ask anything about your field program. It answers from live data with citations, and it drafts recruitment texts.
See the whole workflow on real data
The live demo runs the full DC seed: 268 volunteers, 74 centers, 700+ shifts.
Open the live demo