Benchmark, July 30, 2026
Benchmark: defined-term consistency checking
The problem
Every review team we work with has a version of this problem. Defined-term consistency checking rarely announces itself.
Volume changes the shape of the problem. At ten documents you can hold the exceptions in your head. At four hundred you need the exceptions written down and checkable.
How we measured it
We treat anything the system cannot ground in source text as unverified and show it as such. A visible gap is cheaper than a confident error.
In the current build this runs as part of the standard pass, so it applies to every document in the set rather than only the ones someone thought to check.
Where it breaks
Scanned originals with poor image quality remain the weakest input. So do agreements that were assembled from three precedents and never reconciled, which is common in long-lived supplier relationships.
If you take one thing from this, make it the habit of checking the adjacent provision before you sign off the clause in front of you.
Working notes from the Lawrs team. General information about legal technology and practice, not legal advice.