The event is over, the team is tired, and the temptation is to move straight on to the next one. Write the report first. A post-event report is the one document that turns a finished event into something you can learn from, show sponsors, and use to plan better - and it takes far less time than most organizers think.
What is a post-event report?
A post-event report is a short document that records what happened at your event: who came, what it earned, what it cost, what worked and what to change. Some teams call it an event recap, a debrief or an after-action report - same thing.
It has three audiences:
- Your team, who need honest lessons before the next event
- Sponsors and partners, who need proof their money worked
- Future you, who will plan the next edition from this document
If sponsors are the main audience, build the post-event sponsor report instead - it is a different document with a different job.
What should be included in a post-event report?
Nine sections cover almost every event:
- Executive summary - three to five sentences: what the event was, the headline numbers, the verdict
- Attendance - tickets sold, tickets scanned at the gate, no-shows
- Sales and revenue - by ticket tier, by day, against target
- Marketing performance - what each channel brought in
- Audience - who actually came, as far as your data shows
- What worked - the decisions worth repeating
- What did not - named plainly, with the cause if you know it
- Budget versus actual - planned spend next to real spend
- Recommendations - specific changes for the next edition
Cut any section you have no data for. An honest seven-section report beats a padded nine-section one.
Pick a format people will actually read
The format matters less than the discipline. Three options work:
- One-pager - the summary, the key numbers, the verdict. Right for small events and busy stakeholders.
- Document - three to six pages with charts. Right for flagship events and formal partners.
- Slides - when the report will be presented in a meeting rather than read.
Whichever you choose, put the executive summary first. Most readers stop there, and that is fine - the report did its job.
Where the numbers come from
A report is only as good as its records. Guesswork shows.
- Take attendance from gate scan data, not from tickets sold. The two numbers are never the same, and the gap between them is itself a finding.
- Take sales and revenue from your ticketing dashboard, broken down by tier and by day, so you can see when demand moved.
- Keep bought, refunded, scanned and no-show as separate numbers. Blending them makes every other figure less believable.
If your event ran on an event ticketing and voting platform with live sales tracking and QR check-in, this whole section is an export rather than a reconstruction. For deeper reading of the numbers, see our event data and analytics guide.
The post-event marketing report
If marketing was a big part of your budget, give it its own section - or its own short report. Cover:
- What each channel cost and what it brought in, as far as links and promo codes can show
- Which posts or messages moved ticket sales, read against your daily sales data
- What the WhatsApp groups, flyers and radio spots did that the dashboard cannot see - say so honestly when a channel cannot be measured
The goal is not a perfect attribution model. It is knowing which two or three channels deserve more money next time.
A template you can copy
POST-EVENT REPORT: [Event name] - [Date] - [Venue]
1. Summary
What happened, headline numbers, one-line verdict.
2. Attendance
Sold: ___ Scanned: ___ No-shows: ___
3. Sales & revenue
By tier: ___ By day: ___ Vs target: ___
4. Marketing
Top channels: ___ What moved sales: ___
5. What worked
- ...
6. What didn't
- ...
7. Budget vs actual
Planned: ___ Spent: ___ Variance: ___
8. Recommendations
- ...
Fill it the week after the event, while the memory is fresh. Pair it with the event financial report guide if the money needs a report of its own.
Write it while it still hurts
The best post-event reports are written within two weeks, while the queue that formed at 7pm and the tier that sold out too early are still vivid. Pull the numbers the day after. Write the narrative within the week. Send it to everyone who should see it - then start planning the next one from page one of this report.
FAQ
What do you call a report after an event?
It is usually called a post-event report. Some teams call it an event recap, event debrief or after-action report - they all cover the same ground: what happened, the numbers, and what to change next time.
What should be included in a post-event report?
An executive summary, attendance figures, ticket sales and revenue, marketing performance, audience feedback, what worked and what did not, budget versus actual spend, and recommendations for the next event.
How soon after the event should the report be written?
Within one to two weeks, while the data is fresh and the team still remembers the details. Pull the numbers the day after; write the narrative within the week.
How long should a post-event report be?
As short as it can be while answering the questions your stakeholders will ask. A one-page summary plus a few pages of numbers beats a 30-page document nobody reads.
