In this lesson
Review two edits and a comment separately, then check the delivery copy for revisions hidden by No Markup.
Example
Two reviewers on a client onboarding guide
An onboarding guide needs a clearer equipment checklist. One reviewer proposes a new start date; another asks whether the client can use their own laptop. Simulate both in a copy. Reject the date change, then answer the laptop question and edit that requirement.
How it works
Track Changes records new edits while it is on. Turning it off does not remove earlier revisions. No Markup hides them from view; you still need to accept or reject each change.
Comments discuss a question; tracked changes edit the text. Resolving a comment marks the discussion handled, but you can still delete it from a delivery copy. Cloud version history requires suitable storage, an account and access.
Steps
Save Onboarding-Review.docx. Type “Start date: 14 October” and a three-item equipment checklist. Turn on Review › Track Changes and change the date to 21 October.
Select the laptop item and add the comment “Can the client use their own laptop?” Reply with the agreed answer. Keep the question in the comment until you decide how to change the guide.
Choose All Markup. Use Next and Previous in Changes to inspect the date edit, then reject it. The guide should say 14 October again.
Make a second tracked edit clarifying the laptop requirement and accept that change. Read the date and equipment sentence together to check both decisions.
Resolve the answered comment. Open the review pane to look for anything still outstanding. Switch to No Markup and back to All Markup to see how revisions can be hidden.
If the file is in shared OneDrive or SharePoint storage, check Share permissions and open Version History. View an older version before choosing to restore it. For a local file, keep named copies.
Keep a review copy, then make a delivery copy. Accept or reject any remaining revisions and delete comments that should not be shared. Turn Track Changes off and reopen in All Markup to check the result.
If you have a separately edited local copy, use Review › Compare to see its differences. Read the changes before incorporating them; Compare does not choose the better wording.
Try it yourself
- Create two tracked edits and a comment. Accept the wording improvement, reject the date change and answer the comment. Keep a review copy and save a separate copy with all revisions handled and comments removed.
Show expected result
- The final text says 14 October and includes the accepted laptop wording. Keep the review copy separate from the delivery file.
- The delivery copy has no remaining tracked changes or comments when reopened in All Markup.
If something goes wrong
- A recipient sees revisions that looked hidden on your screen.
- Switch from No Markup to All Markup. In the delivery copy, accept or reject the remaining edits, save and reopen to check them.
- A local DOCX has no Version History.
- Save separately named copies. Cloud history depends on OneDrive or SharePoint storage and account settings; a local DOCX does not automatically have it.
Quick check
Try these questions after the exercise. Check the result in your app before marking the lesson complete.
Choose an answer for all 3 questions to check your understanding.
Optional: try it with Copilot
If you have Copilot, try this after the exercise. Keep the original file and compare its suggestions with your own result.
List unclear sentences and unanswered reviewer questions in this guide. Keep the approved start date, separate wording suggestions from open questions and leave revision decisions to me.
More from Microsoft
These Microsoft guides cover the tools used in this lesson.
Loading your progress…