Evaluation and Post-Event Reporting
Evaluate against stated objectives
Evaluation closes the loop opened in planning: each objective needs a measure, a data source, and a collection point. Use a levels model - reaction (satisfaction), learning (knowledge change), behaviour (application), and results (business or mission outcomes) - and be realistic about what a single event can evidence. Exam traps include reporting satisfaction as if it proved outcomes, and changing success measures after the event to match results.
Data collection and quality
Collect data during and immediately after the event while recall is fresh: post-session polls, registration and attendance data, session scanning, survey links with reminders, interviews with key stakeholders, and financial actuals. Response bias matters - satisfied attendees are more likely to respond, so report response rates and compare respondents with the overall population where possible. Privacy rules apply to all evaluation data.
Reporting and learning
A post-event report typically covers objectives and performance against them, attendance and audience profile, financial results against budget, sponsor and stakeholder fulfilment, incidents and risks realised, lessons learned, and recommendations. Separate findings from recommendations, and make recommendations owned and dated. Share with stakeholders promptly - sponsor reporting deadlines often fall within weeks of the event.
Worked example
Rule of thumb: for each objective, state the metric, target, actual, and interpretation. If the objective was that 80% of delegates report increased confidence, and the survey shows 76% among 210 respondents from 500 attendees, report the response rate alongside the result and avoid over-claiming.