ICDL Advanced Documents study materials
ICDL Advanced Documents study resources

Track Changes Gone Wrong

ICDL Advanced Documents · Put your knowledge to work in context.

All case studies

Track Changes Gone Wrong

Three reviewers edited a 60-page contract with Track Changes on. The author now sees overlapping insertions, deletions, and comments, plus formatting-change marks from a reviewer who restyled whole paragraphs. The author must produce a clean final version, but legal needs an audit trail of who changed what. One reviewer's edits are marked as "Author" (a default name), so attribution is unclear. The deadline is tight and the author is tempted to Accept All Changes and move on.

1. The author wants to Accept All Changes immediately. Explain the risk and a safer sequence that satisfies both the clean-final and audit-trail requirements.

Read the worked answer

Risk of Accept All: It permanently bakes every edit into the text and destroys the record of who changed what. Legal's audit-trail requirement would then be unmet, and there is no undo path once saved. It also silently accepts the misattributed "Author" edits.

Safer sequence:

  1. Preserve the trail first - save a copy of the fully marked-up document, or use Compare/Combine to generate a version showing all changes, before resolving anything.
  2. Resolve attribution - identify the "Author" edits (by context or by asking reviewers) so the record is meaningful.
  3. Review and accept/reject selectively, not wholesale, so contested edits get a decision.
  4. Produce the clean final from the resolved copy, keeping the marked-up copy as the audit record.

Accept All is a last step on a copy, never the first step on the only file.

2. One reviewer restyled entire paragraphs, creating many formatting-change marks that clutter the view. How should the author handle these without losing the substantive text edits?

Read the worked answer

Separate formatting changes from content changes. Use the display/review options to hide formatting changes (show only insertions/deletions/comments), so the substantive edits are visible and reviewable without the noise.

Then handle formatting deliberately:

  • If the restyling is unwanted, reject formatting changes only - this removes the paragraph restyling while leaving text insertions and deletions intact.
  • If some restyling is wanted, accept those specific formatting marks individually.

Why not Accept All: Accept All would accept the formatting and the text together, so you could not reject the restyling without also discarding text edits. Filtering by change type keeps the two decisions independent - which is exactly what the cluttered view is hiding.