Skip to content
Writing

Build log, July 2, 2025

Build log: reconciling three rounds of tracked changes deterministically

Tobias RennerCounsel, Commercial3 min read

The problem

Every review team we work with has a version of this problem. Reconciling three rounds of tracked changes deterministically rarely announces itself.

In testing, the gap between a fast pass and a careful pass was not accuracy on the central question. It was whether the reviewer noticed the interaction with an adjacent provision.

What we do about it

The register is the deliverable. A finding without an owner and a date is an observation, not a control.

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.

We will revisit this once we have a larger sample. The current numbers are directional rather than settled.

redliningretrieval

Working notes from the Lawrs team. General information about legal technology and practice, not legal advice.