How to Redline a Contract in 9 Steps

To redline a contract, set your positions before reading and read for who carries each risk. Mark deal-breakers first, rank every other edit, and write a fallback for each ask. Then explain changes in comments, keep tracked changes clean, trade concessions in order, and version-control the signed copy.

Key Takeaways

• A redline is a marked-up draft that shows every proposed deletion and insertion, usually through Word's Track Changes.
• Decide your positions, fallbacks and walk-away points before you read the counterparty's paper.
• Spend your edits on risk allocation: liability caps, indemnities, data terms, IP ownership and termination.
• Give every substantive edit a short comment explaining why, and keep a fallback ready for each ask.
• Run a document compare before every send and again before signature to catch untracked edits.

What does it mean to redline a contract?

Redlining a contract means marking proposed changes directly in the draft so the other side sees every deletion and insertion. Commercial teams usually redline in Microsoft Word with Track Changes on, then add margin comments explaining each change.

A blackline is a separate comparison document that shows the differences between two versions of a contract. Word builds one through its legal blackline compare feature, which leaves both source files untouched.

Arceus Legal is a US law firm whose licensed, US-barred attorneys work alongside AI agents on its CounselOS platform. Arceus Legal attorneys review, redline, negotiate and draft commercial contracts for B2B software companies at flat per-document prices. The steps below reflect how we approach a counterparty draft, adapted for teams doing the work themselves.

Each step below comes with a worked example, and the nine steps run in this order:

1. 1.Establish your position before you open the document.
2. 2.Read for allocation of risk before you read for wording.
3. 3.Mark the deal-breakers first.
4. 4.Separate must-have edits from nice-to-have edits.
5. 5.Write a fallback position for every ask.
6. 6.Use comments to explain your changes.
7. 7.Keep the redline clean and traceable.
8. 8.Sequence your concessions.
9. 9.Close the loop and version-control the final.

Start Here: four things to do before your next redline

1. 1.Write a one-page position sheet for your five riskiest clauses: liability cap, indemnity, data protection, IP ownership and termination.
2. 2.Save the counterparty's original draft as a read-only file, and name each later version with a date and round number.
3. 3.Turn on Track Changes and set your Word user name to your company name before typing a single edit.
4. 4.Agree internally on who can approve a concession, and by what date, before round one goes out.

For a fuller pre-read, our guide to the contract review process includes a complete contract review checklist.

Step 1: Establish your position before you open the document

Your position is the set of terms you want, the terms you'll accept, and the terms that end the deal. Write it down before you read the counterparty's draft, because their paper anchors your thinking the moment you open it.

A position sheet covers business terms and legal terms on one page. Business terms include price, payment timing, term length and renewal. Legal terms include the liability cap, indemnities, warranties, data handling and IP ownership.

For example, a 25-person cybersecurity startup receives a 41-page vendor MSA from a regional bank. Before opening the file, the founder writes four lines on a position sheet. The lines read: cap at 12 months of fees, indemnity limited to third-party IP claims, net 45 acceptable, no on-site audits.

That sheet turns a 41-page read into a comparison exercise. Every clause now matches the sheet, beats it, or needs an edit.

Companies that sign the same contract type every week should turn the sheet into a standing playbook. A playbook adds approval rules, so everyone on the team applies the same positions.

Step 2: Read for allocation of risk, not for wording

Your first full read should answer one question per clause: who pays if this goes wrong? Wording edits come later, and many of them turn out to be unnecessary.

Risk in a commercial contract sits in a handful of places. Look hardest at the limitation of liability, indemnification, warranties, termination rights, data protection terms and IP ownership.

Definitions deserve the same attention, because a defined term can move risk without touching the clause that uses it. Consider an MSA where the indemnity clause looks standard, but the definition of "Losses" includes regulatory fines and internal costs. That single definition turns a narrow third-party indemnity into broad cost recovery for the customer.

A practical habit is a two-column risk map: clause number on the left, the party carrying the risk on the right. Clauses where your company carries open-ended risk move straight to Step 3.

Style fixes, such as swapping "shall" for "will," rarely change who pays. Skip them unless the wording creates an ambiguity a court could later read against your company.

Step 3: Mark the deal-breakers first

A deal-breaker is a term your company can't sign under any version of the commercial deal. Mark these before any other edit so the counterparty sees your hardest positions in round one.

Deal-breakers for B2B software vendors commonly include uncapped liability for ordinary breaches and assignment of core platform IP. Unlimited audit rights and most-favored-customer pricing clauses often land on the list too.

Regulated data adds its own must-have terms. A DPA under the GDPR needs the processor terms listed in Article 28(3) of Regulation (EU) 2016/679. A HIPAA business associate agreement must meet 45 CFR 164.504(e).

Example: before and after a liability cap redline Before: "Each party's total liability under this Agreement shall be unlimited." After: "Each party's total liability shall [delete: be unlimited] [insert: not exceed fees paid in the prior 12 months]." Comment: "We cap liability at 12 months of fees so our pricing covers the risk we carry. We're open to a separate, higher cap for data breach claims."

Flag deal-breakers in the cover email as well as the document. A short note such as "Sections 9 and 12 are the points we need resolved to sign" tells the other side where to focus first.

Keep the deal-breaker list short. If eight clauses are deal-breakers, none of them carry weight.

Step 4: Separate must-have from nice-to-have edits

Every edit after the deal-breakers belongs in one of two tiers: must-have or nice-to-have. Must-have edits protect against a real cost, while nice-to-have edits improve drafting or shift minor risk.

