Promise
Who is this event for, and what ability, relationship, work, or next step will exist when they leave?
COMMUNITY EVENT PLAYBOOK · v1.2
A tool-agnostic operating model. Use the same promise, ownership, experience, and learning across workshops, meetups, mixers, hacknights, and large events.
PART I
This edition does not invent the author’s values, principles, or voice. The framework can operate first; the stance must be filled by lived experience.
THE OPERATING MODEL
Four core objects keep the event whole. Six states move it forward. Tools only carry the work.
Who is this event for, and what ability, relationship, work, or next step will exist when they leave?
Who owns the result? Which decisions can be made on site, and which must be escalated?
How does a participant understand, prepare, arrive, participate, and continue afterward?
How are participation facts separated, outcomes interpreted, and useful learning left for the next event?
Name who the event serves and what it resolves
Event BriefCommit resources, owners, and partnership boundaries
Ownership MapValidate content, recruitment, venue, tech, and fallback
Experience FlowOperate from shared state and handle exceptions
Run of ShowGive people, assets, payments, and promises a destination
Outcome RecordTurn outcomes into changes for the next event
PostmortemKeep one master version of event state; every other page links back.
Many may collaborate, but final decision and closure cannot be shared.
A date says when; a state says whether conditions are met. Due is not done.
Keep six core artifacts; load format, venue, and brand details as needed.
Record what was decided and why before expanding execution tasks.
Delay, overrun, technical failure, incidents, and data gaps cannot live only in chat.
The run of show, contacts, and roster remain available when tools or network fail.
| Category | Minimum fields |
|---|---|
| Identity | Event name, format, date, place / platform, canonical URL |
| Promise | Audience, leaving outcome, non-goals, primary KPI |
| Ownership | Decision owner, workstream owners, on-site escalation |
| Status | Lifecycle state, next gate, blocker, last update |
| Experience | Participant journey, run of show, access / consent, fallback |
| Learning | Cohort definition, source, outcome, incident, decision, next change |
| Concept | Linear | Notion | Sheet / docs |
|---|---|---|---|
| Event | Project | Event page / database item | Index row + event folder |
| Core objects | Project overview / documents | Page sections / linked databases | Event Brief tabs / docs |
| Lifecycle | Project status / milestone | Status property | Status column |
| Owner | Lead / assignee | Person property | Owner column |
| Gate | Milestone / issue group | Gate checklist | Gate review row |
| Exceptions & learning | Issue / project update | Decision log / postmortem | Issue log / retrospective tab |
This table explains correspondence only. It does not prescribe a tool or interface configuration.
FORMAT MODULES
Complete a verifiable action or artifact on site
Exchange applicable cases, perspectives, and peer connections
Create relevant new connections and follow-up conversations
Produce demonstrable progress, learning, or a failure path
Let tracks deliver independently within one coherent experience
ARTIFACT LIBRARY
Twenty templates grouped by function. Open one to see the decision it carries—not a prescription for tool fields.
Required for every event
05Audience, promise, outcome, constraints, and next gate
Event name: Date / place / format: Decision owner: Who this is for: Need / opportunity observed: Participant leaving outcome: Why an event is the right intervention: Out of scope: Primary outcome KPI: Eligible cohort: Observation window: Evidence source: Critical constraints: Cancel / reduce conditions: Next gate and date:
Decision rights, collaboration, escalation, and backup
Workstream | Final owner | Collaborators | May decide | Must escalate | Backup Overall outcome / scope | | | | | Content / speakers | | | | | Production / on-site | | | | | Technical | | | | | Safety / access / consent | | | | | Budget / partnerships | | | | | Evidence / follow-up | | | | |
The participant path from Discover to Continue
Stage | Participant action | Touchpoint / message | Friction | Owner | Evidence Discover | | | | | Decide / Register | | | | | Prepare | | | | | Arrive / Join | | | | | Participate | | | | | Close | | | | | Continue | | | | |
Timing, outcome, owner, success condition, and fallback
Time | Segment | Participant outcome | Owner | Cue / asset | Success condition | Fallback | | | | | |
Attendance, engagement, outputs, incidents, and open promises
Registered / Approved: Checked in: Completed / meaningfully engaged: Outputs / demos / stories: Incidents / exceptions: Outstanding commitments: Primary KPI status: Known data gaps: Immediate follow-up queues: Decisions to keep / change / stop:
Public information and on-site language
05Audience, outcomes, flow, rules, and one CTA
One-sentence promise Who it is / is not for What participants will do and take away Date, timezone, place / platform, language, fee Prerequisites and what to prepare Flow summary Hosts / speakers and their roles Capacity, waitlist, cancellation, and walk-in rules Access, media, Code of Conduct, contact One registration CTA
Reason, format, fee, rights, and timing
Subject: [Event] invitation to share [topic / case] Hi [name], We are planning [event] for [audience], with the goal that participants leave able to [outcome]. We would like to invite you because [why this person / experience], in a [length + talk / conversation / workshop + Q&A] format. Date / timezone: Place / format: Audience and expected size: Please cover: Please avoid: Fee / travel / recording and asset use: Dry run / submission date: If interested, reply by [date]. We can shape the topic and format together.
Context, attempt, decision, result, limits, and next step
What the audience knows / does not know What they should be able to do afterward Suggested arc: context → attempt → decision → result → limitation / failure → next action Must explain: case context, assumptions, limits, and sources Avoid: long company intros, unexplained terms, feature tours with no takeaway Timing: total / content / Q&A / removable section Format and equipment: ratio, type, video, demo, backup Rights: recording, public slides, adaptation
Arrival, preparation, access, cancellation, and next step
You are confirmed for [event] Time / timezone / address or join link: Check-in and late-arrival rules: Complete / bring in advance: What happens on site: Access, food, media, and contact: Cancellation / waitlist: The one next step after the event:
Opening, transition, overtime, and closing
Opening: who this is for / today’s promise / how to participate / safety and help / next segment Transition: what was completed / what is next / what to prepare Overtime: which outcome to protect / what to cut / when to stop Closing: what was completed / where materials live / one next step / thanks
Turn attendance into participation
04Instructions, grouping, observation, intervention, and output
Segment | Instruction | Time | Grouping | Facilitator observes | Intervention | Output | | | | | |
Completion, blockers, resources, and unfinished paths
Checkpoint | Visible completion | Common blocker | Self-serve resource | Help path | Unfinished path | | | | |
Building, blocked by, can offer, and want to meet
I am building: I am blocked by: I can help others with: I want to meet / ask: I consent to a follow-up introduction: yes / no
Goal, progress, demo, blocker, and review rubric
Team / members: Original intent: What was actually completed: Demo / repo / work link: Biggest blocker and response: Next step: Review rubric: problem and audience / implementation or validation / learning and honesty / communication Judge conflicts and overtime rules:
Infrastructure for participation
03Available support, limits, contact, and alternatives
Venue / platform currently provides: We cannot currently guarantee: Language, captions / transcript, route, seating, toilets, quiet space: Food and allergy information: Request deadline and contact: Response and alternative if a need cannot be met:
Purpose, choices, no-camera signal, and withdrawal
This event may be photographed / recorded for: [purpose and channels] Participants may choose: [consent / no camera / confirm individually] On-site identifier: Contact and deadline for questions or withdrawal: Work, slides, demos, and quotes require separate permission: yes / no
Necessary facts, response, protection, escalation, and change
Time / place: Reporter and receiving owner: What happened (necessary facts only): Immediate response: Protected personal data / access limits: External support or escalation: Follow-up promise and deadline: Process-level change:
Give one event a next step
03Intent, value, completion, blocker, and consent
What did you hope to get from this event? Which part helped most, and why? What did you complete / what will you do next? Where are you still blocked? Did you feel able to participate, ask, and get help? What should we keep, change, or stop next time? Do you consent to follow-up / interview / public quote? (choose separately)
Facts, impact, causes, changes, and owners
Event promise and primary KPI: Expected vs actual: What happened (facts and timeline): What worked / did not work: Impact on participants and team: Root causes / enabling conditions: Keep / change / stop: Action, owner, deadline: Template / module / rule to update:
Consent, attendance, 30d activation, 90d repeat/contribution
Participant ID | Consent | Checked in | In-event action | 30d activation | 90d repeat | 90d contribution | Source | Follow-up owner | | | | | | | |
MEASUREMENT & LEARNING
Separate registration, attendance, engagement, completion, and follow-through. Then choose one primary outcome.
| Field | Meaning | Rule |
|---|---|---|
| Registered / Going | Registration or RSVP | Never add to attendance |
| Approved | Reviewed or confirmed roster | Mark waitlist and cancellation in the denominator |
| Checked in / Attended | Actual check-in / attendance | Preferred denominator for on-site participation |
| Meaningfully engaged | Completed a predefined interaction | Define before the event |
| Completed | Completed a task or checkpoint | An outcome, not an additional person |
| Outputs / Demos / Stories | Number of works, demos, or stories | Do not combine with people |
Among checked-in attendees who had not taken the action before, the share completing a meaningful action within 30 days.
Among traceable, opted-in attendees, the share joining a qualifying activity again within 90 days.
Among eligible attendees, the share completing a verified contribution within 90 days.
Define meaningful action, eligible cohort, qualifying activity, and contribution before the event; do not change definitions after seeing results.
Report numerator and denominator together, for example 18/51 = 35.3%. NPS, satisfaction, registrations, and reach are diagnostics—not community outcomes by default.
Attendance rate = checked-in ÷ approved registrations Engagement rate = meaningful engagement ÷ checked-in Activation rate = new activations ÷ pre-event unactivated checked-in cohort Repeat rate = qualifying repeat participants ÷ follow-up eligible cohort Contribution rate = verified contributors ÷ eligible cohort Cost per activated attendee = fully loaded event cost ÷ new activated attendees
The event is the first identifiable acquisition touch.
The event appears before the outcome; it is not claimed as the sole cause.
Claim lift only with a credible comparison design.
Incremental lift = outcome rate(invited cohort) − outcome rate(random holdout)
Event ROI = (incremental attributable gross profit − fully loaded event cost)
÷ fully loaded event costWhen the sample is small, comparison is absent, or data is incomplete, report influenced outcomes and cost—do not present correlation as causal revenue.
FOLLOW-UP RHYTHM
T+0–2T+7T+14–21T+30T+60T+90Segment attendees, no-shows, speakers, volunteers; send assets, feedback, one CTA
Route by completion state and blocker
Office hour, unfinished clinic, mentor follow-up
Freeze activation cohort; interview both successful and unsuccessful cases
Run a second ritual; invite activated members to a light contribution
Freeze repeat / contribution; update cost and attribution
Complete a postmortem after each Close. Run a cross-event Learning Jam after 3–5 events of the same format.
Compare cohorts only when definitions, format, and acquisition channels are comparable. Write repeated, generalizable practices back into the core or format module; keep city, brand, account, and short-term policy details in event records.
Prefer the median and quartiles from your own 3–5 events. External benchmarks are provisional planning ranges, not universal targets.
APPENDICES
These are execution aids, not the core workflow. Load only the modules relevant to the event’s risks.
Order of use: take the method first, then use the license to decide whether text or files may be copied.
| Source | Reusable layer | Boundary |
|---|---|---|
| Cursor Ambassador workspace | Formats, brand assets, slides, attendance copy, ambassador tools | Mostly workspace / brand restricted; not a general public license |
| 本地 Zeabur Event Guide | On-site execution, technical preflight, media, event records | Use as a practice case; keep brand, accounts, and policies out of the core |
| CNCF Kubernetes Community Days | Complete community-event asset structure | Apache-2.0; verify attribution in the source |
| Write the Docs | Speaker, volunteer, and role design | CC BY-NC-SA 4.0; reassess for commercial publication |
| MLH Organizer Guide | Hackathon flow and judging | CC BY 4.0 |
| OpenHatch Handbook | Technical preflight and contribution continuation | CC BY 3.0 US |
| Community-Led Co-design Kit | Facilitation, access, consent, outcome | CC BY 4.0 |
| Drupal / W3C WAI | Event accessibility | Follow each source document’s license |
This is an organization-neutral Community Event Playbook—not a brand ambassador program, brand asset library, reimbursement policy, or account manual. Brand-specific forms, budgets, benefits, accounts, and governance stay with their sources. Before publicly adapting an original template, return to the asset index and verify license and attribution.