A post-event report template brings together the event's purpose, attendance, costs, feedback and actions. For a corporate audience, lead with what the event achieved and what remains unresolved, then provide the evidence. The copyable structure below helps an event lead give finance and leadership a useful record without confusing a busy room with a successful business outcome.
Use a preliminary report if invoices or follow-up results are still outstanding. Label it clearly and name the person responsible for completing it.
Copy this leadership summary
Event: [name, date and location]
Owner and report version: [name, date, preliminary or final]
Purpose: [the agreed business outcome]
Result: [what happened, supported by evidence]
Attendance: [invited, confirmed and checked-in counts]
Cost: [approved ceiling, current forecast or final total, unresolved invoices]
Main learning: [what to repeat or change]
Decision needed: [decision, owner and deadline]
Keep the summary readable without the supporting appendix. If a result cannot yet be measured, say when it will be checked rather than turning an expectation into a reported outcome.
Add the evidence underneath
| Section | Include | Check before sharing |
|---|---|---|
| Objectives | Original goal, success measure and result | Same definition used before and after the event |
| Attendance | Invitations, confirmations, check-ins and relevant session counts | Duplicate scans or multiple days handled consistently |
| Financials | Baseline, final cost or forecast, payments and open items | Deposits counted within commitments |
| Feedback | Questions, response count and themes | Respondents distinguished from all attendees |
| Suppliers | Delivery against agreed scope and unresolved issues | Evidence separated from personal impressions |
| Programme | Decisions made and sessions that changed | Actions have owners |
| Improvements | Proposed change, reason, owner and due date | More specific than “communicate better” |
Keep individual guest data and sensitive comments out of the general leadership report. Summarise the useful finding and restrict supporting records to the people who need them.
Use clear denominators
An attendance rate needs a definition. You might use checked-in attendees divided by confirmed attendees, or checked-in attendees divided by invitations. State which one you used.
In an illustrative example, 72 check-ins from 80 confirmations produces a 90% attendance rate against confirmations. If there were 100 invitations, the rate against invitations is 72%. Both calculations can be correct; they answer different questions.
For feedback, report the number of replies with the result. If 18 of 24 respondents found a workshop useful, write that. Do not describe it as 75% of the whole company unless the whole company was the respondent group.
Reconcile the money before calling it final
Compare the original event budget with the latest total, explaining changes in attendance, scope or supplier costs. Separate final invoices from estimates for anything still outstanding.
List unresolved deposits, refunds or charges with an owner. A report can close the programme while leaving a financial action open, but readers must be able to tell which parts are complete.
Turn the debrief into the next brief
Hold a short debrief with the people who delivered the event. Ask what should stay, what should change and which evidence supports each suggestion. Record the decision and owner so the discussion produces something the next organiser can use.
The next event brief should inherit those lessons, not just the previous date and guest count. Compare events only where the purpose and metric definitions are sufficiently similar.
Comtev keeps event costs, guest work and an activity trail in the workspace. Those records can inform a manually prepared report; this article does not claim an automatic reporting or ROI feature. Explore Budget and guest management for the underlying workflows.
FAQs
What should a post-event report include?
Include the purpose, results, attendance definitions, cost position, feedback, supplier delivery and follow-up actions. State whether the report is preliminary or final.
When should you write a post-event report?
Capture delivery notes and feedback while details are fresh. Publish an initial report when it is useful, then reconcile outstanding costs and longer-term outcomes on a stated follow-up date.
Can attendee satisfaction prove event ROI?
Satisfaction is one measure of attendee experience. It does not by itself establish a financial return. Use the event's agreed business outcome and evidence, and label outcomes that cannot reasonably be attributed to the event.