Why we built Telamont: the document problem behind construction disputes

Telamont started from an observation that isn't ours alone. Trace a construction dispute back far enough and you usually arrive at the same place: two documents that stopped agreeing, and no point in the process where anyone was going to catch it.

That has nothing to do with diligence. Every document on a project gets read. Usually carefully, usually by someone who knows their scope well. That's exactly what makes the problem hard to see. Nobody is skipping the work.

The trouble is that no single document holds the meaning of a project. The meaning sits in the relationships between them, and those relationships shift every week. Contract and general conditions. Specifications by division. Drawings across revisions. Addenda from the tender period. Change orders, RFIs and their answers, site instructions, minutes, progress reports. Subcontracts that inherit obligations from the prime contract, sometimes faithfully.

Each is correct on its own terms. The failures live in between. A revision that invalidates an assumption three other documents still rest on. A change order that moves a boundary a subcontract still describes the old way. A spec requirement a bid priced around.

We are not the first to notice

Every year Arcadis publishes what its contract solutions team saw in the disputes it handled. The list of causes barely moves between editions. Failure to properly administer the contract. Poorly drafted or unsubstantiated claims. One party not understanding or not complying with its obligations. Over a nine-year stretch, errors and omissions in contract documents came first six times.

Those aren't four findings. They're one finding described four ways.

The cost attached is large enough to feel like someone else's problem. Arcadis put the average US dispute at $60.1 million in its 2025 report, with North American disputes running about 12.5 months. Those figures come from the disputes a global consultancy gets called into, so they skew toward megaprojects. The mechanism doesn't. A $40 million job has the same document problem at a different scale, with less margin to absorb it.

Why nobody fixed it

In 2014, Arcadis's head of contract solutions summed up what should be done: better contract administration, more robust documentation, a proactive approach to risk. He was right. It's still the advice. Dispute values have roughly doubled since.

The industry didn't ignore it. It couldn't act on it. Following that advice properly means holding a project's entire documentation in view, continuously, for the full duration of the work, and re-checking it every time something new arrives. On an eighteen-month job that's thousands of pages compared against each other, over and over. Nobody has ever had those hours.

So the industry built its operating model around the gap. Miss some of it, deal with the consequences later, through claims and negotiation and the twelve months of resolution in the Arcadis numbers. That isn't a failure of the model. It is the model.

What changed

Reading at that scale is now possible. Not summarising, not searching. Reading a project's full document set, holding it in one frame of reference, and continuing to as the set grows.

Construction turns out to be an unusually good fit. The source of truth is text. That text comes from many parties with different incentives. And the cost of two documents disagreeing gets measured in months and money.

What it opens up is broader than a faster contract review. A single read at signature, by one person, was always a partial answer to a problem that unfolds across the whole project. What's possible now runs continuously: documents checked as they arrive, technical, contractual and compliance risks raised while they're still decisions rather than damages, and a system you can question and push back on rather than a report that gets filed.

That's what we're building. We didn't start because contractors were doing something wrong. We started because the industry has been given the same correct advice for fifteen years without the means to follow it, and that constraint has now lifted.

This is the first thing we've written here. What follows will mostly be about the same territory: what happens to documents after award, where scope quietly drifts, and what we're learning from the projects we work on. If that's useful to you, stay with us.