Volunteer field guide. Use campaign-approved messaging. When in doubt, ask HQ before sharing process or legal details.
Field playbook · structure/04-city-team.md
City / town team — responsibilities & cadence
Purpose
Operate the three-person model where most volunteers actually live — tight geography, high familiarity, fast iteration.
City / town triad
Events coordinator
- Run a monthly rhythm locals can memorize (e.g., “2nd Tuesday community coffee, 4th Saturday service project visibility”).
- Partner with credible local hosts (libraries, coffee shops, faith orgs, clubs).
- Always assign: setup, signup flow, program, follow-up.
Social coordinator
- Prioritize local faces and local stories over stock graphics.
- Build a bench of 5–10 posters with clear “when you post, tag X and DM Y”.
- Maintain a FAQ for recurring local questions so messaging stays consistent.
Power of 5 / relational coordinator
- Divide the town into natural micro-communities (school feeder zones, neighborhoods, workplaces).
- Run relational shifts: short windows where volunteers focus on follow-ups, not new novelty.
- Recruit block/zone leads before burnout hits the town coordinator.
Weekly city checklist (the “small but real” bar)
- One public-facing touch (event, table, partner room).
- Three pieces of social activity (posts, stories, responsible shares — adjust to platform realities).
- Five intentional relational touches across the team (not random scrolling).
When to go to precinct / neighborhood teams
Go deeper when:
- Response times suffer because the geography is too big for one triad.
- You have leaders who already live/work in distinct zones.
- You can give each child team non-overlapping turfs and clear dashboards.