Event Recap Example: A One-Page Recap and an Email Template to Copy
An event recap example worth copying fits on one screen: the event and its date, how many people registered and how many came, the result against the goal, what did not go to plan, and what happens next with a date. You send it within three business days, while your client or your own leadership is still being asked how it went.
This page gives you a rule for which numbers go in and which wait, a template table, an event recap email template for a client and one for attendees, and a worked example with hypothetical figures. Copy the text from the page and replace the brackets.
What is an event recap, and how does it differ from a post-event report?
An event recap is a short written summary sent a few days after the event to people outside the planning team: a client, your leadership, attendees, sponsors. It reports the counts that are already final, labels the ones that are not, and says when the full account will follow.
A post-event report is that full account. It covers cost, revenue, marketing, and sponsor results with a source behind every figure, and it takes weeks because invoices and deals take weeks. The post-event report template has the fields. A debrief is a third thing: the internal meeting where the team reviews its own decisions.
| Question | Event recap | Post-event report |
|---|---|---|
| When is it sent? | Within 3 business days | When cost and revenue lines are final, usually weeks later |
| Which numbers? | Registrations, attendance, and two or three results against goals | The same, plus cost, revenue, marketing, and sponsor results |
| How firm are they? | Final or labeled provisional | Final, each with a source |
| What does it end with? | Next steps and the date of the report | A decision about the next event |
If you run events for clients, the recap is the first written thing they receive afterward, and it is usually forwarded to someone who was not there. Write it for that second reader. Who gets the longer documents, and when, is an event reporting decision to make before the event.
Which numbers belong in a recap, and which wait for the report?
A number goes in the recap if it passes three tests.
- It comes from a system export, and you can state when the export was taken. A headcount from memory fails.
- It will not change before the report is written. If it might, it carries the word provisional and the date it becomes final.
- It answers a target set before the event, or a question the reader has already asked.
Registrations and check-ins usually pass all three within a day. Cost fails the second test until the last invoice arrives, and pipeline and revenue fail it for longer. Name those lines in the recap as pending, each with a date.
No-shows = Valid registrations − Checked-in attendees
Variance against target = (Actual − Target) ÷ Target × 100
Survey response rate = Completed surveys ÷ Attendees surveyed × 100
Valid registrations exclude test records, duplicates, and cancellations. Say which definition of an attendee you used, because a check-in and a session scan count different people. The attendance rate page covers the definitions. Compare a rate with its target in percentage points.
Survey figures need one more step. In MPI's Meetings Outlook for Q2 2026, built on 163 responses from MPI members, 47% named low attendee response rates to surveys or feedback requests among the biggest challenges in measuring the human impact of events (MPI). Three days after the event your survey is still open, so a satisfaction figure in the recap goes beside the response count and the closing date. The post-event survey questions page has wording for the survey itself.
What does the event recap template look like?
Nine blocks, in this order. The same blocks work as an email or as a one-page document.
| Block | What to write | Where it comes from |
|---|---|---|
| 1. Subject line | Event name, date, and the word recap | Event plan |
| 2. Headline | One sentence: the main result against the goal set before the event | Event plan and the counts below |
| 3. Attendance | Valid registrations, checked-in attendees, and the attendance rate, each beside its target | Registration and check-in exports |
| 4. Results against goals | Two or three figures the reader asked for, such as meetings held or sessions attended. Mark each final or provisional | The system that recorded each one |
| 5. What did not go to plan | One or two items, stated plainly, with the cause if you know it | Team notes from the day |
| 6. Feedback so far | Responses received, response rate, one figure, and the date the survey closes | Survey tool |
| 7. Still to come | Final cost, pipeline, revenue, and the date each will be reported | Finance and CRM |
| 8. Next steps | Each action with an owner and a date, including the date of the full report | Project plan |
| 9. Data note | The date and time of the exports, and the definition of an attendee | Your own record of the export |
Teams tend to cut block 5. A client who watched a session start late and then reads a recap with no mention of it will discount the attendance figures too.
What does an event recap email say?
Version for a client or for leadership.
Subject: [Event name], [date]: recap
Hi [first name],
[Event name] ran on [date] at [venue, city]. [One sentence: main result against the goal.]
Attendance: [number] valid registrations against a target of [target], and [number] checked in against a target of [target]. The attendance rate was [rate]% against a planned [rate]%.
Against the goals: [figure, target, final or provisional]. [Figure, target, final or provisional.]
What did not go to plan: [item and cause, in one or two sentences].
Feedback so far: [number] of [number] attendees have answered the survey. [One figure.] The survey closes on [date].
Still to come: final cost on [date]. Pipeline, revenue, and the full report on [date].
Next steps: [action, owner, date]. [Action, owner, date.]
Counts are from [system] exports taken on [date, time]. An attendee is [definition].
[Sender name, title, reply address]
Version for attendees.
Subject: [Event name]: recordings, slides, and what happens next
Hi [first name],
Thank you for joining [Event name] on [date]. [Number] people from [number] organizations took part.
Recordings and slides: [link], available until [date].
If you have 3 minutes, tell us what to change: [survey link]. The survey closes on [date].
[Next edition: date and city, with a link to register interest.]
[Sender name, title, reply address]
Send the attendee version only to people who checked in. Sponsors get the client version with their own delivery lines in block 4, and their full account follows in the sponsor report.
Event recap example: a one-day customer conference
Take an agency that ran a one-day customer conference for a client on Thursday, October 15, and sends the recap the following Tuesday. The goals agreed before the event were 400 registrations, 300 attendees, and 35 sales meetings held on site, on a budget of $186,000. All figures are hypothetical.
| Line | Target | Actual | Variance | Source | Status |
|---|---|---|---|---|---|
| Valid registrations | 400 | 436 | +9.0% | Registration export: 445 records, 9 tests and duplicates removed | Final |
| Checked-in attendees | 300 | 318 | +6.0% | Check-in export | Final |
| Attendance rate | 75.0% | 72.9% | −2.1 points | 318 ÷ 436 | Final |
| Customers | none set | 221 of 284 came, 77.8% | Same exports, by registration type | Final | |
| Prospects | none set | 97 of 152 came, 63.8% | Same exports, by registration type | Final | |
| Sales meetings held | 35 | 42 | +20.0% | Sales desk booking sheet | Provisional |
| Survey responses | none set | 89 of 318, 28.0% | Survey tool | Provisional, open until October 23 | |
| Cost | $186,000 | $182,300 | −2.0% | Contracts and invoices received | Provisional, 2 invoices outstanding |
Run the three tests. The first five lines come from exports and will not move. The meeting count sits in a booking sheet the sales team is still completing, so it goes in as provisional. Cost goes in block 7 with its date.
Cost per attendee waits for the report. At $182,300 and 318 attendees it would read $573, against a planned $620 ($186,000 ÷ 300), and it would need correcting if either outstanding invoice comes in above its estimate.
The no-show line needs the split. Of 436 registrants, 118 did not come: 63 customers and 55 prospects. Prospects were 35% of registrations and 47% of no-shows.
Subject: Customer Summit, October 15: recap
Hello,
Customer Summit ran on October 15 at the conference hotel. Attendance beat the goal: 318 people checked in against a target of 300.
Attendance: 436 valid registrations against a target of 400. The attendance rate was 72.9% against a planned 75.0%. Customers came at 77.8% (221 of 284) and prospects at 63.8% (97 of 152).
Against the goals: 42 sales meetings were held on site against a target of 35. That count is provisional until your sales team finishes logging on October 23.
What did not go to plan: 118 registrants did not come, and 55 of them were prospects. One afternoon breakout started 20 minutes late after a projector failure.
Feedback so far: 89 of 318 attendees have answered the survey, a response rate of 28.0%. Of those, 71 rated the day 4 or 5 out of 5. The survey closes on October 23.
Still to come: cost stands at $182,300 against a budget of $186,000, with two invoices outstanding. Final cost follows on November 6. Pipeline from the meetings and the full report follow on November 13.
Next steps: the attendee recap with recordings goes out on October 21 (account lead). Your sales team receives the meeting list on October 23 (sales operations).
Counts are from registration and check-in exports taken on October 19 at 5:00 p.m. Eastern. An attendee is a registrant with a check-in record.
The email runs to about 240 words. The shortfall among prospects sits in the same message as the good news, and every unfinished number has a date beside it.
Which mistakes make a recap useless?
Sending it late. After a week your client has already answered "how did it go" without your numbers, and the recap becomes a correction.
Registrations reported as attendance. "436 people" in the headline, when 318 came, is the error a finance reader finds first.
A figure with no target beside it. 318 attendees means little to someone who does not know the goal was 300.
Pipeline or ROI on day three. Cost is not final and no deal has closed, so both figures will be restated later.
What to do this quarter
- Write the goals for your next event as numbers with targets before registration opens, so the recap has something to report against.
- Decide the attendee definition and the export time now, and put both in the data note.
- Build the recap from the nine blocks and book the send date three business days after the event.
- List the pending numbers with the date each becomes final.
- Keep every recap you send. Next year's targets start from this year's actual column.
Common questions
How long should an event recap be?
One screen as an email, which is about 150 to 250 words, or one page as a document. If it needs a second page, it is turning into the report, and the report has its own date.
When should you send an event recap email?
Within three business days for a client or leadership. The attendee version goes out when the recordings are ready. If a number is not final by day three, send the recap with that line marked provisional.
Should an event recap include photos and quotes?
In the attendee version, yes: a photo and a link to the gallery. In the client version, put one photo or one attendee quote after the numbers, and get permission before you quote anyone by name.
Where EventIQ fits
EventIQ replaces nothing. It connects on top of the platforms you already run: event platforms (Cvent, Zoom, Swapcard), CRM (Salesforce, HubSpot, GoHighLevel), and marketing (Google Ads, Meta Ads, LinkedIn Ads, Mailchimp, Google Analytics). Platforms with an API outside that list are connected on request.
EventIQ does not write the recap and does not send email. The message goes out from your own mailbox or your email tool.
What it holds is the counts behind block 3. Registrations from Cvent arrive with their date, ticket type, and price where the platform provides them, along with a check-in mark, and registration and attendance are kept as separate records. Zoom adds attendance by participant with time in session. Swapcard adds session views, survey answers, and questions per participant, and booth visits as totals per sponsor. By default Swapcard syncs every 15 minutes and Cvent every 30, configurable per source, so the counts are there when you sit down to write.
Four limits. EventIQ does not calculate the attendance rate, so that division is yours. Cvent is the only registration source: Zoom gives attendance and time in session, without registrants per webinar, so registered against attended for a webinar comes from your own Zoom report. Survey answers reach it only from Swapcard. And it makes no recommendations, so the line about what did not go to plan is your team's to write.
Book a demo to see the registration and check-in records a recap starts from on a sample event, in a 20-minute demo.