# Turn Word comments into changes your team can verify

> **The short answer**: Use Word comments to assign review responsibilities, anchor each comment to the relevant passage and state both the problem and the requested outcome. Modern Word comments must be posted before collaborators receive them. Use comments for discussion and tracked changes for direct text suggestions, then inspect the revision before resolving the thread.[^1][^2]

**Key takeaways**

- Give each comment one clear issue.
- Post the comment rather than leaving it in the composer.[^1]
- Separate a proposed edit from approval of that edit.[^2]
- Check the revised passage before resolving the discussion.

![Diagram: Issue, Owner, Decision](https://tiswa.app/assets/blog/word-team-review-comments/cover-en.webp)

The report comes back with twenty margin notes: unclear, rewrite, check source. The author knows something is wrong but cannot tell whether to define a term, remove a claim or add evidence. A second conversation begins outside the document and decisions get lost. Word comments become useful when another person can act on the request and recognise when it has been satisfied.

> **tiswa's take**: Do not assign review solely by page count. Give people responsibilities such as evidence, consistency or results, then have one editor reconcile conflicts. Four reviewers reading the same pages without defined roles often repeat the same suggestions while leaving unowned problems untouched.

## What are you checking in this review round?

One possible sequence is argument and data first, coherence and wording second, formatting and export last. Adjust it to the deadline. The reason is practical: there is little value in fixing line spacing in a chapter the team may remove. Agree when substantial revisions stop and who resolves conflicting suggestions against the assignment instructions. That person coordinates decisions; they do not automatically overrule the subject specialist.

| Responsibility | Reviewer question | Useful output |
|---|---|---|
| Evidence | Does the source support this claim? | A comment identifying the claim and missing support |
| Reasoning | Does the result answer the research question? | A request to explain the connection or limit |
| Language | Is the sentence precise and readable? | A wording proposal that preserves the meaning |
| Submission | Does the package meet the instructions? | A check of names, appendices and export |

If the team circulates local attachments, label them and name the person who merges feedback. A shared document reduces attachment traffic but does not remove the need for someone to approve changes. Before the round starts, confirm that everyone has the same working file and an appropriate role. Discovering at midnight that two reviewers commented on separate drafts makes even excellent feedback harder to use.

## How do you write an actionable comment?

1. **Anchor the passage**: Select the relevant text or insertion point and add a comment through the Review controls.[^1]
2. **Describe the problem**: Explain what prevents understanding or verification. “Unclear” alone does not identify the issue.
3. **Request an outcome**: For example: define a completed response and state whether partial responses were excluded.
4. **Post and check the revision**: Post the comment, then return to the actual passage after revision. Modern comments include a separate posting action.[^1]

![Workflow: Agree review roles, Comment on a passage, Check tracked edits, Close with a decision](https://tiswa.app/assets/blog/word-team-review-comments/workflow-en.webp)
A reply does not prove that the text is now correct.

Consider an illustrative survey report stating that most participants prefer remote learning. That sentence leaves the denominator and question unclear. An actionable comment asks the author to add the number agreeing out of valid responses, link it to question five and avoid generalising to every university student. The author can now collect the missing evidence and respect the intended limit without guessing what the reviewer meant.

For a software report, replace “explain the test” with a request for the input, expected result and observed result. A screenshot alone may not explain why the team judged the case successful. Do not invent the outcome for the author. Ask for missing evidence and keep the conclusion tied to what the team actually executed. A precise request is often shorter than the back-and-forth caused by a vague one.

## When should you use comments or tracked changes?

Microsoft distinguishes comments attached to a document location from tracked changes that propose direct edits to the text.[^2] Use a comment when you need an explanation or decision. Suggest a text change when the alternative wording is clear and the author can accept or reject it. Avoid turning every comma into a discussion, but do not silently change a scientific conclusion under the label of proofreading.

Before accepting a large set of edits, inspect numbers, technical terms and conclusions. A small wording change can turn “associated with” into “caused by.” The person responsible for the analysis should therefore review scientific edits even when someone else improves the prose. Clearing coloured markup is not the objective. Preserving the correct meaning in a readable final document is.

## How do you show Word review comments?

In modern comments, use Review > Show Comments and choose List view to see active and resolved threads together. If a new comment is missing, check that its author posted it and that you are both opening the same file.[^1]

## Resolve after checking

A useful response describes the change: the sample definition was added at the start of the section and linked to the table. The reviewer opens that location, checks it and resolves the thread. If the team declines a request, record the reason and agreed decision. Resolution means that the issue has been decided, not that one contributor won an argument.

![Checklist: Comments answered, Changes reviewed, No unresolved task, Export inspected](https://tiswa.app/assets/blog/word-team-review-comments/checklist-en.webp)
Close the discussion when the underlying issue is settled.

If a later edit reintroduces the problem, reopen the discussion where the available controls allow it. Microsoft describes interacting with resolved comments through list view.[^1] The existing thread preserves the decision’s context. Conversely, avoid putting five unrelated problems into one comment: the author may fix two, reply “done” and accidentally leave the rest behind. Separate requests make completion easier to assess.

## Check accessibility and the submitted copy

Do not use comment colour alone to indicate ownership or urgency. Write the meaning explicitly and use direct requests. Microsoft provides instructions for adding, reading and deleting comments with a screen reader.[^3] If a teammate depends on keyboard navigation or a screen reader, try the review workflow with them instead of assuming the visible margin works equally well for everyone. A review process should let each contributor participate.

Before submission, check whether the course requires a clean document or a marked-up review copy. Open the actual Word file or PDF you intend to upload and inspect comments and revision marks there. Hiding them in the editing view is not proof that the export is clean. Continue with [Word research formatting](https://tiswa.app/en/blog/word-research-formatting/), [report table layout](https://tiswa.app/en/blog/word-report-table-layout/) and [capstone version control](https://tiswa.app/en/blog/capstone-drive-version-control/) for the final preparation.

The University of Wisconsin-Madison Writing Center recommends reading the whole draft before commenting, addressing major issues before smaller ones and explaining suggestions.[^4] Read the report once before reviewing your assigned section so you do not request a definition that already appears elsewhere.

Check what your university account already provides before paying for extra review tools, then browse [student deals](https://tiswa.app/en/deals/) if needed. [Browse student deals](https://tiswa.app/en/join/)

## Questions

### What makes a comment useful?

Identify the passage, the problem and the requested outcome, such as defining a term or supporting a claim.

### Why are Word review comments not showing?

Check that the comment was posted and that you opened the correct file. In modern Word comments, List view includes resolved threads that Contextual view hides. Use Review > Show Comments to inspect the available views.[^1]

### When should I use tracked changes?

Use them for direct proposed edits, and comments for discussion or requests for missing information.[^2]

### Does resolving a Word comment delete it or hide it?

Resolving does not delete the thread. List view still shows resolved comments, which can be reopened. Inspect the revision before resolving it.[^1]

### Should I delete Word review comments before submission?

Follow the course instructions for clean or marked-up copies and inspect the exported file before upload.


## Sources

[^1]: Microsoft: modern comments in Word, https://support.microsoft.com/en-au/word/using-modern-comments-in-word
[^2]: Microsoft: give and receive feedback, https://support.microsoft.com/en-us/word/give-and-receive-feedback-in-word
[^3]: Microsoft: accessible comments in Word, https://support.microsoft.com/en-us/accessibility/word/use-a-screen-reader-to-add-read-and-delete-comments-in-word
[^4]: University of Wisconsin-Madison Writing Center: peer reviews, https://writing.wisc.edu/handbook/processandstructure/peerreview/