To use Track Changes in Microsoft Word, open the Review tab, switch Track Changes on, and edit the document normally. Word marks suggested insertions, deletions, and some formatting changes so a reviewer can accept or reject them before the final copy is shared.
The safest workplace process is to keep one review copy, distinguish comments from proposed wording changes, and finish with a deliberate markup check. Here is a practical method for reports, policies, proposals, and other documents that pass through several hands.
What does Track Changes actually do?
Track Changes records proposed edits in a Word document instead of silently replacing the original wording. When someone deletes a sentence, the deletion remains available for review; when someone adds a phrase, the insertion can be inspected before it becomes final. This is especially useful when two people disagree about wording or a manager must approve a client-facing statement.
A comment serves a different purpose: it asks a question or explains a concern without necessarily proposing a specific replacement. Use a tracked edit for an exact wording change, such as replacing a deadline; use a comment for a decision, such as asking whether the deadline has been approved. Microsoft’s Track Changes guidance describes the markup views and reviewer controls.
Tracking is not a substitute for document ownership, version history, or permission management. Someone still needs to decide which suggestions to accept and which version is ready to send.
How do you turn on Track Changes in Word?
- Open the working Word document and save a clearly named review copy before changing anything important.
- In Word for Windows or Mac, open Review and select Track Changes. Depending on the version, you may choose to track everyone’s changes or just your own.
- Make a small, reversible edit to a sentence. Switch to All Markup so the proposed change is visible.
- Ask your reviewer to edit that same shared document or the agreed review copy rather than creating several independently edited attachments.
- When reviewing is complete, turn tracking off for future edits only after you have resolved the existing suggestions.
In Word for the web, select Reviewing mode to make tracked suggestions. Editing mode does not automatically show every edit as a tracked suggestion. Microsoft’s Word for the web explanation notes that its reviewing features are more limited than the desktop application.
Worked example: revise a client report deadline
Imagine a coordinator drafts a client update. The original sentence says, “We will send the final report on Friday.” After a planning call, a colleague believes Thursday noon is the agreed deadline, but the project owner has not confirmed it. Simply overwriting Friday would hide the unresolved decision.
With Track Changes enabled, the colleague replaces “Friday” with “Thursday at noon.” Word displays the proposed deletion and insertion in the review view. The colleague also adds a comment: “Can the project owner confirm the earlier deadline before we send this?” The owner can accept the wording if the schedule is confirmed or reject it if Friday remains correct.
Use this short decision record alongside the review: Document: Client status update; Proposed change: Friday to Thursday noon; Reason: meeting discussion; Decision owner: project lead; Status: awaiting confirmation; Final action: accept or reject after confirmation. This is a practical example, not a Word-generated audit log.
For decisions that affect multiple files, keep the rationale outside the document as well. A simple work decision log gives the team a durable place to record who approved the change and when.
How can you review every change without missing one?
Start with All Markup, not No Markup. Simple Markup reduces visual clutter; All Markup exposes more of the actual insertions, deletions, and formatting suggestions. You can use Show Markup to choose which types of changes or which reviewers appear, but a filtered display is not proof that other suggestions are gone.
Move through the document with the Previous and Next controls on the Review tab. For each change, read the surrounding paragraph, not just the highlighted words. A harmless-looking deletion can remove an exception, date, approval condition, or limitation that changes the meaning of the whole sentence.
Check comments separately. A resolved discussion does not automatically mean its related wording was accepted, and an accepted wording change does not answer every open question. Before approval, switch the reviewer filter back to everyone and make sure all relevant markup categories are visible.
If a document has multiple reviewers, decide in advance who owns the final decision. Without a named approver, reviewers may accept one another’s suggestions inconsistently or assume someone else has checked the final wording.
How do you accept or reject changes safely?
- Save a review copy or confirm that your team’s version history can restore the earlier draft.
- Open Review, show All Markup, and start at the beginning of the document.
- Select each suggestion and choose Accept if the replacement is correct, or Reject to keep the prior wording.
- Repeat through the document, checking headings, tables, footnotes, dates, names, and figures that may have been revised.
- Only use Accept All Changes when every suggestion has already been approved; otherwise, work through them individually.
Important: selecting No Markup only hides suggestions from the current view. It does not remove them from the file. Microsoft’s accept-or-reject instructions explicitly distinguish hiding markup from resolving revisions. Turning tracking off also does not clear previously tracked changes.
A copy-ready review handoff for a small team
Paste this brief into your team’s handoff note or email before sending a draft for review. It prevents the vague request “please check this” from becoming an open-ended rewrite.
File: Proposal_2026-10-24_review.docx
Review purpose: verify scope, dates, and client-facing claims
Reviewers: operations lead for facts; account lead for tone
Change method: Track Changes on; comments for unresolved questions
Deadline: Monday 12:00 HKT
Final approver: project owner
Output: one approved clean copy plus the retained review version
Choose one owner for the final document and a shared folder location that the team already uses. If files must be exchanged rather than coedited, use a consistent filename and make the handoff order explicit. Our shared-folder naming guide covers a lightweight naming system that reduces “final-v2-really-final” confusion.
Common Track Changes mistakes and their fixes
- “The edits disappeared.” Check whether the view is set to No Markup or whether the display is filtered to one reviewer. Restore All Markup and show all reviewers before concluding the changes were removed.
- “My new edits are not tracked.” Confirm that Track Changes is enabled or that Word for the web is in Reviewing mode. Merely opening a file that contains old revisions does not guarantee future edits are tracked.
- “The client saw internal comments.” Never assume a visually clean page is a clean file. Resolve revisions and comments, then inspect the copy you intend to share.
- “Two reviewers made conflicting edits.” Ask the designated approver to choose the authoritative wording and record the decision. Avoid combining separate versions by manually copying paragraphs without checking the differences.
- “Accept All removed something important.” Restore the saved review version or use available version history, then resolve the disputed changes one by one. Do not rely on Undo after closing and reopening the file.
What should you check before sharing the final document?
First, save a separate clean deliverable while retaining the review copy for internal reference. Confirm the final file opens with the intended wording and no outstanding suggestions. Review comments, hyperlinks, tables, page breaks, and headers. If the document contains confidential notes or reviewer names, consider whether those details belong in the recipient’s copy.
In supported desktop Word for Windows versions, use File > Info > Check for Issues > Inspect Document on a copy to look for hidden information and metadata. The Microsoft Document Inspector guide explains the feature and its platform differences; do not assume the same inspection controls are available on Mac or in the browser.
When the approval has consequences beyond one document, add the final wording and decision owner to the team’s change log. If the document is being transferred to another colleague, use a clear handoff note to state what is approved, what remains open, and where the final file lives.
Final checklist: one review version, one approved version
Track Changes works best when the team agrees on three things: who may suggest edits, who decides whether to accept them, and which copy is approved for distribution. Before sending, verify that tracking was used during review, all meaningful suggestions were considered, outstanding comments were handled, and the clean copy was checked independently.
For the next report or proposal, start with a single review document and the short handoff template above. You will have a clearer trail of proposed wording, fewer competing attachments, and a final file that reflects an explicit decision rather than an accidental overwrite.