The event debrief template: turning complaints into next-event fixes
Feedback doesn't die from being ignored — it dies from being archived. A 400-row spreadsheet gets opened once. One page, three fixes, twenty minutes: the debrief that survives Monday.
APR 16, 2026 · 4 MIN READ · BY THE GUESTSIGHT TEAM
The one-page rule
A debrief has one job: convert last event's feedback into changes at the next one. Anything that doesn't survive until the next event — a tab of raw comments, a 40-slide recap, fourteen action items — has failed at that job, however thorough it felt to produce.
So the constraint comes first: one page. If it doesn't fit, you haven't finished deciding what matters.
EVENT DEBRIEF
FRIDAY CLUB NIGHT · JUN 19
1 · THE NUMBERS
214 responses
4.2 avg rating
21:20–21:50 worst window (BAR)
2 · WHAT CLUSTERED
Bar waits 20+ min — 31 mentions · BAR · 21:00–22:00
Restrooms out of paper — 9 mentions · RESTROOMS · after 23:00
Too hot near stage — 7 mentions · DANCEFLOOR · 22:00–23:00
3 · DON'T TOUCH
The DJ's second set — 48 positive mentions
Terrace heaters — “best decision of the winter”
Door staff — friendliness named 12×
4 · THREE FIXES — OWNER · DEADLINE · PROOF
Second bar station from 21:00 — Lena · next Friday · bar mentions <10
Restroom check every 45 min after 22:00 — Aisha · next Friday · zero paper mentions
Fans on stage rig before doors — Jon · next Friday · heat mentions <5
5 · ONE EXPERIMENT
Open the terrace bar for the first two hours — does it pull queue pressure off the main bar?
The 20-minute agenda
Run it within 72 hours, while the night is still arguable. Longer than 20 minutes means you're re-litigating the event instead of deciding three things.
0–4 Last debrief's fixes — did they work?
4–7 The numbers
7–15 Clusters & don't-touch list
15–20 Pick three fixes, assign owners
The rules that keep it alive
- Three fixes, never more. A debrief that outputs fourteen actions outputs none. If a fourth is truly urgent, it bumps one of the three.
- Every fix has an owner, a deadline, and a proof. “Improve bar speed” is a wish. “Second station from 21:00 — Lena — bar mentions under 10” is a fix. The proof is measured in next event's feedback.
- Clusters only. One guest hating the playlist is taste; thirty mentions of bar waits is data. Single complaints go to a parking lot, not the page. (Zone-tagged live feedback makes clustering automatic — that's the during-the-event playbook.)
- The don't-touch list is mandatory. Debriefs skew negative; without it, next month's “improvements” will sand off the thing guests actually came for.
Copy the template
Plain text, ready for your notes app or print-out:
EVENT DEBRIEF — [event] · [date] 1 · NUMBERS [responses] · [avg rating] · [worst window + zone] 2 · CLUSTERED [theme — count · zone · window] ×3 3 · DON'T TOUCH [what guests loved] ×3 4 · THREE FIXES [fix — owner · deadline · proof in next event's data] ×3 5 · EXPERIMENT [one thing we'll try next event]