Run Event
12 weeks · 4 milestones
Milestone map
Milestone map
3 milestones
A community event is a coordination test before it is a production challenge. The plan must specify the event's purpose, date, venue, intended audience, and volunteer roles — and each volunteer role must have a named person who confirmed it before the plan is considered complete. The GOVERNANCE constraint applies from the start: every person involved is choosing to help; the plan must be realistic about what can be coordinated without authority to compel attendance or fill gaps.
Proof required
Submit: (1) an event plan document (one page minimum) covering the event purpose, date, venue or platform, expected attendance range, and the list of volunteer roles; (2) a confirmed volunteer roster showing at least 3 volunteers with their assigned roles and evidence of their confirmation (reply, planning meeting attendance, or sign-up record); (3) a brief written assessment (100 words) of what would happen to the event if one of your key volunteers dropped out the day before.
What gets checked
- Event plan specifies a real venue or platform, a real date, and a clear purpose — 'a community event to bring people together' is not a sufficient purpose; what specifically will attendees do or learn at this event?
- At least 3 confirmed volunteers with specific named roles — confirmed means they responded to an ask with a yes, attended a planning meeting, or added their name to a roles document; verbal agreement with no follow-up is not confirmed
- The contingency assessment is honest about single points of failure — if the event cannot run without one specific person, the plan has a dependency that must be acknowledged and partially mitigated before M2