Review by exception: proofread a filled document fast

Review by exception means checking only what changed. In a filled document the fixed text was settled long ago; today’s risk lives entirely in the names, numbers and dates that were entered for this case. Check that short list against the sources, resolve every gap, and the review of a routine document takes a couple of minutes instead of a full re-read.

Why re-reading the whole document fails

Re-reading fails for two reasons: it reviews mostly text that carries no risk, and it reviews the risky part badly. The settled clauses have been correct for years; reading them again spends attention where nothing can be wrong. Meanwhile the eye moves through familiar text at skimming speed, and skimming is blind to exactly the errors that matter. A transposed digit in a thirteen-digit number is invisible at reading pace. A correctly spelled wrong name reads as a name. The longer the document, the worse the trade: attention falls as pages pass, and the values near the end get the weakest review of all.

What does review by exception mean in practice?

It means the review runs over a list of entered values, not over the document’s prose. Instead of hunting through pages for the things that changed, the things that changed are presented to you, and you compare each one against its source. Three properties make the method work.

• Completeness: the list contains every entered value, so nothing changed outside it. If values can change without appearing on the list, the method collapses back into re-reading.
• Traceability: each value can be seen where it landed in the document, so you confirm it in context, not in the abstract.
• Sources at hand: you compare against the ID, the deed, the registry extract, never against memory. Memory is what typed the error in the first place.

What makes gaps visible

A review can only be fast if the dangerous failures are loud. The quietest failure in document work is the plausible wrong value: a field filled with something that looks right. The loud failure is the empty field, which anyone can see at a glance. Good process therefore pushes every uncertainty toward emptiness. A value the sources do not contain should stay blank, not be guessed from habit or copied from a previous case. During review, each blank becomes a deliberate decision: obtain the value, or confirm it genuinely does not apply. Two outcomes, both conscious. Compare that with a guessed value, which produces no decision at all, only a defect waiting for the signing appointment.

The two-minute routine

• Go down the list of entered values, comparing each against its source document. Most values take a second or two.
• Check long identifiers digit by digit, once. Identity numbers, account numbers and registration numbers cannot be verified at reading speed, only digit by digit.
• Resolve every empty field deliberately: fill it from a source, or confirm it does not apply to this case.
• Spot-check each value in its place in the document, so a right value in a wrong field cannot slip through.
• Finish with a glance at the places prose review forgets: the header, the footer, the signature block, the file name.

Two minutes is realistic for a routine document with a dozen values and sources at hand. A first-time document or one with many parties takes longer, and should.

What review by exception cannot catch

The method reviews data, not drafting. It will not tell you that the wrong template was chosen, that a clause no longer fits this kind of case, or that the law changed under a paragraph last year. Those need a lawyer’s read, and they need it at a different rhythm: when a template is created or amended, read all of it, slowly. Review by exception is what the settled text earns after that. Two reviews, two speeds, and neither pretends to be the other.

The short version

Re-reading a familiar document is slow where it is safe and blind where it is risky. Review by exception inverts that: check the list of entered values against the sources, verify long numbers digit by digit once, resolve every empty field deliberately, and glance at headers, footers and the signature block. Keep the full slow read for the moments the fixed text itself changes.