3.5 · The post-event week

ExpertDuration ~10 min readTools A blank doc, Your Luma guest list, The shot list from 3.3

The big idea: the week after the event is a sequence, and you write it before the event. Hot wash, survey, thank-you wave, recap, debrief, in that order, because the version of you that exists on Sunday morning is not going to write any of it from scratch.

The analogy

You know the moment the AD calls the wrap. People cheer, somebody takes a photo, and the room empties faster than it filled. And then nothing is actually finished.

The camera cards still have to come off that night, verified and backed up, while the DIT is in the building and still awake, because a card that goes home in somebody’s bag is a card that gets wiped by accident on Tuesday. The gear goes back on the day the rental house says it goes back, tired or not. The crew who gave you their weekend get thanked while they still remember the weekend. And the only reason anyone ever gets a film out of it is that the footage was offloaded properly on the one night nobody felt like offloading anything.

Here is the part worth stealing. None of those steps get invented at wrap. They were written into the schedule during prep, by a person who was rested and thinking clearly, exactly so the exhausted version of the team could just follow the list.

Your post-event week is a wrap-out. Same problem, same fix.

How it works

Every organizer means to do the follow-up. Most of it does not happen, and the reason is not laziness. It is a scheduling mistake. The work is small, an hour or two spread over a week, but you have scheduled it for the seven days of the year when you have the least energy in the tank. So move the writing forward into the calm weeks and leave the sending where it is. That single swap is most of this lesson.

Start the same day, or the next morning at the latest, with a hot wash. The name comes from emergency management, where teams debrief immediately after an incident while everything is still hot, and event teams borrowed it because it solves the same problem. Get whoever ran the room into a circle or a group call. Three questions only: what worked, what did not, what we would change. Somebody types while everyone talks. Nobody solves anything, nobody defends anything, and nobody is allowed to say the word “but.” You are not looking for decisions yet, you are looking for the raw version, because within about a day people begin explaining every problem to themselves until it sounds reasonable, and the honest account is gone. Keep it short. It ends when the list stops growing.

Inside 48 hours, the survey goes out, and short beats thorough. A handful of questions, one of them open text, and one of them the recommend question that produces your NPS. Net Promoter Score asks how likely somebody is to recommend the thing to a friend, on a fixed scale, and turns a room full of feelings into one number. The number on its own is not that interesting. What makes it worth collecting is that it is comparable, so the August event can be measured against the next one and the one after that, using a question you never change. It is also the only piece of attendee sentiment you can put in front of a sponsor without inventing anything.

Then the thank-you wave. It is a wave rather than a message because it goes out in segments, and the segments want different things. People who came get thanked and pointed at the recap. People who registered and did not come get something warm that does not make them feel caught, just the recap, an honest “we would love to see you at the next one,” and the date. Speakers, guests and the podcast side get something personal and specific, referencing the thing they actually said. Volunteers get the most personal message of all, by name, because they gave you a Saturday. Sponsors get a short holding note saying the full report is coming, which buys you the time 3.6 is about to ask for. And the house sequencing rule applies here the way it applies everywhere: the volunteer team hears the hot wash and gets their thank-you before anything goes public.

Next comes the recap wave, which is this course’s label for the content drop that follows an event. It is built entirely from the shot list you handed to a named content owner in 3.3, which is why that lesson insisted the list be written before doors rather than remembered afterwards. Recap post first, then the photo album, then the highlight cut when it is ready, then the quieter drip of clips over the following fortnight. Write these in the brand’s own defaults: hook first, lead with a human or the mission rather than with logistics, close on one clear call to action. If a newsletter goes with it, keep it to one topic and open on something the reader actually feels. Sharing the night back to the room is part of the culture at Filmmakers Connect, not an afterthought, and it has a second job too. This recap is the launch material for next August, and it lands on a warm audience instead of a cold one. That is the flywheel 3.7 takes apart.

A week or two out, once the survey has landed, you run the structured debrief. This is a different meeting from the hot wash and it is worth saying so out loud, because teams collapse the two and end up with neither. The hot wash captured feelings while they were true. The debrief takes those notes plus the survey plus your attendance numbers and produces decisions with a name and a date attached to each one. Run it against the three questions the practitioner templates all converge on, what worked, what did not, what we do differently, and protect one rule above the others: this is not the room where anyone gets blamed. People only tell you the useful things when it is safe to.

Sitting inside the same window is the highest-stakes item of the whole week, the sponsor report, due inside ten business days. It is its own lesson, next. And one habit from a working producer that costs nothing: put the debrief on everybody’s calendar before the event happens, so the deadline exists whether you feel like it or not.

August is the first Filmmakers Connect event where this week has real weight. More people in the room, sponsor booths that expect a report, a live podcast that produces content nobody will have time to sort. Give each piece a named owner from the volunteer departments now, and write the words now, while writing them is easy.

The receipts (evidence, if you want it)

