Industry panels and stakeholder forums
Publishing forum outcomes without implying consensus
Participants discussed a difficult issue for half a day, and now someone must write it up for people who were not in the room.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A forum summary should say who discussed what, not what everyone agreed. Choose the type of record first, agree its approval route with panellists in advance, and word every line so that readers can tell views from decisions.
If the forum did reach agreement, say so and name who agreed. If it did not, say that too.
Types of record and what each can claim
| Type | What it states | Approval needed | Risk of implying consensus |
|---|---|---|---|
| Summary of discussion | What was raised and by which kind of participant | Programme owner; panellists for any attributed lines | Low if worded as discussion |
| Key themes note | Themes and questions that came up | Programme owner | Medium: themes can read as conclusions |
| Communique or joint statement | A position agreed by named institutions | Each institution in writing | High, and only valid if each has agreed |
| Association position paper | The association's own view | Committee or council | Must not be presented as the forum's view |
| Recording or transcript | Words spoken | Speaker permissions; see recording permissions | Low, but taken out of context |
Words that imply consensus, and alternatives
| Avoid | Prefer |
|---|---|
| The forum agreed that | Participants discussed whether. Several speakers said |
| Industry consensus is | Views differed. Some participants argued |
| The panel concluded | The moderator summarised three points raised by speakers |
| Stakeholders support | Representatives of two institutions said they support; others did not state a position |
| It was decided | It was proposed. The association committee will consider |
A drafting and approval sequence
- Agree the type of record at the panellist briefing, including who sees drafts and by when.
- Draft from the note-taker's record and evidence log, as described in planning evidence-based follow-up.
- Mark each statement as attributed, institution-only or unattributed, matching the agreement.
- Send attributed quotes to each speaker for correction, with a deadline and a statement that silence means the line is removed, if that is what was agreed.
- Have the programme owner approve the whole summary, and the committee approve any action list or position.
- Publish with a short note saying what the document is and is not.
A disclaimer line that helps
Add one clear statement near the top: this summary records the discussion at the forum on a stated date; it does not represent agreement among participants or a position of the association or any institution, unless stated.
Where an institution has agreed to a statement, place it in a clearly labelled box with the institution's name and the date of its approval.
Worked example · Fictional example
A fictional summary of a forum on professional fees
Fictional organisation and figures, for illustration only.
The Persatuan Fiktif Perunding Kejuruteraan hosted a forum on how members should price long-running projects. Views split between fixed fees and time-based fees, and one institution made a point that the others did not endorse.
The secretariat produces a three-page summary of discussion. It lists five points raised, notes which were widely supported in the room and which were not, and records two attributed quotes with the speakers' written approval. The committee approves a separate list of three actions for the association.
Use this yourself
Pre-publication checklist
Work through this before any forum outcome is sent to members, the press or other institutions.
- Type of record chosen and agreed with panellists beforehand.
- Every statement marked as attributed, institution-only or unattributed.
- Attributed quotes sent to speakers, with replies filed.
- No sentence says agreed, decided, concluded or consensus unless a named group did.
- Differences of view are shown, not smoothed over.
- Facts and figures traced to the evidence log or removed.
- Legal, regulatory or technical statements reviewed by the competent adviser.
- Programme owner has approved the whole document.
- Committee has approved any action list or position.
- Disclaimer line present near the top.
- Distribution list and date agreed.
Handle it in-house, or bring in help?
Your team can usually handle this when
- The forum was small and the record is a short internal note.
- Everyone agreed beforehand that nothing would be published beyond members.
- The programme owner is happy to review a draft.
Outside planning help earns its fee when
- Several institutions want to review and each wants different wording.
- The summary may be read by press, regulators or the public.
- The secretariat needs a structured approval workflow and someone to chase replies.
Need the summary and approvals managed?
A conference project lead can set up the record template, run the approval round with speakers and keep the wording checklist with your programme owner, working from the moderator briefing to confirm attribution early. The committee decides what is published and in what words.
Questions organisers ask
Can we publish without asking panellists?
Only the parts you agreed to publish. Where you attribute remarks to a person or institution, check with them. Agree this at the briefing so no one is surprised.
What if participants disagree with the summary?
Invite corrections by a set date. Fix factual errors. Where views differ on emphasis, show both rather than choosing one.
Should the association add its own view?
Keep it separate and labelled. A position paper needs the committee's approval and should not be mixed into the forum summary.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.