14 Aug 2026 · The CivitasOPS team

The worst kind of wrong

Software that reads documents can fail in two ways.

It can fail loudly: an error, an empty page, a spinner that never stops. That is annoying, and it is safe. You know something went wrong, so you go and look at the document yourself.

Or it can fail quietly. You ask what is in a document and get back a short, tidy, confident list — and one line is missing. Nothing about the answer says so. An answer with one thing missing looks exactly like a complete one, right up until the point where it matters, which is usually in front of a client or a court.

That second failure is the one we design against, because it is the only one that can put a professional seal on something untrue.

Where quiet failures come from

Almost always from something being dropped on the way through, rather than from a piece of software confidently inventing an answer. Reading that did not go cleanly. A step that ran out of room and returned what it had. The danger is not in the difficulty; it is entirely in not noticing.

What we do about it

Two habits, and they cost us speed.

Show the page. Every finding points back at where it came from, so checking one is a glance rather than an afternoon. Findings you cannot check are not findings; they are rumours with good typography.

Say what is missing. What is unconfirmed is marked unconfirmed, and a document that did not read cleanly says so at the top. We would rather hand a surveyor an honest gap than a confident sentence, because they can do something with the gap.

Why it is worth the slower answer

A surveyor's signature is a professional undertaking. The value of a tool that reads a document is not that it is quick — you could skim it yourself in twenty minutes — it is that what it hands back can be checked in two, and that when it is unsure, it tells you.

Anything that is fast and occasionally, silently wrong is worse than nothing, because it costs you the habit of looking.