ThemeCapture & close
CardCard 47 of 60
Questions5 to explore

Reporting & Delivery

What to deliver after the workshop?

What you deliver after the workshop often matters more than what happened in the room.

Reporting and delivery covers everything that leaves your hands after the session: the summary, the photos of the wall, the typed-up outputs, the decision log, the follow-up email, the presentation to leadership. This is where most workshops quietly die. If nothing is delivered after, the work in the room rarely continues.

Decide before the session what you will produce after it, in what format, by when, and for whom. Then protect the time to do it. Post-workshop delivery is easy to delay once normal work resumes, and a summary sent three weeks late carries almost no weight.

The format should serve the audience, not the facilitator. A leadership team needs a one-page summary with decisions and next steps. Participants may want the raw outputs and a note of what they committed to. These are rarely the same document.

Easy to missAssign someone other than the lead facilitator to capture photos and notes during the session, because the person running the room almost never has spare attention for documentation and you will regret the gaps afterward.

How experienced facilitators handle it

The same building block, handled by people who have run a lot of workshops. Patterns and illustrations to react to, not rules to follow.

Send something the same day

Experienced facilitators send at least a short message within 24 hours of the session ending: what was decided, what comes next, and who is responsible. This keeps momentum alive before it evaporates.

Match format to audience

They write the summary for the person who reads it, not for the record. A bullet-point email for participants, a structured brief for the sponsor, photos for those who want to relive the day.

Document during, not after

They build capture into the session itself: a scribe, a designated photographer, a shared note on the wall, so reconstruction from memory is not required afterward.

Questions to plan around

Use these on your own or in a group. There are no right answers, only better conversations.

What will you deliver after the workshop, in what format, and to whom?
Who is responsible for writing up and sending the post-session summary?
What is your deadline for delivery, and is that deadline realistic given your schedule?
What does the sponsor or client need to receive after the session, and is it different from what participants need?
Who will capture outputs during the session so you are not reconstructing everything from memory afterward?

Watch for

Leaving the write-up until you have time almost guarantees it gets squeezed or forgotten, and a workshop without documentation quickly becomes a disputed memory.
Delivering everything at once in one massive report often means nothing gets read; shorter, targeted outputs for different audiences land better.
Participants interpret silence after a session as a sign that nothing came of it; even a brief 'here is what we concluded' email restores confidence that the day mattered.