Executive and practitioner roundtables
Writing a roundtable summary without exposing remarks
Guests spoke on the basis of a rule, and the summary is where that promise is kept or broken.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Write the summary as themes, disagreements and next steps, not as a record of who said what. Then check each line for details that would let a reader work out who the speaker was, and give guests a chance to review before release.
The summary should match the rule on the ground-rules card. If the card says shared without names, a summary with a distinctive anecdote or a single-organisation statistic can break it even with no name attached.
What kind of summary the rule allows
| Rule | Summary may include | Summary must not include |
|---|---|---|
| Open and attributed | Named remarks the speaker has approved | Named remarks the speaker has not seen |
| Shared without names | Themes, positions in general terms, areas of agreement and disagreement | Names, organisation names, or details that identify a speaker |
| Private to the room | Date, topic, number of attendees and agreed next steps | Substance of remarks |
Writing it
- Group the notes by question, not by speaker.
- Write each point as a pattern, such as several guests said or views were split, and avoid counts that could single someone out in a small group.
- Remove unusual examples, figures and phrases that point to one organisation.
- Add a short section of agreed actions, with owners, only if guests accepted them in the session.
- Mark clearly what is the host's view and what is a record of the discussion.
Check for re-identification
- Could a guest's colleague tell who said this from the example alone?
- Is there only one person from a given sector, size of organisation or role in the room?
- Does a figure or date identify a project the reader will recognise?
- Would the sentence read differently if it were attributed to a regulator or a competitor?
- Is any remark about a named person or organisation that was not part of the discussion's purpose?
Review and release
Send the draft to guests with a short window to flag any line that worries them. Treat a flag as final: reword or remove, and do not argue.
Decide in advance who sees the notes behind the summary and how long they are kept, and ask your adviser if that raises any data-protection question. Release only to the group the card promised. Follow-up actions are covered in planning follow-up after the roundtable.
Worked example · Fictional example
A summary after a closed table on supplier failure
Fictional organisation and figures, for illustration only.
A fictional association of risk professionals held a shared-without-names roundtable of 12 members. The first draft said that the only participant from a regional insurer had found the supplier's recovery plan untested.
The secretariat rewrote it as: several participants reported that supplier recovery plans had not been tested end to end. It removed the insurer reference, grouped the notes under the three questions and sent the draft to guests for five working days. One guest asked to remove a figure, and it was removed.
Use this yourself
Summary drafting and release checklist
Work through this before any summary leaves the secretariat.
- Rule on the ground-rules card:
- Summary type allowed by that rule:
- Notes grouped by question, not by speaker:
- Remarks reworded as patterns, with no counts that identify anyone:
- Distinctive examples, figures and phrases removed or approved:
- Re-identification check done by a second reader:
- Host view and discussion record clearly separated:
- Draft sent to guests on [date], with review window to [date]:
- All flagged lines resolved:
- Release list matches what the card promised:
- Notes behind the summary stored by [role], kept until [date], deleted by [role]:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The rule is simple and the group small and trusting.
- One person took clear notes and can write by theme.
- The summary goes only to the people who attended.
Outside planning help earns its fee when
- The summary will be published or shared beyond the guests.
- Guests come from small sectors where identification is easy.
- Several reviewers must approve before release and the process needs running.
Need the summary written and released safely?
An Event Blueprint can set the note-taking method, the review and release process and the checklist above before the session. A project lead can manage the draft, guest review window and release list, while the host keeps final approval of every line and your adviser handles any legal question.
Questions organisers ask
Can we quote a guest if they agree afterwards?
Yes, if the person agrees in writing to the exact words and attribution. Keep the agreement with the notes.
Should the summary say who attended?
Only if the rule and guests allow it. A list of attendees can itself reveal who was involved, so ask guests first.
How long should the review window be?
Long enough for busy guests to read it, commonly several working days. State the date in the covering message so silence does not become a delay.
What if a guest objects after publication?
Remove or amend the material quickly, tell the guest what was done, and review your process. Ask your adviser if the matter raises a legal or data-protection question.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.