The clauses that quietly move risk from one side of the table to the other, what they cost when they go unread, and why the technology to catch them is finally getting good.
A principal at a well-run Arizona subcontractor signed a seven-figure subcontract from the cab of his truck, parked at a job site that was not his office, with a second site to visit and a flight to catch that afternoon.
This is not a story about a careless guy. He is good at what he does. Twenty-plus years in the trade, a reputation GCs respect, a backlog most of his competitors would envy. He recognized the GC’s standard form, skimmed the scope, saw the number he expected, and signed. He had reviewed a hundred of these. This one, he told himself, was the same one.
It was not the same one. Tucked into a back page was a single provision his estimating team would have flagged in about four seconds, if anyone had looped them in before signature. It was a clause he had been burned by once before. Same clause. Same lesson. New project. Roughly $180,000 to relearn it.
I am not sharing that to scare anybody. I am sharing it because I have now heard a version of it in more leadership meetings than I care to count, and the details barely change.
First, my disclaimer. Then my seat at the table.
I am not a construction attorney. I do not draft contracts, I do not redline them for a living, and if you need legal advice you should call someone who does. That is the honest disclaimer up front.
Here is what I am. I sit on multiple construction industry committees, I co-host an AI in Construction series with a GC partner, and I run an MSP whose entire client base is AEC. Which means I spend a lot of time in rooms where owners, CFOs, and estimators talk candidly about what went sideways and why. I am the technology eyes in those rooms. The vCIO in the corner who keeps noticing that the same expensive mistakes keep tracing back to the same two failures.
A contract quietly costs you in one of two ways
Almost every painful story I hear lands in one of two buckets. The first is a legal clause that shifted risk onto the sub, and nobody read it closely. The second is a number or a scope that was wrong on the way in, and nobody pressure-tested it. Different problems, same root cause: the document moved faster than the conversation around it.
Bucket one: the clauses worth a second read
These are not written to trick you. They are written to protect the people who wrote them. That is exactly why they deserve your attention, because by default they are not protecting you.
Pay-if-paid versus pay-when-paid. Two phrases that sound like cousins and behave like strangers. Pay-when-paid generally means the GC pays you within a reasonable window after they get paid. Pay-if-paid can mean you only get paid if the GC gets paid, which quietly turns the owner’s nonpayment into your cash flow problem. I have watched a sub float a six-figure receivable for months on the wrong one of those two phrases. Know which one you signed.
No damage for delay. If someone upstream delays your work, you absorb the cost of waiting. You bought the material, you staged the crew, and now you are paying people to stand around because a wall moved three floors above you. The clause says that is yours to eat.
Termination for convenience. The other side can cancel for any reason, or no reason, and pay you only for what is already installed. The material sitting in your yard for next month can become yours to keep and yours to write off. You can usually negotiate reimbursement for purchased materials, but only if you catch the clause before you sign it.
No-lien clauses. A lien is one of the strongest tools you have against not getting paid. A no-lien clause asks you to hand it over. In a lot of cases your lien rights are protected by law, so this one should stop you cold and make you ask why it is in there.
Flow-down and the vague catchall. Flow-down binds you to obligations in the prime contract between the GC and the owner, a document you may never have seen. For GCs it is fair and necessary, but only when it is specific. The trap for both sides is the catchall: the subcontractor assumes all obligations the contractor owes the owner. That sentence feels tidy and means nothing until a dispute, when it suddenly means whatever the prime contract says. Subs should ask for the prime contract. GCs who write specific flow-downs instead of catchalls have fewer fights later.
Bucket two: the number nobody pressure-tested
The other half of the stories are not about legal language at all. They are about a scope read too quickly and a number that went out the door without the right second set of eyes. A missed exclusion. An allowance that should have been a hard quote. Estimators have a name for the worst version: the Winner’s Curse. You win the job not because you were sharper, but because your bid was incomplete, and now you get to perform the mistake at your own expense.
This is the bucket my parking-lot principal fell into too. The clause was the headline, but the deeper miss was that the contract and the estimate never met in the same room before he signed. The people closest to the risk were never asked.
And it is happening in a market that does not do anyone any favors. Material prices have been unpredictable enough, for long enough, that an escalation clause is worth understanding on every job. An escalation clause lets you adjust the contract price when a key material spikes past a defined trigger, usually tied to a published index. No escalation clause, and the contractor absorbs the volatility alone. Whether you want that clause in or out depends on which side of the table you are on. Either way, it should be a decision, not a surprise.
The pattern underneath both buckets is the same. The document moved faster than the conversation. The signature happened before the people who understood the risk got a look.
The good news: the tools are finally catching up
Here is the part that ties back to my actual job. For most of construction history, the only defense against these mistakes was a careful human with enough time and enough coffee. Time is the one thing nobody signing a contract between job sites actually has. That is changing, and it is worth knowing what to watch for.
On the scope-and-number side, estimating and takeoff platforms have gotten genuinely good at catching the misses in bucket two. Tools like Bluebeam now use AI-assisted symbol detection to scan a drawing set and count every fixture in seconds, work that used to eat hours, while keeping the estimator as the validator rather than the clicker. Bid-leveling features line up subcontractor quotes side by side to expose the scope gaps that create the Winner’s Curse, and platforms like Procore keep the estimate, the contract, and the field tied to one source of truth.
On the contract side, an entire category has grown up to read agreements the way a tired human cannot. Platforms like Document Crunch are trained on construction contracts, not generic legal language, so they flag the pay-if-paid, indemnification, and lien provisions that general-purpose tools miss, and they translate the legalese into plain-English summaries in minutes. The category is consolidating fast: Trimble just announced it is acquiring Document Crunch to make contract-risk intelligence a built-in layer of its construction platform. When a software giant buys the contract-review startup, that is the market telling you this problem is worth solving with software.
I am not here to sell you any of these, and this is not a product bake-off. The right tool depends entirely on how your team works. The point is simpler than a shopping list: as this software gets better, and as AI gets layered on top of it, the gap between a contract that got a real review and one that got a windshield skim is going to get very wide, very fast. Be on the lookout for what these tools do well, and start asking how they would fit your process.
The MSP angle, said honestly
Dimensions does not sell estimating software or contract-review software. We support the construction companies who use them, along with everything underneath: the network, the security, the data, the access controls, and the question of whether any of these shiny AI tools can actually be trusted with your contracts and your numbers.
And what we see every single day is that the AI tool is only as good as the foundation beneath it. A contract-review platform is fantastic until the contracts live in four personal OneDrives and an inbox. An estimating database is powerful until nobody owns the standards behind it. Clean infrastructure first, then clean data, then the AI on top of all of it. Skip a step and the whole stack wobbles. That is the part we own, and the part most firms discover they skipped right about the time they try to adopt the good stuff.
A few questions worth asking before you sign
If the parking-lot story felt a little too familiar, here is the version you can act on this week:
- Did the estimate and the contract ever meet? Before signature, did the people who built the number actually see the terms that govern getting paid for it? If the honest answer is not really, you have a process problem, not a luck problem.
- Have we been burned by this exact clause before? If a provision cost you money on a past job, it belongs on a checklist that someone is actually required to run. Repeating a mistake is optional.
- Could we even find our last ten signed contracts in under ten minutes? If the answer involves a sigh and a search across three people’s laptops, no contract-review tool on earth will save you, because it will never see the documents. That is an infrastructure question, and it is the one we can help with directly.
None of these are legal questions. All of them are the difference between technology that protects you and technology that just makes your blind spots faster.
P.S. Part 2 of our AI in Construction webinar series is the hands-on workshop, and this is exactly where we put the idea to work. We take a real Arizona subcontractor’s actual GC contracts and watch AI read them live, flag the terms worth a second look, summarize what is unusual, and even draft the response back to the GC. Less framework, more rolling up sleeves.
For over 20 years, Dimensions has been the trusted IT partner for Arizona’s architecture, engineering, and construction industry. We help AEC firms communicate better, collaborate smarter, and actually use the technology they’ve invested in. Because in construction, the tools only work if your team does.
IT Built For Builders.
