Event committee feedback consolidation
Seven committee members have each sent comments on the draft programme in different formats, and some of them contradict each other.
The short answer
Set one deadline and one format for comments, log every comment in a single table, group them by section, and resolve conflicts by naming who decides rather than splitting the difference. Then issue one consolidated version with a short note of what changed and what did not.
The result should let every member see their comment, the outcome and the reason.
Collect in one place and one format
- Send one version with a reply-by date and one address or shared file for comments.
- Ask for comments to name the section or page, state the change wanted and, if possible, the reason.
- Accept comments in other formats, but have one person copy them into the log within a day.
- Close collection on the date. Late comments go to the next round unless the chair decides otherwise.
Sort the comments
- Number each comment and record who made it and the section it refers to.
- Mark the type: correction of fact, wording, preference, or a new request.
- Group comments that touch the same section so conflicts show up.
- Flag any comment that changes scope, cost or dates and send it to the decision owner using the decision request format.
Resolve conflicts without splitting the difference
When two members want opposite things, do not combine them into something neither asked for. Put the choice to the person who owns the section in the responsibility matrix, or to the chair, and record the decision and reason in the decision log.
Corrections of fact can be accepted by the secretariat. Preferences should be decided, not averaged.
Issue one consolidated version
- Update the document and keep a changes list: accepted, accepted in part, not accepted, referred.
- Give each non-accepted comment a one-line reason.
- Send the new version and the changes list to everyone, with a date after which the version is fixed.
- Tell members whose comments are referred when they will hear back.
Worked example · Fictional example
Consolidating committee comments on a draft forum programme
Fictional organisation and figures, to show the level of detail that is useful.
The fictional Persatuan Fiktif Kejuruteraan Alam Sekitar sent its draft programme to seven committee members on Monday with a Friday deadline. By Friday it had 31 comments by email and two phone calls.
The secretariat logged them, found 12 were corrections or wording changes, 14 were preferences and five were new requests. Three preferences conflicted on the lunch break length. The chair decided on 45 minutes and the reason was logged. Two new requests changed the session count and were referred to the committee as decisions D-14 and D-15. Version 2 went out on Monday with a one-page changes list.
Use this yourself
Committee comment log
Copy these columns into a spreadsheet. One row per comment.
| No. | From | Section or page | Comment | Type | Conflicts with | Outcome | Reason | Decided by |
|---|---|---|---|---|---|---|---|---|
| C-07 | Member name | Day 1, lunch | Make lunch 60 minutes | Preference | C-12 (30 minutes) | Not accepted | Chair decided 45 minutes | Chair |
| C-08 | Member name | Session 4 title | Correct speaker's job title | Fact | Accepted | Confirmed by speaker | Secretariat |
Handle it in-house, or bring in help?
Your team can usually handle this when
- Few reviewers and comments that rarely conflict.
- One person can log and consolidate within a day.
- Section owners are clear.
Outside planning help earns its fee when
- Many reviewers across organisations send comments in different formats and at different times.
- Comments repeatedly change scope, cost or dates.
- Disagreements stall and no one is clear who decides.
Want the feedback rounds managed?
A conference project lead can run the feedback round, log and group the comments, take conflicts and scope changes to the right decision owner, issue the consolidated version and keep the committee's decisions in the log. Your committee still decides each point. Send the document and the comments received so far.
Questions organisers ask
How many rounds of comments should we run?
One round for each major version is usually enough. Set the deadline and say that late comments go to the next round.
What if a senior member keeps adding comments after the deadline?
Ask the chair to agree the rule at the start. Log the comment and decide with the chair whether it is an urgent correction or can wait.
Should we show who said what?
Share the log with the committee if that is your norm. Otherwise show outcomes and reasons without names.
Can we use a shared document with tracked changes?
Yes, but still keep a changes list. Tracked edits show what changed, not why.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.