Hot wash is borrowed from emergency management, where it means the immediate same-day or next-day debrief run while details are fresh. The public-sector template that names the practice is the BC Government hot wash and debrief summary report template. For how it differs from an agile retrospective, and why teams run both, see Scott Graffius on retrospectives and hot washes.
The structured debrief. EventsAir’s guide defines it as a structured review meeting held after the event with the core team, run on three core questions: what worked well, what didn’t work well, what would we do differently next time. Their five-step method is prepare in advance and circulate the agenda, gather the data first, create a safe environment (“an event debrief is not the place to start pointing fingers”), focus on the core questions, and document the findings. The same piece carries a bank of 40 plus questions grouped by objectives, planning, marketing, registration and attendance, venue and logistics, program and content, attendee experience, vendors and partners, budget, technology, and post-event follow-up (EventsAir, post-event debrief guide with template and questions). A second template with the same shape: vFairs event debrief template.
Evaluation is meant to be quantitative and qualitative together: registrations, attendance rate, revenue and NPS on one side, open-text responses, sponsor feedback and team notes on the other (Samaaro, how to write a post-event evaluation report).
The 48-hour survey window and the NPS scoring basis are TEDx’s own rule. Organizers “must send out our TEDx attendee survey within 48 hours after your event has completed,” with results returned in three to four weeks, and the results are “based on the Net Promoter Score system.” The same post-event checklist asks organizers to upload photos and videos and refresh the event page afterwards, and the post-event engagement page adds the follow-through: share the talk videos with attendees, send updates and news, stay active on social, keep the community meeting between events (TEDx organizer guide, post-event checklist; post-event engagement).
Event NPS is the cross-event loyalty measure named in the survey literature this course drew on (SurveyMonkey, post-event survey questions). Attendance rate, checked in divided by registered, is the other half of the pair, and you only have it if you checked people in properly in 3.2.
The thank-you wave. The industry map records this from Maclyn’s pre, during and post checklist: the two to four weeks after an event are where pipeline, community and re-bookings are built, via a thank-you wave sending tailored messages to attendees, no-shows, sponsors, speakers and media with relevant next steps (Maclyn, the ultimate event marketing checklist). That single line is what the course quotes from it, and this lesson does not claim more of the source than that.
The standard post-event content stack in the same section: recap post and highlight video, attendee testimonials, a survey with NPS, a drip of recorded or exclusive content, sponsor reports, and using the recap assets as the launch material for the next event.
DevOpsDays keeps it blunt and optional: “Surveying your attendees and blogging about the results is optional, but strongly recommended.” Their website guidance also asks organizers to embed speaker slides and upload the videos, because the event’s content is meant to outlive the day (devopsdays.org/organizing).
The honest failure mode, from someone it happened to. After DevOpsDays Halifax, the organizing team “worked relentlessly leading up to and during the event, but once it was over, we were quickly consumed by our regular jobs,” with slides still to publish, 12,000 photos to sort and 20 hours of video to edit, and the student volunteers already back at school. His conclusion is the same as this lesson’s: assign someone to lead post-conference tasks, and put post-event activities into the overall plan rather than discovering them afterwards (Dewan Ahmed, hosting a DevOpsDays tech conference).
The ten business day sponsor report standard comes from Bridged’s sponsorship ROI guide, and the report’s contents are taught in full in 3.6.

Your one move

Open a blank doc and title it “August post-event week.” Write the survey first, five questions maximum, one of them open text and one of them the recommend question. Then write four short messages with the blanks left as blanks: attendees, no-shows, volunteers and guests, sponsors. Put a send date next to each one.

Twenty-five minutes. Done when the doc exists, every message has a date, and none of it needs to be composed after the event.

Want to go further?

Book two calendar invites right now, before the event exists in anyone’s mind as a thing that is over. The hot wash goes on the night of the event or the following morning, and the structured debrief goes ten to fourteen days out. Invite the whole core team to both. A deadline that already exists in everyone’s calendar survives exhaustion much better than a good intention does.

The needle: an event is won before doors open, and so is the week after it. Everything that ships that week is either already sitting in a folder you wrote in one calm hour, or it is not shipping.

Terms introduced

Check

You can move on when you can… say the five steps of the post-event week in order, explain the difference between the hot wash and the structured debrief without hedging, and point at the folder where the survey and the four thank-you messages are already written.

Go deeper

Next up: 3.6 · The sponsor report, the highest-stakes document in this window, where the fulfillment audit turns a sponsor into a returning one.
A short practitioner clip, not a template, about eight minutes: 3 Lessons Learned in Events in 2024 from producer Logan Clements. Skip to her third lesson, where she argues for shipping the post-event report inside five days and for putting the debrief on the calendar before the event happens. She is candid that she owes a client a report from two months ago and that her own fix is a thirty-minute timer and whatever gets done in it. Her first two lessons belong to 2.6 and 3.2, so take only the post-event half.
Optional reading, about fifteen minutes: the EventsAir post-event debrief guide. Read the five-step method, then treat the 40 plus question bank as a menu rather than an agenda. Pick six questions for August and leave the rest.
Worth one look before your first hot wash: the BC Government hot wash and debrief template. It is written for emergency response, so the register is not yours, but it shows you what a same-day capture looks like when the people using it have no time to be elegant.