Workshop follow-up checklist: what to do in the 24 hours after the workshop

The workshop went well. The wall is full, the sponsor nodded, the room empties. What happens in the next 24 hours decides whether any of it turns into work. This checklist is for the facilitator or organiser: four time windows, one short task list each, and the traps that make a good workshop evaporate.
Why the first day matters
In SessionLab's State of Facilitation report, 43,5 % of facilitators name missing follow-up as the main barrier to impact, and only 29 % follow up after most of their sessions. The day after a workshop is a normal working day, and the summary competes with everything that piled up while you were in the room.
So the rule is simple: the follow-up is part of the workshop. Block two hours after the session in your calendar before you send the invitation, and treat the list below as the last item on the agenda.
Within one hour
- Photograph the wall. Every board, every cluster, every dot vote, before anyone starts taking things down. One photo per board, straight on. This is your backup, not your summary.
- Write the three decisions while they are fresh. Open a note and type what the room decided, in full sentences: "We test the self-service return flow with ten customers in November." If you cannot write it as a sentence, it was not a decision; it goes into the open questions.
- Thank the sponsor, with the decisions in the mail. Three lines: thank you, here is what we decided, the full summary follows today. The sponsor gets something to repeat in their next meeting, and it is your version.
Same day
- Write the one-page summary. Four headings and nothing else: the question the workshop set out to answer, the decisions, the open questions, and the owners with dates. One page, plain text, readable on a phone. No slides.
- Send it to everyone who was in the room. Same mail, same day, including the people who left early. Put the decisions in the first lines of the mail, not only in an attachment.
Next morning
- Put the first steps in calendars. Every owner gets an invite for their first working session, even if it is thirty minutes alone. An action without a time slot is a wish.
- Assign the open questions. Each open question gets one name and a date for the answer. "We'll discuss it in the next meeting" is not an assignment.
- Store the parked ideas somewhere findable. The ideas you deliberately did not pursue go into one place the team can search, with one line on why they were parked. Tools like IdeaHone keep them with their scores; a shared document works too.
- Set the review date. Pick the day you check whether the decisions turned into results, usually four to six weeks out, and send that invite now, while people still remember why.
Within the week
- Check that owners have started. A short message to each owner: "Did the first step happen?" Just a yes or a blocker. A blocker on day five is cheap; on day thirty it has already killed the idea.
- Close the loop with the sponsor. Tell them which first steps happened and which did not. If something stalled, say what you need from them, in one sentence. That is the moment their support is still worth something.
The summary is the follow-up. If you only have time for one item on this list, write the one page and send it the same day. Everything else can be caught up; that cannot.
Five habits that stall the follow-up
- Sending the photo instead of the summary. A photo of forty sticky notes is a puzzle, not a result. Even people who were in the room cannot reconstruct it after two days. Attach it to the summary, never send it alone.
- The summary written a week later from memory. By then three people remember three different decisions and the summary becomes a negotiation.
- Owners who were not in the room. It feels efficient and almost never works. If the right owner was not there, the action is "talk to X by Friday", owned by someone who was.
- "We'll discuss it in the next meeting." This is where open questions go to die. Every open question needs a name and a date, or it is a parked idea and should be stored as one.
- Follow-up as a separate project. If the follow-up needs its own kickoff, it will not happen. Block the time when you build the workshop agenda, not afterwards.
Every decision from the summary also gets one line, with its reason, in the team's decision log, so it stays decided when the next workshop comes round.
Never lose an idea between sessions
IdeaHone follows every idea from first mention to decision, across all your workshops and teams.
What should a workshop summary contain?
Four things: the question the workshop set out to answer, the decisions, the open questions with a name and a date each, and the actions with owners and dates. One page, sent the same day.
How soon after a workshop should you send the follow-up?
The decisions should reach the sponsor within an hour and the one-page summary should reach all participants the same day.
What do you do with ideas that were not chosen?
Store them in one searchable place with a one-line reason why they were parked. Keep the scores from your prioritisation, for example from an impact and effort matrix, so the reasoning survives.
What should you do after a workshop?
Within 24 hours: send all participants a summary of decisions and open actions, give each action an owner and a date, store the raw outputs where the team can find them, and book the first check-in.
How do you write a workshop follow-up email?
Three parts: decisions made, actions with owner and date, next touchpoint. No narrative recap of the day.