How do I collect comments on a draft presentation without losing track of revisions?
Quick answer
Choose one feedback log and record each suggestion with its slide, reviewer, follow-up owner, decision, and status. Update the log when you revise the deck, and keep pending questions visible until they’re decided. In Google Slides, collaborators with comment or edit permission can reply to and resolve comment discussions; with a work or school account, comments can also assign action items. Track acceptance separately: resolving a discussion doesn’t show that a suggestion was accepted. [S1]
The question, the details, the next step.
I’m collecting comments on a draft presentation from several people. How do I stop feedback and revisions from becoming a jumble?
Use one feedback log as your decision record, and treat comments in the presentation as pointers to the relevant slide or discussion. For each suggestion, capture the slide number or title, the request in a few words, the reviewer, who will follow up, the decision, and the work status. This helps distinguish “we changed this” from “we still need to decide.”
Agree on a comment cutoff and choose one person to maintain the log. Add feedback before editing. After making a change, note what changed and where it appears in the new draft. If you decide not to make a suggested change, record that decision and a brief reason so it doesn’t look like an unfinished task. This simple process works independently of which presentation app you use.
What should go in the log, and how do I distinguish accepted changes from open suggestions?
Use separate fields for the decision and the work status. For example:
| ID | Slide | Suggestion | Reviewer | Owner | Decision | Status | Revision note |
|---|---|---|---|---|---|---|---|
| 01 | 4, “Approach” | Explain timeline | [Reviewer] | [Owner] | Accept | Applied | Added dates in v2 |
| 02 | 7, “Costs” | Add another scenario? | [Reviewer] | [Owner] | Pending | Open | Confirm scope |
Keep the choices simple: Accept, Decline, or Pending for the decision; Open, In progress, or Done for the work. A declined suggestion can be Done once the decision and reason are recorded—it is not an accepted revision. If you partly address a suggestion, note what remains instead of marking the whole item complete. The names of the fields matter less than using them consistently.
We’re using Google Slides. Can its comments and action items handle the whole process?
They can support discussion and follow-up, but keep a decision log as well. In Google Slides on a computer, collaborators with comment or edit permission can reply to comment discussions and resolve them; resolved discussions can be reopened. With a work or school account, a comment can assign an action item to a named person, who receives an email and can mark it done. The file’s follow-up count can show open action items and suggestions. [S1]
Those features don’t establish whether a presentation suggestion was accepted. Record an accept, decline, or pending decision in the comment thread or your separate log, and note the resulting slide change there too. Use the action item for assigned follow-up when it fits your setup; don’t treat resolving a discussion or marking an action item done as proof that the suggested edit was made.
What’s a reliable routine for moving from comments to the next draft?
Use the same sequence for each review round:
- Collect: Ask reviewers to identify a slide and state a requested change or question. Log each distinct suggestion. Combine duplicates only when they really ask for the same thing, and note the reviewers.
- Assign: Give each open item one follow-up owner. If a decision needs input, record who or what is needed to reach it.
- Decide: Mark the item Accept, Decline, or Pending. Add a short reason for a decline, or state what remains unresolved for a pending item.
- Revise: Make accepted edits and add a revision note, such as “shortened slide 4 timeline; draft v2.” Keep unresolved items visible rather than silently dropping them.
- Reconcile: Before sharing the next draft, compare each log item with the slide. Mark it Done only when the decision and required follow-up are recorded. Carry pending items into the next review round.
For the example above, item 01 can be marked Done once the timeline change is in v2. Item 02 stays Pending until someone confirms whether the extra scenario is in scope. That leaves a clear path from comment to decision to revision without treating every comment as an instruction to change the deck.
A practical checklist
Choose one feedback log and one person to maintain it.
Record each suggestion with its slide, reviewer, follow-up owner, decision, and status.
Keep decision labels separate from work-status labels.
Add a revision note when an accepted change appears in a new draft.
Review pending items before sharing the next version, and carry unresolved questions forward.
A few more useful answers
Should I resolve a comment as soon as I make the edit?
Resolve or close the discussion when its conversation is finished, but separately record whether the suggestion was accepted and where the change appears. A resolved Google Slides discussion does not itself indicate acceptance. [S1]
What if two reviewers suggest the same change?
Use one log item if the requests genuinely match and note both reviewers. Keep separate items if the suggestions differ in scope or need different decisions.
What should I do with feedback I can’t decide on yet?
Mark it Pending, identify the person or information needed to decide, and keep it visible for the next review. Don’t mark it Done just because the discussion has paused.
Sources
References used for this guide.
- [S1] Use comments, action items, and emoji reactions — Google Docs Editors Help support.google.com · Checked