
Shared Documents
Part of Collaborative document editing
Tracking document changes across several contributors
Track proposals, comments, direct edits and approval separately so a multi-author document remains understandable.
undefined
When several people edit one document, separate proposed wording, edits already in the working text, reasons in comments and approval. Use one working copy and a clear review point, and ask contributors to use recognisable accounts. The owner records decisions; a history entry is not approval.
Mark the start of review
Identify the document and the version under review. Ask contributors to use recognisable accounts and explain substantial rewrites in a comment when the reason is unclear. Assign responsibility for sections or questions where several people may edit the same passage.
A named version or short handover note can mark a meaningful stage. Use it to identify the review baseline, not as a label for every small edit.
Inspect the right record
| Question | Useful record | Limit |
|---|---|---|
| What wording is proposed? | Suggestions or tracked changes | A proposal may still be rejected. |
| Why was it proposed? | The related comment and response | The final text may not reflect the discussion. |
| What did the document say earlier? | Version history | It may group edits or retain fewer versions than expected. |
| Who approved the release? | The team's approval record | Later edits may change the working copy. |
When a change is disputed, inspect the proposal and its explanation before looking at the resulting version. Ask the owner to record the decision rather than expecting the software to infer it.
Key Facts About Document Review in Shared Environments
- Proposed Wording Source
- Tracked changes or suggestions
- Reason for Change
- Comment or response to suggestion
- Previous Version History
- Available but may group edits or retain fewer versions
- Approval Record
- Team’s approval record — not automatically updated
- Final Text Authority
- Owned by document owner — not inferred by software
Check contributor attribution
In Microsoft Word, on the Review tab select Tracking > Track Changes. The section is highlighted while tracking is on; additions are underlined, deletions are struck through and different authors’ changes use different colours.
To track everyone's changes, choose Review > Tracking > Track Changes > For Everyone; to track only your own, choose Review > Tracking > Track Changes > Just Mine. Check this setting before review so the edits being marked match the task.
Choose All Markup from the Markup drop-down to display different colours of text and lines for each reviewer. In Editing or Reviewing mode, select a tracked change to see a collaborator's full suggested change in a card.
When Track Changes is off, Word stops marking changes, although coloured underlines and strikethroughs remain in the document. Treat edits made while tracking was off as an attribution gap: ask the contributors or owner to clarify them and record the decision.
If a document has been shared for review, you may not be able to turn off Track Changes. To edit without tracking, save a copy or ask the person who shared it to share it again with review mode turned off.
Comments are separate from tracked changes, so review both. A comment can explain a proposed change, but the owner still needs to record whether it was accepted.
In Google Docs, Suggest edits lets contributors propose wording. Treat each suggestion as a proposal, not proof of approval; ask contributors to use recognisable accounts and explain unclear changes in a comment.
Neither product decides whose wording is authoritative. The owner must settle conflicting proposals and confirm the released text.
Microsoft Word vs Google Docs: Tracking Changes and Comments
- Tracking Changes FeatureTrack Changes (Word), Suggest edits (Docs)
- Author AttributionDifferent colours per contributor in Word; names shown in Docs
- Editing Without TrackingSave a copy or request re-sharing in non-review mode (Word); use 'suggest' mode only (Docs)
- Comment IntegrationSeparate from tracked changes in both platforms
- Decision RecordingOwner must record decisions manually in both systems
Resolve changes in context
Suppose one contributor updates a technical requirement while another simplifies the same section for customers. Read both proposals, confirm the intended meaning with the relevant people and write one coherent passage. Then check headings, examples and later references for consequences.
Accepting each change separately can leave contradictions. At the end of review, record the approved version and clear open suggestions and comments, or assign an owner to each item left open.
Ask a colleague who did not edit the document to find the released wording. If they cannot distinguish it from the working draft, make the release rule clearer.
How to Review Document Changes Across Multiple Contributors
- Identify the review baselineUse a named version or handover note to mark the start of review
- Inspect proposals and commentsCheck tracked changes and related comments before reviewing final text
- Confirm intended meaningDiscuss conflicting proposals with relevant stakeholders
- Merge changes coherentlyWrite one clear passage that reflects agreed content
- Check downstream impactsReview headings, examples, and later references for consistency
- Record final decisionClear open suggestions and comments; assign ownership if needed



