Event Recap Template: Structure, Prompts, and Examples
By Attendir Team
An event recap summarizes what happened at an event for the people who were not there and for the attendees who want to remember it. A working recap has six parts: a one-line summary, the numbers, the three most useful takeaways, quotable moments, what is available next, and a clear next step. Publish it within five days.
Most recaps read like minutes. They walk through the agenda in order, thank everyone by name, and end. The person who attended does not need the walkthrough, and the person who did not attend has no reason to read one. Both would read something that told them the three things worth knowing.
This guide covers the recap's actual job, the six-section structure with prompts for each, how the blog, email, and LinkedIn versions differ, the mistakes that make recaps unreadable, and how to get the material without transcribing your own event.
Last updated: August 17, 2026.
What a Recap Is For
A recap serves three audiences at once, and the structure below works because it serves all three without writing three documents.
Attendees want confirmation that their time was well spent and a reference for what they half-remember. They will forward it to a colleague if it is good.
People who did not attend want the substance without the four hours. This is the largest audience by far and the one recaps most often ignore. It includes the registrants who did not show up, who are a warm and specific segment worth writing for.
Future attendees are evaluating whether to come next time. Your recap is the closest thing to a preview they will get, and it will still be indexed and doing that job a year from now.
Written recaps have a structural advantage here that video does not: they are skimmable, searchable, quotable, and they get read on a phone in ninety seconds. Publish the video too, but the written version is the one that travels.
The Six-Section Structure
1. The one-line summary
Open with the single sentence you would say if someone asked "so how was it?" in an elevator. Not "our annual summit brought together industry leaders" — something with content in it.
Prompt: If a colleague who missed it asked what happened, what would you say in one sentence before they interrupted?
This line does most of the work. It is what gets quoted, what becomes the meta description, and what AI assistants extract when someone asks about your event.
2. The numbers
Three to six figures, no commentary. Attendance, sessions, countries or companies represented, questions asked, whatever is genuinely interesting about the scale or composition.
Prompt: Which numbers would surprise someone who was not there?
Keep this honest. A recap that reports 400 registrations for an event 180 people attended is a recap nobody in the room will share, and the people in the room are your distribution.
3. The three takeaways
The core of the recap. Three substantive things attendees learned, written so that reading them delivers real value to someone who was not there.
Prompt: What did you hear in the hallway three separate times? What made people take out their phones to write something down?
Write each as a claim with support, not a topic label. "Pricing was a major theme" is a table of contents entry. "Three separate speakers argued that annual contracts are dying in mid-market SaaS, and the pushback from the audience was sharper than the panel expected" is a takeaway.
Three is the right number. Five becomes a list nobody finishes; one looks thin.
4. Quotable moments
Two to four direct quotes with attribution. Real sentences people actually said, not paraphrases smoothed into corporate register.
Prompt: What line got repeated back to you afterwards?
Quotes are the most reusable component of the recap. Each one becomes a graphic, a social post, and something the speaker will share with their own audience — which matters, because individual LinkedIn accounts earn roughly 8x the engagement of brand pages for the same content.
5. What is available now
Recordings, slides, transcripts, the photo gallery, the community channel. Link each one directly. This section is why attendees open the recap at all, and it is why the recap keeps getting traffic for months.
6. The next step
One clear action. Next event's save-the-date, the waitlist, the newsletter, or a specific piece of content. Not four options — one.
Prompt: What is the single thing you want a reader to do, and is it visible without scrolling?
Three Versions, One Source
Write the blog version first, then cut it down. The three versions differ in length and in what they lead with.
Blog recap (600-1,200 words). All six sections in order. This is the canonical version, the one that gets indexed, and the one everything else links back to. Publish it on your own site rather than only on a social platform — a recap that lives only on LinkedIn stops existing when the feed moves on.
Email recap (200-350 words). Lead with the takeaways, not the summary line — your subscribers already know the event happened. Compress the numbers into one line, keep one quote, and make the "what is available now" section the visual centerpiece, because that is what recipients click. Send it to attendees and no-shows with different opening lines: attendees get "here is what you saw," no-shows get "here is what you missed, and here is the recording."
LinkedIn recap (100-200 words). One takeaway, one quote, one number, one link. Post it from a personal account rather than the company page. If you want reach, ask the speakers to post their own version — a speaker's recap of their own session outperforms your recap of their session, and they are usually glad to have the material handed to them.
The Mistakes That Kill Recaps
Chronological structure. "The morning began with registration and coffee." Nobody reads past this. Lead with the most interesting thing that happened, wherever in the agenda it occurred.
Thanking everyone. Sponsor and speaker recognition belongs in the recap, but as a line near the end, not as the opening three paragraphs. A recap that opens with gratitude reads as an internal document that leaked.
No substance for non-attendees. If the recap only makes sense to someone who was there, it has forfeited its largest audience. Test it on a colleague who did not attend.
Publishing late. Five working days is the outer edge. A recap published three weeks later gets a fraction of the readership because the event is no longer a live topic and the attendees have moved on.
No next step. A recap with no action is a nice document that produces nothing. It sits in the middle of your post-event marketing sequence and should hand the reader onward.
Getting the Material Without Transcribing Your Own Event
The reason recaps get written late is almost always that nobody captured the raw material during the event.
Fix it with three habits. Assign one person per session to note the strongest line and the audience's sharpest question — a shared doc with a row per session is enough. Photograph deliberately rather than hoping: the speaker mid-gesture, the full room from the back, one candid hallway conversation. And pull the survey's open-text responses, which routinely contain better takeaway phrasing than anything the marketing team would write, because attendees describe value in their own words.
From there the recap becomes an editing job rather than a writing job, and the same raw material feeds the rest of the cycle — see post-event content repurposing for turning it into the clips, quote cards, and session breakdowns that carry the event through the following months. The internal counterpart to the public recap is the event debrief template, which handles what went wrong rather than what went well.
Frequently Asked Questions
What should an event recap include?
Six sections: a one-line summary that says what actually happened, three to six numbers that convey scale or composition, three substantive takeaways written as claims with support rather than topic labels, two to four real quotes with attribution, a list of what is now available with direct links to recordings and slides, and one clear next step. The takeaways are the core — they are what makes the recap valuable to the large audience that did not attend, which is the audience most recaps fail to write for.
How long should an event recap be?
The blog version runs 600 to 1,200 words, which is enough for three developed takeaways and a few quotes without becoming a transcript. The email version compresses to 200 to 350 words and leads with the takeaways rather than the summary, since subscribers already know the event happened. The LinkedIn version runs 100 to 200 words: one takeaway, one quote, one number, one link. Write the blog version first and cut the others from it rather than drafting three times.
How soon after an event should you publish a recap?
Within five working days, and sooner is better. The recap competes for attention with the event's own afterglow, and that window closes quickly — a recap published three weeks later reaches a fraction of the audience because the event is no longer a live topic and attendees have moved on to the next thing. The way to hit the deadline is to capture raw material during the event rather than reconstructing it afterwards, which turns the recap into an editing task rather than a writing task.
What is the difference between an event recap and an event debrief?
A recap is public and describes what was valuable; a debrief is internal and describes what needs to change. The recap is written for attendees, non-attendees, and prospective future attendees, and it leads with substance and takeaways. The debrief is written for the team that ran the event, includes what went wrong and what it cost, and produces a list of decisions with named owners. Both should happen in the same week after an event, and neither substitutes for the other.
Should an event recap be written or video?
Publish both, but write the recap. Written recaps are skimmable, searchable, quotable, indexed by search engines, and readable on a phone in ninety seconds, which is why they travel further and keep earning traffic months later. Video recaps convey atmosphere better and are worth producing for social and for the event page, but a video alone gives search engines and AI assistants almost nothing to extract, and it cannot be forwarded to a colleague who has ninety seconds rather than three minutes.
Turning the Recap Into Reach
A recap only performs if people distribute it, and the people best positioned to do that are the speakers, sponsors, and attendees whose own moments are in it.
Attendir for B2B conferences gives each of them a branded share page and a tracked link, so the recap's distribution is measurable and you can see which advocates actually moved it — the same list that makes the next event's promotion easier. Plans start at $408 per month billed yearly, with a 7-day free trial and no credit card required.