Challenge 3: Re-Uploading an Edited .docx With Tracked Changes — Solution Walkthrough

What happens on upload:

Per Chapter 8, the writer has the same two paths available as any
other uploaded Microsoft file: open it in Office compatibility mode,
staying closer to the original .docx (including, generally, its
tracked-changes markup), or explicitly convert it into a native Google
Doc via Save as Google Docs. Word's own Track Changes markup is a
Microsoft-specific feature, not a universal one, so how faithfully it
carries over depends on which path is chosen and isn't guaranteed to
be pixel-for-pixel identical to how it displayed in Word.

What the writer should check before assuming a clean transfer:

  - Whether the tracked changes actually appear as recognizable
    suggestions/edits once opened in Google Docs, rather than being
    silently flattened into the text as if already accepted.
  - Whether any comments the stakeholder left in Word survived as
    genuine Google Docs Comments, or were dropped/altered.
  - Whether formatting the stakeholder applied in Word (styles, any
    advanced field codes) rendered correctly, per Chapter 8's own
    named risk areas for advanced Word features.

This is the same category of check Chapter 8's own "What Happens
During the Conversion" section already established — most everyday
content survives, but specific feature areas (here, Track Changes
markup and comments from a different application entirely) are exactly
where fidelity is most likely to be imperfect and worth verifying by
eye rather than assuming.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise applies Chapter 8's own upload/conversion framework to a
new, more specific case it didn't spell out directly — Word's own
Track Changes and Comments features crossing into Google Docs — using
the same "check the known risk areas, don't assume a clean transfer"
discipline the chapter established for every other feature type.