The tiering matters because each edit you send invites a response. A redline with 60 changes can draw 60 replies, and a redline with 15 targeted changes keeps the next round short.

We take a firm view here: a shorter redline is usually a stronger one. Dropping nice-to-have edits often does more for cycle time than winning them.

Take a 60-person AI company reviewing a customer's MSA that bans any use of customer data. The must-have edit adds a right to use aggregated, de-identified usage data to run and improve the service. Nice-to-have edits include a 30-day cure period instead of 15 days and a switch to New York governing law.

Governing law is a common nice-to-have, though its weight depends on the states involved and where disputes would be heard. Nice-to-have edits don't vanish when you drop them; park them on a list you can trade in Step 8.

Step 5: Write fallback positions for every ask

A fallback position is the next-best term you'll accept if the counterparty rejects your first ask. Write one for every must-have edit before the redline goes out, so no one improvises on a live call.

A simple format uses three lines per clause: the opening ask, the fallback and the walk-away point. The walk-away point is the line where your company would rather lose the deal than sign.

For payment terms, a vendor might open at net 30, fall back to net 45, and walk away at net 90. For the liability cap, the ladder might run from 12 months of fees to 24 months, plus a separate super cap. A super cap is a higher, separate liability limit reserved for specific risks such as data breaches.

Fallbacks help when the person negotiating has authority to use them. Write down who can approve each rung, especially when sales runs the call and finance owns payment terms.

Keep fallbacks out of the contract file itself. Anything typed in a comment or hidden text can reach the other side, as Step 7 explains.

Step 6: Use comments to explain, not to argue

A redline comment should tell the counterparty why you made a change and what problem it solves. One or two sentences per comment is enough, since long persuasive notes slow the other side's legal review.

Strong comments name the business reason behind the legal change. The counterparty's lawyer usually decides what gets escalated, so write every comment with that reader in mind.

Example: before and after a redline comment Before: "Deleted. Unacceptable to us. Our standard terms apply here." After: "We've limited audits to once a year with 30 days' notice. Our SOC 2 report covers the same controls, and we'll share it on request."

The revised comment gives the reviewer a reason to accept and a document to check. It also moves the conversation from whether audits happen to how they happen.

Reply to the counterparty's comments in the same thread instead of a separate email. A reply such as "Accepted, with the 30-day notice added" keeps the decision attached to the clause it changes.

Skip comments on edits that speak for themselves, such as fixing a broken cross-reference. Substantive edits sent without a reason tend to come back rejected in the next turn.

Step 7: Keep the redline clean and traceable

A clean redline shows every change as a tracked edit and nothing else. Turn on Track Changes before the first keystroke, and don't accept or reject the counterparty's edits without saying so in a comment.

Run a comparison before every send. Word's legal blackline option creates a third document that shows every difference between an original and a revised version.

Suppose the counterparty's second draft returns with tracked edits to the indemnity clause. A compare against your first-round draft also reveals an untracked change to the cure period, from thirty days to ten.

Scrub hidden data before each send. Word's Document Inspector finds comments, revision marks and document properties, which can carry internal notes and author names.

Leftover metadata can expose your fallbacks to the other side. ABA Formal Opinion 06-442 concluded the Model Rules generally permit a lawyer to review metadata in documents received from opposing counsel. Some state bars take a stricter view, so the answer depends on where the lawyers practice.

Keep one master file per round, with one person responsible for merging internal edits into it. Two colleagues editing parallel copies is a common way to lose a tracked change.

Name files with the date, round number and sender, such as "MSA_2026-10-02_R2_Vendor.docx." That naming pattern lets anyone rebuild the negotiation history in minutes.

Step 8: Sequence your concessions

Sequencing concessions means giving ground in a planned order, each time in exchange for something. A concession made without a trade tells the counterparty that pushing works.

Start by conceding nice-to-have items from Step 4 while holding the must-haves. Pair each concession with a specific ask, such as accepting the customer's governing law in exchange for your liability cap.

Consider a 90-person healthcare software vendor negotiating with a hospital system. Round two concedes the hospital's insurance certificate form and net 45 payment. Round three trades a longer cure period for the vendor's 12-month cap.

Keep agreed points closed. Reopening a clause the parties settled in round two signals bad faith and can cost more goodwill than the clause is worth.

Save one meaningful concession for the final round. A last-round trade gives both sides a reason to close instead of opening another turn.

In the negotiations we handle, rounds to signature tend to climb when concessions arrive singly with nothing asked back. Log every concession with the clause, the round and what you received, since that concession log feeds Step 9.

Step 9: Close the loop and version-control the final

Closing the loop means confirming every open comment is resolved, producing a clean execution copy, and filing the full history. Skipping any part invites a later dispute over which version the parties signed.

1. 1.Accept all agreed changes and delete every comment in a copy of the last redline.
2. 2.Compare that execution copy against the final agreed redline, and confirm the remaining differences are formatting alone.
3. 3.Send the execution copy as a locked PDF or through your e-signature platform.
4. 4.Store the signed PDF, the final redline and the concession log in one folder.
5. 5.Update your position sheet or playbook with what you conceded and why.

A common failure happens when the counterparty builds the execution copy from an older draft. A final compare catches a reverted net 30 payment term before signature, rather than at the first invoice.

Electronic signature works for most B2B software contracts. The federal E-SIGN Act, at 15 U.S.C. § 7001(a), bars denying a contract legal effect solely because an electronic signature was used. The statute lists exceptions, and some state rules add their own requirements for specific document types.

A two-minute compare costs far less than an argument about which draft governs.