In plain English
Negotiate contracts in Word with Track Changes on, one canonical .docx, clear comments, and disciplined accept/reject passes. Send redlines your counterparty can open in Word (not PDF screenshots) and keep version history so FINAL(2) never becomes the source of truth. Process beats heroics.
Not legal advice. This is a process guide for founders and deal owners; escalate material risk to a licensed attorney.
By version90 staff Published Updated How this was made
Why Word still runs the deal
Enterprise CLM demos love portals. Counterparties love email + Word.
If you force a buyer or vendor into a strange workflow for a $25k SOW, you didn't "modernize legal ops." You added friction to a deal that already had enough.
Word-native negotiation means:
- Track Changes shows inserts/deletes
- Comments explain why, not just what
- The file opens on their laptop without a training webinar
- Your record of who changed liability last Tuesday still exists
Related: contract version control · AI contract review with citations.
The minimum viable redline process
- One owner for the canonical file (ops, founder, or deal desk, pick a human).
- Turn Track Changes on before the first edit. Leave it on.
- Name versions like humans who respect future-you:
Acme_MSA_2026-09-13_v3.docx, notfinal_FINAL_use_this. - Comment with intent: "Pushing to mutual cap = 12 months fees; matches our insurance."
- Send
.docx. PDFs of redlines are how meaning dies. - On return: save their file as the next version; don't overwrite blindly.
- Accept/reject in a dedicated pass, not while also rewriting scope.
Use the Startup MSA redline checklist so you're negotiating substance, not vibes.
Track Changes etiquette that speeds deals
| Do | Don't |
|---|---|
| Edit with Track Changes visible | Paste "clean" text that hides diffs |
| Comment once per issue cluster | 40 overlapping balloons on one word |
| Propose fallback language | Only write "disagree" |
| Keep formatting noise down | "Fix" fonts while arguing indemnity |
| Summarize open issues in the email body | Make them hunt the markup |
Sharp truth: If you turn Track Changes off "just for this paragraph," you are the reason trust evaporates.
Accept / reject without lighting the deal on fire
When their redline returns:
- Skim the summary email (if they wrote one).
- Filter by author if multiple people touched the file.
- Walk high-risk clauses first: liability, indemnity, auto-renew, IP, fees, see how to review an MSA without a lawyer.
- Accept unambiguous fixes (typos, party names you already agreed).
- Counter remaining points with tracked edits + short comments.
- Lock a clean execution copy only after both sides agree the markup is done, and still archive the last redline.
Never "accept all" on a file you haven't read. That button is not a productivity hack. It's a trap door.
Comments vs edits
- Edits change the legal text.
- Comments explain commercial intent, ask questions, or park an escalate item.
If a point is non-negotiable for insurance or board reasons, say so in the comment. Silence reads as soft.
Version hygiene checklist
- Canonical folder / system owns the latest file
- Prior versions retained (not deleted "to reduce clutter")
- Filename includes counterparty + date + version
- Email thread links to the version ID/name you mean
- Execution copy generated from agreed text, then hashed/stored
- No parallel edits in Google Docs and Word and Notion
If this list feels aggressive, re-read the last time someone asked "which final?"
Where AI helps (and where it doesn't)
Useful: surfacing "this liability paragraph changed," citing clause locations, comparing versions, flagging missing DPA references.
Not useful: pretending a model is your lawyer.
AI that cites the clause it is talking about helps humans decide faster. It is still not legal advice, still your judgment, and still a job for counsel when the risk is material.
Common Word negotiation failure modes
| Failure | Symptom | Fix |
|---|---|---|
| Clean copy bait | "Here's a clean version" that differs | Demand a diff / prior redline |
| PDF ping-pong | Screenshots of Word | Return to .docx |
| Parallel drafts | Two people editing two finals | Single owner + version history |
| Comment graveyard | Unresolved balloons at signature | Issue list → close or escalate |
| Formatting wars | 200 markup bubbles that are bold/italic | Separate style pass |
About this page
Who. Written by version90 staff at Latent Ape LLC, the company that builds version90, working with AI tools. We build contract software and run our own contracts through it; we are not a law firm, and nothing here is legal advice.
How. Each piece starts from the review workflow version90 is built around. AI drafts and structures the text; staff edit, fact-check, and rewrite it before it is published, and we update the date shown above whenever the substance changes.
Why. The library exists to give founders and ops teams a shared standard for reviewing contracts without a legal department. If you spot an error, email [email protected] and we will fix the page.