What belongs in an event's final report

After running the Yonsei Medicine clinical practicum evaluation forum, zzzarit didn't just hand over event photos and a satisfaction score — we put together a final report the client could actually use to plan the next one. Having written final reports for a number of academic events by now, here are the six sections that are easiest to leave out.

Six sections a final report needs

1. 1Event overview — date, venue, audience, and purpose stated clearly in one paragraph
2. 2Program — a table of the run of show with speakers and presenters, so the next event has a reference point
3. 3Planning timeline — the steps from kickoff to event day, so the next organizer can follow the same path
4. 4Attendance — planned versus actual turnout broken out by group, to check how accurate the forecast was
5. 5Satisfaction survey results — scores by question alongside response count and method, so the numbers hold up as evidence
6. 6Recommendations — open-ended feedback turned into specific suggestions the next event can act on

Response rate matters more than question count

More questions can look more rigorous, but they also drive up survey fatigue and drag down the response rate. For the clinical practicum evaluation forum, we ran five questions on a five-point scale and got responses from 24 of 26 attendees (92%), landing on an overall average of 4.90. Collecting responses online (Google Forms) on the day of the event also helped keep the response rate high.

A final report isn't just paperwork to close out the event

Treat the final report as budget documentation and nothing else, and it won't feed into the next event. Include the planning timeline and recommendations, and the next organizer avoids repeating the same mistakes.