Event recap email template, with a worked example

Most post-event emails are written for the organizer. They open with how many people came, thank the sponsors, link to a gallery and ask for a survey. That's all fine, but none of it is why the attendee spent a day away from their desk.

The recap that gets read leads with the thing they came for: what was said that's worth keeping. The template below is built that way. After it there's a filled-in example and some notes on when to send.

The structure

Six blocks, in this order. The first two do most of the work.

Subject line that names the event and promises the takeaways. “Thank you!” does neither.
The takeaways. Three to five ideas from the day, each with the example or quote that made it land, and who said it.
One question back. “Which of these are you going to use?” Make replying easy.
The materials. Slides, recordings, transcripts. Links, with an honest “available until” date if there is one.
One next step. The next event, a community link, or the survey. Pick one.
A human signature. A real name and a reply address that reaches a person.

The thank-you goes in one sentence at the top. Attendance numbers and sponsor thanks can go at the bottom, or in a separate email to the people who care about them.

The template

Subject

What we heard at [Event name]: [number] ideas worth keeping

Body

Hi [First name],

Thank you for being at [Event name] on [day]. Here is what we heard that's worth holding on to.

1. [Takeaway in one plain sentence.]
[One or two sentences with the example, story or number that made it memorable.]
“[Short quote from the talk.]” [Speaker name], [session title]

2. [Takeaway.]
[Supporting detail.]
“[Quote.]” [Speaker], [session]

3. [Takeaway.]
[Supporting detail.]
“[Quote.]” [Speaker], [session]

Which one are you going to use first? Hit reply and tell me. I read every answer.

Slides and recordings: [link] (available until [date])

[One next step: Save the date for [next event] / Join the [community] / Tell us what to change, 3 minutes: [survey link]]

[Your name]
[Role], [Organization] · [reply address]

A worked example

This is the template filled in for a fictional one-day product conference. The speakers and quotes are invented for illustration.

Subject

What we heard at Field Notes 2026: 3 ideas worth keeping

Body

Hi Sam,

Thank you for being at Field Notes on Thursday. Here is what we heard that's worth holding on to.

1. Ask for one thing before someone has used your product.
Dana's team cut their sign-up form from five questions to one. The people who used to drop out weren't the uninterested ones; they were the unsure ones.
“We saved the rest of the questions for after their first win.” Dana Whitlock, The first five minutes

2. Write the recovery screen before the success screen.
Teams spend weeks on the happy path and an afternoon on the error state, but the error state is where users decide whether to trust you.
“People forgive the failure. They remember how you behaved after it.” Maya Chen, Designing for trust

3. Read raw tickets before you read the dashboard.
Tomás reads fifty support tickets every Monday before looking at a single metric.
“The dashboard tells you how much. The tickets tell you why.” Tomás Ibarra, What support tickets know

Which one are you going to use first? Hit reply and tell me. I read every answer.

Slides and recordings: fieldnotes.example/2026 (available until December 31)

Save the date: Field Notes 2027 is April 22.

Yossi
Field Notes · yossi@fieldnotes.example

Picking the takeaways

Most recaps skip this part, and it's the hard one.

Choose ideas over sessions. Three strong ideas from two sessions beat one weak line from each of ten. If you want full coverage, link to a page with every session's takeaways and keep the email short.
Keep the concrete detail. “Simplify onboarding” is forgettable. “Cut the form from five questions to one” isn't.
Quote the speaker, briefly. A real sentence from the talk is more credible and more memorable than your paraphrase. Check it against the recording or the speaker's slides; a misquote in an email to every attendee is hard to take back.
Credit the right person. On panels, check who actually said it. Getting attribution wrong is the most common mistake we see, from people and from AI alike.

Subject lines that work

The subject line should tell people there is something in the email for them.

What we heard at [Event]: [number] ideas worth keeping
[Event] in [number] ideas (plus slides and recordings)
The [number] things people kept talking about at [Event]
[First name], your [Event] takeaways

Avoid “Thank you for attending!” on its own. It's polite, and it tells the reader there is nothing to open.

When to send it

As soon as you can, ideally the same evening or the next morning. Memory research is consistent that most forgetting happens in the first day or two, and a review inside that window does far more than the same email a week later. (I wrote more about this in What attendees actually remember after a conference.)

If speed means sending it before the recordings are ready, send it anyway. Say “Recordings will follow by [day]” and send a short second email when they do.

Send a slightly different version to registered people who didn't come: “Here is what you missed” rather than “Thank you for being there.” People notice when you thank them for an event they skipped.

Doing this without a week of work

The bottleneck is almost always writing the takeaways, not sending the email. A few options, roughly in order of effort:

Ask moderators for three takeaways each before they leave the room. Give them the format above.
Work from recordings. Listen at 1.5x and pull the quotes yourself. Slow, but accurate.
Use software that drafts takeaways from the recording, then review them before sending.

That last one is what Gemlo does: a phone in the room records the session, and takeaways with their source quotes are drafted within minutes of the talk ending. You can review them before attendees see them, or let them release automatically. Attendees get them in the app the same day, which covers the timing problem; the recap email then becomes a highlights reel rather than the only record.

Whatever you use, the template doesn't change: open with what people came for.