Negotiating contracts in Microsoft Word without breaking tracked changes

The problem is conversion, not Word

A .docx is a zip of XML parts. A tracked insertion is a w:ins element wrapping a run; a deletion is w:del; a comment is a w:comment part joined to the body by a pair of range markers and an anchor. None of that is decoration. It is structure, and it carries the legal record of who changed what.

When a contract is opened in a browser-based editor, that structure is parsed into the editor's own document model, rendered, edited, and then written back out. That is a conversion, twice. Anything the intermediate model has no concept of is dropped silently on the way in or reconstructed approximately on the way out. The file still opens. It just is not the same file.

This is why the failure is so hard to catch. Nothing errors. The document looks broadly right. The damage shows up three rounds later, when counsel asks who deleted the limitation of liability and the revision history cannot say.

What actually gets lost

In rough order of how often it bites, and how expensive it is when it does:

• Revision attribution. Changes survive as text but lose the author and timestamp, or get re-attributed to whoever last saved. The audit trail is gone even though the words are right.
• Comment anchors. A comment scoped to a phrase re-anchors to a paragraph, or detaches entirely and lands at the end. Replies collapse into a flat list, losing who answered whom.
• Numbering. Multi-level clause numbering is driven by a numbering definition. Lose the link and 7.3.1 becomes a literal string, or restarts at 1 in the middle of a schedule. Cross-references then point at the wrong clause.
• Styles. Named styles collapse into direct formatting, so the next person editing changes a heading and nothing else follows.
• Content controls, section breaks and headers. Signature blocks and annexures are usually where these live, which is why they break at execution rather than during negotiation.

Why in-browser editors are built this way anyway

Not out of carelessness. Rendering a .docx faithfully in a browser is genuinely hard, and building an editor that stores its own model is far easier than one that manipulates OOXML in place. It also gives the vendor a cleaner product surface: their own editor, their own shortcuts, their own collaboration.

The trade is invisible while a document is only being drafted internally. It becomes expensive the moment a counterparty is involved, because that is when the revision record starts to matter and when the file starts moving between organisations that each have their own tooling.

The test to run before you trust any tool

Take a real executed agreement with schedules, multi-level numbering, cross-references and a signature block. Not a sample. Then:

• Upload it, open it in the tool, make one tracked edit, and download it. Open the downloaded file in desktop Word.
• Check that your edit is attributed to you with a timestamp, and that earlier revisions still carry their original authors.
• Check that clause numbering is still automatic: insert a clause mid-document and confirm everything after it renumbers.
• Check that a comment anchored to a phrase is still anchored to that phrase.
• Repeat the cycle three times. Most breakage compounds rather than appearing on the first pass.
• Do the same round trip with the counterparty's copy, edited in their Word, not yours.

What a non-destructive setup looks like

The principle is simple: there should be exactly one .docx, and every editor should open that same file rather than a copy of it. In practice that means editing over a protocol Word itself speaks, so Word Online and desktop Word are both operating on the stored document with locking, rather than importing and exporting it.

Three things follow from that. Edits are made by Word, so Word's own revision structures are written, not reconstructed. Offline editing is safe, because the desktop client checks the file out and back in rather than producing a second version by email. And version history is a series of states of one document, which is what you want when someone asks what changed between round two and round three.

This is the design behind IntelloContract: contracts stay as real .docx files edited in Word Online or desktop Word with tracked changes intact, with the AI review layer running in the Word pane rather than in a separate editor. The point is not that AI in Word is novel. It is that the lawyer never leaves the document, so nothing is ever converted.

Housekeeping that prevents most of the rest

Even with the right setup, a few habits remove most remaining risk:

• Accept or reject all revisions deliberately before sending for signature, rather than letting a signing platform flatten them for you. A PDF generated from a document with open tracked changes may render text that was supposed to be deleted.
• Never email a copy mid-negotiation. The moment two files exist, someone will merge them by hand.
• Keep templates free of direct formatting. A template built on named styles survives editing; one built on manual bold and indents does not.
• Fix numbering in the template, not in the executed copy. Numbering that was broken at draft stage cannot be repaired cleanly later.