Written . Original operational guidance, not legal advice.
Walk card record structure
A walk card is the smallest useful record of a door visit. Keep it to fields a volunteer can complete in under a minute, and make the owner of each field explicit. The structure below is a starting point, not a compliance document: required disclaimers and data-handling rules depend on your jurisdiction and should be confirmed separately.
- Household or address identifier (and its source)
- Date, shift and canvasser
- Outcome: not home, refused, conversation, follow-up requested
- Support level or issue noted, using your team's agreed scale
- Free-text note with a clear owner for follow-up
Call log record structure
A call log captures the same discipline for phone conversations: who called whom, when, what was asked and what happens next. Avoid recording sensitive personal details in free-text fields; agree as a team what belongs in a note and what does not.
- Person called and the list or source they came from
- Caller, date and attempt number
- Outcome: no answer, left message, conversation, do-not-call request
- Pledge, commitment or question raised, with its owner
- Next action and the date it is due
Use the templates to evaluate software
Bring these structures into any product evaluation. Ask the vendor to show where each field lives, which fields are required, how outcomes are counted in reports and whether the structures export intact. A tool that cannot represent your agreed fields forces your team to improvise, and improvised fields rarely survive a handoff.
The BlueRoots Doors and reporting previews use fictional records that follow this kind of structure. Use them to inspect how outcome, ownership and period labels appear on screen, then confirm the live capabilities, data sources and export behavior directly. These templates are operational aids, not legal guidance.