Before a single pile is driven or a foundation poured, the most consequential decisions on any construction project have already been made. They were made in a boardroom, across a negotiating table, or, perhaps most dangerously, in the absence of one. The contract was signed. The risk was allocated. And somewhere in the careful, considered language of that document, the seeds of future disputes were quietly planted.
This is not a story about force majeure clauses or liquidated damages caps, the familiar terrain of construction risk management articles. It is a question about something more fundamental: whether the way we approach risk allocation in construction contracts is, by design, slightly detached from the reality of how projects actually unfold.
The Assumption Embedded in Every Contract
Every construction contract is, at its core, a prediction. It predicts what will be built, how long it will take, who will bear the cost if something goes wrong, and, critically, what “something going wrong” even looks like. Those predictions are fixed in clauses, schedules, and definitions that, at the point of signing, feel like a comprehensive map of the project ahead.
But consider what a contract cannot anticipate: the subcontractor who becomes insolvent in month eight; the employer’s representative who interprets “practical completion” differently from every other party; the supply chain disruption that arrives not as a force majeure event but as a slow, grinding escalation that fits neatly into no clause at all. The contract was drafted for a version of the project that never existed, the clean, linear, fully scoped version that lives only in tender documents.
The question worth asking is not whether contracts fail to anticipate every risk. Of course they cannot. The more uncomfortable question is whether, during negotiation, parties are genuinely interrogating their assumptions about how the project will proceed, or whether they are negotiating the document while assuming the project will behave.
The Standard Form Problem — Or Is It?
There is a well-worn debate about standard form contracts in construction. Proponents argue that forms such as NEC, FIDIC, or JBCC bring consistency, familiarity, and a body of adjudicated case law that reduces uncertainty. Critics argue that standard forms are too readily adopted without sufficient consideration of whether their risk philosophies align with the specific project.
Both positions are largely correct. But they miss a more interesting tension.
Standard forms are drafted based on assumptions about the parties’ relative sophistication, bargaining power, and project context. The NEC suite, for instance, is built around a philosophy of collaborative risk management, early warning notices, compensation events, and proactive programme management. It assumes a level of contract administration discipline that, in practice, many projects simply do not sustain. What happens when the collaborative machinery of an NEC contract is operated by parties who do not share its underlying philosophy? The answer, increasingly, is that the standard form produces outcomes its drafters never intended.
This is not an argument against standard forms. It is an observation that a standard form is not a neutral vessel into which any project can be poured. It carries assumptions. And when those assumptions are unexamined, the risk allocation it creates may bear no meaningful relationship to the risk profile of the actual project.
What Is Actually Being Transferred?
Here is a question that is asked far less often than it should be during contract negotiation: when a risk is allocated to a party, does that party actually have the capacity to manage or absorb it?
In practice, risk allocation in construction contracts is not only about assigning liability – it is about whether the party receiving that risk can realistically manage it. Risk transfer in construction contracts is frequently treated as a zero-sum exercise in commercial positioning. The employer wants to push risk down. The contractor wants to price or exclude it. The result is a negotiation about who holds the liability, conducted in relative isolation from the question of who is best placed to control the underlying risk. These are not the same questions.
Consider ground conditions risk, allocated in many contracts entirely to the contractor, subject perhaps to a site investigation report prepared at a level of detail appropriate for tender purposes, not for construction. The contractor prices the risk. The contract is signed. And then the ground conditions differ materially from what was assumed, in a way that no reasonable contractor could have priced, and that the employer’s own designers had flagged internally as a genuine uncertainty.
Who bears that risk under the contract? The contractor. Who was best placed to investigate and manage it? Arguably, the employer who commissioned the site investigation and controlled its scope. The risk has been transferred. Whether it has been meaningfully allocated is a different matter.
This distinction between risk transfer and risk allocation is one of the most underexplored areas of construction contract negotiation. A risk that has been contractually transferred to a party that cannot effectively manage or absorb it has not truly been allocated at all. It has been deferred, and it will return, usually in the form of a claim, an insolvency, or a project that simply does not deliver what was promised.
The Clause That Nobody Read Carefully
There is a particular category of contractual provision that deserves closer attention than it typically receives: the notice clause.
In many construction contracts, the right to recover additional time or money is conditional on notices given within specified timeframes, sometimes as short as 14 or 28 days of the event arising. These clauses are negotiated, if they are negotiated at all, with relatively little attention. They seem administrative. Procedural. A matter of good contract management practice rather than substantive risk allocation.
They are, in reality, some of the most significant risk allocation provisions in the entire contract.
Consider a contractor who encounters unforeseen conditions, manages the impact as best they can, and issues a notice 35 days after the event, three days outside the contractual window. In a contract where notice is a condition precedent to recovery, the right to claim has been lost. Not because the underlying entitlement was questionable. Not because the employer was prejudiced by the delay in notification. But because the administrative machinery of the contract was not operated precisely as written.
The question is not whether notice provisions are enforceable; our South African courts have generally taken a strict approach to contractual notice requirements. The question is whether, when that clause was being negotiated, both parties genuinely understood that it would function as a hard substantive bar rather than a procedural requirement. And whether, if they had understood that the risk allocation they agreed would have looked the same.
The Evolving Project and the Static Contract
Perhaps the most fundamental tension in construction risk allocation is this: projects change, and contracts do not.
A contract is a snapshot. It captures the parties’ intentions, assumptions, and risk positions at a specific moment, the moment of signing. From that moment, the project begins to diverge from the snapshot. Designs are developed, the scope is clarified, programmes are revised, and subcontractors are appointed. Each of these developments changes the project’s risk profile. The contract, frozen at the point of execution, can accommodate only those changes through its variation and claims machinery, which is itself subject to interpretation, notice requirements, and the parties’ willingness to operate it transparently.
What this means in practice is that risk allocation often shifts during a project without any formal renegotiation, and without either party fully recognising that the shift is occurring. The contractor absorbs an expanding scope because raising a formal variation feels commercially awkward. The employer acquiesces to programme extensions without understanding the cost implications. By the time the project reaches practical completion, or the dispute that often precedes it, the actual risk allocation bears little resemblance to what was agreed.
This is not primarily a legal problem. It is a behavioural one. And it raises a question that contract drafters and negotiators would do well to consider: is the risk allocation framework in a construction contract designed to accommodate the reality of how projects evolve, or does it assume a level of contractual discipline that rarely exists in the heat of a live project?
A Pattern Worth Recognising
Across construction disputes of all scales, a pattern emerges that is consistent enough to be instructive. The dispute rarely begins with the event that finally triggers it. It begins, often years earlier, with a risk allocation decision that seemed reasonable in the abstract but proved unworkable in practice. The notice provision that no one fully understood. The ground conditions clause that allocated risk to the party least able to manage it. The standard form adopted without examining whether its underlying philosophy matched the project’s commercial structure.
By the time the dispute surfaces, the parties are arguing about events, instructions, and entitlements, but the real argument is about a set of decisions made long before the project started, when there was still time to make them differently.
The value of interrogating risk allocation at the contract stage is not that it eliminates disputes. No contract does that. The value is that it replaces uninformed risk transfer with a genuine assessment of who should bear what, and why. That assessment will not always be comfortable, it may reveal that a preferred position is commercially indefensible, or that a risk being pushed to the contractor is one that will return, expensively, before the project is finished.
But that discomfort, experienced during negotiation, is considerably cheaper than the alternative.
Before the First Dispute Is Filed
Construction contracts are sophisticated documents, negotiated by sophisticated parties. The suggestion here is not that the parties to major construction contracts are unaware of what they are signing. It is something more nuanced: that the negotiation of risk allocation in construction contracts is often conducted at a level of abstraction that does not fully engage with the specific project, its specific uncertainties, and the specific capacities of the parties involved.
The contract that is signed is the contract that governs. But is it the contract that was meant? And if it is not, if the risk allocation it creates was never really interrogated, if the standard form was adopted without sufficient consideration of its assumptions, if the notice provisions were treated as administrative boilerplate rather than substantive risk allocation, then the fine print will eventually speak for itself.
It usually does.
