How to summarise a workshop
Last reviewed by The thinkdrop facilitation team
A workshop summary should open with the decisions and owners, not with the agenda. Send it within 24 hours, keep it under a page, and include the ideas that were rejected and why — that section is what stops the same debate reopening in three weeks. The board itself is the appendix, not the summary.
Key facts
- Send within
- 24 hours
- Length
- Under one page
- Opens with
- Decisions and owners
- Always include
- What was rejected and why
- Audience
- Written for the person who missed it
Step by step
- Lead with the decisions — First three lines: what was decided, who owns it, by when. Most workshop write-ups open with the agenda and the attendee list, which is the part nobody needs. If a reader stops after the first paragraph, they should still know what changed.
- Name owners, not teams — "Marketing will look at it" is an action nobody does. A person's name and a date is the entire difference between a workshop that changes something and a workshop that was pleasant.
- Record what was rejected and why — The most valuable and most commonly omitted section. Without it, the same suggestion returns next month and the group re-runs the discussion from scratch. Two lines per rejected option is enough.
- Keep the themes, drop the raw cards — Summarise the themes that emerged and link to the board for the full set. Pasting 60 raw cards into a document guarantees the document is not read.
- Write it for the person who was not there — The people who attended already know what happened. The summary exists for the person on holiday, the stakeholder who could not join, and the reader in three months trying to understand why the decision was taken. Write for them and it will work for everyone.
- Send it within 24 hours — The summary's usefulness decays fast: after a week the actions have already been overtaken and nobody will read it. A rough summary today beats a polished one on Friday.
A structure that gets read
Decisions and owners. Themes, three to six of them, one line each. What was rejected and why. Open questions with a named person responsible for closing each. A link to the board. That is the whole document, and it fits on a page.
- Decisions and owners — the top of the page, always.
- Themes — one line each, not a transcript.
- Rejected options — two lines each, with the reason.
- Open questions — each with a name attached.
- Link to the board for anyone who wants the detail.
Using AI for the first draft
AI is good at turning a board of cards into grouped themes and a readable draft in seconds, which removes the main reason summaries never get sent. The rule is that it drafts and a human confirms: a model will happily write a confident sentence about a conclusion the group never reached, and the facilitator is the only person who can catch it. Never send an unread AI summary.
- AI drafts the themes; the facilitator confirms the decisions.
- Check every named owner and date by hand.
- Delete any conclusion you cannot point to on the board.
Where the summary should live
Wherever your team already looks. A summary in a tool nobody opens is the same as no summary. Paste it into the channel where the work happens and keep the canonical copy with the board so the ideas and the conclusions stay together.
Frequently asked questions
How long should a workshop summary be?
Under a page. If it is longer, it is minutes rather than a summary, and minutes are read by nobody except the person who wrote them.
Should the summary include everyone's name?
Attendees, yes, briefly. Attribution of individual ideas, only where it credits someone or clarifies ownership of an action.
Can AI write the whole summary?
It can write the draft. A human must confirm the decisions, owners and dates before it is sent, because a plausible invented conclusion in a circulated summary is worse than no summary at all.