Legal operations
The order you review a redline in changes what you catch
Reading a marked-up contract from page one to the end feels thorough and is the least reliable way to do it. Attention is highest at the start, and the clauses that cost money are rarely at the start.
The problem with reading front to back
A redline arrives, and the natural move is to start at the top. Two problems follow. First, attention degrades: by the time you reach the indemnity and liability sections — usually two thirds of the way in — you are reading with less care than you gave the definitions. Second, front-to-back reading treats every change as equally important, which they are not.
The changes that matter are concentrated in a small number of places, and they are almost never in the order the document presents them.
The order we use instead
- Deletions first. Something removed is easy to miss and often more consequential than something added. A struck-out cap on liability does not announce itself the way new text does.
- Money, term and exit. Fees, payment timing, renewal, notice periods, termination rights. These decide what the agreement costs and how you get out.
- Risk allocation. Liability caps, indemnities, warranties, exclusions. Read these as a set, because a change in one is often offset — or quietly not offset — by another.
- Definitions last, but never skipped. A redefined term changes every clause that uses it. This is the highest-leverage edit in a contract and the least visible.
- Then the rest, front to back. Now the sweep is a check, not the whole review.
Three habits that catch more than knowledge does
Compare against the last executed version, not the last draft
Negotiation produces a chain of drafts. Reviewing the newest against the previous draft tells you what changed this round. It does not tell you how far the document has drifted from what was actually agreed. Both comparisons are useful; only one of them is usually done.
Write down what you decided, not just what you changed
Six weeks later someone will ask why a clause was accepted. If the only record is the redline, the answer is lost. A one-line note per accepted change — why it was acceptable, and what it was traded for — costs seconds and prevents re-litigating settled points.
Separate "unacceptable" from "not our preference"
Reviews stall when every deviation from the template is raised with equal force. Mark each item as blocking or negotiable before sending comments. It shortens the round trip and makes the blocking items credible.
What tooling can and cannot do
Software is good at the mechanical part: finding every difference between two versions, including the ones a reader skims past, and doing it consistently at two in the morning when a human would not. That is genuinely valuable, because missed changes are usually a detection failure rather than a judgement failure.
What it cannot do is decide whether a change is acceptable for your business. A cap that is fine for one deal is unacceptable for another, and no tool knows your risk appetite, your other commitments, or what you traded away last round. Treat comparison output as a complete list of what changed, then apply judgement — yours or your counsel's — to what it means.
The short version
Deletions before additions. Money before boilerplate. Definitions never skipped. Decisions written down. And a clear line between what you cannot accept and what you would simply rather not.
Written and reviewed by the ContractDiff team. This describes our own review process and is operational guidance only. It is not legal advice, it does not interpret any law or regulation, and it is not a substitute for review by qualified counsel on your own agreements.