There’s a moment in almost every infrastructure project where an owner signs a contract feeling reasonably confident. The scope looks covered. The price seems fair. The vendor came well-recommended. What they often don’t realize until months later is that the document they signed was written by people who have executed hundreds of these agreements, designed to protect the vendor’s position in every scenario where things don’t go as planned.
That’s not an accusation. It’s just how contracting works on the vendor side. They’ve been through enough projects to know where disputes arise, where costs escalate, and where owners are most likely to make decisions that create additional work. So they draft language that accounts for all of it, in their favor.
Owners who understand this going in are in a much stronger position. Owners who don’t tend to find out what those clauses mean when it’s too late to renegotiate.
This is one of the core issues we address in Hidden Risks in Infrastructure Contracts, and it’s worth walking through in detail because the patterns are consistent enough that recognizing them is a learnable skill.
The Contract Is Written by People Who Do This Every Day
This is the starting point that owners often miss.
The vendor’s legal and contracts team, whether that’s in-house counsel, a dedicated contracts department, or an experienced project executive, has been refining that document through dozens or hundreds of prior engagements.
Every clause that benefits the vendor exists because something happened in a past project that exposed them to cost, liability, or dispute. They fixed it in the contract. Then they kept that fix in every subsequent contract.
The owner, in most cases, is reviewing a contract for a project type they may execute once every several years. They bring in legal counsel who may be excellent at contract law but don’t have deep familiarity with infrastructure project dynamics. The asymmetry in experience is significant, and the document usually reflects it.
Where the Protection Gets Built In
Understanding the specific mechanisms helps owners ask the right questions during contract review rather than after the fact.
Scope Definition Language
The most valuable protection a vendor builds into a contract isn’t in the risk or liability section. It’s in how the scope is defined.
Vendor contracts frequently use language that defines scope by reference to the vendor’s proposal or a set of assumptions rather than a detailed, owner-approved specification. When actual conditions differ from those assumptions, and they often do, the vendor has a contractual basis for a change order. They didn’t misrepresent anything. The contract simply said their obligation was limited to work covered by the stated assumptions, and the rest is additional scope.
Owners who want protection here need a scope defined by outcome and specification, not by reference to a proposal document that the vendor wrote themselves.
Exclusions Written as Standard Terms
Most infrastructure contracts contain exclusion clauses. Some are reasonable. Many are written broadly enough to cover scenarios the owner would never agree to if they understood what was being excluded.
Common exclusions include:
- Subsurface or concealed conditions
- Existing infrastructure that doesn’t meet current standards
- Work required by regulatory changes during the project period
- Coordination with other vendors or third parties
Each of these is a real category of cost exposure. Written as exclusions in the contract, each one becomes a change order when it surfaces.
The vendor isn’t hiding these clauses. They’re listed in the contract. But they’re often written in language that doesn’t make the practical implication immediately obvious to someone who isn’t reading contracts of this type regularly. [→ See: Contract Clauses Owners Should Understand]
Change Order Mechanisms
How a contract handles change orders tells you a great deal about how a vendor expects the project to unfold.
Vendor contracts frequently contain change order procedures that require the owner to respond within a short window, sometimes 48 to 72 hours, or the change is deemed accepted. They may include markup rates for changes that are significantly higher than the original contract rates. They often allow the vendor to proceed with changed work immediately and bill for it later, which limits the owner’s ability to evaluate and negotiate before costs are committed.
None of this is unusual. It’s fairly standard in vendor-drafted agreements. The issue is whether the owner has negotiated terms that give them enough time and information to make real decisions, or whether they’ve signed a document where the change order process systematically favors the vendor’s billing position.
Limitation of Liability Clauses
Most vendor contracts cap the vendor’s liability for errors, delays, or failures at a fraction of the contract value, sometimes as low as the fees paid for a specific phase of work. Consequential damages, meaning the downstream costs to the owner from a vendor’s failure, are almost universally excluded.
For an owner, the downstream cost of a vendor failure in an infrastructure project can vastly exceed the contract value. A missed deadline on a data center buildout, a network outage caused by implementation errors, a building systems failure during a critical operational period — these carry real business costs. Under a standard vendor limitation of liability clause, the owner bears most of that cost regardless of where the fault lies.
Want to know exactly where your cost exposure sits before a problem surfaces? The Hidden Cost Exposure Report™ is a paid diagnostic that maps the specific gaps in your contract and project structure. → Get the Report
A Practical Checklist for Owner Contract Review
Before signing any major infrastructure contract, an owner should be able to answer the following clearly:
- Is the scope defined by specification and outcome, or by reference to the vendor’s proposal and assumptions?
- What conditions or events are explicitly excluded from scope, and what is the cost exposure if those conditions arise?
- What are the change order notification and response timeframes, and are they realistic given how your organization makes decisions?
- What markup rates apply to change order work, and how do they compare to the original contract pricing?
- What is the vendor’s liability cap, and does it bear any reasonable relationship to the owner’s actual exposure in the event of a significant failure?
- Are consequential damages excluded entirely, and if so, what does that mean for your specific project risk?
These questions don’t require a law degree. They require someone with enough project experience to understand the practical implications of the answers. If the people reviewing the contract on the owner’s side can’t answer these questions with confidence, that’s worth addressing before signature, not after.
The Bottom Line
Vendors structure contracts to protect themselves because they have the experience, the counsel, and the institutional knowledge to do so effectively. That’s not a criticism, it’s a practical reality of how the industry works.
If you’re heading into a significant infrastructure commitment and want an independent review of your contract structure before you sign, that’s a conversation worth having early.
Heading into a significant infrastructure commitment? A private strategy call with Lightwater gives you an independent read on your contract structure before you sign. → Request a Private Strategy Call
Lightwater Infrastructure Advisory works exclusively on the owner side — no design, no construction, no vendor relationships that create conflicts. Our role is to make sure you understand what you’re signing and what it will mean when the project is under pressure.
→ Download the Owner’s Guide to Avoiding Infrastructure Project Failure