---
name: event-debrief
description: Runs a structured post-event debrief or retrospective. Writes a short team questionnaire, then combines the answers, Slack threads, budget vs actual, lead and meeting counts and survey highlights into a keep, change, cut summary with owners and dates, plus a starter brief for the next edition. Use after a trade show, conference, field event, executive dinner or webinar series when the user wants a retro, lessons learned, a wrap-up doc or post-mortem.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: measurement
  source: https://eventmarketingsoftware.com/skills/event-debrief
---

# Event Debrief

Lessons get lost between shows. This skill runs a fast, consistent debrief: collect what the team saw, put it next to the numbers, and turn it into keep, change, cut decisions with owners and dates, then a starter brief for next time.

It has three modes. Pick from the request, or ask if unclear:

- **Questions:** write the team questionnaire (before or right after the event).
- **Wrap-up:** combine answers, Slack threads and numbers into the debrief doc.
- **Next edition:** turn a finished debrief into a starter brief with deadlines.

## Intake

If the user has an `event-context.md` file, read it first. If a strategy brief or ROI report exists for this event, ask for it: its goals and KPIs are what the debrief judges against.

Ask for whatever is missing in ONE message:

1. Event name, dates, motion (exhibit, sponsor, attend to meet, field event, own conference, webinar series) and the goal set before it.
2. Team input: answers to the questionnaire, a Slack channel export or thread, meeting notes, or a pasted list.
3. Numbers, if they exist: budget vs actual, badge scans, leads by tier A/B/C, meetings held, pipeline so far, survey NPS or top themes.
4. Date of the next edition (or the rebooking deadline), so action items can have real dates.
5. Who reads it (event team only, or leadership).

Missing numbers don't block the debrief. List them under "Data still to come".

## Connectors (all optional)

- If a Slack connector is available, read the event channel or thread the user names (read only). Ignore jokes and logistics chatter; keep observations, problems and wins.
- If a Google Sheets connector is available, read the budget and lead counts there, or write the action table to a new tab after a preview.
- Otherwise, work from pasted text or uploaded CSV/XLSX and return Markdown plus a CSV of actions.

## Mode 1: questionnaire

Write 6 to 8 questions that take under 5 minutes. Default set (adapt to the role and motion; more options in [references/questionnaire.md](references/questionnaire.md)):

1. Rate the event for our goals, 1 to 5.
2. What worked that we should keep?
3. What didn't work, and what did it cost us (time, money, leads)?
4. What one thing would you change next time?
5. Best conversation: which account, and why does it matter?
6. Was anything missing (people, tools, materials, training)?
7. Should we go back? Yes, yes with changes, or no, and why.

Send within 48 hours of the event, while memories are fresh. Offer a Slack message or email draft that introduces it; never send it without approval.

## Mode 2: wrap-up

```
- [ ] 1. Clean: dedupe answers, note who answered (roles, not names, for leadership)
- [ ] 2. Pull out every observation as one line with its source
- [ ] 3. Group observations into themes; count how many people raised each
- [ ] 4. Put the numbers next to the goal
- [ ] 5. Decide keep, change or cut for each theme
- [ ] 6. Assign owner and due date to every change
- [ ] 7. Validate
```

Rules:

- One observation can come from several people; count people, not lines. Duplicate submissions count once.
- A theme raised by one person is still listed if it cost money or leads (for example "lead app crashed, about 20 scans lost").
- **Keep:** worked and supports the goal. **Change:** right idea, wrong execution, cost or timing. **Cut:** cost more than it returned or didn't support the goal, raised by several people or backed by numbers.
- Every Change and Cut item needs an action, an owner role, and a date tied to the next edition's calendar (rebooking date, early-bird deadline, outreach start, and so on).
- Separate facts (numbers, things that happened) from opinions (ratings, suggestions). Quote no one by name in a leadership version.
- If numbers and opinions disagree (team says "day 3 was dead", scans show 40% of leads on day 3), show both and recommend checking.

## Mode 3: next-edition starter brief

From the debrief, draft:

```
# [Event] [next year]: starter brief
## Decision: go / go with changes / don't go (and why)
## Goal and KPIs (carry over or reset, with last year's actuals)
## Changes from last time (from the debrief)
## Budget starting point (last actual, adjusted for changes)
## Key dates and deadlines (working back from the event)
## Owners
## Open questions
```

For a full brief, hand off to the event-strategy-brief skill.

## Output template (wrap-up)

```
# [Event] Debrief

## Summary
3 to 5 bullets: did we hit the goal, top win, top problem, go-back recommendation.

## Goal vs actual
## What the team said (themes)
## Keep
## Change
## Cut
## Action items
## Data still to come
## Appendix: observations by source
```

Table columns:

- **Goal vs actual:** Metric | Goal | Actual | Status (hit, close, missed, pending) | Note
- **Themes:** Theme | Raised by (count of people) | Example observation | Linked number | Decision (Keep, Change, Cut)
- **Action items:** # | Action | Owner (role) | Due date | Linked theme | Status
- **Observations appendix:** Source (role or Slack) | Observation | Theme

A worked example from the sample file is in [references/examples.md](references/examples.md).

## Validation checklist

- [ ] Every respondent's answers are reflected in at least one theme or the appendix
- [ ] Duplicate submissions counted once
- [ ] Every Change and Cut item has an owner and a date
- [ ] Numbers in the summary match the goal vs actual table
- [ ] Opinions aren't presented as facts
- [ ] Leadership version has no names attached to criticism

## Approval gates

Never post to Slack, send email or write to a shared sheet without showing the exact content and getting a yes. Default to drafts. Don't assign tasks in a project tool on anyone's behalf without approval.

## Privacy

Team answers and Slack threads can include candid comments about colleagues and customers. Keep them in the user's tools, use roles instead of names in anything shared beyond the event team, and leave out personal details about attendees.

## Related skills

event-roi-report and post-event-survey-analysis (numbers and attendee feedback that feed the debrief), event-strategy-brief (next edition), trade-show-budget (budget vs actual).
