The Risk Is in the Fine Print: Five Contract Clauses That Quietly Shift Construction Risk
Risks arising out of a construction project do not start on site. They start with the contract. The drawings may be clear, the schedule reasonable, and the team experienced, but a few sentences in the contract can quietly change who carries the financial risk when something goes wrong.
Most contractors price labour, materials, and productivity carefully. Fewer spend the same time pricing legal risk. That gap matters because several common clauses routinely transfer risk downstream in ways that affect cash flow, margins, and claims long before a dispute ever arises.
This article highlights five provisions that deserve a closer look during procurement and contract negotiation. None of these provisions are unusual or inherently improper. In fact, many are standard tools used by sophisticated owners to manage project risk. The issue is simply understanding how they work so that you can price them properly or negotiate where appropriate.
1. Indemnity Clauses – When You Become the Project’s Backstop
An indemnity clause is a contractual provision that requires one party to compensate or make whole another party if certain losses occur. In construction contracts, these provisions often require the contractor to cover losses suffered by the owner and other parties when claims are connected to the contractor’s work.
While indemnity clauses are not uncommon, broad or ambiguous clauses can significantly expand a contractor’s responsibility beyond occurrences for which they may be considered at fault.
An indemnification clause might read as follows:
“The Contractor shall indemnify and hold harmless the Owner, Consultant and their agents from any and all claims, damages, losses and expenses arising out of or relating to the performance of the Work.”
It is helpful to break down the above provision into three separate parts that determine how broad it is: who benefits from the indemnity, what types of losses or claims are covered, and what event triggers the obligation.
First, the beneficiaries of the indemnity clause can extend well beyond the parties to the contract. It is common to see the indemnity provision apply not only to the owner but also to the consultant, affiliated companies, and sometimes the directors, officers, employees, and agents of those entities. This means the contractor may be agreeing to protect a wide group of parties who are not themselves signatories to the contract.
Second, the clause will define the types of losses or claims that must be indemnified. Phrases such as “any and all claims, damages, losses and expenses” are very broad. They may capture legal costs, settlements, and other financial consequences of a claim. Depending on the wording, the obligation may arise even before liability is determined because the contractor may be required to defend the claim as it proceeds.
Third, the trigger for the obligation to indemnify can also be very broad. Language such as “arising out of” or “relating to” the work can capture situations where the contractor’s involvement is indirect or only one part of a larger issue. It also does not require there to be any fault on the part of the contractor. The result can be that the contractor is required to respond to claims even where responsibility is shared or primarily lies elsewhere.
Indemnities are not unusual, but their scope should never be assumed. Contractors can manage this by looking for language that ties the indemnity to their own negligence or breach and that limits the scope of who and what is covered by the indemnification obligation.
2. Pay-When-Paid Language – How Cash Flow Risk Moves Downstream
Pay-when-paid clauses shift the risk of payment delays down the contractual chain. These provisions make the contractor’s obligation to pay a subcontractor dependent on the contractor first receiving payment from the owner.
A typical clause might read:
“Payment to the Subcontractor is conditional upon the Contractor receiving payment from the Owner for the Subcontract Work.”
At first glance, language like this can look like an administrative payment term. In substance, however, it reallocates credit risk on the project. If the owner delays payment or disputes an invoice, the subcontractor may have to wait to be paid even where the subcontractor’s work has been completed properly.
The practical impact is usually felt in cash flow. Labour, suppliers, and equipment costs continue to accrue whether or not funds have moved down the project chain.
In Ontario, there is some debate about the interplay between pay-when-paid clauses and the prompt payment regime under the Construction Act, R.S.O. 1990. The Act establishes mandatory timelines for payment following the delivery of a proper invoice and requires parties to issue notices of non-payment if they intend to withhold funds. In theory, this framework is intended to promote the timely flow of funds down the construction pyramid.
With that said, the prompt payment regime has not eliminated the existence of pay-when-paid clauses or attempts to rely on them.
The practical takeaway is that subcontractors should understand the risk they are assuming when they agree to this language, particularly where the timing of upstream payment is uncertain or if there is a dispute between those further up the construction pyramid.
3. Strict Notice Requirements – When Good Claims Are Lost on Procedure
Strict notice clauses can defeat otherwise legitimate claims. These provisions require contractors to give written notice of delays, extras, or impacts within a defined period of time and often in a particular form.
A typical clause might read:
“The Contractor shall provide written notice of any claim within five (5) days of the event giving rise to the claim, failing which the claim is waived.”
There is sometimes an assumption that these provisions will not be applied strictly, particularly where the contractor has a valid claim or where the other party is aware of the issue through less formal channels. In practice, Canadian courts have generally enforced contractual notice requirements strictly according to their terms. The reasoning is straightforward. Construction contracts allocate risk through agreed procedures, and courts are reluctant to rewrite those procedures after the fact.
Owners also rely on these provisions for practical reasons. Early notice allows potential issues to be investigated while the work is ongoing and gives the owner an opportunity to mitigate costs or adjust the project approach. Courts often view notice provisions as serving this legitimate commercial purpose, which is one of the reasons they tend to be enforced.
The practical takeaway is that contractors need to treat notice provisions as operational requirements, not just legal language in the contract. Contractors should review the timelines and notice requirements before executing the contract and consider whether they are realistic in the context of the work.
Once the contract is signed, contractors should make sure the project managers and coordinators running the project know what those requirements are. These individuals are usually the first to see an issue developing on site. If they understand when notice needs to be given, a short written notice can preserve the contractor’s rights while the details are still being investigated.
4. Limitation of Liability and Waiver of Consequential Damages– When Remedies Are Restricted
Limitation of liability clauses and waivers of certain remedies restrict what one party can recover if something goes wrong on a project. These provisions usually operate when an unexpected event has occurred and a claim would otherwise follow. Their purpose is to place limits on the amount or type of liability that one party may face.
Two common examples are a cap on liability and a waiver of certain categories of damages.
A limitation clause might read:
“The Owner’s total liability arising out of or relating to this Contract shall not exceed the Contract Price.”
A waiver clause might read:
“The parties waive all claims against each other for consequential, indirect, or special damages arising out of or relating to the Contract.”
Clauses like these determine what remedies are available when a problem or issue arises on a project. If an issue leads to losses that exceed the agreed cap, the excess cannot be recovered. Similarly, if certain types of damages have been waived, they fall outside the scope of any claim regardless of who caused the problem.
The corresponding impact of these provisions is that they shift risk to the other party. If the contract prevents recovery of particular losses, the party that experiences those losses must absorb them. This is why these provisions can become significant when an unforeseen event affects schedule, cost, or project performance.
These types of clauses are common in construction contracts. Owners and contractors often use them to create greater certainty around potential exposure if a dispute arises. The practical point is that contractors should understand what types of losses have been excluded and whether any overall cap on liability is reasonable in the context of the project.
5. Unforeseen Conditions and Inferred Scope – When What is Included in the Contract Isn’t Obvious
Unforeseen conditions and inferred scope provisions address situations where work is required that is not expressly described in the contract documents. These clauses typically allocate the risk of those gaps to the contractor, rather than the owner.
A typical clause might read:
“The Contractor shall satisfy itself as to the conditions of the site and the completeness of the Contract Documents. No adjustment to the Contract Price shall be made for work reasonably inferable from the Contract Documents or reasonably discoverable upon a site review.”
The practical effect of this type of language is that the contractor may be responsible for performing work that is not expressly described in the drawings or specifications if it can be said to be reasonably inferred from them. Similarly, conditions that could have been identified through a reasonable site inspection may be treated as the contractor’s responsibility rather than an unforeseen condition.
From an owner’s perspective, provisions like this are intended to promote certainty in pricing. Owners want bids that reflect a contractor’s full assessment of the project rather than a price that assumes gaps in the documents will later become change orders.
The corresponding implication is that contractors are expected to undertake a careful review of the tender documents and the site before submitting a price. If the contract allocates the risk of inferred scope or discoverable conditions to the contractor, gaps in the drawings or issues that could have been identified through a reasonable investigation may ultimately become the contractor’s responsibility.
These provisions do not eliminate the possibility of legitimate change orders or unforeseen conditions claims. Their purpose, however, is to place greater responsibility on the contractor to identify issues that are reasonably apparent before the work begins. Understanding where that line is drawn in the contract documents can make a significant difference once construction is underway.
Conclusion – Read the Risk Before You Price the Work
The common thread across these clauses is simple: they allocate risk before the first day on site. None of them are inherently problematic and all serve legitimate purposes in managing projects. The question is not whether they should exist, but whether their effect is understood and bargained for.
Contracts are ultimately about allocating risks between the parties. If a contractor accepts broader indemnities, delayed payment, strict notices, limited remedies, or expansive scope obligations, those risks need to be priced or negotiated intentionally. Surprises tend to arise only when the contractual language is skimmed.
A short review at the procurement or negotiation stage can often prevent months of frustration later. Marking up key clauses, asking questions, and clarifying expectations are practical steps that pay dividends.