A 500-millisecond budget: why review latency is a product decision
Inline review either keeps pace with drafting or it interrupts it. We set a hard budget of half a second at the 95th percentile, and most of our architecture follows from it.
Inline review either keeps pace with drafting or it interrupts it. We set a hard budget of half a second at the 95th percentile, and most of our architecture follows from it.
Most firms’ cap positions are conditional on fees, contract value or role. Here is how to write them down so Review can apply them, and a checklist before you switch them on.
Review 4.0 remembers which redlines you declined on this matter and stops proposing them. Nothing leaves the matter, and nothing reaches the playbook unless its owner puts it there.
A flag without a reason cannot be checked, cannot be disagreed with and cannot be defended later. The audit argument for citations is stronger than the usability argument, and it is the one that matters.
Review 3.8 replaces our custom annotation layer in Word with the native comments and tracked-changes APIs. Flags are now real Word comments; redlines are real tracked changes. What that fixes, and what it costs.
A year ago we had just over a hundred accounts. Now there are 340 in 28 countries. Some of what we expected to happen did. Much of it didn’t, and that is the more useful list.
Survival clauses are short, late in the document and easy to skim. Here are the five patterns that cause problems after termination, and how Review flags each one.
Time saved is the easiest number to inflate. Here is how we define first-pass review time, who we measure, what we exclude and where the measurement still misleads.
A playbook is not a precedent bank or a style guide. It is a set of positions, fallbacks and red lines, written so that a reviewer, human or model, can apply them consistently.
Review 3.6 replaces the single risk score with three severity tiers, High, Medium and Note, and lets each practice group decide where the lines sit.