A draft has margin notes saying “unclear,” “please check,” and three conflicting suggestions for the same heading. Everyone has contributed feedback, yet nobody knows what should happen next. A useful comment round needs a clearly bounded question, an anchor in the text, and a decision that can be followed. Keep the discussion about a change distinguishable from the change itself.
Give each thread one question
Anchor the comment to the passage it concerns. A note attached to the beginning of the document is difficult to interpret if it really concerns a sentence on page four. State the issue and the clarification needed: “Is this the registration deadline or the payment deadline?” is more actionable than “Date?”
When suggesting wording, explain the reason if it matters. That allows the owner to find a suitable alternative instead of merely accepting or rejecting your sentence. Tracked changes may be better for an actual text correction; comments work particularly well for questions, explanations, and decisions that are still open.
Separate questions that can be resolved independently. A long note about price, image choice, and timing makes individual items difficult to close. Conversely, reply within the existing thread when discussing the same question so that several parallel conversations do not develop.
Make ownership and status understandable
For a small group, agree who will consolidate the feedback. Mentions or assignments in the application can help, but they do not replace that agreement. Check that the person has document access and knows to expect notifications.
When closing a comment, record the outcome if the edit is not obvious. For example: “Changed the deadline to June 12; confirmation is in the project folder.” This connects the discussion to the resulting text more clearly than a bare “done.”
In many applications, resolving a thread removes it from the active view without necessarily deleting it from the file. Agree whether comments should remain as a working record or be removed before external distribution. Check the actual behavior in the application being used.
Close the review round deliberately
Before release, review the remaining threads and decide explicitly which suggestions to accept, decline, or postpone. A postponed question needs a visible status and, where relevant, a later decision date. Deleting its comment should not make it appear resolved.
Then read the continuous text. Sensible responses to individual comments do not guarantee a coherent paragraph; two separate edits may contradict each other. For an external copy, also check whether internal names, discussions, or discarded wording remain visible or retrievable. Keep any required working record separate from the approved version.