Public-interest, policy and sustainability forums
Documenting consultation outputs without claiming endorsement
The write-up of a consultation is read by people who were not in the room, and the wording decides whether it looks like a record or an endorsement.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Write the outcome note as a record of what was discussed, with attribution as agreed, and state its status on the first page: who convened, who contributed, who has seen the draft and what it is not. Official endorsement, if any, comes from the body that holds that authority, in its own words.
Agree the status wording and the approval route with the convening committee before the event, then apply them to every output: note, slides, press release and social posts.
Decide the status of the output before the event
Is the output a summary of views, a set of recommendations from the convener, a joint statement or input to a public body? Each has a different approval route. Write the answer in one sentence and place it at the top of the document.
If any official body will use the output, ask that body how it wants to receive and describe it.
Language that records without endorsing
| Instead of | Consider |
|---|---|
| The forum agreed that... | Participants discussed... ; views differed on... |
| Supported by the ministry | The ministry's representative took part in the session on... |
| Official recommendations | Recommendations from the convener, drawn from the discussion |
| Government-approved outcomes | Outcomes as recorded by the secretariat; not reviewed by any agency unless stated |
| Participants endorsed... | Participants who commented before release: [names], with the changes they requested |
What each output must carry
- Title that names the convener and the date.
- A status statement: who convened, who contributed, who reviewed, and what the document does not claim.
- Attribution rule used: named, by group or non-attributed.
- Version number and the date of last factual correction.
- Logos only of organisations that approved logo use in writing.
- Where disagreements are recorded and how.
- Contact for corrections.
Sequence for producing the record
- Agree the status statement and the attribution rule with the convening committee.
- Take notes against the agenda structure, not against positions.
- Draft the note without evaluating or ranking views.
- Send the draft to named participants for factual correction only, with a deadline.
- Record requests and the response to each.
- Check logos, quotes and titles against written permission.
- Publish with the version and status statement, and keep the approval trail.
Fast-moving outputs
Press releases, social posts and slide recaps repeat the same status risk in shorter form. Put the status wording into a short sentence everyone can reuse, and ask the committee to approve each outward output. A shared content ownership list helps; see content ownership matrix.
Worked example · Fictional example
A fictional consultation on urban mobility
Fictional organisation and figures, for illustration only.
A fictional association hosts a half-day consultation with a municipal agency, two industry bodies and three community groups. A draft note says "The agency supported the proposal on lane use".
The agency's representative replies that she took part in the session but the agency has no position. The secretariat changes the line to record her participation and the points she raised, and adds a status statement: not reviewed by any agency.
The note is released as version 2 with the date of factual correction and a note on which three participants commented.
Use this yourself
Consultation output status checklist
Copy this table, run it before any note, slide or post is released.
| Output | Status statement present | Attribution rule applied | Participants who reviewed | Logos and titles permitted in writing | Approved by | Version and date |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- A small internal consultation with one convener and an agreed attribution rule.
- No outward publication beyond participants.
- The committee chair reviews every output.
Outside planning help earns its fee when
- Several organisations, a public body in the room and public release planned.
- Participants disagree and wording is contested.
- Speed of release is putting pressure on checking logos, quotes and status.
Need the record written and approved cleanly?
A conference project lead can agree the status statement and attribution rule with your committee, run the notes against the agenda, circulate drafts for factual correction, check logos and quotes against written permissions and keep the version trail. Positions and the right to speak for any organisation stay with the participants and the bodies concerned. Send your agenda and participant list to scope the work.
Questions organisers ask
Can we say a ministry was involved?
State what is true: a representative attended or contributed. Do not imply the ministry endorsed the result unless it has said so in writing.
Do we need participants' approval of the note?
For factual correction and for attributed quotes, yes. The convener decides the final text.
Can sponsors' logos appear on the note?
Only if the committee has approved and the funder relationship is stated plainly. See the funder visibility page.
What about recordings?
Treat the transcript or recording as a separate output with its own permission and status.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.