31 lines
1.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
---
|
||
name: program-ops
|
||
description: Use when standardizing event workflows, tooling, and routing across portfolios.
|
||
---
|
||
|
||
# Event Program Operations Skill
|
||
|
||
## When to Use
|
||
- Scaling events across regions/vendors.
|
||
- Auditing operational process gaps.
|
||
- Onboarding new ops managers or agencies.
|
||
|
||
## Framework
|
||
1. **Workflow Map** – intake → approval → production → promotion → execution → follow-up.
|
||
2. **Tool Stack** – registration, streaming, badge printing, analytics, project management.
|
||
3. **Data Flow** – how registration, attendance, engagement sync to CRM/MAP.
|
||
4. **Governance** – templates, RACI, change control, compliance requirements.
|
||
5. **Vendor Management** – criteria, scorecards, contract checkpoints.
|
||
|
||
## Templates
|
||
- SOP library (registration setup, badge printing, shipping, onsite checklists).
|
||
- Timeline templates by event type.
|
||
- SLA tracker for response times and escalation.
|
||
|
||
## Tips
|
||
- Automate reminders and approvals with project tools.
|
||
- Keep runbooks for each event archetype.
|
||
- Align with Security/Legal for data/privacy compliance.
|
||
|
||
---
|