Benchmark, November 20, 2025
Benchmark: cross-reference validation after renumbering
The problem
The short version: cross-reference validation after renumbering is easier to get wrong than most teams assume, and the failure is usually silent.
What makes this hard is that the signal is distributed. A single clause read in isolation looks fine. Read against the definitions section and two schedules, the same clause does something different.
How we measured it
We score against a human baseline drawn from executed matters rather than a synthetic set, because synthetic contracts do not contain the drafting scars that cause real misses.
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.
The practical takeaway is narrow: write the exception down, point it at a source, and give it an owner.
Working notes from the Lawrs team. General information about legal technology and practice, not legal advice.