How to catch missing terms in third-party paper

When you review your own template, you are reading a diff. Redlines sit in the margin and everything unmarked is language you already signed off on. On the counterparty's paper there is no diff. You get thirty pages of someone else's drafting with no marks anywhere.

So people read. Front to back, hoping the bad parts stand out.

The bad parts usually do stand out. A one-sided liability cap is right there on the page. A payment term you hate is right there on the page. What reading front to back does not reliably surface is the term that should be in the contract and is not, because there is nothing on the page to react to. A clause nobody wrote does not announce itself.

That gap is what your first pass should be built around.

The other side's draft decides what you talk about

Read someone's contract and you end up negotiating their outline. Your time goes to the sections they chose to write, in the order they chose to write them.

There is data behind this. In a 2024 study of US government contracting, the Commerce & Contract Management Institute (a not-for-profit set up by NCMA and World Commerce & Contracting) asked participants to rank the terms they negotiate most, and separately the terms they think matter most. The two lists do not line up. The report's read on it: contract managers are well aware of what is most likely to go wrong, but policies, templates and rules push them to focus elsewhere. It is a government procurement study, so the specific rankings are not yours. The pattern is worth taking.

On third-party paper, the counterparty's template is one of those rules. It just belongs to someone else.

Write down what has to be in the document

Per contract type, list the terms that have to appear before you will sign. Not your preferred language. Presence only. For inbound vendor software paper that might be a liability cap, mutual confidentiality, a data security exhibit, breach notification timing, an audit right, termination for convenience, assignment on change of control, and proof of insurance.

Keep it to a dozen or so. A list of forty gets skipped by week three.

Two things make the list usable. Each entry names what the term is called in other people's drafting, because vendors do not use your headings. And each entry says where it tends to hide. Insurance is often nowhere near a section called Insurance. It is in an exhibit, or the order form, or a document the agreement points at by URL. If you are already writing playbook entries that tell a reviewer where to look, this is the same discipline pointed at presence instead of position.

Run the absence check first

Order of operations matters. Check presence before you read language.

A reviewer who starts on page one spends judgment on whatever is in front of them, and by the signature block their attention is gone. Do the presence check cold, at the top, in five minutes. Walk the list, mark each entry present, absent, or unclear. Then read.

More reviewers would fix this, and you are probably not getting more reviewers. In ACC's 2026 survey of 1,049 chief legal officers, 63% expected department headcount to hold flat. Presence checking also happens to be the part of review that software handles reasonably well, and it is a fair sanity check on someone who is nine files into the afternoon. Confirming that the security exhibit named on page 4 was never attached is not judgment work. Software that reads an inbound contract against a list of required terms will not tell you what an absence means for this deal. It will tell you the exhibit is not there.

A missing term is not automatically a problem

Every absence needs a route, and you decide the routes once per contract type, not file by file.

Some entries you will sign without. Say so on the list, so nobody burns a call on it.

Others you just add, with standard language ready to paste and no discussion needed.

What is left goes to a person, because the absence might be deliberate, or because the answer turns on what the vendor is actually doing for you.

Skip the routing and a missing-terms report becomes a list of complaints somebody has to think through from scratch every time.

One number to watch

Count how often each list entry comes back absent, sorted by counterparty type.

If the data security exhibit is missing from more than half of your inbound vendor paper, you are pushing against a market norm. That belongs in a conversation with procurement about what to require at intake, not in a redline every time.

And if an entry comes back present on every contract for six months, take it off the list. It is costing attention it has stopped earning.

Try it on your next inbound contract

Take one contract type, write down the twelve terms that have to be there, and run your next ten files against it before anyone reads a word.

You can try goHeather free and point it at a contract you were going to read anyway.

This is legal information, not legal advice; consult a lawyer for legal advice.