1---2name: event-briefs3description: Use when documenting event objectives, requirements, and alignment across stakeholders.4---5
6# Event Brief Systems Skill
7
8## When to Use
9- Kicking off any event (webinar, field, flagship).
10- Aligning cross-functional partners before production starts.
11- Handing event concepts to producers or regional teams.
12
13## Framework
141. **Overview** – goal, target audience, date, format, tier.
152. **Narrative** – theme, key messages, CTA, proof assets.
163. **Experience** – agenda, speakers, demos, activations.
174. **Promotion** – channels, audience segments, partner amplification.
185. **Operations** – budgets, vendors, timelines, risks, approvals.
196. **Measurement** – KPIs, dashboards, survey plan, follow-up flows.
20
21## Templates
22- Master event brief doc (editable copy with the sections above preformatted).
23- Reviewer checklist (approvals, dependencies, instrumentation, follow-up).
24- Handoff packet outline for producers/regional teams.
25
26## Checklist
27- ✅ Approvers + owners defined.
28- ✅ Dependencies captured (product readiness, content, sales enablement).
29- ✅ Data instrumentation planned.
30- ✅ Post-event follow-up mapped.
31
32## Tips
33- Keep briefs in shared workspace; version by event iteration.
34- Reuse sections for series; highlight delta vs prior runs.
35- Pair with `manage-production` outputs to ensure continuity.
36
37---
majiayu000