The first round of a contract is the one everybody prepares for. You read the draft, you mark it up, you know exactly what you asked for and why.

The round that comes back is the one that costs money, and almost nobody reads it with the same attention. By then the deal has momentum, the business is asking when it can be signed, and the document in front of you looks like the one you already read. So you scan the coloured text, confirm the big asks survived, and move.

A markup is a poor instrument for that moment. It tells you precisely where the two sides disagree and nothing whatsoever about why, and the three things it hides are the three things most likely to matter.

1. The term that moved with nothing marking it

Tracked changes mark the words that changed. They do not mark the words whose meaning changed because something else did.

A definition gets one word added three pages away and a liability cap you negotiated hard now covers less than you think it does. Nothing in the cap clause is coloured. The cap is untouched, and the number in it is the number you agreed. What moved is what the number counts.

This is the most expensive category and the hardest to see, because the thing you need to look at has no markup on it at all. The only way to find it is to re-read the clauses you care about as they now stand, rather than reading what changed.

2. The concession you made, taken slightly further

You gave something up in round one. You remember giving it up, so when you see that clause in round two your eye reports it as settled and moves on.

But the clause you conceded is the one with the least scrutiny on it for exactly that reason, and it is a sensible place for the other side to go a little further. A carve out gains a qualifier. A notice period you agreed to shorten gets shortened again. A right you accepted as mutual stops being mutual.

None of that requires bad faith. Their counsel is doing their job, and the clause you have stopped guarding is the cheapest place to do it. The habit worth building is to re-read what you conceded on their turn, specifically because you have already decided it is fine.

3. Volume as cover

Forty edits come back. Thirty-seven are house style, defined terms, a numbering fix, a preference about where the governing law clause sits. Three change the allocation of risk.

The thirty-seven are not a smokescreen, usually. They are what happens when a document goes through a firm with a template. But the effect is the same either way: by the time you reach the third substantive edit you have made thirty-nine judgement calls and your attention is a different instrument than it was on page one.

An exhaustive markup is also a signal in its own right. A document where every clause has been touched tells you something about how it was produced and how much human judgement is behind any individual change. That is worth knowing before you spend an afternoon treating each edit as considered.

The question a redline cannot answer

What you actually need to know on the returning round is not "what changed". It is "what happened to what I asked for".

Those are different questions and the markup only answers the first. Your position was accepted, or rejected, or quietly reworded into something that reads like acceptance and is not. The third is the common one and the markup presents it identically to the first.

So the second pass is where the work is. Not reading their changes again, but reading your own positions against the document as it now stands and asking, for each one, whether it survived. That is a different pass with a different starting point, and it is the one that gets skipped when the business is waiting.

What this has to do with how I build

Most contract software is built around the first round. Draft from a template, apply a playbook, produce a document. That is the easy half and it is where the market is.

The round that comes back is the harder problem and it is the one I care about, because it is where the money is and because it is the round a small team is least equipped for. It needs the document held whole rather than read in order, your own prior positions tracked across rounds rather than remembered, and the edit with nothing marking it surfaced rather than scrolled past.

That is the thing I wanted and could not buy, which is a large part of why Midly exists.

Read the round that comes back

Midly tells you what happened to each of your changes when their markup returns, accepted, rejected, or reworded into something else, and catches the term that moved with nothing marking it.