News & Insights · 15 July 2026 · 5 min read

White Constructions v PBS Holdings: The Day the Court Rejected Both Delay Experts

Two qualified experts, two SCL Protocol methods, one judge unimpressed by both. The decision that re-centred Australian delay analysis on facts and site records.

Malachy MullinClaims Management · Dispute Resolution
Abstract graphic of two competing delay analyses set aside in favour of a site diary

Every delay analyst in Australia knows this case, and every commercial manager should. In White Constructions Pty Ltd v PBS Holdings Pty Ltd [2019] NSWSC 1166, two experienced programming experts ran two recognised delay-analysis methods — both drawn from the Society of Construction Law Delay and Disruption Protocol — and Hammerschlag J rejected the pair of them. The court then did something more confronting than choosing a winner: it engaged its own adviser, went to the site diary, and decided causation on the facts. The claim failed.

Six years on — and with the same orientation visible in the referees' and court's treatment of delay evidence in Santos v Fluor [2025] QSC 184 — White Constructions remains the clearest statement of how Australian courts actually decide delay: method serves facts, never the reverse.

The facts

White Constructions was developing a 100-lot subdivision at Kiama on the NSW South Coast. Registration of the subdivision required a certificate under the Sydney Water Act 1994 — which in turn required an approved sewerage design. White engaged a water servicing coordinator and a sewer designer; the designer proposed a pumping-station solution, and the design eventually approved (in August 2016) was a different, gravity-based solution. White alleged the designers' approach delayed approval and, with it, completion of the whole project from July 2016 to March 2017 — roughly seven and a half months — and claimed $1,935,199 in disruption costs, prolongation overheads, funding costs and land tax.

The expert contest

White's expert ran an as-planned versus as-built windows analysis and found 240 calendar days of critical delay attributable to the sewer issues. The defendants' expert ran a collapsed as-built ("but-for") analysis and concluded the works could not have finished materially earlier in any event. Both methods appear in the SCL Protocol, which the judgment noted enumerates six methods of delay analysis. The experts agreed on almost nothing except the as-built programme.

What the court held

Hammerschlag J dismissed the proceedings — finding no breach, but going on to deal with the delay question in terms that have echoed since.

First, on the Protocol (at [191]): "the fact that a method appears in the Protocol does not give it any standing, and the fact that a method, which is otherwise logical or rational, but does not appear in the Protocol, does not deny it standing." Method earns its place by fitting the dispute, not by appearing in a recognised publication.

Second, on the two analyses (at [195]): "neither method is appropriate to be adopted in this case." With the parties' agreement, the court had engaged its own specialist adviser under the court rules, whose advice "demonstrated that the complexity that has been introduced is a distraction".

Third, the path actually taken (at [196]–[197]): close consideration of "the actual evidence of what was happening on the ground", applying "the common law common sense approach to causation" from March v E & MH Stramare Pty Ltd (1991) 171 CLR 506. The only appropriate method, his Honour said, was "to determine the matter by paying close attention to the facts".

And the facts were thin. The builder's site diary — the primary contemporaneous record — was, as the judgment put it, more significant for what it did not say: it did not show sewer-design delay driving the works. Despite the court repeatedly emphasising the need to be taken to the raw data, the plaintiff took it to very little. The burden on causation was not discharged.

What this means in practice

  1. Choose the method the records can support — and say why. The question is never "which method is best in the abstract" but "which method can this project's records actually sustain". An expert report should open with that reasoning. A windows analysis without reliable progress records, or a collapsed as-built without a credible as-built logic, is an invitation to White Constructions treatment.
  2. The site diary is the claim. The case turned on a diary that didn't say what the claimant needed it to say. The delay claims that survive scrutiny are built from daily records that capture crew locations, activities, idle time and the reason — contemporaneously, not reconstructed. That habit costs minutes a day and decides seven-figure disputes.
  3. Complexity is not credibility. The judgment's most quoted lesson is its impatience with elaborate modelling detached from events on the ground. Sophistication that obscures rather than explains is a forensic liability — courts can and will engage their own advisers to cut through it.
  4. Common-sense causation is the test, in court and beyond. The same orientation governs how referees and adjudicators weigh delay evidence — Santos v Fluor shows the SCL Protocol treated as an accepted benchmark applied with common sense, never as a trump card. Prepare every EOT and prolongation claim to answer the plain question: what actually delayed the works, and how do the records show it?
  5. Claim presentation follows the same rule. Don't lead with the model; lead with the story the records tell, then use the analysis to quantify it. The model corroborates the facts — it cannot replace them.

Key takeaways

  • Both experts' SCL Protocol methods were rejected as inappropriate to the case; causation was decided on the site records and common sense (White Constructions [2019] NSWSC 1166 at [191], [195]–[197]).
  • A method's appearance in the SCL Protocol gives it no presumptive standing in an Australian court.
  • The claimant failed because the contemporaneous records — chiefly the site diary — did not evidence the alleged delay path.
  • The discipline: select the method the records support, keep records worth analysing, and present facts first, models second.

This article is general information only and is not legal advice. For advice on a specific contract or dispute, seek legal counsel or contact Sumit Consulting for commercial and claims advisory support.

The record, delivered

The analysis, before you need it.

Commentary on Security of Payment, delay, variations and quantum — direct to your inbox as it's published. Unsubscribe any time.

Facing this issue on a live project?

The analysis above is general commentary, not advice. For your specific contract and records, talk to us directly.