The post-event report that gets next year approved

Your client did not spend the budget. Somebody above them approved it, and that person was not in the room. The post-event report is how they justify it, and it is the last thing your event will be judged on.

Most organisers send a photo gallery and a headline attendance figure. That is a souvenir, not a business case.

Send it within 48 hours

Not because it is hard to produce, but because of when it is read.

The internal conversation about whether the event was worth it happens in the days immediately after. A report that arrives two weeks later arrives after the decision. It gets filed, not used.

Forty-eight hours is achievable if the numbers already exist, which they do if every path through the door wrote to the same record. It is not achievable if half the check-ins happened in a notebook and someone is retyping them.

What actually goes in it

1. Registered, attended, and the gap

The three numbers, together, at the top. Not attendance alone.

The gap is the useful one. It sizes next year's invite list, it explains the catering spend, and it is the number the client cannot get anywhere else. An organiser who reports attendance only is hiding the most actionable figure in the document, usually because they do not have it.

If the gap looks bad, report it anyway with the context. Free corporate events lose a substantial share of registrations by nature — that is a property of free registration, not a failure of the event, and the no-show section of our 500-pax guide explains why. A client who understands the mechanism does not blame you for it. A client who is surprised by it in a spreadsheet six months later does.

2. The arrival curve

When people actually turned up, in fifteen-minute blocks.

This settles the annual argument about start times, and it is the evidence for how many check-in lanes to budget next time. It costs nothing to produce from scan timestamps and it is the single most reused chart in the whole document.

3. Session and workshop attendance

If the event had a programme, which parts of it people went to. Room by room, session by session.

This is what tells the client which speaker to invite back and which topic to drop. It also quietly justifies the platform, because it is not obtainable from a door count.

4. Walk-ins and late registrations

How many people arrived who were not on the original list, and how many registered in the final 48 hours.

A high walk-in count is not a problem to hide. It tells the client their invitation is being forwarded, which is usually good news, and it is the argument for keeping registration open later next time.

5. The attendee export

In the format their CRM takes, with a clear note about what may and may not be done with it. This is the deliverable their marketing team actually wants, and handing it over cleanly is worth more than three pages of commentary.

6. What went wrong, briefly

One short honest section. Not a confession, and not a list of excuses about the venue.

Two or three operational things that did not work and what you would change. Clients trust a supplier who names a problem before they do, and next year's brief gets easier because the conversation has already happened.

7. Photos, last

Everyone wants them and nobody makes a decision from them. Put them at the end, or link them separately so the numbers are not buried under a gallery.

What to leave out

• Social media impressions, unless the event was a marketing campaign and someone asked. It reads as padding on a corporate event.
• Satisfaction scores from a survey four people answered. A small-sample average looks like data and is not. Report the response count or do not report the score.
• Anything you cannot source. Every number in this document should be traceable to a system. The moment one is "about right", the whole report becomes about right.

The shape that works

Two pages, then appendices.

• Page one: registered, attended, the gap, the arrival curve. Four numbers and one chart. This page is the one that gets forwarded.
• Page two: session attendance, walk-ins, what went wrong, what we would change.
• Appendices: the attendee export, the full session breakdown, photos.

Write page one for someone who will read only page one, because that is who approves next year.

Why this is a platform question, not a design question

None of this is hard to produce. It is hard to produce accurately, and only if the data exists.

Registered versus attended requires that every arrival wrote to the same record, including the walk-ins and the people who lost their QR code. The arrival curve requires timestamps, which means scans rather than ticks on paper. Session attendance requires the programme and the attendee list to live in the same system.

Get the door right and the report writes itself in an afternoon. Get it wrong and you will spend two days reconstructing numbers you cannot fully stand behind, which is the worst possible use of the 48 hours that matter most.

The short version

Within 48 hours. Registered, attended and the gap at the top, not attendance alone. The arrival curve, because it is reused every year. Name two things that went wrong before the client does. Photos last. And write page one for the person who reads only page one.