A few years ago, a sales director sent me a vendor MSA at 4:47 on a Friday. Subject line: “quick redline?” The contract was 38 pages. He had already promised the vendor we would turn it around Monday morning. He had also already redlined three clauses himself, in red font, not Track Changes. And he had cc’d the vendor.

That email is the reason I have rules.

Redlining a contract is not the hard part. The hard part is everything that happens in the fifteen minutes before anyone opens Word and clicks Review > Track Changes. Skip that fifteen minutes and you spend the next two weeks cleaning up.

This post is the checklist I run through before I touch a single comma. None of it requires software you don’t already have.

Why redlines go sideways at normal companies

Most contract redlining problems are not about contract knowledge. They are about coordination.

Three people open the same Word file. Two of them are not using Track Changes. One of them is editing a version that is already a version behind. Someone forwards a copy to the other side before legal sees it. Procurement adds a comment that contradicts what sales already verbally agreed to. The fallback position never got written down, so the junior person on the call concedes a point we would never concede.

This is normal. It happens at companies with 50 employees and companies with 50,000. The fix is not more software. The fix is agreeing on a small set of rules before the markup starts.

Here is my list.

Rule 1: Name the business owner before you open the file

Every contract has a business owner. That is the person who actually wants this deal to happen and who will live with the outcome. For a vendor deal, it might be the IT director. For a customer contract, it might be the account executive. For a partnership, it might be the head of BD.

The business owner is not legal. Legal is a reviewer. The business owner makes the call when there is a tradeoff between commercial terms.

Before I redline anything, I send one email and ask:

• Who is the business owner for this contract?
• What is the deal we are actually trying to do?
• What is the deadline, and is it real or made up?

If I cannot get a clear answer to those three questions, I do not start redlining. I have learned this the hard way. Redlining without a business owner is how you end up arguing with yourself in the margins.

Rule 2: Lock down version control before anyone edits

This is the single biggest source of pain. If you do nothing else from this post, do this.

Pick a single source of truth for the document. One folder. One file. One naming convention. My convention is boring on purpose:

VendorName_AgreementType_v01_OurCompany.docx

Then v02, v03, and so on. Each new version gets a new number, even if the change is tiny. The current working version sits in one place. Old versions stay in an “archive” subfolder so nobody opens them by accident.

A shared drive works. SharePoint works. A Dropbox folder works. Email does not work. Email is where versions go to die.

If two people need to edit at the same time, one of them waits. I do not care how urgent it is. Two simultaneous editors in two copies of the same document will cost you more time than just taking turns.

Before redlining starts, I send a one-line note: “Working version is here. Please do not edit the file directly. Send me your suggestions and I will consolidate.”

That last sentence is the one that saves the weekend.

Rule 3: Write down the fallback position before the first comment

A fallback position is the answer to the question “what would we accept if we cannot get what we want?”

For every clause we plan to push back on, I write three things on a single page:

• Ideal: what we are asking for
• Acceptable: what we will live with
• Walk-away: what we will not sign

This page does not get sent to the other side. It lives in our folder. It is the cheat sheet for whoever ends up on the negotiation call.

Without a fallback, every redline becomes a fresh debate. The lawyer pushes for the ideal. The salesperson caves to the walk-away. Nobody knows where the middle is because nobody wrote it down.

You can do this on a notepad. You can do it in a Google Doc. You can do it in the same email thread where the business owner approved the deal. The format does not matter. The act of writing it down is what matters.

Rule 4: Use comments like a professional, not a diary

Track Changes is for edits. Comments are for everything else. The mistake I see most often is people using comments to think out loud.

A comment that says “not sure about this, what do you think?” is fine inside our own team. It is not fine when the document goes back to the other side. It tells them exactly where we are unsure, which is information we do not need to give away.

My rule: every comment in a document that goes to the other side has to be a complete thought addressed to a specific person. “We need this clause to reflect Section 4.2 of the SOW. Please confirm.” That is a comment. “Hmm” is not a comment.

Before the file leaves our hands, I do one pass that does nothing except clean up comments. Internal-only comments get deleted. Vague comments get rewritten. Comments addressed to the wrong person get fixed. This takes ten minutes and prevents a surprising number of awkward emails.

Rule 5: Decide who owns which clauses

Most contracts have natural splits. Commercial terms belong to the business owner. Payment terms belong to finance. Data and security clauses belong to IT or security. Indemnification, limitation of liability, and governing law belong to legal. Insurance belongs to whoever buys the insurance.

I write this out in a quick table at the top of the working folder, often just five lines in a Notes app:

• Pricing and term: business owner
• Payment terms: finance
• Data and security: IT
• Liability and indemnity: legal
• Insurance: ops

Now when I see a redline on a security clause, I know exactly who has to sign off before it goes back. I do not have to guess. The business owner does not have to guess. The lawyer does not have to chase three people.

This is also how you keep a sales director from quietly conceding a security commitment that the CISO would have rejected on sight.

Rule 6: Agree on what happens after the redlines go out

This is the rule everyone forgets. Sending the redline is not the end of the process. It is the start of a new cycle. Someone has to manage that cycle.

Before I send anything back to the other side, I answer four questions:

• Who is the single point of contact on our side from this point forward?
• What is the response timeline we are committing to internally?
• What happens if the other side sends back changes that touch a clause one of our reviewers already approved?
• Who decides when we are done negotiating and ready to sign?

That last one matters more than people think. I have watched contracts get stuck for weeks because nobody had the authority to say “this is good enough, send it for signature.” Pick that person at the start. Tell them they are the deciders. Move on.

I also set an expectation with the other side. Something like: “We will get you a turn within three business days. Please send your next turn to me directly.” This keeps the file from getting forwarded to six different inboxes on their end.

A quick word on low-tech versus software

You can run all six of these rules with Word, a shared folder, and email. That is how I did it for years. The naming convention does the version control. A one-page Word doc holds the fallback positions. A short email at the start of every contract lays out the owners.

There are tools that do this for you. Some of them are good. Most of them are overkill for a team doing fewer than fifty contracts a year. Get the discipline right first. Buy the software later, if you still need it, once you actually know what you want it to do.

The biggest gains in contract redlining come from the boring stuff: naming files correctly, knowing who owns what, writing down the fallback before the call. None of that is technology.

Your next action this week

Pick the next contract sitting in your queue. Before you open it in Word, do this:

1. Email the business owner and confirm what deal we are trying to do.
2. Save the file in the right folder with the right name.
3. Write down the fallback position on whichever two or three clauses you expect to push back on.
4. Decide who owns the rest of the clauses.
5. Pick the single point of contact for the back-and-forth.
6. Then turn on Track Changes.

It will feel slower for the first contract. By the third one, it will be muscle memory. By the tenth one, you will wonder how you ever worked without it.

---

I’m Dave, and I write about contract management the way it actually works. No jargon, no sales pitch, just what I’ve learned from 15+ years of doing this job. If this was useful, stick around.