Volunteer field guide. Use campaign-approved messaging. When in doubt, ask HQ before sharing process or legal details.
Field playbook · structure/03-county-team.md
County team — responsibilities & cadence
Purpose
Translate statewide standards into weekly county motion: local events, local digital rhythm, local relational depth.
County triad lanes
Events coordinator
- Build a county event lane that matches community patterns (weekday coffees vs weekend canvass-adjacent events, fairs, partner-hosted rooms).
- Maintain a 4-week rolling plan so volunteers can schedule around life.
- Recruit event hosts and site captains; never be the only person who knows the run-of-show.
Social coordinator
- Run county accounts or sub-pages where relevant; otherwise coordinate trusted volunteers’ personal posting cadence.
- Localize the social kit: names of places, local allies, local civic hooks — not generic national copy.
- Track two numbers weekly: reach (rough) and inbound asks (“how do I volunteer?”).
Power of 5 / relational coordinator
- Maintain a living list of relational nodes: clergy networks, union stewards, coaches, small business hubs, alumni circles.
- Set a weekly relational goal that is achievable with one hour lanes (see Relational playbook).
- Coach volunteers on scripts and boundaries; celebrate logged conversations, not just activity.
Weekly county checklist
- Pick one anchor event in the next 14 days with a named owner.
- Publish minimum social cadence agreed for the county (quality over spam).
- Confirm relational circles are mapped for each captain — no orphan leads.
Launch checklist (first 14 days)
- Name geographies (town clusters, precinct groupings) and assign parent captains.
- Host a county onboarding huddle using the weekly agenda template.
- Create a single source of truth for times/locations/links (one doc or one channel policy).
Common failure mode
County leads try to personally cover every town — fix by spinning city/precinct triads early.