contracts

Redlining Etiquette: How to Mark Up a Contract Professionally

Adira EditorialLegal AI desk5 min read

What does it mean to redline a contract professionally? Redlining is marking up a contract to show the changes one side proposes, so the other side can see exactly what moved and decide whether to accept it. Done well, redlining makes a negotiation faster and builds trust, because the other side can rely on your markup to show everything you changed. Done badly, it hides changes, buries the other side in a mess of edits, and slows the deal while people argue about process instead of terms. Professional redlining is mostly etiquette: a set of habits that make your markup honest, readable and easy to act on. Here are the rules. This is general guidance, not legal advice. ## The rules of professional markup - Always use tracked changes. Make every edit with track changes turned on, in the editable file (usually Word). Never make silent edits to a clean copy and send it as if nothing changed. Hidden edits are the fastest way to lose the other side's trust.

  • Turn the draft in one clean pass. Send one consolidated set of changes, not a trickle of separate edits. If several people on your side have comments, consolidate them into a single markup before it goes out.
  • Use comments to explain, not to argue. A short comment that says why you changed a clause (for example, "capped liability at fees paid, in line with our policy") saves a call. Keep comments professional; the other side may forward the document internally.
  • Do not retype the other side's document. Edit the file they sent so the comparison stays clean. If you must rebuild it, run a document compare and share the comparison so nothing is hidden.
  • Name versions clearly. Use a consistent naming pattern with the party and date, for example "MSA v3 - [YourCo] markup 2026-02-10". Never leave two files both called "final".
  • Know who holds the pen. One side should control the master document at a time. Agree who is turning the next draft so two markups do not fork.
  • Accept and reject cleanly. When you agree a change, accept it. Do not leave a document full of accepted-in-principle edits still showing as tracked, or the next version becomes unreadable.
  • Send Word for negotiation, PDF for signing. Negotiate in the editable format so both sides can mark up. Convert to PDF only for the final signature version.
  • Include a short cover note. A few lines summarising your main changes and open points helps the other side prioritise. ## A quick redlining checklist Before you send a markup, check: - Track changes is on and every edit is visible
  • All internal comments are consolidated and professional
  • Comments explain the why on any significant change
  • The file is named with party and date, not "final"
  • You have run a compare if you rebuilt the document
  • A short cover note lists your main changes and open points
  • You have saved your own clean copy of what you sent ## Common mistakes to avoid - Making silent edits with track changes off, which destroys trust the moment the other side runs a compare.
  • Sending edits in several messages instead of one consolidated turn.
  • Leaving sarcastic or blunt internal comments in a document that gets forwarded.
  • Two people on the same side marking up different copies, which forks the document.
  • Retyping the other side's draft so the comparison is lost.
  • Negotiating in PDF, which forces the other side to recreate the document to edit it. ## How to handle multiple rounds A contract rarely settles in one turn, and the etiquette matters more as the rounds add up. - Keep a running issues list. Alongside the document, track the open points, who is holding each, and the agreed position. This stops the same point being reopened three turns later.
  • Narrow with each turn. Each round should close points, not reopen them. If your side wants to revisit a term you already accepted, flag it clearly and explain why, rather than quietly re-editing it.
  • Know when to pick up the phone. When two or three points are going back and forth with no movement, a short call usually resolves them faster than another markup. Capture the outcome in the document afterwards so the record stays complete.
  • Do not reset the version history. Carry the same document through the rounds so the full trail of changes is visible. Starting a fresh clean document mid negotiation loses the history both sides rely on. ## Who should hold the pen On most deals, one side drafts and controls the master document and the other marks up. The side that holds the pen has an advantage, because it frames the starting position and controls how changes are incorporated, so it is worth asking to draft on important contracts. Whoever holds the pen carries the duty to incorporate the other side's agreed changes faithfully and to keep the version history clean. If you hand the pen over, keep your own copy of the last version you sent so you can confirm nothing moved that was not agreed. ## A note on tools and jurisdiction Most contract negotiation still happens in Microsoft Word with tracked changes, and the etiquette above assumes that. Some teams use contract platforms that track changes and versions automatically, which removes the file naming and version forking problems. The etiquette is the same whatever the tool: every change visible, one clean turn, clear versions, professional comments. Redlining etiquette does not vary by jurisdiction, though the clauses you negotiate and the law that governs them do. ## Where a workspace makes redlining cleaner The habits above solve most redlining problems by hand. The pain that remains is version control: knowing which draft is current, what changed between versions, and whether the final signed copy matches what you agreed. That is where a contract workspace helps. When a contract is modelled as structured clauses rather than flat text, every edit is tracked precisely, each version is kept with a timeline of who changed what and when, and you can edit a clause in plain language and get a clean diff. A workspace such as Adira is built around that idea, so the professional etiquette you practise by hand becomes the default rather than a discipline you have to remember on every turn.

Frequently asked questions

What is redlining a contract?
Redlining is marking up a contract to show the changes one side proposes, using tracked changes so the other side can see exactly what moved. The name comes from the red lines that marked edits on paper. Done professionally, it lets both sides negotiate from a single document where every change is visible, rather than guessing what was altered.
Should I redline in Word or PDF?
Negotiate in Word (or another editable format) with tracked changes, so both sides can mark up and see each other's edits. Convert to PDF only for the final version that will be signed. Sending a PDF during negotiation forces the other side to recreate the document to edit it, which wastes time and risks introducing errors.
Is it acceptable to make changes with track changes turned off?
No. Making silent edits to a clean copy and presenting it as unchanged is the fastest way to lose the other side's trust, because a simple document compare will expose it. Always edit with track changes on so every change is visible. If you rebuilt the document for a good reason, run a compare and share it so nothing is hidden.
Was this useful?

See how Adira drafts in your voice and reads contracts from your side.

Explore the showroom

Working through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.

Try Weave — free