Skip to main content

Volunteers

Field playbook

How county, city, precinct, and neighborhood teams fit together — same three roles at every layer. Start at Join the Field Team if you are new.

Skip to chapter content

Back to volunteer onboarding

Volunteer field guide. Use campaign-approved messaging. When in doubt, ask HQ before sharing process or legal details.

Field playbook · roles/01d-fundraising-receptions-county.md

Fundraising receptions and county fundraising objectives

Strategic objective: each county should host at least one fundraising event between now and September where feasible — more is welcome when hosts and compliance capacity exist.

This doc covers receptions (venue-based or larger homes), ticketed or minimum-suggested formats, and county tracking before a dedicated fundraising dashboard exists.

County fundraising tracker (copy to your sheet)

CountyHost(s) identifiedDateVenueFundraising goal ($)Guest targetInvites sentRSVPAmount raisedTreasurer reconciledFollow-up complete

Encourage multiple events where hosts and volunteer labor allow — stagger dates so the same circle isn't exhausted.

Roles

  • Events — venue, run-of-show, volunteer assignments, RSVP logistics.
  • Treasurer / compliance — disclaimers, receipts, FEC or state rules — no improvisation.
  • Social — save-the-date, proof-of-event graphics, dignified recap.
  • P5 / VR — relational fill for the room; registration table optional at entry.

T-6 weeks — feasibility

  • Confirm legal path for the ask (in-kind, ticket, contribution link — per counsel).
  • Name honorary host or committee if that unlocks the room.
  • Set minimum viable guest count below which you cancel or merge.

T-3 weeks — fill the room

  • Host committee each names 10–15 personal invites.
  • Brief surrogates on one consistent message; avoid rival “asks.”
  • Confirm program length ≤ 45 minutes of formal program; mixing matters.

T-1 week — operations

  • Checklist: signage, registration, photographer brief, press only if comms approves.
  • Volunteer roles: greeters, name tags, floaters for shy guests.
  • Run tech test for microphone and seating sightlines.

Run-of-show (reception example)

  • Greeter + name tag table live 30 minutes before “program.”
  • 10 minutes — welcome and gratitude to hosts.
  • 15 minutes — Kelly or surrogate: values + concrete Arkansas stake (factual).
  • 10 minutes — compliant fundraising explanation (treasury-approved).
  • Remainder — mixing; surrogates circulate with signup / give options.

What good looks like

  • Host prospects move from “maybe” to named dates within two touch cycles.
  • RSVP ratio healthy enough to hit minimum; honest cancel if not.
  • Follow-up within one week for every pledge or “considering.”

Automation note

When creating the event in Admin → Events, use type FUNDRAISER and set campaignIntent to vos_county_fundraiser so the Action Queue can stack donor outreach tasks on top of generic appearance prep. See events-workflow-intents.ts.

Volunteer web hub: /volunteer/resources/events-lane → Fundraising Event Toolkit card.

On this page