Field playbook

Events coordinator — lane guide

Mission

Create high-trust gatherings that move people from curiosity → participation → leadership.

Weekly responsibilities (minimum viable)

1. Plan the next public or partner-hosted touch with a named owner for each function.
2. Recruit attendees through relational lists and social promotion working with the other two coordinators.
3. Document what happened: attendance estimate, signups, follow-ups owed.

Event quality checklist (fast)

• Purpose in one sentence (“recruit precinct captains”, “train Power of 5”, etc.).
• Agenda with times and who leads each block.
• Signup path tested on a phone (short URL or QR).
• Accessibility basics: seating, hearing, scent/smoke considerations when applicable.
• Safety plan for public spaces — two-person rule when appropriate.

Monthly responsibilities

• Train one new event host intentionally.
• Retire formats that don’t recruit; double down on what does.

Metrics you own (with ops support)

• Events executed vs planned.
• Volunteer signups attributed to events.
• Follow-up completion rate within 72 hours.
• County fundraising rows moving: host → date → goal → raised → follow-up (see Fundraising Event Toolkit).
• Faith-visit and County Clerk pipelines honest (no “claimed complete” without thank-you sent).

Hand-offs

Anything touching permits, venue contracts, or legal questions goes up to campaign coordinator / HQ per protocol.

Deep dive

Open the Events · hosting playbook when you are inside seven days of a touch.

Operating manual (web hub): /volunteer/resources/events-lane — table of contents for house parties, county fundraisers through September, weekend immersions, two-day city visits, faith communities, travel rhythm, and automation intents for the Action Queue.

Train others: start a new host on House party playbook, then have them shadow County Clerk and Faith visit checklists before they fly solo.