Volunteer field guide. Use campaign-approved messaging. When in doubt, ask HQ before sharing process or legal details.
Field playbook · structure/01-fractal-overview.md
Fractal model — how the layers fit
The idea in one sentence
Same three roles, smaller geography, more frequent touchpoints.
Stack (typical cascade)
State team
→ County team(s)
→ City / town team(s)
→ Precinct team(s)
→ Neighborhood / block team(s)
Each layer is still only three coordinators: Events, Social, Power of 5 / relational.
Why fractals work in the field
- Clarity — volunteers are never guessing what their job is; the role survives the zoom-in.
- Accountability — each layer has a triad that can report numbers without a heavy bureaucracy.
- Speed — local teams decide local timing; state supplies templates, training, and escalation paths.
Decision rule: when to spin out a new triad
Spin out when two of these are true:
- You have three people willing to own distinct lanes for ~90 days.
- You can name a geography the new team exclusively serves (no overlap fights).
- The parent team cannot cover the needed contact frequency (events, posts, relational touches).
Anti-patterns (avoid)
- Mixing “everyone does everything” — lanes blur and throughput dies.
- Naming a team without a recurring huddle — you created a group chat, not a field unit.
- Skipping documentation of who owns which geography — duplicates or gaps appear instantly.
Next pages
Open your layer and run the checklist for that geography size: State → County → City → Precinct → Neighborhood.