📝 Lesson 5.2: Comments, Track Changes & Real-Time Co-authoring
This is the lesson where a shared document becomes real teamwork. You'll learn the three tools every collaborator uses: Comments for conversation in the margins, Track Changes for edits you can see, review, and accept or reject, and live co-authoring so several people can write in the same document at once. Master these and "let's work on this together" stops being a headache and starts being a superpower.
📚 What You'll Learn
By the end of this lesson, you will be able to:
- Add, @mention, reply to, and resolve modern threaded Comments from the Review tab
- Turn on Track Changes and read insertions, deletions, and formatting as reviewable markup
- Switch Display for Review modes (Simple Markup, All Markup, No Markup, Original) and use the Reviewing Pane
- Accept and Reject changes one at a time or all at once, and Lock Tracking so no one sneaks edits in untracked
- Co-author live with presence indicators, and compare Word honestly with Google Docs' Suggesting mode
⏱️ Estimated Time: 45 minutes
🎯 Project: Turn on Track Changes, make a few edits, add a comment with an @mention, then walk through accepting and rejecting the tracked changes.
In This Lesson
Three Tools, One Shared Document
Collaboration in Word rests on three distinct tools, and beginners often blur them together. Keeping them straight is half the skill, so here's the clean mental model before we dig into each one:
| Tool | What it's for | Does it change the text? |
|---|---|---|
| Comments | Talking about the document — questions, suggestions, notes in the margin | No — comments live alongside the text and never alter it |
| Track Changes | Recording actual edits so they can be reviewed and approved | Yes — but every change is marked up until someone accepts or rejects it |
| Co-authoring | Several people editing the same live document at the same time | Yes — everyone's typing lands in the one shared file instantly |
The short version: comments discuss, track changes proposes, co-authoring does. They also combine beautifully — you can co-author live with Track Changes on, leaving comments as you go, so a whole team can draft, suggest, and discuss in one place without ever losing the thread. And all three, as you learned last lesson, work best when the document lives on OneDrive or SharePoint.
discuss the document"] --> D["☁️ One shared
cloud document"] B["✏️ Track Changes
propose edits as markup"] --> D C["👥 Co-authoring
edit live together"] --> D D --> E["✅ Review, accept or reject,
resolve, finalize"]
🧠 Mindset
Don't think of these as "advanced" features to fear. Think of them as manners for shared writing: you leave a comment instead of scrawling in the margin, you track your changes so the author can see what you touched, and you co-author instead of emailing versions. Used well, they make you the collaborator everyone wants on their document.
Comments — Threaded Conversation
A comment is a note attached to a specific spot in the document — a word, a sentence, or a selection — without changing the text itself. Modern Word comments are threaded: each one is a little conversation you can reply to, so a back-and-forth stays neatly grouped instead of scattered.
Adding and using comments
Select the text you want to comment on, then either click Review > New Comment, use the
Insert > Comment button, or press Ctrl+Alt+M (⌘+Option+A in Word for Mac). Type your note
and post it. From there you and your collaborators can:
- Reply — respond right inside the same thread, so the discussion stays with the text it's about.
- @mention someone — type @ and their name to tag them. In a Microsoft 365 work/school account this emails them a notification with a link straight to the comment — a genuinely useful "hey, can you look at this?" that they can't miss.
- Resolve — when a comment thread is handled, mark it Resolved. It dims and collapses out of the way but isn't deleted, so you keep the history. You can reopen a resolved thread anytime.
- Delete — remove a comment entirely when it's no longer needed.
The Comments pane (a Comments button in the top-right, and on the Review tab) shows every thread in one scrollable list, which is the fastest way to work through feedback on a long document. Comments travel with the file, so anyone who opens it later sees the full conversation.
💡 @mentions are the killer feature
The difference between a comment nobody reads and one that gets acted on is often an @mention. Tagging the right person turns a passive margin note into a direct, notified request — "@Sam can you confirm this figure?" On work/school accounts they get an email with a jump link. It's the closest Word comes to tapping someone on the shoulder, and it's how comments actually drive a document forward.
⚠️ Comments are not edits
A common beginner mix-up: writing your proposed change as a comment ("this should say quarterly, not monthly") when you could just make the change with Track Changes on. Comments are for discussion — questions, reasoning, "why did we do this?" If you want to actually change the words but let the author approve it, that's Track Changes, which we turn to next. Use the right tool and reviewers thank you.
Track Changes — Edits You Can See
Track Changes is the feature that made Word the standard for serious collaborative editing. When it's on, every edit you make is recorded as visible markup instead of silently altering the text. The author can then see exactly what you did and choose to keep it or throw it away. Nothing you change is permanent until someone accepts it.
Turning it on
Go to Review > Track Changes and toggle it on (the keyboard shortcut is
Ctrl+Shift+E; ⌘+Shift+E on a Mac). On the web, at the
time of writing, Track Changes is a dropdown instead of a simple toggle — choose For Everyone to track
everyone's edits, Just Mine to track only yours, or Off. The button highlights while tracking is active. From that moment,
everything you type, delete, or reformat is marked. Turn it back off the same way when you're done proposing
changes.
How different edits show up
Word shows each kind of change distinctly, and gives every reviewer their own color so you can tell who did what:
| Edit type | How it appears |
|---|---|
| Insertion | New text shown underlined and in the reviewer's color |
| Deletion | Removed text shown |
| Formatting change | Noted in a balloon or the Reviewing Pane — e.g. "Formatted: Bold" |
| A change bar | A vertical line in the margin flags any line that contains a tracked change |
Because insertions and deletions stay visible (not silently applied), the author keeps full control. A reviewer can rewrite an entire paragraph and the author still sees, word for word, what the original said and what's proposed — then accepts the good and rejects the rest. That's the whole point: edits become a proposal, not a fait accompli.
🌐 Web vs desktop note
Track Changes works in both Word for the web and the desktop app — you can turn it on, make tracked edits, comment, and accept/reject on the web just fine. The desktop app is a bit richer for heavy review work: it has the full Reviewing Pane, more granular Show Markup options (choose which reviewers or change types to display), and Lock Tracking with a password. At the time of writing, the web's Display for Review list may also be shorter (you may not see Original). If you do a lot of formal review, the desktop app is more comfortable, but the web covers the essentials.
Display for Review & the Reviewing Pane
A document full of tracked changes can get visually noisy, so Word lets you control how much markup you see without changing what's actually recorded. This is the Display for Review dropdown on the Review tab, and it's one of the most misunderstood controls in Word — so let's be precise.
| Display for Review mode | What you see |
|---|---|
| Simple Markup | A clean view with just a change bar in the margin — click the bar to reveal the detail. Great for reading. |
| All Markup | Everything shown — insertions, deletions, formatting, comments — in full color. The working view for reviewing. |
| No Markup | A preview of the document as if every change were accepted — clean, but changes are still there. |
| Original | The document as if every change were rejected — what it looked like before edits. |
⚠️ The trap everyone falls into: No Markup ≠ changes gone
This is the single most important thing to understand about Display for Review: "No Markup" only
hides the markup — it does not remove or accept the changes. The tracked edits are still in
the file. People send a document in "No Markup," think it's clean, and the recipient switches to "All Markup"
and sees every edit and comment. To actually finalize a document you must accept or
reject the changes (next section) — and it's smart to run the Document Inspector
(File > Info > Check for Issues on desktop) before sending anything final, to catch leftover
tracked changes and comments.
The Reviewing Pane
For a detailed, list-style view of every change and comment, open the Reviewing Pane from
Review > Reviewing Pane (you can dock it vertically or horizontally). It shows each change with
who made it and when, and gives you a running count — invaluable on a heavily edited document where markup in the
margins gets overwhelming. It's most fully featured in the desktop app.
changes still present"] B -->|"Original"| F["Preview as if rejected"] D --> G["Accept or Reject to finalize"]
Accept, Reject & Lock Tracking
Reviewing markup is only half the job — at some point someone decides what stays. That's Accept and Reject, both on the Review tab in the Changes group.
- Accept keeps a change and removes its markup, making the edit part of the final text.
- Reject discards a change and restores the original for that edit.
You can work through changes one at a time — click Accept and Move to Next (or the Reject equivalent) to step through the document decision by decision, which is the careful way. Or, when you've reviewed everything and you're confident, use Accept All Changes or Reject All Changes to finish in one click. A useful middle option, Accept All Changes and Stop Tracking, both finalizes and turns tracking off.
💡 Accept and Reject only touch changes, not comments
A neat detail: accepting or rejecting handles tracked edits, but comments are separate — you resolve or delete those on their own. So a fully finalized document means: all changes accepted or rejected, and all comments resolved or deleted. Check both before you call something done.
Lock Tracking — no sneaky untracked edits
Sometimes you need to guarantee that everyone's edits are tracked — say you're the author gathering
feedback and you don't want a reviewer to quietly turn tracking off and change text invisibly. That's
Lock Tracking (Review > Track Changes > Lock Tracking, a desktop-app
feature). You set a password, and now no one can turn Track Changes off without it. Every edit is forced
to be tracked. It's not high-security encryption — it's a courtesy lock that keeps an honest review honest.
🌐 Where these live
Accept and Reject (including accept/reject all) work in both web and desktop. Lock Tracking and the more advanced Show Markup filtering are desktop-only. If you only have the web version and need to lock tracking, that's one of the moments the desktop app earns its subscription.
Real-Time Co-authoring vs Google Docs
Co-authoring is the live version of collaboration: multiple people editing the same document at the same time. When your file is on OneDrive or SharePoint and others open it, you'll see presence indicators — colored flags and cursors showing where each person is working, and their avatars up in the corner. Type, and others see your changes appear within moments; AutoSave keeps the single cloud document in sync for everyone. No more "close the file so I can edit it."
Co-authoring works most seamlessly in Word for the web (it's built for it) and in the desktop app with AutoSave on for a cloud file. You can co-author with Track Changes on and leave comments as you go, so a team can draft, propose, and discuss all at once.
The honest Google Docs comparison
Google Docs was cloud-native from birth, and its live collaboration has long been the benchmark — it simply felt more instant and frictionless for years. Word has matured a great deal and modern co-authoring is genuinely good, but here's the fair, honest picture, especially around the "suggest an edit" idea:
| Collaboration concept | Microsoft Word | Google Docs |
|---|---|---|
| Live co-editing | Strong; best on web and on desktop with AutoSave — matured over time | Best in class — instant, cloud-native from day one |
| Suggesting edits | Track Changes — record edits as reviewable markup, then accept/reject | Suggesting mode — same idea, edits appear as suggestions to approve |
| Comments | Threaded, @mentions, resolve/reply | Threaded, @mentions, resolve/reply |
| Presence | Colored cursors and avatars showing who's where | Colored cursors and avatars showing who's where |
| Depth behind it | Full Word layout, references, and review power | Lighter, but wonderfully simple |
The key honest mapping: Word's Track Changes and Google Docs' Suggesting mode are the same concept — "propose an edit the owner can approve." Google's Suggesting is arguably a touch simpler to toggle per-edit; Word's Track Changes is more powerful for formal, heavily-reviewed documents (change types, reviewer filtering, lock tracking, the Reviewing Pane). If your collaboration is quick and casual, Docs is delightfully frictionless; if it's formal, multi-reviewer, or long-form, Word's review machinery is hard to beat. And the concepts transfer both ways — learn one and you understand the other.
🎯 Project: Track, Comment, Resolve
Now you'll run the full review cycle on your report: turn on Track Changes, make some real edits, add a comment with an @mention, then step through accepting and rejecting so you feel how a reviewer's proposal becomes final text. This is the exact loop that happens on every collaborative document at work and school.
🏋️ Run a full Track Changes review
Objective: Practice proposing edits as markup, discussing with a comment, and finalizing with Accept and Reject.
Instructions (about 12 minutes):
- (1 min) Open your report (on OneDrive from last lesson). Go to
Review > Track Changesand turn it on (or press Ctrl+Shift+E / ⌘+Shift+E). On the web, choose For Everyone from the Track Changes dropdown. - (3 min) Make three edits: insert a new sentence, delete a phrase, and reformat something (bold a word, say). Watch each one appear as colored markup.
- (2 min) Select a sentence and add a comment (Ctrl+Alt+M; ⌘+Option+A in Word for Mac). Include an @mention if you have a collaborator's name available — e.g. "@Alex does this figure look right?"
- (2 min) Try each Display for Review mode — Simple Markup, All Markup, No Markup, Original (the web may not list Original) — and notice that "No Markup" only hides the edits.
- (3 min) Go to the Changes group. Accept one change, Reject another, then resolve your comment. Notice the accepted edit becomes normal text and the rejected one reverts.
- (1 min) Turn Track Changes off and confirm your document reflects only the changes you accepted.
💡 Hint — the review workflow at a glance
THE TRACK CHANGES LOOP
1. Review > Track Changes = ON (Ctrl+Shift+E)
2. Edit normally -> everything shows as MARKUP
insert = underlined, colored
delete = struck through
format = noted in balloon / pane
3. Comment (Ctrl+Alt+M) + @mention to ask a question
4. Reviewer sends it back
5. Author reviews:
Display for Review = All Markup (see everything)
Accept -> keep the edit
Reject -> restore the original
(comments: Resolve or Delete separately)
6. Accept All + Stop Tracking -> finalize
7. Check for Issues -> no leftover changes/comments
Remember: "No Markup" HIDES, it does NOT finalize.
Working solo? You can play both roles — make the edits as "the reviewer," then switch hats and accept or reject them as "the author." The muscle memory is identical.
✅ Project Completion Checklist
- You turned Track Changes on and saw the button highlight
- You made an insertion, a deletion, and a formatting change, each shown as markup
- You added a comment (bonus: with an @mention)
- You tried all four Display for Review modes and understood "No Markup" only hides
- You accepted at least one change, rejected at least one, and resolved your comment
🎯 Quick Quiz
Question 1: You set Display for Review to "No Markup," the document looks clean, and you send it off as final. What's the risk?
Question 2: Which pairing correctly matches Word's feature to the equivalent idea in Google Docs?
Best Practices for Reviewing
✅ Do's
- Turn Track Changes on before editing someone else's document. It's the courteous default — the author sees exactly what you touched.
- @mention the person who needs to act. A tagged comment gets a reply; an untagged one gets ignored.
- Resolve threads and accept/reject changes to truly finalize. Then run Check for Issues to catch leftovers.
- Use the Reviewing Pane on heavily edited documents. The list view beats hunting through margins.
❌ Don'ts
- Don't confuse "No Markup" with finalizing. It only hides — the changes are still there.
- Don't write proposed edits as comments. If you mean to change the text, make the edit with Track Changes on.
- Don't accept-all blindly on someone else's document. Step through changes you don't understand.
- Don't send a "final" file without inspecting it. Leftover tracked changes and comments have embarrassed many people.
💡 Pro Tips
- Each reviewer gets their own color automatically — perfect for seeing at a glance who suggested what.
- On a big review, work in "All Markup" while editing and switch to "Simple Markup" to read for flow.
📓 Learning Journal
Keep a learning journal as you work through this course — a separate document, a note, or even a second Word file right beside the one you're building. After each lesson, take a few minutes to write down:
- Key concepts you learned
- Techniques that clicked for you
- Questions or confusion points to revisit
- Ideas you want to try in your own documents
- Your progress and feelings about learning this — including where your confidence grew
✍️ This lesson's prompt: Which of the three tools — comments, track changes, or live co-authoring — do you see yourself using most, and why? Have you ever received a "final" document that still had tracked changes or comments hidden in it? How will knowing the difference between "No Markup" and actually accepting changes change the way you finish a document before sending it?
📝 Lesson Summary
🎓 Key Takeaways
- Collaboration uses three tools: Comments discuss, Track Changes proposes, co-authoring does — and they combine in one shared cloud document.
- Comments are threaded — reply, @mention to notify someone, and resolve when handled (they're not deleted, just dimmed).
- Track Changes (
Review > Track Changes, Ctrl+Shift+E) records insertions, deletions, and formatting as reviewable, per-reviewer-colored markup. - Display for Review (Simple Markup / All Markup / No Markup / Original) changes what you see — "No Markup" only hides; it does not finalize.
- Accept and Reject (one at a time or all) finalize the edits; Lock Tracking (desktop-only) forces everyone's edits to be tracked; the Reviewing Pane lists every change.
- Co-authoring shows live presence; Word's Track Changes maps to Google Docs' Suggesting mode, and the concepts transfer both ways.
🎉 What You've Accomplished
You can now collaborate in Word like a pro: leave threaded comments that actually get answered, propose edits that the author can see and approve, control how much markup clutters your view, and finalize a document cleanly. You also understand the honest lay of the land versus Google Docs — same concepts, different strengths. These are the skills that make you trusted on any shared document.
❓ Common Questions at This Stage
Can I use Track Changes and comments in free Word for the web?
Yes. You can turn on Track Changes, make tracked edits, add threaded comments with @mentions, and accept or reject changes all in the free web version. The desktop app adds the fuller Reviewing Pane, more granular Show Markup filtering, and Lock Tracking with a password — nice for heavy formal review, but not required for everyday collaboration.
I sent a document but the recipient saw all my edits and comments — what happened?
Almost certainly you were viewing in "No Markup," which only hides the markup on
your screen — the tracked changes and comments were still in the file. To truly finalize, accept or
reject every change and resolve or delete every comment, then run File > Info
> Check for Issues (desktop) to confirm nothing's left behind before you send.
How is this different from Google Docs?
The concepts are the same. Google Docs' Suggesting mode is Word's Track Changes; comments and @mentions work alike; both show live presence. Google's live editing has long felt a touch more instant (it was cloud-native from day one), while Word's review tools are more powerful for formal, multi-reviewer, long-form documents. Learn one and you understand the other.
🔭 Looking Ahead
In the next lesson — Lesson 5.3: Version History & Comparing Documents — we round out the collaboration module. You'll see how cloud saving gives you a full version history you can view and restore, how AutoSave fits in, and how the desktop Compare and Combine tools merge different drafts and reviewers into one marked-up document.
✅ Before the Next Lesson
- Confirm you can turn Track Changes on and off and accept/reject a change
- Add and resolve at least one comment, ideally with an @mention
- Write your Learning Journal entry for this lesson
📚 Additional Resources
- Microsoft Word Help & Learning (Microsoft Support)
- microsoft365.com — open Word for the web
- Microsoft Word — product overview
🌟 Encouragement for the Journey
Comments, track changes, co-authoring — the exact tools that turn "who has the latest version?" into calm, orderly teamwork. You just learned the skills that make you the collaborator everyone wants on their document. One more lesson and this module is yours: version history, so you can rewind time itself. 📝