Event Recap Deck

About this template

Written within three days of the event

Ten slides for reporting a one- to three-day event: a seminar, an internal workshop, a booth, a customer session. Write it within three days while on-site notes and memory are fresh. It is not a pre-event plan or a budget request, since there is no line-item budget or schedule table here.

Where the ten slides sit

1. Slide 1 cover – REPORTS label, title, one description line, presenter line.
2. Slide 2 agenda, five lines.
3. Slides 3-4 section 01 divider and body; slides 5-6 section 02 divider and body.
4. Slide 7 plan versus actual, three lines per side.
5. Slide 8 four metric cards; slide 9 four trend bars.
6. Slide 10 closing – THANK YOU plus one line.

What the five agenda lines point at

The agenda already uses event wording: event overview, attendance, plan versus actual, key figures, trend analysis. Only the first two lines bring a divider-and-body pair with them (slides 3-4 and 5-6); the third is the two-column slide 7, the fourth the cards on slide 8, the fifth the bars on slide 9. In other words only slides 4 and 6 are free prose; everything else is a fixed format. If something like program operations or spend deserves its own slide, duplicate the 5-6 pair, add a line to the agenda and renumber the SECTION labels. For a talk under ten minutes, do the opposite: keep one pair and shorten the agenda to match.

Numbers for the metric cards

The four cards carry 636 actual attendees, 74% show rate, 4.3 satisfaction and KRW 67M total spend, with a “unit: internal tally” footnote underneath. All four interlock with the two body slides, so edit them together.

• The 74% comes from 636 of 860 pre-registered. Change the denominator and the percentage must be recomputed.
• Cost per attendee has no card, so add KRW 67M / 636, about KRW 105,000, as a body bullet; it heads off the budget question.
• Next to the 4.3, state the response count and the question wording. The simplest route is to replace the “internal tally” footnote with the number of surveys returned.
• Keep figures with a different denominator, such as 92 partner invitees, on their own line rather than mixed into the show rate.

The hourly bars are an operations record

The trend slide shows arrivals by hour: 148 at 09:00, 92 at 11:00, 176 at 13:00, 64 at 16:00. The peak at 13:00 and the fall at 16:00 line up with the line on slide 6 about 18% drop-off in the afternoon sessions. You can repurpose the bars for registrations by channel, but then all four labels change and the link to the drop-off narrative breaks. The bars are shapes, so lengths do not follow edited values.

Plan and actual, line by line

Slide 7 is three lines of plan on the left and three of actual on the right, aligned item by item: 600 pre-registered against 512 attending (85%), eight sessions and twelve booths against all eight sessions running, twenty operations staff against four extra people added on site. The rows that missed are the substance of the report, so add a cause under anything that diverged, such as the 85%. Note that these sample figures use a different denominator from slides 4 and 6 (860 registered, 636 admitted); in your own report make the registration and attendance numbers agree across both places. To compare with the previous edition, change only the left column heading and keep the same three rows.

What event reports usually omit

• Attendance with no denominator – the same headcount is 74% against registrations and 39% against invitations.
• An average score with no response count, which cannot be compared next time.
• Leaving the improvements for next time nowhere. There is no dedicated slide for them, so either duplicate the 5-6 pair or add owner and due date under the right-hand column of slide 7, or nobody reopens the file at the next planning meeting.