In this practice area
Extension of time and delay cost claims, liquidated damages, disruption and acceleration, practical completion and superintendent disputes on building and infrastructure projects.
Delay is a question of cause, not only of time
Every late project has a story about why it was late. A delay dispute asks whether that story can be proved against the programme, the contract and the records. Late design information, authority approvals, utility connections, latent conditions, variations, weather, labour shortages and the performance of other contractors can each delay the critical path, and the contract allocates the risk of each event differently.
We act for principals, developers, head contractors, subcontractors and authorities in delay disputes on building and infrastructure projects. The financial stakes are often greater than the cost of the work itself: liquidated damages, prolongation costs, lost revenue from late occupation and financing costs can all depend on whether a single extension of time was granted.
Extensions of time and notice requirements
Most construction contracts entitle the contractor to an extension of time for qualifying causes of delay, provided it gives notice and particulars within specified periods. Courts generally give effect to those time bars. A contractor that fails to notify in time may lose its entitlement, and a principal that relies on the bar must be able to show that the contractual requirements were not met.
Many contracts also give the superintendent or principal a discretion to extend time even where the contractor has not claimed. In Peninsula Balmain Pty Ltd v Abigroup Contractors Pty Ltd [2002] NSWCA 211, the Court of Appeal held that such a power, under the form of contract in that case, was to be exercised honestly and fairly, and could operate despite the contractor's failure to claim in time. The effect of a reserve power depends on its wording, and it is not a general licence to disregard notice clauses.
The prevention principle and concurrent delay
The prevention principle holds that a principal cannot insist on a completion date, or recover liquidated damages, where its own conduct prevented the contractor from completing on time, unless the contract provides a mechanism to extend time for that conduct. An effective extension of time clause usually answers the problem; where it does not, time may be at large and the contractor obliged to complete within a reasonable time.
Concurrent delay, where a contractor caused delay and a principal caused delay at the same time, has no single settled answer in Australian law. Many contracts now address it directly, either by allowing time but not costs or by excluding an extension altogether. The outcome usually depends on the contract's wording and on detailed programme evidence about which events actually affected completion.
Delay costs, disruption and acceleration
An extension of time and an entitlement to delay costs are different things. Contracts commonly allow delay costs only for specified causes, at specified rates or subject to caps. Prolongation claims for extended site overheads must be supported by actual cost records, and disruption claims, alleging that work became less productive rather than later, require evidence that connects cause and effect.
Courts are cautious about global or total cost claims that do not link particular events to particular losses. A contractor who accelerated to avoid liquidated damages after an extension was wrongly refused may have a claim for the cost of acceleration, but it must prove both the entitlement it was denied and the cost it incurred as a result.
Programme evidence and the project record
Delay disputes are decided on programming evidence. A forensic delay analyst will typically examine the baseline and updated programmes, the as-built record and contemporaneous documents to determine the critical path and the effect of each delaying event. The method chosen, whether an as-planned versus as-built comparison, a windows analysis or another approach, can significantly influence the result, and the opposing expert will test it.
That analysis is only as reliable as the project record. Site diaries, minutes, requests for information, notices, photographs and correspondence made at the time are far more persuasive than reconstruction after the event. Preserving and organising that record early is one of the most valuable steps a party can take.
Practical completion, superintendents and infrastructure projects
Practical completion triggers the release of security, the end of liquidated damages and often the start of the defects liability period, so disputes about whether it has been achieved are common. The definition in the contract governs, and it frequently depends on certificates, documentation and authority approvals as well as physical works.
A superintendent who assesses claims and certifies completion must act honestly and impartially in performing those functions, as recognised in Perini Corporation v Commonwealth (1969) 12 BLR 82. On infrastructure and large building projects, delay can arise from interfaces with authorities, utilities and other contractors who are not parties to the head contract, and the contractual chain must be traced to identify who bears that risk and who can be pursued.
Legal framework

