© 2026 Zoe. All rights reserved.
Zoe is a legal information platform. Always consult the Federal Register of Legislation for authoritative text.
[2025] NSWCA 49
Court of Appeal (NSW)
2025-04-02
Gleeson JA at [1], Payne JA at [2], Griffiths AJA at [306]
Original judgment source is linked above.
Source: NSW Caselaw (www.caselaw.nsw.gov.au). Converted to plain text by ZoeLaw. Not the official version.
Medium Neutral Citation: Martinus Rail Pty Ltd v Qube RE Services (No.2) Pty Ltd [2025] NSWCA 49
Hearing dates: 4 and 5 December 2024
Date of orders: 2 April 2025
Decision date: 02 April 2025
Before: Gleeson JA at [1];
Payne JA at [2];
Griffiths AJA at [306]
Decision: (1) Appeal allowed.
(2) Cross-appeal dismissed.
(3) Summons seeking leave to appeal dismissed.
(4) Set aside:
(a) orders 1, 2, and 3 of the orders made on 26 September 2024 and orders 1, 2, 3, 4 and 7 of the orders made on 15 November 2024 in proceedings 2024/286961; and
(b) order 3 of the orders made on 26 September 2024 and order 2 of the orders made on 15 November 2024 in proceedings 2024/278963; and
(c) order 2 of the orders made on 15 November 2024 in proceedings 2024/278984.
(5) Vary order 6 of the orders made on 26 September 2024 (as varied by order 5 made on 15 November 2024) in proceedings 2024/286961 by deleting the words on and from the words “on terms” in that order.
(6) Vacate order 7 of the orders made on 26 September 2024 (as varied by order 6 made on 15 November 2024) in proceedings 2024/286961 (interlocutory regime pending appeal).
(7) Order that Qube’s summons filed 5 August 2024 in proceedings 2024/286961 is dismissed with costs.
(8) Order Qube to pay Martinus’s costs of the appeal, the cross-appeal and the application for leave to appeal.
Catchwords: BUILDING AND CONSTRUCTION – adjudication – judicial review – whether adjudication affected by jurisdictional error – principles of jurisdictional error under Building and Construction Industry Security of Payment Act 1999 (NSW)
ADMINISTRATIVE LAW – Judicial review – content of obligation “to consider” – whether failure specifically to refer to a matter reveals failure to consider that matter – scope of obligation to consider under Building and Construction Industry Security of Payment Act 1999 (NSW), s 22(2) – whether procedural unfairness established – whether decision legally unreasonable
Legislation Cited: Building and Construction Industry Payments Act 2004 (Qld)
Building and Construction Industry Security of Payment Act 1999 (NSW) ss 3, 8, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 25, 29, 32, 32A, 32B
Commercial Arbitration Act 2010 (NSW)
Cases Cited: Attorney-General for the States of New South Wales v Quin (1990) 170 CLR 1; [1990] HCA 21
Brodyn Pty Ltd t/as Time Cost and Quality v Davenport (2004) 61 NSWLR 42; [2004] NSWCA 394
Ceerose Pty Ltd v A-Civil Aust Pty Ltd (2023) 112 NSWLR 225; [2023] NSWCA 215
Chase Oyster Bar Pty Ltd v Hamo Industries Pty Ltd (2010) 78 NSWLR 393; [2010] NSWCA 190
Demex Pty Ltd v McNab Building Services Pty Ltd (2023) 113 NSWLR 282; [2023] NSWCA 261
Downer Construction (Australia) Pty Ltd v Energy Australia (2007) 69 NSWLR 72; [2007] NSWCA 49
Dualcorp Pty Ltd v Remo Constructions Pty Ltd (2009) 74 NSWLR 190; [2009] NSWCA 69
Hossain v Minister for Immigration and Border Protection (2018) 264 CLR 123; [2018] HCA 34
House v the King (1936) 55 CLR 499
Icon Co (NSW) Pty Ltd v Australia Avenue Developments Pty Ltd [2018] NSWCA 339
Iskra v MMIR Pty Ltd [2019] NSWCA 126
Ismail v Minister for Immigration, Citizenship and Multicultural Affairs (2024) 98 ALJR 196; [2024] HCA 2
John Holland Pty Ltd v Roads and Traffic Authority of New South Wales [2007] NSWCA 19
Joye Group Pty Ltd v Cemco Projects Pty Ltd [2021] NSWCA 211
Kennedy Civil Contracting Pty Ltd (Administrators Appointed) v Richard Crookes Construction Pty Ltd; In the matter of Kennedy Civil Contracting Pty Ltd [2023] NSWSC 99
Kruger v The Commonwealth (1997) 190 CLR 1; [1997] HCA 27
LPDT v Minister for Immigration, Citizenship, Migrant Services and Multicultural Affairs (2024) 98 ALJR 610; [2024] HCA 12
M1 v R1 [2024] NSWCA 256
Martinus Rail Pty Ltd v Qube RE Services (No 2) Pty Ltd (No 2) [2024] NSWSC 1223
Martinus Rail Pty Ltd v Qube RE Services (No 2) Pty Ltd (No 3) [2024] NSWSC 1483
Martinus Rail Pty Ltd v Qube RE Services (No 2) Pty Ltd [2023] NSWSC 1550
Minister for Home Affairs v DUA16 (2020) 271 CLR 550; [2020] HCA 46
Minister for Immigration and Border Protection v SZVFW (2018) 264 CLR 541; [2018] HCA 30
Minister for Immigration and Citizenship v Li (2013) 249 CLR 332; [2013] HCA 18
Minister for Immigration and Citizenship v SZIAI (2009) 83 ALJR 1123; [2009] HCA 39
Minister for Immigration and Multicultural Affairs v Eshetu (1999) 197 CLR 611; [1999] HCA 21
Probuild Constructions (Aust) Pty Ltd v Shade Systems Pty Ltd (2018) 264 CLR 1; [2018] HCA 4
R J Neller Building Pty Ltd v Ainsworth [2009] 1 Qd R 390; [2008] QCA 397
Secretary, Department of Education v Dawking [2024] NSWCA 4
Seymour Whyte Constructions Pty Ltd v Ostwald Bros Pty Ltd (in liq) (2019) 99 NSWLR 317; [2019] NSWCA 11
TFM Epping Land Pty Ltd v Decon Australia Pty Ltd [2020] NSWCA 118
Transgrid v Siemens Ltd (2004) 61 NSWLR 521; [2004] NSWCA 395
Texts Cited: M Aronson, M Groves and G Weeks, Judicial Review of Administrative Action and Government Liability (Thomson Reuters, 6th ed, 2017)
Category: Principal judgment
Parties: Martinus Rail Pty Ltd (appellant)
Qube RE Services (No.2) Pty Ltd (first respondent)
John Tuhtan (second respondent)
Representation: Counsel:
S Robertson SC, D Hume and A R Langshaw (appellant)
J Giles SC, T Boyle, and J Bridgett (first respondent)
Solicitors:
Maddocks Lawyers (appellant)
King & Wood Mallesons (first respondent)
File Number(s): 2024/00386902
2024/00386888
2024/00362269
Publication restriction: Nil
[This headnote is not to be read as part of the judgment]
These proceedings arose out of two adjudications under the Building and Construction Industry Security of Payment Act 1999 (NSW) (“SOP Act”) involving two separate contracts between Qube RE Services (No.2) Pty Ltd (“Qube”) and a sub-contractor Martinus Rail Pty Ltd (“Martinus”). The primary judge held that each of the adjudications was, in part, affected by jurisdictional error and set aside the affected parts of the adjudications.
Martinus appealed. Qube cross-appealed and filed a notice of contention. The essential issues raised by Matinus’s appeal and Qube’s notice of contention and cross-appeal were whether the adjudicator’s decisions with respect to a number of issues were affected by jurisdictional error either because of failure to consider submissions “duly made”, a breach of procedural fairness or legal unreasonableness.
In considering complaints of jurisdictional error, the Court first addressed the identification of jurisdictional error under the SOP Act.
The Court applied those principles to address the issues raised by the notice of appeal, the notice of contention and the notice of cross-appeal.
Finally, there was an issue about whether leave to appeal should be granted from the primary judge’s decision that Qube was not entitled to a stay of the adjudicator’s decision pending final determination of a commercial arbitration.
The Court (per Payne JA, Gleeson JA agreeing at [1] and Griffiths AJA agreeing at [30****6]), allowing the appeal and dismissing the cross-appeal, held:
On the identification of jurisdictional error under the SOP Act:
(1) The policy of the SOP Act is to ensure that a contractor who carries out construction work for a principal receives progress payments for carrying out that work. The risk that the contractor might not be able to refund moneys ultimately found to be due to the principal after a successful determination of the merits of the claim under the contract is a risk which is assigned to the principal. The clear policy of the SOP Act is to “pay now, fight later” to ensure cashflow to contractors, even if the contract has been terminated: at [3], [8], [292]-[294], [299], [303]. The SOP Act creates an entitlement that is to be determined informally, summarily and quickly and so the Court will not readily find jurisdictional error: at [45], [57], [68], [117], [237], [292]-[293]. This is so, even where the quantum of the claim is large and even where the adjudicator obtains an extension of time: at [45], [68].
Probuild Constructions (Aust) Pty Ltd v Shade Systems Pty Ltd (2018) 264 CLR 1; [2018] HCA 4; R J Neller Building Pty Ltd v Ainsworth [2009] 1 Qd R 390; [2008] QCA 397; Seymour Whyte Constructions Pty Ltd v Ostwald Bros Pty Ltd (in liq) (2019) 99 NSWLR 317; [2019] NSWCA 11 applied.
(2) The failure to identify a particular claim or response in reasons will not of itself demonstrate that the adjudicator failed to consider it. Even assuming the submission had been misunderstood, the facts mistaken or the law wrongly identified, that would explain absence from the reasons of something expected to be addressed but not lack of consideration. The duty to consider a submission is different from a duty to deal with it correctly, whether in law or in fact: at [67], [69], [73], [101], [148], [202]-[203], [211]-[213], [237]. Similarly, only if there has been a substantial denial of procedural fairness by an adjudicator will there be jurisdictional error under the SOP Act: at [117]
Probuild Constructions (Aust) Pty Ltd v Shade Systems Pty Ltd (2018) 264 CLR 1; [2018] HCA 4; Chase Oyster Bar Pty Ltd v Hamo Industries Pty Ltd (2010) 78 NSWLR 393; [2010] NSWCA 190; Ceerose Pty Ltd v A-Civil Aust Pty Ltd (2023) 112 NSWLR 225; [2023] NSWCA 215; Icon Co (NSW) Pty Ltd v Australia Avenue Developments Pty Ltd [2018] NSWCA 339; Brodyn Pty Ltd t/as Time Cost and Quality v Davenport (2004) 61 NSWLR 42; [2004] NSWCA 394*; Downer Construction (Australia) Pty Ltd v Energy Australia* (2007) 69 NSWLR 72; [2007] NSWCA 49; Demex Pty Ltd v McNab Building Services Pty Ltd (2023) 113 NSWLR 282; [2023] NSWCA 261 applied.
(3) It is for the adjudicator to determine the content and scope of the Payment Claim and the Payment Schedule, including the scope and content of the dispute between the parties: at [60]-[64], [80], [174], [186]-[187], [219]-[220], [234], [274]. It is for the adjudicator to determine the relationship between the detail contained in the Adjudication Response and the reason for non-payment provided in the Payment Schedule: at [104]. The adjudicator’s decision is valid even if he misconstrued the contract: [99], [107], [111]-[112], [131], [144], [160]-[161]. Findings of fact are matters for the adjudicator: at [190]. It is for the adjudicator to determine whether a submission has been “duly made”: at [65], [228], [274]. The weight to be accorded to a submission is a matter for the adjudicator: at [93], [95]. Even assuming that there was no reference to the matters identified by Qube in the adjudicator’s decision, it was not established that the adjudicator failed to consider any submission he regarded as “duly made”: at [97], [109].
John Holland Pty Ltd v Roads and Traffic Authority of New South Wales [2007] NSWCA 19; Downer Construction (Australia) Pty Ltd v Energy Australia (2007) 69 NSWLR 72; [2007] NSWCA 49; Joye Group Pty Ltd v Cemco Projects Pty Ltd [2021] NSWCA 211; Ceerose Pty Ltd v A-Civil Aust Pty Ltd (2023) 112 NSWLR 225; [2023] NSWCA 215; Icon Co (NSW) Pty Ltd v Australia Avenue Developments Pty Ltd [2018] NSWCA 339; Iskra v MMIR Pty Ltd [2019] NSWCA 126 applied.
(4) Failure to comply with s 22(2) is not helpfully characterised as procedural unfairness, but rather as failure to comply with a mandatory statutory obligation, the scope of which will be identified on quite a different basis: at [72].
(5) The principles of judicial restraint in finding jurisdictional error on the basis of legal unreasonableness apply even more stringently in addressing an adjudicator’s decision made under the SOP Act: at [75]-[80], [129]
Minister for Immigration and Citizenship v Li (2013) 249 CLR 332; [2013] HCA 18; Attorney-General for the States of New South Wales v Quin (1990) 170 CLR 1; [1990] HCA 21; Kruger v The Commonwealth (1997) 190 CLR 1; [1997] HCA 27; Minister for Immigration and Multicultural Affairs v Eshetu (1999) 197 CLR 611; [1999] HCA 21; Minister for Immigration and Citizenship v SZIAI (2009) 83 ALJR 1123; [2009] HCA 39; Ismail v Minister for Immigration, Citizenship and Multicultural Affairs (2024) 98 ALJR 196; [2024] HCA 2; Minister for Home Affairs v DUA16 (2020) 271 CLR 550; [2020] HCA 46; Minister for Immigration and Border Protection v SZVFW (2018) 264 CLR 541; [2018] HCA 30 applied.
Whether the adjudicator failed to consider submissions made by Qube in the Adjudication Response in relation to claim CN-420:
(6) The adjudicator dealt with all of the reasons advanced by Qube in its Payment Schedule for failing to pay Martinus’ claim and did not fall into jurisdictional error. Qube could not include in its Adjudication Response any reasons for withholding payment unless those reasons have already been included in its Payment Schedule. The adjudicator was under no obligation to explain why he did not expressly deal with every argument contained in the Adjudication Response: at [92]. [102]-[104], [108]-[110].
(7) In any event, the adjudicator did consider the relevant submissions: at [97]-[114].
Whether the adjudicator failed to consider submissions made by Qube in relation to an extension of time claim:
(8) No breach of the obligation to consider submissions “duly made” pursuant to s 22(2) of the SOP Act was established. The adjudicator dealt with Qube’s submissions to the extent necessary to determine the claim: at [120]-[128].
Whether the adjudicator had fallen into jurisdictional error by failing to consider Qube’s submissions in relation to the “Directions Show Cause Notice”:
(9) As Qube conceded, the primary judge proceeded from the incorrect understanding about the Qube submissions allegedly not taken into account: at [134], [146].
Whether the adjudicator failed to consider Qube’s alleged entitlement to terminate the contract “for cause” at common law*:*
(10) This point could not be agitated in absence of a notice of contention: at [151]-[153]. In any case, the submissions were considered by the adjudicator to the extent required: at [154].
Whether the adjudicator’s finding that the “Program Show Cause Notices” lacked sufficient detail was affected by procedural unfairness:
(11) There was no jurisdictional error. It was obvious that if Qube wished to rely on the notices, it would need to adequately state the alleged breaches. This was the subject of complaint by Martinus. It was not procedurally unfair for the adjudicator to come to the conclusion that the notices lacked sufficient detail: at [156]-[157].
Whether the adjudicator, in construing the contract, interpreted the contract in a legally unreasonable way:
(12) Even if the construction of the contract adopted by the adjudicator was incorrect, it was not legally unreasonable: at [158]
Whether the adjudicator’s conclusion that Martinus was entitled to apply a margin of 45.31% to works consequential on Qube’s termination was legally unreasonable:
(13) The adjudicator was entitled to characterise the work as a variation to the initial scope caused by Qube’s conduct. There was no jurisdictional error: at [161].
Whether the adjudicator’s conclusion that the appellant was entitled to the costs of “unfixed materials” was legally unreasonable because it effectively allowed double payment when considered alongside amounts awarded premised on the supply and installation of unfixed materials:
(14) The conclusion reached by the adjudicator was not legally unreasonable. The adjudicator gave reasons why Martinus was entitled to the cost of the supply of unfixed materials and, in any event, the adjudicator was entitled to conclude that it followed from Qube’s own assessment that there were materials which needed to be taken from the stockpile post-termination: at [162]-[163].
W**hether the adjudicator’s decision with respect to the bank guarantees was affected by jurisdictional error:
(15) There was no jurisdictional error. By adding the sum of the bank guarantee to the adjusted contract sum, Qube put in issue the value of the work. The “dispute propounded by the parties” which the adjudicator was empowered by the SOP Act to determine was that which arises after both the Payment Claim and the Payment Schedule have been considered. The meaning of the Payment Claim and the Payment Schedule were matters falling within the jurisdiction of the adjudicator: at [173]-[175]
Whether the adjudicator failed to consider submissions duly made by Qube with respect to the bank guarantees:
(16) There was no jurisdictional error. It was an impermissible incursion into the role of the adjudicator for the primary judge to construe the Payment Schedule as having “only set off” $463,703.76: at [176]
Whether the adjudicator failed to address the dispute between the parties with respect to “preliminaries” or otherwise decided on a basis that was procedurally unfair or legally unreasonable:
(17) There was no jurisdictional error. The primary judge erred in treating the scope of the “dispute” between the parties as if it was a matter for objective determination by the Court. The interpretation of the Payment Schedule was a matter for the adjudicator: at [186]-[188]
(18) The adjudicator’s interpretation of the Payment Claim and Payment Schedule was clearly open to him. It was a decision far removed from one affected by jurisdictional error as being legally unreasonable: at [195]
(19) It was not a denial of procedural fairness for the adjudicator to act upon his understanding of the law and rely on binding authority of the Court of Appeal: at [196]
Whether the adjudicator’s decision was legally unreasonable due to an arithmetical error:
(20) There was no jurisdictional error. The mathematical error was incorrectly characterised as an absence of a “reason”, when, at most, it was an incorrect reason. A mathematical computation is a finding of fact: at [190]-[192].
Whether the adjudicator failed to consider submissions made by Qube with respect to claim CN-421:
(21) It was permissible for the adjudicator to say that Qube had not provided an explanation. It was not a jurisdictional error to fail to refer to a document buried in Qube’s Payment Schedule, because it was within the adjudicator’s jurisdiction to determine that it was directed to a different issue. Even if the adjudicator misunderstood the submission, that does not mean that it was not considered: at [200]-[204].
Whether the adjudicator failed to consider submissions made by Qube in the Payment Schedule as to signal design management:
(22) There was no failure to consider Qube’s submission. Even if the adjudicator did not appreciate a subtlety in the submissions, that is not a jurisdictional error: at [205]-[215].
Whether the adjudicator failed to consider submissions made by Qube in the Adjudication Response as to wet weather costs:
(23) It was a matter for the adjudicator to construe Qube’s Payment Schedule and, having construed it, to form a view as to what (if any) valid reasons for withholding payment were given by Qube in that Payment Schedule. If the adjudicator was of the view that no valid reasons for withholding payment were given in the Payment Schedule, the adjudicator was obliged to decline to consider any further submissions on the issue contained in the Adjudication Response: at [216]-[221].
Whether the adjudicator was required to correct Qube’s Payment Schedule lest he be held to have acted in a legally unreasonable or procedurally unfair way:
(24) The adjudicator’s decision was not legally unreasonable. The adjudicator was not required to fix mistakes made by Qube in its Payment Schedule. There is no procedural unfairness in reading Qube’s Payment Schedule in the terms in which it was expressed: at [222]-[225], [230].
W**hether the adjudicator failed to consider submissions duly made by Qube in the Adjudication Response as to storm water pit design:
(25) Having concluded that Qube’s Payment Schedule did not give valid reasons because it responded to the wrong claim, the adjudicator did not fall into jurisdictional error: at [226]-[229].
Whether the adjudicator fell into jurisdictional error because he found the Payment Schedule was “incomprehensible”:
(26) Qube was free to adopt whatever methodology and format it wished to adopt in its Payment Schedule responding to Martinus’s Payment Claim. However, having chosen what was fairly described as a confusing method, it open to the adjudicator to find that it was not comprehensible. The adjudicator’s interpretation of the Payment Schedule and conclusion that it did not relevantly set out reasons on the relevant matters was open to him. There was no denial of procedural fairness, nor was it legally unreasonable. There is a risk with this type of argument that claims about failure to address matters can shade into claims about arguments being resolved incorrectly because misunderstood, or not really grappled with, which tends towards merits or appellate review: at [244]-[288].
M1 v R1 [2024] NSWCA 256 applied.
Whether leave to appeal should be granted from the primary judge’s decision that Qube was not entitled to a stay of the adjudicator’s decision pending final determination of a commercial arbitration*:*
(27) Leave to appeal was refused. The grant of a stay until the end of the arbitration would be contrary to the statutory purpose of the SOP Act. There is a heavy burden on a party who seeks injunctive relief or a stay pending the outcome of proceedings contemplated by s 32 of the SOP Act on the basis that a payment may become unrecoverable due to the possible or even likely insolvency of the payee at a later date: at [8], [290]-[304].
Probuild Constructions (Aust) Pty Ltd v Shade Systems Pty Ltd (2018) 264 CLR 1; [2018] HCA 4; R J Neller Building Pty Ltd v Ainsworth [2009] 1 Qd R 390; [2008] QCA 397; Kennedy Civil Contracting Pty Ltd (Administrators Appointed) v Richard Crookes Construction Pty Ltd; In the matter of Kennedy Civil Contracting Pty Ltd [2023] NSWSC 99*; Colbran, in the matter of PBS Building Pty Limited (Administrators Appointed)* [2023] FCA 276 applied.
GLEESON JA: I agree with Payne JA.
PAYNE JA: These proceedings arose out of two adjudications under the Building and Construction Industry Security of Payment Act 1999 (NSW) (“SOP Act”) involving two separate contracts between the same parties. The adjudications obliged the head contractor (Qube RE Services (No.2) Pty Ltd (“Qube”)) to pay $71 million in total to the sub-contractor (Martinus Rail Pty Ltd (“Martinus”)). The proceedings before the primary judge, Parker J, involved a complaint by Qube that each of the adjudications was affected by jurisdictional errors. The primary judge upheld a number of complaints of jurisdictional error and set aside the affected parts of the adjudications, relying upon s 32A of the SOP Act. Martinus appealed against the findings of jurisdictional error. Qube cross-appealed against the findings of the primary judge where his Honour had not found jurisdictional error.
As I will explain in detail, the policy of the SOP Act is to ensure that a contractor who carries out construction work for a principal receives progress payments for carrying out that work. The risk that the contractor might not be able to refund moneys ultimately found to be due to the principal after a successful action under the contract is a risk which is assigned to the principal. The SOP Act creates an entitlement that is to be determined informally, summarily and quickly, and then summarily enforced without prejudice to the rights of both parties to the construction contract which can be determined in due course: Probuild Constructions (Aust) Pty Ltd v Shade Systems Pty Ltd (2018) 264 CLR 1; [2018] HCA 4 at [44] (Kiefel CJ, Bell Keane, Nettle and Gordon JJ); R J Neller Building Pty Ltd v Ainsworth [2009] 1 Qd R 390; [2008] QCA 397 at [39]-[40] per Keane JA (discussing the equivalent Queensland statute, the Building and Construction Industry Payments Act 2004 (Qld)). It was confirmed by the High Court in Shade Systems that judicial review of an adjudicator’s determination is available, but only for jurisdictional error on the part of the adjudicator.
There was no debate in the present case about the correct identification by the primary judge of the legal principles to be applied in finding an adjudication under the SOP Act to be affected by jurisdictional error. What was controversial was the application of those principles and, in particular, the inferences the primary judge drew about the internal reasoning processes of the adjudicator.
The adjudicator in the present case was faced in this case with over 15,700 pages of material. Over 5000 pages were contained in Qube’s Adjudication Response. The adjudicator expressly stated that he had considered Qube’s Payment Schedule together with all submissions, including relevant documentation, that had been properly made by Qube in support of the Payment Schedule: at [145]. The adjudicator returned to this issue, and repeated that in making his adjudication he had considered all submissions that, in his view, had been duly made by Qube:
[194] I have then considered each amount claimed, the reasons for withholding payment, the calculation of quantum as proffered by the Claimant and the Respondent, the parties’ rights and obligations under the Contract, submissions properly made and determined each disputed claim separately.
Despite the adjudicator’s 550 pages of reasons explaining how the adjudicator had taken Qube’s submissions and relevant documentation into account, Qube advanced challenges to 37 separate components of the adjudications as comprising jurisdictional error, on the principal basis that the adjudicator had “failed to consider” some matter contained in Qube’s Adjudication Response.
The primary judge inferred that the adjudicator had failed to consider a number of matters contained in Qube’s Adjudication Response and thus had fallen into jurisdictional error for the purposes of s 22(2) of the SOP Act. As I will explain in detail, I have concluded that Qube failed to prove that the adjudicator failed to consider the matters complained about by Qube for the purposes of the SOP Act. Further, I am not satisfied that any of the grounds of Qube’s notice of contention are made out nor that Qube has established any of the grounds of its cross-appeal. It follows that the appeal should be allowed and the cross-appeal dismissed.
Finally, the primary judge refused to stay the orders that his Honour made until the determination of the underlying arbitration proceedings, which have now been commenced. His Honour was correct to do so. The clear policy of the SOP Act is to “pay now, fight later”. The grant of a stay until the end of the arbitration would be contrary to the statutory purpose of the SOP Act. The primary judge was correct to refuse to grant a stay until the determination of the underlying arbitration proceedings. Leave to appeal that order should be refused.
The contracts in question related to an infrastructure development in Moorebank known as the Moorebank Intermodal Terminal Project which is being carried out by a Commonwealth government business enterprise named National Intermodal. The contract between National Intermodal and Qube is known as the “Development and Operation Deed”.
The two sub-contracts at the heart of this case between Qube and Martinus were both dated July 2022. They are styled “Interstate Terminal Works Contract” dated 8 July 2022 (“INTS Contract”) and “Interstate Rail Access Works Contract” of the same date (“ISRA Contract”).
At the heart of the dispute are delays which occurred on the project. Martinus claimed that it was not responsible for the delays and that Qube was liable for additional costs caused by those delays. Martinus claimed that necessary designs were delivered late or were otherwise inadequate and that Qube failed to give access to the site, in some cases by more than a hundred days after the originally scheduled date, causing Martinus to incur substantial additional costs.
The administration of the contracts took place under the direction of a superintendent appointed by Qube (the “Superintendent”), Mr Marshall of Rail Planning Services Pty Limited.
Martinus’s Payment Claims under the SOP Act for the period up to 31 May 2023 were determined in August 2023 by an adjudicator, Mr Stapleton. The adjudicated amount in favour of Martinus was $11.1 million. That amount was paid by Qube and is not the subject of dispute in these proceedings.
In August 2023, Qube issued formal notices invoking the show cause procedure required for termination of the contracts. On 25 September 2023, Qube issued formal notices of termination for cause. On the same date, Qube issued formal notices of termination for convenience to take effect if the terminations for cause proved to be invalid. It is common ground that the contracts were terminated on 25 September 2023.
Martinus’s Payment Claims under the contracts for the period up to 31 August 2023 were determined in November 2023 by Mr Stapleton. The adjudicated amount in favour of Martinus was $4.6 million. That amount was also paid by Qube and is not the subject of dispute in these proceedings.
In early December 2023, Qube issued formal notices of dispute under the dispute resolution clauses of the contracts. Qube alleged that it was entitled to substantial damages from Martinus for breach of contract, and to reimbursement of moneys which Qube said should not have been allowed in the adjudications before Mr Stapleton.
Following the issue of the notices of dispute, Martinus applied under the Commercial Arbitration Act 2010 (NSW) for an injunction restraining Qube from calling on the bank guarantees provided as security for Martinus’s obligations under the contracts. Rees J dismissed the application: Martinus Rail Pty Ltd v Qube RE Services (No 2) Pty Ltd [2023] NSWSC 1550. Although the injunction was refused, Qube did not call on the bank guarantees until 8 February 2024.
The Payment Claims which resulted in the proceedings below were made on 8 February 2024, in ignorance of the call by Qube on the same day of the bank guarantees. On 22 February 2024, Qube lodged a Payment Schedule in relation to each Payment Claim. Qube alleged that under each contract it was owed money by Martinus. The scheduled amounts were credits in favour of Qube of $1.4 million for the INTS Contract and $1.4 million for the ISRA Contract.
Qube elected not to put its Payment Schedules in a format which corresponded with the items in Martinus’s Payment Claims. Instead, Qube adopted its own methodology and format. This made it difficult to understand Qube’s position on a number of issues.
On 7 March 2024, Martinus made Adjudication Applications seeking payment of $104.1 million under the INTS Contract and $33.3 million under the ISRA Contract. Martinus complained that the form of Qube’s Payment Schedules made it difficult to understand what Qube was saying. The Adjudication Applications were referred to another adjudicator, Mr Tuhtan. On 15 March 2024, Qube provided its Adjudication Response. Qube said then, and repeated in this Court, that the Payment Schedules were not difficult to understand.
The adjudicator ultimately concluded that the Payment Schedule was difficult to comprehend, and that Qube had not explained its reasons for rejecting each of Martinus’s claims. As I will explain, that conclusion was not only open to the adjudicator, but was clearly correct.
The adjudication proceedings before Mr Tuhtan were complex, protracted and costly. Mr Tuhtan delivered his Adjudication Determinations on 22 July 2024. He determined that payments should be made by Qube of $63.1 million under the INTS Contract and $7.1 million under the ISRA Contract. He also decided that Qube should pay the whole of the costs of the adjudications. The adjudicator’s fees totalled $543,000 which was split $209,000 for the ISRA adjudication and $334,000 for the INTS adjudication.
The dispute resolution clause in the contracts provided for an elaborate dispute resolution process. On 2 February 2024, Qube gave notices pursuant to the dispute resolution procedure under the contracts escalating the dispute to executive level. A mediation took place unsuccessfully and it seems there were no further attempts at resolution. On 27 March 2024, while the adjudication proceedings were pending, Qube issued formal notices of referral to arbitration under the contracts. On 26 July 2024, four days after delivery of the adjudicator’s determinations, Qube served notices of arbitration under the rules of the Resolution Institute, the body responsible for the arbitration under the contracts.
Under the SOP Act the time for payment of the adjudicated amounts was 29 July 2024. Qube did not pay the adjudicated amounts by the due date and the commencement of the proceedings below followed soon after.
There were three proceedings before the primary judge. The first two proceedings (2024/278963 and 2024/278984) were commenced by Martinus to enforce payment of the adjudicated amounts under the SOP Act (which I will call “the first and second enforcement proceedings”).
Adjudication certificates were filed on 30 July commencing the enforcement proceedings. On 31 July 2024, judgments were entered, pursuant to s 25 of the SOP Act. For the INTS Contract the judgment amount was $66.087 million. For the ISRA Contract the judgment amount was $7.595 million.
On 5 August 2024, Qube filed its own proceedings (2024/286961) seeking to set aside the determinations on the grounds of alleged jurisdictional errors on the part of the adjudicator.
On 9 August 2024, the following orders of remaining relevance were made by Ball J:
Interlocutory regime
(a) By 5.00pm Friday, 9 August 2024 Qube pays the sum of $4,010,108.43 in cleared funds to the Judgment creditor (“Martinus”). (b) By 5.00pm Tuesday, 13 August 2024 Qube provides to the Associate to Ball J:
(i) an unconditional bank guarantee in favour of Martinus issued by Westpac Banking Corporation in the sum of $62,707,365.90; and (ii) an unconditional bank guarantee in favour of Martinus issued by Westpac Banking Corporation in the sum of $7,671,781.73.
Evidence and Hearing
(a) proceedings 2024/286961 (“Judicial Review Proceedings”); (b) paragraph 1 of the amended notices of motion filed by Qube on 2 August 2024 in proceedings 2024/278963 and 2024/278984 (“Grosvenor Applications”); and (c) paragraph 1 of the notice of motion filed by Martinus on 31 July 2024 in proceedings 2024/278963 and 2024/278984 (“Garnishee Applications”),
are set down for hearing on 4 and 5 September 2024 (“Hearing”).
….
As envisaged by Ball J’s orders, the primary judge heard the proceedings together on 4, 5 and 6 September 2024 and promptly delivered reasons and made orders on 26 September 2024. The orders made in the judicial review proceedings were:
Order pursuant to s 32A of the Building and Construction Industry Security of Payment Act 1999 (NSW):
(a) that the adjudication determination dated 22 July 2024 (ABCDRS NSW 586) (INTS Determination) is set aside in the amount over and above $22,703,118.54 including GST and interest; (b) that the said adjudication determination be confirmed as the Adjudicated Amount of $22,703,118.54 including GST and interest.
(a) giving the usual undertaking as to damages; and (b) Qube continuing to pay one month’s interest at a daily rate of $16,942.76 on the last day of each month thereafter until this stay is dissolved or any appeal is determined,
order that:
(c) order 6 of these orders is stayed; (d) the First Defendant is restrained from taking any steps by way of enforcement of the judgment referred to in order 3 of these orders (being the varied judgment entered in proceedings 2024/278983) or the judgment entered in proceedings 2024/278984,
until further order of this Court in this Division or by the Court of Appeal.
Costs be reserved.
The orders made in the first enforcement proceedings were:
Order that the amended notice of motion filed 2 August 2024 is dismissed.
Costs be reserved.
Order that the judgment entered in these proceedings on 31 July 2024 is varied by changing the “Claim amount” to $22,925,489.49 and the “TOTAL” amount to $22,925,711.49.
The orders made in the second enforcement proceedings were:
Order that the amended notice of motion filed 2 August 2024 is dismissed.
Costs be reserved.
As I have said, the primary judge’s first judgment was delivered on 30 September 2024: Martinus Rail Pty Ltd v Qube RE Services (No 2) Pty Ltd (No 2) [2024] NSWSC 1223 (the “September judgment”). This decision did not, however, deal with all of the claims made in the proceedings. Following a further hearing on 18 and 21 October 2024, the remaining claims were determined on 15 November in Martinus Rail Pty Ltd v Qube RE Services (No 2) Pty Ltd (No 3) [2024] NSWSC 1483 (the “November judgment”).
The orders made in the November judgment in the judicial review proceedings were:
INTS Determination
(a) that the adjudication determination dated 22 July 2024 (ABCDRS NSW 586) (INTS Determination) is set aside in the amount over and above $17,247,488.19 including GST; (b) that the said adjudication determination be confirmed as the Adjudicated Amount of $17,247,488.19 including GST.
ISRA Determination
(a) that the adjudication determination dated 22 July 2024 (ABCDRS NSW 585) (ISRA Determination) is set aside in the amount over and above $6,936,389.69 including GST; (b) that the said adjudication determination be confirmed as the Adjudicated Amount of $6,936,389.69 including GST.
Bank Guarantees
Order that the unconditional bank guarantees provided to the Court in compliance with order 1(b) of the orders made on 9 August 2024 be provided to the First Defendant on terms that:
(a) the First Defendant may not make a demand under the unconditional bank guarantee provided to the Court in compliance with order 1(b)(i) of the orders made on 9 August 2024 in an amount exceeding the amount owing under the judgment entered in proceedings 2024/278963 as varied; and (b) the First Defendant may not make a demand under the unconditional bank guarantee provided to the Court in compliance with order 1(b)(ii) of the orders made on 9 August 2024 in an amount exceeding the amount owing under the judgment entered in proceedings 2024/278984 as varied.
Stay
(a) giving the usual undertaking as to damages; and (b) Qube continuing to pay into court one month’s interest at a daily rate of $16,942.76 on the last day of each month thereafter until this stay is dissolved or any appeal is determined, order that: (c) order 6 of these orders is stayed; (d) the First Defendant is restrained from taking any steps by way of enforcement of the judgments entered in proceedings 2024/278963 and 2024/278984, until further order of this Court in this Division or by the Court of Appeal.
Costs
The Plaintiff is to pay the First Defendant’s costs of the challenges to the components of the INTS and ISRA Determinations on which it was unsuccessful and/or not pressed, insofar as those costs were additional and incurred solely in respect of those challenges, and otherwise the First Defendant is to pay the Plaintiff’s costs of the proceedings.
The orders made in the November judgment in the first enforcement proceedings were:
The judgment debtor is to pay the judgment creditor’s costs of the notice of motion filed 31 July 2024 (including as subsequently amended) insofar as those costs are solely referrable to the issues raised in this proceeding.
Order that the judgment entered in these proceedings on 31 July 2024 is varied by changing the ”Claim amount” to $18,165,684.76 and the ”TOTAL” amount to $18,165,684.76.
The orders made on in the November judgment in the second enforcement proceedings were:
The judgment debtor is to pay the judgment creditor’s costs of the notice of motion filed 31 July 2024 (including as subsequently amended) insofar as those costs are solely referable to the issues raised in this proceeding.
Order that the judgment entered in these proceedings on 31 July 2024 is varied by changing the ”Claim amount” to $7,447,619.38 and the ”TOTAL” amount to $7,447,619.38.
In the September judgment and the November judgment, the primary judge, having found jurisdictional error, also set aside the order requiring Qube to pay 100% of the adjudicator’s fees and expenses for that determination. The practical effect of that order was that each side was responsible for 50% of the adjudicator’s costs.
The notice of appeal attacks the primary judge’s findings of jurisdictional error. The notice of contention and notice of cross-appeal address virtually all of the remaining issues which were before the primary judge. Rather than summarising the contents of the September judgment and the November judgment at this stage, I will address the relevant findings in those judgments when dealing with the notice of appeal, notice of contention and notice of cross-appeal.
No jurisdictional error in relation to “CN-420- Vehicle Management Plan**”**
1 The primary judge erred in finding (at [157] of the reasons for judgment delivered on 30 September 2024 (J1)) that the determination made by the Second Respondent (Adjudicator) under the Building and Construction Industry Security of Payment Act 1999 (NSW) (Act) on 22 July 2024 (INTS Determination) was affected by jurisdictional error insofar as it dealt with “CN-420 - Vehicle Management Plan”.
No jurisdictional error in relation to “CN 277.5 - EOT 34 Update 2”
2 The primary judge erred in finding (at [197] of J1) that the INTS Determination was affected by jurisdictional error insofar as it dealt with “CN-420 - Vehicle Management Plan”.
No jurisdictional error in relation to “CN-522- Termination for Convenience”
3 The primary judge erred in finding (at [235] of J1) that the INTS Determination was affected by jurisdictional error insofar as it dealt with “CN-522 - Termination for Convenience”.
No jurisdictional error in relation to “Bank guarantees”
4 The primary judge erred in finding (at [290] and [303] of J1) that the INTS Determination was affected by jurisdictional error insofar as it dealt with “Bank guarantees”.
Adjudicator’s determination as to fees and expenses should not have been set aside
5 The primary judge erred in concluding (at [316] of J1) that the Adjudicator’s determination under s 29(3) of the Act as to the parties’ liability to contribute to the payment of his fees and expenses should be set aside. That conclusion was in error because it was based on the findings of jurisdictional error referred to in grounds 1 to 4 above.
No jurisdictional error in relation to “Preliminaries”
6 The primary erred in finding (at [39]-[45] and [46]-[53] of the reasons for judgment dated 15 November 2024 (J2)) that the INTS Determination was affected by jurisdictional error insofar as it dealt with “Preliminaries”.
No jurisdictional error in relation to “Design management resources CN 421 (INTS)”
7 The primary judge erred in finding (at [65] of J2) that the INTS Determination was affected by jurisdictional error insofar as it dealt with “Design management resources CN 421 (INTS)”.
No jurisdictional error in relation to “Signal design management CN 422 (INTS)”
8 The primary judge erred in finding (at [75] of J2) that the INTS Determination was affected by jurisdictional error insofar as it dealt with “Signal design management CN 422 (INTS)”.
No jurisdictional error in relation to “Wet weather recovery variation CN 451 (INTS)”
9 The primary judge erred in finding (at [100] of J2) that the INTS Determination was affected by jurisdictional error insofar as it dealt with “Wet weather recovery variation CN 451 (INTS)”.
No jurisdictional error in relation to “Storm pit design clashes CN 299 (ISRA)”
10 The primary judge erred in finding (at [131]-[132] of J2) that the determination made by the Adjudicator under the Act on 10 July 2024 (ISRA Determination) was affected by jurisdictional error insofar as it dealt with “Storm pit design clashes CN 299 (ISRA)”.
No jurisdictional error in relation to “Termination of intertrack drainage CN-353 (ISRA)”
11 The primary judge erred in finding (at [139] of J2) that the ISRA Determination was affected by jurisdictional error insofar as it dealt with “Termination of intertrack drainage CN-353 (ISRA)”.
1 The primary judge erred in finding at PJ2 [177]-[ 178] that there was no jurisdictional error in the decision of the Second Cross Respondent (the adjudicator) in circumstances where the adjudicator’s apparent conclusion that the payment schedule could not be understood:
a. involved a denial of procedural fairness, because the notion that the payment schedule could not be comprehended by the First Cross Respondent (Martinus) was never raised by Martinus or raised with the Cross Appellant and Martinus had in fact dealt with the substantive issue between the parties at length (see PJ2 [168]-[169]);
b. involved a constructive failure to exercise jurisdiction, because the concluded incomprehensibility or incoherence led the adjudicator into an error that meant he failed to apply himself to the real question to be decided (including by reference to the extensive submissions that were ‘duly made’ under s 22 of the Building and Construction Industry Security of Payment Act 1999 (NSW)) (see PJ2 [172]); and/or
c. was so unreasonable and irrational as to be infected by jurisdictional error in circumstances where the adjudicator adopted a position on the payment schedule that was inconsistent with the position that had been adopted by Martinus, viz. to conclude the payment schedule gave no reasons for withholding payment because it was allegedly incoherent when Martinus had engaged with the substance of the Cross Appellant’s reasons for withholding payment in submissions and had sought to meet the Cross Appellant’s reasons with evidence.
2 The primary judge erred in finding at PJ2 [179]-[ 181 ] that there was no jurisdictional error in the decision of the adjudicator in circumstances where the adjudicator’s apparent conclusion that the payment schedule could not be understood and that no reasons had been given by the Cross Appellant in the payment schedule in respect of the Contract works variations 2.1-2.6, 2.8-2.9, 2.11, 2.14-2.15 and 2.17:
a. relied on the same reasons as addressed in ground 1 above; and
b. was infected by the same jurisdictional errors identified in ground 1 above.
3 If ground 1 or ground 2 above is successful then the primary judge would (and should) have determined that the First Cross Respondent ought to have been ordered to pay 50% of costs of the adjudication in respect of the ISRA Contract (see PJ2 [316]-[317] and PJ3 [141 ]-[153]).
Jurisdictional error in relation to “CN-420 - Vehicle Management Plan”
1 The primary judge’s finding of jurisdictional error at [157] of the primary judgment (PJ2) was correct for the additional reason that the second respondent’s (the adjudicator) decision was made in circumstances where there was a denial of procedural fairness, in that no argument was ever put forward by the appellant that the relevant directions were “deemed to be variation orders” or were variation orders “for all intents and purposes”: see PJ2 [134] and [158]. This error was material in the requisite sense because treating the relevant directions as variation orders had the consequence that a markup of 45.31% was applicable to the works in question in light of a previous adjudicator’s decision.
Jurisdictional error in relation to “CN 277.5 - EOT 34 Update 2”
2 The primary judge’s finding of jurisdictional error at PJ2 [197] was correct for the additional reason that the adjudicator’s decision was made in circumstances where it was so unreasonable and irrational as to be infected by jurisdictional error (cf PJ2 [192]).
Jurisdictional error in relation to “CN-522 - Termination for Convenience”
3 The primary judge’s finding of jurisdictional error at PJ2 [290] and [303] was correct for the additional reasons that the adjudicator’s decision was made in circumstances where:
a. the adjudicator failed to consider submissions ‘duly made’ in relation to substantial breaches relied upon by the first respondent as justification for the exercise of a contractual right to terminate the Contracts “for cause”, in answer to a claim by the appellant for amounts under clause 40A of the Contracts (PJ2 [206] - [212], [220]-[222]);
b. the adjudicator’s apparent finding that the “Program Show Cause Notice” was not a valid notice (PJ2 [218]) was reached without affording procedural fairness to the first respondent, not having been an argument that was put forward by the appellant (PJ2 [221]) and never having been raised by the second respondent;
c. the adjudicator failed to consider submissions duly made by the first respondent with respect the limits of recovery under clause 40A of the Contracts;
d. it was so unreasonable and irrational as to be infected by jurisdictional error, in that the adjudicator determined to treat the claim as a “variation” and thus apply a 45.31% mark up to the claimed costs despite the lack of any textual basis or justification for this in clause 40A of the Contracts (and when the termination of the Contracts was never claimed to constitute or involve a “variation” within the meaning of clause 36); and
e. it was, further, so unreasonable and irrational as to be infected by jurisdictional error when the adjudicator determined that the appellant was entitled to amounts under clause 40A in respect of the costs of “unfixed materials” where he did not thereafter reconcile those claims with other amounts claimed and awarded in respect of related contract works items (being items premised on the supply and installation of unfixed materials - and incorporation of those unfixed materials into the works), such that the appellant would practically be paid twice for the same materials.
Determination as to fees and expenses
4 The primary judge’s conclusion (PJ2 [316]) was correct because the findings of jurisdictional error were correct, including for the reasons set out in the above grounds of this notice.
Jurisdictional error in relation to “Preliminaries”
5 The primary judge’s finding of jurisdictional error at [39]-[45] and [51] of Martinus Rail Pty Ltd v Qube RE Services (No 2) Pty Ltd (No 3) [2024] NSWSC 1483 (PJ3) were correct for the additional reasons that the adjudicators decision was made in circumstances where:
a. the adjudicator’s finding that there were “no reasons for withholding payment save for providing its method of calculating the value of the Preliminaries” (extracted at PJ3 [16]) was reached without affording procedural fairness to the first respondent, not having been an argument that was put forward (see PJ3 [18] and [37]-[38]);
b. the adjudicator had awarded more than was sought by the appellant which involved a denial of procedural fairness; and
c. it was so unreasonable as to be infected by jurisdictional error, in that the adjudicator:
i. found there were “no reasons for withholding payment save for providing its method of calculating the value of the Preliminaries” (extracted at PJ3 [16]) when this was inconsistent with the first respondent’s payment schedule and adjudication response (see PJ3 [19]); and
ii. had awarded more than the amount which the appellant had sought in its payment claim.
Jurisdictional error in relation to “Wet weather recovery variation CN451 (INTS)”
6 The primary judge’s finding of jurisdictional error at PJ3 [ 100] was correct for the additional reasons that the adjudicator’s decision was made in circumstances where:
a. it was so unreasonable as to be infected by jurisdictional error, in that he effectively treated obvious typographical errors in the payment schedule as entitling him to disregard the first respondent’s adjudication response and ignore that the appellant had substantively responded to the first respondent’s contentions, the appellant having understood the issues despite the typographical errors; and
b. there was a denial of procedural fairness because he proceeded on the basis that the typographical errors meant no reasons had been given (see PJ3 at [98]-[99]) and he could therefore simply adopt the appellant’s claimed value.
Jurisdictional error in relation to “Storm pit design clashes CN299 (ISRA)”
7 The primary judge’s finding of jurisdictional error at PJ3 [131]-[132] was correct for the additional reasons that the adjudicator’s decision was made in circumstances where:
a. it was so unreasonable as to be infected by jurisdictional error, in that he effectively treated obvious typographical errors in the payment schedule as entitling him to disregard the first respondent’s adjudication response and ignore that the appellant had substantively responded to the first respondent’s contentions, having understood the issues despite the typographical errors; and
b. there was a denial of procedural fairness because he proceeded on the basis that the typographical errors (see PJ3 [127]) meant no reasons had been given (PJ3 [128]) and he could therefore simply adopt the appellant’s claimed value (see PJ3 [131]).
Jurisdictional error in relation to “Termination of intertrack drainage CN353 (ISRA)”
8 The primary judge’s finding of jurisdictional error at PJ3 [140] was correct for the additional reasons that the adjudicators decision was made in circumstances where:
a. the adjudicator had awarded more than was sought by the appellant which involved a denial of procedural fairness (see PJ3 [134]-[137]); and
b. it was so unreasonable as to be infected by jurisdictional error, in that the adjudicator had awarded more than the amount which the appellant had sought by its adjudication application.
I will first address the issues raised by the notice of appeal and notice of contention before moving to the issues raised by the notice of cross-appeal.
Qube also moved upon an application for leave to appeal from the refusal of a stay pending the outcome of the arbitration referred to at [23] above. Rather than take up space in what is already a lengthy judgment, I will address the relevant principles and authorities when dealing with the application for leave to appeal.
[23] Jurisdiction, in the most generic sense in which it has come to be used in this field of discourse, refers to the scope of the authority that is conferred on a repository. In its application to judicial review of administrative action the taking of which is authorised by statute, it refers to the scope of the authority which a statute confers on a decision-maker to make a decision of a kind to which the statute then attaches legal consequences. It encompasses in that application all of the preconditions which the statute requires to exist in order for the decision-maker to embark on the decision-making process. It also encompasses all of the conditions which the statute expressly or impliedly requires to be observed in or in relation to the decision-making process in order for the decision-maker to make a decision of that kind. A decision made within jurisdiction is a decision which sufficiently complies with those statutory preconditions and conditions to have “such force and effect as is given to it by the law pursuant to which it was made” [Minister for Immigration and Multicultural Affairs v Bhardwaj (2002) 209 CLR 597 at [46]].
[24] Jurisdictional error, in the most generic sense in which it has come to be used to describe an error in a statutory decision-making process, correspondingly refers to a failure to comply with one or more statutory preconditions or conditions to an extent which results in a decision which has been made in fact lacking characteristics necessary for it to be given force and effect by the statute pursuant to which the decision-maker purported to make it. To describe a decision as “involving jurisdictional error” is to describe that decision as having been made outside jurisdiction [Bhardwaj at [17]]. A decision made outside jurisdiction is not necessarily to be regarded as a “nullity”, in that it remains a decision in fact which may yet have some status in law [Bhardwaj at [46]; Jadwan Pty Ltd v Department of Health and Aged Care (2003) 145 FCR 1 at [42]]. But a decision made outside jurisdiction is a decision in fact which is properly to be regarded for the purposes of the law pursuant to which it was purported to be made as “no decision at all” [Bhardwaj at [51]]. To that extent, in traditional parlance, the decision is “invalid” or “void” [Baxter v NSW Clickers’ Association (1909) 10 CLR 114 at 157; Probuild at [63]].
[2] Jurisdictional error can refer to breach of an express or implied condition of a statutory conferral of decision-making authority which results in a decision made in the purported exercise of that authority lacking the legal force attributed to exercise of that authority by statute. Though a decision affected by jurisdictional error is a decision in fact, [Oakey Coal Action Alliance Inc v New Acland Coal Pty Ltd (2021) 272 CLR 33 at [94]; Minister for Immigration, Citizenship, Migrant Services and Multicultural Affairs v Moorcroft (2021) 273 CLR 21 at [20]] it is “in law ... no decision at all” [Minister for Immigration and Multicultural Affairs v Bhardwaj (2002) 209 CLR 597 at [53]] and is in that sense “void”. [Hossain v Minister for Immigration and Border Protection (2018) 264 CLR 123 at 133 [24], 143 [62]]
[3] Because an express or implied condition of a statutory conferral of decision‑making authority can take many different forms, and because breach can occur in many different circumstances, the categories of jurisdictional error are not closed [Kirk v Industrial Court (NSW) (2010) 239 CLR 531 at 573 [71], 574 [73]; Minister for Immigration and Border Protection v SZMTA (2019) 264 CLR 421 at 455 [81], citing Minister for Immigration and Multicultural Affairs v Yusuf (2001) 206 CLR 323 at 351 [82]]. Jurisdictional error can result from breach by a third party of a condition of a statutory process preceding a decision, [See, eg, Wei v Minister for Immigration and Border Protection (2015) 257 CLR 22 at 32-33 [23]-[24], 35 [32]-[33]; SZMTA (2019) 264 CLR 421 at 444 [44]] but more often results from breach by a statutory decision-maker of a condition of the making of a decision. Jurisdictional error on the part of a statutory decision-maker in making a decision can include: misunderstanding the applicable law; asking the wrong question; exceeding the bounds of reasonableness; identifying a wrong issue; ignoring relevant material; relying on irrelevant material; in some cases, making an erroneous finding or reaching a mistaken conclusion; or failing to observe some applicable requirement of procedural fairness [See, eg, Craig v South Australia (1995) 184 CLR 163 at 179; Kirk (2010) 239 CLR 531 at 572 [67]; Hossain (2018) 264 CLR 123 at 134‑135 [30], 147-148 [70]-[72]; SZMTA (2019) 264 CLR 421 at 455 [81]].
[4] A statute which contains an express or implied condition of a conferral of decision-making authority is not always to be interpreted as denying legal force and effect to every decision that might be made in breach of that condition [Project Blue Sky Inc v Australian Broadcasting Authority (1998) 194 CLR 355 at 388-389 [91]]. Only by construing the statute so as to understand the limits of the statutory conferral of decision‑making authority is it possible to determine, first, whether an error has occurred (that is, whether there has been a breach of an express or implied condition of the statutory conferral of decision‑making authority) and, second, whether any such error is jurisdictional (that is, whether the error has resulted in the decision made lacking legal force) [Hossain (2018) 264 CLR 123 at 133 [24], 133‑134 [27], 147 [72]; SZMTA (2019) 264 CLR 421 at 456 [83]; Minister for Immigration, Citizenship, Migrant Services and Multicultural Affairs v Thornton (2023) 276 CLR 136 at 154-155 [53]].
[5] Determining whether an error exists as well as whether it is jurisdictional starts with an analysis of the nature of the error alleged in the statutory context within which the decision has been made. Given the broad range of decisions in which errors might be made, the large variety of statutory schemes in which those decisions might be made, and the range of circumstances which may attend the making of any particular decision, it is impossible to divine a rigid classification of the errors that constitute jurisdictional errors [See Kirk (2010) 239 CLR 531 at 574 [73]; Hossain (2018) 264 CLR 123 at 137 [42]]. There are no bright lines to be drawn – “[t]he nature of the error has to be worked out in each case concerning a specific decision under a particular statute” [MZAPC v Minister for Immigration and Border Protection (2021) 273 CLR 506 at 543 [101]; Nathanson v Minister for Home Affairs (2022) 276 CLR 80 at 117-118 [78]; Thornton (2023) 276 CLR 136 at 162 [77]].
[51] Finally, it takes the matter no further to say, as Probuild submitted, that it is “absurd” that a “manifestly” erroneous determination, in the sense that it is affected by non-jurisdictional error of law, may stand. A non‑jurisdictional error of law may have serious consequences. But those consequences are dealt with by s 32 of the Security of Payment Act. The limited exclusion of review does not irrevocably entrench the consequences of an erroneous determination. Where it is contended that an adjudicator has made an error of law within jurisdiction, resulting in a progress payment that is inadequate or excessive, the dispute may be resolved through civil proceedings under the construction contract. If necessary, a restitutionary order can be sought [s 32(3)(b) of the Security of Payment Act]. The risk that the party placed at an advantage by an underpayment or overpayment may later become incapable of meeting such an order is a risk that is assigned to the other party. [Neller [2009] 1 Qd R 390 at 401 [40]] What Probuild characterised as an “absurd” outcome is more aptly seen as the coherent application of a statutory choice of forum rule. And private law proceedings in relation to a progress payment under a construction contract can hardly be expected to be less convenient than judicial review proceedings.
3 Object of Act
(1) The object of this Act is to ensure that any person who undertakes to carry out construction work (or who undertakes to supply related goods and services) under a construction contract is entitled to receive, and is able to recover, progress payments in relation to the carrying out of that work and the supplying of those goods and services.
(2) The means by which this Act ensures that a person is entitled to receive a progress payment is by granting a statutory entitlement to such a payment regardless of whether the relevant construction contract makes provision for progress payments.
(3) The means by which this Act ensures that a person is able to recover a progress payment is by establishing a procedure that involves—
(a) the making of a payment claim by the person claiming payment, and
(b) the provision of a payment schedule by the person by whom the payment is payable, and
(c) the referral of any disputed claim to an adjudicator for determination, and
(d) the payment of the progress payment so determined.
(4) It is intended that this Act does not limit—
(a) any other entitlement that a claimant may have under a construction contract, or
(b) any other remedy that a claimant may have for recovering any such other entitlement.
13 Payment claims
(1) A person referred to in section 8 who is or who claims to be entitled to a progress payment (the claimant) may serve a payment claim on the person who, under the construction contract concerned, is or may be liable to make the payment.
(1A) A payment claim may be served on and from the last day of the named month in which the construction work was first carried out (or the related goods and services were first supplied) under the contract and on and from the last day of each subsequent named month.
(1B) However, if the construction contract concerned makes provision for an earlier date for the serving of a payment claim in any particular named month, the claim may be served on and from that date instead of on and from the last day of that month.
(1C) In the case of a construction contract that has been terminated, a payment claim may be served on and from the date of termination.
(2) A payment claim—
(a) must identify the construction work (or related goods and services) to which the progress payment relates, and
(b) must indicate the amount of the progress payment that the claimant claims to be due (the claimed amount), and
(c) must state that it is made under this Act.
(3) The claimed amount may include any amount—
(a) that the respondent is liable to pay the claimant under section 27(2A), or
(b) that is held under the construction contract by the respondent and that the claimant claims is due for release.
(4) A payment claim may be served only within—
(a) the period determined by or in accordance with the terms of the construction contract, or
(b) the period of 12 months after the construction work to which the claim relates was last carried out (or the related goods and services to which the claim relates were last supplied),
whichever is the later.
(5) Except as otherwise provided for in the construction contract, a claimant may only serve one payment claim in any particular named month for construction work carried out or undertaken to be carried out (or for related goods and services supplied or undertaken to be supplied) in that month.
(6) Subsection (5) does not prevent the claimant from—
(a) serving a single payment claim in respect of more than one progress payment, or
(b) including in a payment claim an amount that has been the subject of a previous claim, or
(c) serving a payment claim in a particular named month for construction work carried out or undertaken to be carried out (or for related goods and services supplied or undertaken to be supplied) in a previous named month.
(7) A head contractor must not serve a payment claim on the principal unless the claim is accompanied by a supporting statement that indicates that it relates to that payment claim.
Maximum penalty—1,000 penalty units in the case of a corporation or 200 penalty units in the case of an individual.
(8) A head contractor must not serve a payment claim on the principal accompanied by a supporting statement knowing that the statement is false or misleading in a material particular in the particular circumstances.
Maximum penalty—1,000 penalty units in the case of a corporation or 200 penalty units or 3 months imprisonment (or both) in the case of an individual.
(9) In this section—
supporting statement means a statement that is in the form approved by the Secretary and (without limitation) that includes a declaration to the effect that all subcontractors, if any, have been paid all amounts that have become due and payable in relation to the construction work concerned.
Note—
An offence against subsection (7) or (8) committed by a corporation is an executive liability offence attracting executive liability for a director or other person involved in the management of the corporation—see section 34D.
14 Payment schedules
(1) A person on whom a payment claim is served (the respondent) may reply to the claim by providing a payment schedule to the claimant.
(2) A payment schedule—
(a) must identify the payment claim to which it relates, and
(b) must indicate the amount of the payment (if any) that the respondent proposes to make (the scheduled amount).
(3) If the scheduled amount is less than the claimed amount, the schedule must indicate why the scheduled amount is less and (if it is less because the respondent is withholding payment for any reason) the respondent’s reasons for withholding payment.
(4) If—
(a) a claimant serves a payment claim on a respondent, and
(b) the respondent does not provide a payment schedule to the claimant—
(i) within the time required by the relevant construction contract, or
(ii) within 10 business days after the payment claim is served,
whichever time expires earlier,
the respondent becomes liable to pay the claimed amount to the claimant on the due date for the progress payment to which the payment claim relates.
Section 14(2)(b) makes clear that what a Payment Schedule must do is indicate the amount of the payment, if any, that the respondent proposes to make. It is open to a respondent to include in a Payment Schedule any amount it chooses. That amount becomes the “scheduled amount”. It is well settled that it is a matter for an adjudicator and not the Court on judicial review to construe the Payment Schedule.
If the recipient of the Payment Claim does not, relevantly, pay the scheduled amount, the consequences are provided for in ss 15 and 16 respectively which, in essence, provide remedies including that the maker of the Payment Claim may recover the scheduled amount as a debt due to the claimant, in any court of competent jurisdiction.
If the amount identified in a Payment Schedule is less than the claimed amount the maker of a Payment Claim may make an “Adjudication Application”: s 17(1)(a)(i). The Adjudication Application identifies the Payment Claim and the Payment Schedule and contains any relevant submissions that the maker of the Payment Claim would like to make. The eligibility and appointment of adjudicators are provided for in ss 18 and 19. The respondent to the Adjudication Application may then lodge an Adjudication Response containing their submissions. Section 20 of the SOP Act provides:
20 Adjudication responses
(1) Subject to subsection (2A), the respondent may lodge with the adjudicator a response to the claimant’s adjudication application (the adjudication response) at any time within—
(a) 5 business days after receiving a copy of the application, or
(b) 2 business days after receiving notice of an adjudicator’s acceptance of the application,
whichever time expires later.
(2) The adjudication response—
(a) must be in writing, and
(b) must identify the adjudication application to which it relates, and
(c) may contain such submissions relevant to the response as the respondent chooses to include.
(2A) The respondent may lodge an adjudication response only if the respondent has provided a payment schedule to the claimant within the time specified in section 14(4) or 17(2)(b).
(2B) The respondent cannot include in the adjudication response any reasons for withholding payment unless those reasons have already been included in the payment schedule provided to the claimant.
(3) A copy of the adjudication response must be served on the claimant.
As I will explain in greater detail, s 20(2B) is an important provision for the determination of the present case.
Section 21(3) provides that an adjudicator is to determine an Adjudication Application “as expeditiously as possible”.
Section 22 provides:
22 Adjudicator’s determination
(1) An adjudicator is to determine—
(a) the amount of the progress payment (if any) to be paid by the respondent to the claimant (the adjudicated amount), and
(b) the date on which any such amount became or becomes payable, and
(c) the rate of interest payable on any such amount.
(2) In determining an adjudication application, the adjudicator is to consider the following matters only—
(a) the provisions of this Act,
(b) the provisions of the construction contract from which the application arose,
(c) the payment claim to which the application relates, together with all submissions (including relevant documentation) that have been duly made by the claimant in support of the claim,
(d) the payment schedule (if any) to which the application relates, together with all submissions (including relevant documentation) that have been duly made by the respondent in support of the schedule,
(e) the results of any inspection carried out by the adjudicator of any matter to which the claim relates.
(3) The adjudicator’s determination must—
(a) be in writing, and
(b) include the reasons for the determination (unless the claimant and the respondent have both requested the adjudicator not to include those reasons in the determination), and
(c) be served by the adjudicator on the claimant and the respondent.
(4) If, in determining an adjudication application, an adjudicator has, in accordance with section 10, determined—
(a) the value of any construction work carried out under a construction contract, or
(b) the value of any related goods and services supplied under a construction contract,
the adjudicator (or any other adjudicator) is, in any subsequent adjudication application that involves the determination of the value of that work or of those goods and services, to give the work (or the goods and services) the same value as that previously determined unless the claimant or respondent satisfies the adjudicator concerned that the value of the work (or the goods and services) has changed since the previous determination.
(5) If the adjudicator’s determination contains—
(a) a clerical mistake, or
(b) an error arising from an accidental slip or omission, or
(c) a material miscalculation of figures or a material mistake in the description of any person, thing or matter referred to in the determination, or
(d) a defect of form,
the adjudicator may, on the adjudicator’s own initiative or on the application of the claimant or the respondent, correct the determination.
32 Effect of Part on civil proceedings
(1) Subject to section 34, nothing in this Part affects any right that a party to a construction contract—
(a) may have under the contract, or
(b) may have under Part 2 in respect of the contract, or
(c) may have apart from this Act in respect of anything done or omitted to be done under the contract.
(2) Nothing done under or for the purposes of this Part affects any civil proceedings arising under a construction contract, whether under this Part or otherwise, except as provided by subsection (3).
(3) In any proceedings before a court or tribunal in relation to any matter arising under a construction contract, the court or tribunal—
(a) must allow for any amount paid to a party to the contract under or for the purposes of this Part in any order or award it makes in those proceedings, and
(b) may make such orders as it considers appropriate for the restitution of any amount so paid, and such other orders as it considers appropriate, having regard to its decision in those proceedings.
32A Finding of jurisdictional error in adjudicator’s determination
(1) If, in any proceedings before the Supreme Court relating to any matter arising under a construction contract, the Court makes a finding that a jurisdictional error has occurred in relation to an adjudicator’s determination under this Part, the Court may make an order setting aside the whole or any part of the determination.
(2) Without limiting subsection (1), the Supreme Court may identify the part of the adjudicator’s determination affected by jurisdictional error and set aside that part only, while confirming the part of the determination that is not affected by jurisdictional error.
It is well established that the purpose of the legislative scheme established by the SOP Act is best served by restricting the scope of intervention by the courts: Chase Oyster Bar Pty Ltd v Hamo Industries Pty Ltd (2010) 78 NSWLR 393; [2010] NSWCA 190 at [55] per Spigelman CJ. As this Court held in Ceerose Pty Ltd v A-Civil Aust Pty Ltd (2023) 112 NSWLR 225; [2023] NSWCA 215 at [179], it is quite unrealistic in the context of the time sensitive and document heavy adjudication process required under the SOP Act to require an adjudicator, lest he or she commit jurisdictional error, to treat minutely with repetitive arguments or repetitively reject what is essentially the same contention. The adjudicator’s findings with respect to matters of fact, within jurisdiction, are unreviewable. Further, there being no review for errors of law on the face of the record, the adjudicator’s determination of legal issues will also be unreviewable unless jurisdictional error is established: Icon Co (NSW) Pty Ltd v Australia Avenue Developments Pty Ltd [2018] NSWCA 339 at [15].
In Brodyn Pty Ltd t/as Time Cost and Quality v Davenport (2004) 61 NSWLR 42; [2004] NSWCA 394 at [53], Hodgson JA (with the agreement of Mason P and Giles JA) identified a number of basic and essential requirements of the Act, which included the following:
1. The existence of a construction contract between the claimant and the respondent, to which the Act applies (s 7 and s 8).
2. The service by the claimant on the respondent of a payment claim (s 13).
3. The making of an adjudication application by the claimant to an authorised nominating authority (s 17).
4. The reference of the application to an eligible adjudicator, who accepts the application (s 18 and s 19).
5. The determination by the adjudicator of this application (s 19(2) and s 21(5)), by determining the amount of the progress payment, the date on which it becomes or became due and the rate of interest payable (s 22(1)) and the issue of a determination in writing (s 22(3)(a)).
Hodgson JA then identified certain “more detailed requirements: for example, s.13(2) as to the content of payment claims” at [54] as to which he said that “the reasons given above for excluding judicial review on the basis of non-jurisdictional error of law justify the conclusion that the legislature did not intend that exact compliance with all the more detailed requirements was essential to the existence of a determination”: at [55].
In Downer Construction (Australia) Pty Ltd v Energy Australia (2007) 69 NSWLR 72; [2007] NSWCA 49, Giles JA explained at [87]-[89] that great care must be taken by the Court in conducting a judicial review of an adjudication under the SOP Act not to slip impermissibly into merits review. Determination of the parameters of the Payment Claim is a matter for the adjudicator, and a reasonable but erroneous decision by the adjudicator is not a jurisdictional error. The scope and nature of the Payment Claim will often be elucidated and evaluated with the benefit of the adjudicator’s specialised knowledge. Care must be taken in addressing a complaint of a failure by an adjudicator to consider the matters to which s 22(2) refers to ensure that the Court does not impermissibly impose the Court’s opinion about the correct outcome as the determinant of the adjudicator’s jurisdiction.
In Icon, this Court explained that it is within the jurisdiction of the adjudicator to act upon their understanding of the contractual obligations and of the content of a Payment Claim and Payment Schedule. In Icon, this Court dealt with a similar issue to one which arises in the present case. The head contractor in that case asserted that the adjudicator had awarded amounts which were not the subject of the Payment Claim. The primary judge in Icon identified the ground in the following terms, referring to the head contractor as the Principal, quoted on appeal at [20]:
[5] …The Principal’s second contention concerns certain previous deductions made by the Superintendent from the contract works price (‘backcharges’). The Adjudicator made allowances in favour of the Contractor on these items. The Principal’s argument is that the allowances fell outside the scope of the payment claim and that the Adjudicator thereby exceeded her jurisdiction.
[56] Counsel for the Principal argued that: (1) the Adjudicator made an error in entertaining a challenge to the five backcharge items, in that those items had not been part of the payment claim and were not properly part of the adjudication process; and (2) that this error was a jurisdictional one which invalidated the determination. Initially it was contended on behalf of the Principal that the Court could, and should, remit the application for re-determination by the Adjudicator but this contention was abandoned on the second day of argument.
The Court in Icon concluded at [33] that an adjudicator has not fallen into jurisdictional error by addressing a dispute between the parties in relation to what were described as “backcharges”. There was a dispute to be resolved by the adjudicator, notwithstanding that the “backcharges” identified in the Payment Schedule in that case were not part of the Payment Claim as served. This Court reversed the primary judge, finding that the Payment Claim as served and adjudicated upon identified the construction work, as required by s 13(2)(a). It was not deficient in that respect. The dispute was as to the calculation of the value of that work, which was the task vested in the adjudicator. The respondent on that case had put the calculation of the value of that work in issue in the Payment Schedule by purporting to apply “backcharges” to reduce the amounts which had been claimed in the Payment Claim.
As I will explain, in the present case Qube introduced the sum secured by the bank guarantees by deploying those sums in the Payment Schedules to reduce the amounts which had been claimed in the Payment Claim. In doing so, Qube introduced to the dispute to be resolved by the adjudicator an issue about the calculation of the value of the work claimed by Martinus in the Payment Claim, notwithstanding that restitution of the sum paid out by reason of the guarantees was not part of the Payment Claim as served by Martinus.
In Ceerose this Court held:
[31] It is now well settled that whether a submission referred to in s 22(2)(c) or (d) has been “duly made” is a matter within the jurisdiction of an adjudicator and error in identifying a submission as having been “duly made” is not jurisdictional: John Holland Pty Ltd v Roads & Traffic Authority of New South Wales (2007) 23 BCL 205; [2007] NSWCA 19 at [57]; Perform (NSW) Pty Ltd v MEV-AUS Pty Ltd [2009] NSWCA 157 at [65]; Coordinated Construction Co Pty Ltd v Climatech (Canberra) Pty Ltd (2005) 21 BCL 364; [2005] NSWCA 229 at [24]-[26]…
The obligation imposed on the adjudicator by s 22(2) of the SOP Act and the manner of proof of a failure to discharge that obligation are at the heart of the present case. Section 22(2) of the SOP Act provides that in determining an Adjudication Application, the adjudicator is to consider certain identified matters only. The concept of “consideration” is not obscure. Nevertheless, the duty to “consider” has given rise to an extensive history of judicial exegesis, which I examined in Ceerose and will not repeat here, save to the extent necessary to address arguments made in the present case.
At [62]-[68] in Ceerose, I referred to the practical problem for a party challenging the internal processes of an adjudicator under the SOP Act; that is to identify a basis on which it could be concluded that consideration of a submission the adjudicator considered to have been “duly made” did not occur. It is clear that the failure to identify a particular claim or response in reasons will not of itself demonstrate that the adjudicator failed to consider it. Reasons are not necessarily, or even usually, a comprehensive statement of all aspects of a decision-maker’s thinking. Even judicial reasons, which are expected to be more comprehensive and detailed than those of an administrative decision-maker, are not required to deal with all the evidence or all the submissions. A process of selection is undertaken as a necessary part of the process.
The scope of the adjudicator’s reasons reflects the practical circumstances under which the adjudicator is operating. Section 21(3)(a)(ii) of the SOP Act requires the adjudicator to determine an Adjudication Application “as expeditiously as possible and, in any case … within 10 business days after ... the date on which notice of the adjudicator’s acceptance of the application is served on the claimant and the respondent”. One of the matters which the adjudicator is to consider is the “adjudication response” filed by the respondent to the claim. The Adjudication Response may be lodged five business days after receiving a copy of the application, or two business days after receiving notice of the adjudicator’s acceptance of the application, whichever is later: s 20(1). Thus, unless time is extended by the parties, the adjudicator may have as few as eight business days to determine the application by reference to the Adjudication Response. Even in this case, where extensions of time were sought and granted, the adjudicator addressed thousands of pages of evidence and submissions in a relatively short time frame. In accordance with the statutory scheme in the SOP Act, the adjudicator was entitled to spend more time on some items within a claim than on others. I reject the respondent’s contention that the significance of the deadlines the SOP Act imposes on an adjudicator that I referred to in Ceerose is of less weight here because the adjudicator “had about 19 weeks to deliver the adjudications”. As I have said, the adjudicator here received more than 15,700 pages of material. These materials were addressed in a relatively short time frame.
Where there is an absence of reference to a particular submission or contention, there are a range of possible explanations, only one of which is that the material was not considered. Even assuming the submission had been misunderstood, the facts mistaken or the law wrongly identified, that would explain absence from the reasons of something expected to be addressed, but not lack of consideration. The duty to consider a submission is different from a duty to deal with it correctly, whether in law or in fact. An unreviewable error may explain why the reasons do not advert to a particular matter. Often it will be equally likely that an adjudicator who does not refer in reasons to a particular matter mistook the facts or misunderstood the contractual provision or the legal principle to be applied, as that he or she did not consider the factor at all. In those circumstances, a complaint of failure to consider will not be proven. Jurisdictional error is not established in such a case. As I concluded in Ceerose about claims that an adjudicator has fallen into jurisdictional error by failing to consider a matter required by s 22(2) of the SOP Act:
[69] For all of these reasons, there are likely to be few cases in which an applicant for judicial review can establish a breach of the duty to consider the matters set out in s 22(2). That is not to say that there may not be circumstances in which the inference of omission to consider is demonstrated. Thus, failure to refer to a submission on a centrally important matter, clearly articulated and based on uncontested facts, may demonstrate a failure to consider at all. Such is likely to be a rare case.
In addressing the notice of contention in the present case, procedural fairness is an important topic. As I said in Ceerose at [43]-[51], conventionally, procedural fairness has two limbs, namely the bias rule and the “hearing rule”. The bias rule is not relevant in the present case. The “hearing rule” does not necessarily require a hearing, but rather requires that the decision-maker afford a party an opportunity to address material likely to affect adversely that party’s interests or expectations. A breach of that duty is not concerned with the manner in which the decision-maker has processed the material and should, in principle, be addressed separately.
Section 22 of the SOP Act contains two separate mandates. First, s 22(1) identifies the matters which the adjudicator “is to determine”; secondly, s 22(2) identifies the matters which the adjudicator “is to consider”, a formulation which covers five matters which are the “only” matters to be considered. The statute distinguishes between that which the adjudicator must determine and that which he or she must consider. Failure to determine the three matters set out in s 22(1), if required to do so to resolve a particular claim, would likely constitute jurisdictional error. Compliance with s 22(2) is less readily so characterised. Further, s 22(2) does not address the question of procedural fairness in the sense of the steps which the adjudicator must take to allow a party to address adverse material. Failure to comply with s 22(2) is not helpfully characterised as procedural unfairness, but rather as failure to comply with a mandatory statutory obligation, the scope of which will be identified on quite a different basis.
As I said in Ceerose at [51], because procedural fairness is concerned with the conduct of the adjudicator towards the parties, once it is established what fairness requires in a particular case, the question of compliance will be readily determined by the objective facts, being primarily the communications, or lack of them, between the adjudicator and the parties. By contrast, as I have explained, the question whether the adjudicator has considered a matter for the purposes of s 22(2) will involve an inquiry into the private processes of decision-making, and even the mental processes of the adjudicator. While those processes may be revealed by the reasons required to be given under s 22(3), those reasons will not necessarily demonstrate a negative proposition, namely a failure to consider a particular matter required to be considered simply because it is not referred to in the reasons.
In Demex Pty Ltd v McNab Building Services Pty Ltd (2023) 113 NSWLR 282; [2023] NSWCA 261, this Court said:
[32] Consistently with the effect of what was said in Brodyn, and with the arguments put by the appellant in this case, it should be understood that only if there has been a substantial denial of procedural fairness by an adjudicator in determining an adjudication application will there be jurisdictional error under the Act. Put another way, the content of the requisite procedural fairness is reduced: note Cardinal at [60]. What this means in practice will turn on the particular circumstances of cases. But generally a conclusion of invalidity would only be reached if there was a significant departure from what would ordinarily be the requirements of procedural fairness for a person exercising a statutory power, and where that departure could be characterised as leading to substantial practical injustice in all the circumstances. This approach reflects the fact that the Act provides for a “rough and ready” process (Chase Oyster Bar at [208]), not intended readily to be held invalid on judicial review.
The unreasonableness ground of judicial review is no longer limited to what is in effect an irrational, if not bizarre, decision – which is to say one that is so unreasonable that no reasonable person could have arrived at it: Minister for Immigration and Citizenship v Li (2013) 249 CLR 332; [2013] HCA 18 at [68] (Hayne, Kiefel and Bell JJ). In Judicial Review of Administrative Action and Government Liability by M Aronson, M Groves and G Weeks (Thomson Reuters, 6th ed, 2017) at [6.450], it is suggested, in my view correctly, that Li “invites a qualitative assessment of the impugned discretionary decision, but it does not allow an appeal to the judicial review judge’s subjective sense of reasonableness”.
In Li, French CJ said:
[30] The requirement of reasonableness is not a vehicle for challenging a decision on the basis that the decision-maker has given insufficient or excessive consideration to some matters or has made an evaluative judgment with which a court disagrees even though that judgment is rationally open to the decision-maker. Gleeson CJ and McHugh J made the point in Eshetu that the characterisation of somebody’s reasoning as illogical or unreasonable, as an emphatic way of expressing disagreement with it, “may have no particular legal consequence”. As Professor Galligan wrote [DJ Galligan, Discretionary Powers: A Legal Study of Official Discretion (Oxford University Press, 1986) at 140]:
“The general point is that the canons of rational action constitute constraints on discretionary decisions, but they are in the nature of threshold constraints above which there remains room for official judgment and choice both as to substantive and procedural matters. In other words, within the bounds of such constraints, different modes of decision-making may be employed.”
A distinction may arguably be drawn between rationality and reasonableness on the basis that not every rational decision is reasonable. It is not necessary for present purposes to undertake a general consideration of that distinction which might be thought to invite a kind of proportionality analysis to bridge a propounded gap between the two concepts. Be that as it may, a disproportionate exercise of an administrative discretion, taking a sledgehammer to crack a nut, may be characterised as irrational and also as unreasonable simply on the basis that it exceeds what, on any view, is necessary for the purpose it serves. That approach is an application of the principles discussed above and within the limitations they would impose on curial review of administrative discretions. (footnotes omitted)
[65] In Sharp v Wakefield [[1891] AC 173 at 179], it was said that when something is to be done within the discretion of an authority, it is to be done according to the rules of reason and justice. That is what is meant by “according to law”. It is to be legal and regular, not arbitrary, vague and fanciful. The discretion must be “exercised within the limit, to which an honest man competent to the discharge of his office ought to confine himself”. It is pointed out in Wade and Forsyth [Administrative Law (Oxford University Press, 10th ed, 2009) at 293-294] that the legal conception of discretion dates from at least the 16th century. In Sharp v Wakefield, Lord Halsbury LC had referred to Rooke’s Case [(1597) 5 Co Rep 99b at 100a; 77 ER 209 at 210], in which it was stated that the discretion of commissioners of sewers “ought to be limited and bound with the rule of reason and law”.
[66] This approach does not deny that there is an area within which a decision-maker has a genuinely free discretion. That area resides within the bounds of legal reasonableness. The courts are conscious of not exceeding their supervisory role by undertaking a review of the merits of an exercise of discretionary power. Properly applied, a standard of legal reasonableness does not involve substituting a court’s view as to how a discretion should be exercised for that of a decision-maker. Accepting that the standard of reasonableness is not applied in this way does not, however, explain how it is to be applied and how it is to be tested.
…
[68] Lord Greene MR’s oft-quoted formulation of unreasonableness in Wednesbury has been criticised for “circularity and vagueness”, as have subsequent attempts to clarify it. However, as has been noted, Wednesbury is not the starting point for the standard of reasonableness, nor should it be considered the end point. The legal standard of unreasonableness should not be considered as limited to what is in effect an irrational, if not bizarre, decision - which is to say one that is so unreasonable that no reasonable person could have arrived at it - nor should Lord Greene MR be taken to have limited unreasonableness in this way in his judgment in Wednesbury. This aspect of his Lordship’s judgment may more sensibly be taken to recognise that an inference of unreasonableness may in some cases be objectively drawn even where a particular error in reasoning cannot be identified. This is recognised by the principles governing the review of a judicial discretion, which, it may be observed, were settled in Australia by House v The King, before Wednesbury was decided. And the same principles evidently informed what was said by Dixon J about review of an administrative decision in Avon Downs Pty Ltd v Federal Commissioner of Taxation, which was decided less than two years after Wednesbury, at a time when it was the practice of the High Court to follow decisions of the Court of Appeal in England which appeared to have settled the law in a particular area. (footnotes omitted)
[90] Implication of reasonableness as a condition of the exercise of a discretionary power conferred by statute is no different from implication of reasonableness as a condition of an opinion or state of satisfaction required by statute as a prerequisite to an exercise of a statutory power or performance of a statutory duty [R v Connell; Ex parte The Hetton Bellbird Collieries Ltd (1944) 69 CLR 407 at 432; [1944] HCA 42; Enfield City Corporation v Development Assessment Commission (2000) 199 CLR 135 at [34]; [2000] HCA 5]. Each is a manifestation of the general and deeply rooted common law principle of construction that such decision-making authority as is conferred by statute must be exercised according to law and to reason within limits set by the subject matter, scope and purposes of the statute [Sharp v Wakefield [1891] AC 173 at 179, cited in R v Connell; Ex parte The Hetton Bellbird Collieries Ltd (1944) 69 CLR 407 at 431; [1944] HCA 42 and in Shrimpton v The Commonwealth (1945) 69 CLR 613 at 620; [1945] HCA 4. See generally R v Anderson; Ex parte Ipec-Air Pty Ltd (1965) 113 CLR 177 at 189; [1965] HCA 27; Murphyores Incorporated Pty Ltd v The Commonwealth (1976) 136 CLR 1 at 17-18; [1976] HCA 20; Minister for Immigration and Multicultural Affairs v Jia Legeng (2001) 205 CLR 507 at [62]; [2001] HCA 17].
Considerable care is warranted in addressing a complaint of judicial review on the ground of legal unreasonableness, lest the review for jurisdictional error slide impermissibly into merits review. There is usually a high threshold for a conclusion that a power has been unreasonably exercised as a matter of law: Ismail v Minister for Immigration, Citizenship and Multicultural Affairs (2024) 98 ALJR 196; [2024] HCA 2 at [25]; Minister for Home Affairs v DUA16 (2020) 271 CLR 550; [2020] HCA 46 at [26]; Minister for Immigration and Border Protection v SZVFW (2018) 264 CLR 541; [2018] HCA 30 at [11], [52], [89] and [135].
These principles of judicial restraint in finding jurisdictional error on the basis of legal unreasonableness apply even more stringently in addressing an adjudicator’s decision made under the SOP Act. As I have said, under the SOP Act, it is for the adjudicator to determine the content and scope of the Payment Claim and the Payment Schedule, including the scope and content of the dispute between the parties: John Holland Pty Ltd v Roads and Traffic Authority of New South Wales [2007] NSWCA 19 at [57]; Downer at [86]; Joye Group Pty Ltd v Cemco Projects Pty Ltd [2021] NSWCA 211 at [12]; Ceerose at [80], [100]-[106]; Icon at [13]-[19], [27]-[32].
Please refer to Appendix 6 - Heads of Claim Folder and further navigating to subfolder Appendix 6F - Resequencing folder which contains the relevant revised notices, detailed cost breakdown, further documentation and substantiation in support to the Contractor’s CN420 RevA Claim.
Appendix 6F was headed “Variation Claim” and stated that Martinus was directed to vary the Works under Contract (“WUC”) as a result of the delayed, altered and interrupted site access provided by Qube. Appendix 6F identified Martinus’s CN-420 claim as based on cll 32.1, 36.1 and 36.3A of the INTS Contract.
Clause 32.1 of the INTS Contract provided:
32.1 Progress
The Contractor shall proceed with WUC with due expedition and without delay.
The Superintendent shall give to the Contractor the information, materials, documents and instructions by the times or within the periods both stated in Annexure Part A.
The Contractor shall give the Superintendent reasonable advance notice of when the Contractor needs other information, materials, documents or instructions from the Superintendent or the Principal.
The Principal and the Superintendent shall not be obliged to give any information, materials, documents or instructions earlier than the Principal or the Superintendent, as the case may be, should reasonably have anticipated at the date of the Contract.
The Superintendent may direct in what order and at what time the various stages or portions of WUC shall be carried out. If the Contractor can reasonably comply with the direction, the Contractor shall do so. If the Contractor cannot reasonably comply, the Contractor shall give the Superintendent written notice of the reasons.
If compliance with any such directions under this clause, except those pursuant to the *Contractor’*s default, causes the Contractor to incur more or less cost than otherwise would have been incurred had the Contractor not been given the direction, the difference shall be assessed by the Superintendent and added to or deducted from the contract sum.
36.1 Directing variations
The Contractor shall not vary WUC except as directed in writing by the issue of a variation order.
The Superintendent, before the date of commissioning completion, may direct the Contractor to vary WUC by any one or more of the following which is nevertheless of a character and extent contemplated by, and capable of being carried out under, the provisions of the Contract (‘variation’):
a) increase, decrease or omit any part;
b) change the character or quality;
c) change the levels, lines, positions or dimensions;
d) carry out additional work;
e) demolish or remove material or work no longer required by the Principal.
A variation may involve the omission of any part or parts of WUC and the Contractor acknowledges and agrees that the Principal may engage others to carry out that part or parts so omitted. The Contractor further acknowledges that any one or more omission will not constitute a basis to allege that the Principal has repudiated the Contract notwithstanding the extent or timing of the omission.
**36.3A Contractor’**s claim for a variation
If the Contractor considers that it has been required to carry out a variation (whether as a result of a direction or any other event) but the Superintendent has not given a written direction in the form of a variation order, the Contractor must, within 5 business days after receipt of the direction or after that other event, give written notice of:
a) its opinion that the work involves a variation which should have been directed in the form of a variation order;
b) the reasons for its opinion; and
c) the *Contractor’*s estimate of the:
i) effect of the work on the approved delivery program (including the date for practical completion and the date for commissioning completion); and
ii) cost (including all time-related costs, if any) of the work calculated in accordance with the principles in subclause 36.4, including a full breakdown of costs in support of the estimate.
In response to a written notice by the Contractor under this subclause, the Superintendent may:
e) confirm that the work involves a variation and issue a Variation Order under subclause 36.1;
f) withdraw the relevant direction; or
g) notify the Contractor that the work does not involve a variation.
If the Contractor fails to give the notice required by this subclause, it shall have no Claim against the Principal for any additional time or cost arising out of or in any way connected with the direction or event to the extent that either is claimed to be the basis for a variation claim.
In the INTS Payment Schedule, Qube disputed the claim in whole. Importantly, however, in its Payment Schedule, Qube made no reference to cl 32.1.
In the INTS Adjudication Application, Martinus addressed each of the reasons relied on by Qube in the INTS Payment Schedule for denying liability to pay the Payment Claim. Qube addressed CN-420 at [10.97]-[10.153] of the Adjudication Response.
The adjudicator set out and addressed CN-420 at [1331]-[1397] of the INTS Determination. The adjudicator specifically identified each of the reasons relied upon by Qube in its Payment Schedule to deny the payment in whole in relation to CN-420:
[1343] The Respondent provided the following reason for withholding payment;
*“*CN 420 relates to a claimed variation for works associated with the construction and relocation of the Haul Road, additional site access roads and associated infrastructure works required as a result of alleged directions from the Superintendent and the Principal and delay in the provision of Site access by the Principal.
The principal and quantum of CN 420 are disputed.
Reference is made to the Superintendent’s letter dated 18 September 2023 (ref INTS-RPS-PM-LTR-113) for details of the Superintendent’s assessment of $nil fo**r the initial CN 420 claim titled *‘*CN-420- Variation Claim (MRT Ref VCR-161) – Relocation of Access Roads and Associated Infrastructure Works’ (Initial CN 420 Claim) in the sum of $1,117,998.07 (exc. GST) submitted by the Contractor on 31 August 2023.
Within PC 15, the Contractor has claimed the sum of $14,168,170.75 (exc. GST)[1] for the updated CN 420 submitted on 8 February 2024 under the heading ‘CN–420 – Resequencing - Vehicle Management Plan (VMP)’ (Updated CN 420 Claim) [2]. This is an increase of $13,050,172.68 (exc. GST) from the Initial CN 420 Claim.
The Superintendent retains its assessment of $nil for the Updated CN 420 Claim in PS 15.
*Further details of the Superintendent’*s response to CN 420 are provided at Appendix C.1 to INTS and ISRA Payment Schedule 15.
In summary, the Superintendent notes that:
• the works which are the subject of the Initial CN 420 Claim and the updated CN 420 Claim do not constitute a variation under the Contract;
• the Contractor failed to submit CN 420 in accordance with clause 36.3A of the Contract and therefore has no entitlement to claim for any additional time or cost arising out of or in any way connected with the alleged directions or delay in the provision of site access;
• in the event CN 420 is not time barred (which is denied), the construction and location of the Haul Road, site access roads and associated infrastructure works form part of WUC and remain the responsibility of the Contractor;
• there is no causal link between alleged directions or delay in the provision of site access and the alleged construction and relocation of the Haul Road, additional site access roads and associated infrastructure works;
• the Contractor has failed to substantiate or provide evidence of the costs allegedly incurred; and
• the Contractor has already been compensated for delay and disruption costs associated with an**y delay in the provision of site access on the dates referred to in CN 420 as part of the sums claimed for CN 277 (EOT-34) and paid to the Contractor p**ursuant to the Adjudication Determinations of Alan Stapelton #525 dated 2 August 2023 and #551 dated 2 November 2023.
• In accordance with clause 34.9 of the Contract, the Contractor’s entitlement to delay costs is in full satisfaction of all loss suffered or incurred by the Contractor in respect of any delay in the provision of site access which are subject of EOT 34*.*
The Contractor has no entitlement under the Contractor at law for this claim.
The adjudicator expressly dealt with each of the reasons for withholding payment given by Qube in the INTS Payment Schedule:
at [1354]-[1362], the adjudicator addressed Qube’s argument that the works were not variation works;
at [1363]-[1370], the adjudicator addressed Qube’s argument that there is a time bar under cl 36.3A;
at [1371]-[1384], the adjudicator addressed Qube’s argument that the works were works under contract; and
at [1385]-[1397], the adjudicator addressed Qube’s argument that Martinus had not substantiated the quantum of its claim.
The adjudicator clearly addressed each of the complaints made by Qube in its Payment Schedule and rejected them. Having considered and rejected each of the reasons Qube gave in the INTS Payment Schedule about CN-420, the adjudicator allowed the claim at [1397].
In these circumstances, it is difficult to see what room there was to conclude that the adjudicator had not “considered” a submission “duly made” in Qube’s case. The essence of the primary judge’s finding was that, in addressing CN-420, the adjudicator had failed to consider two arguments Qube developed in the Adjudication Response about the proper operation of cl 36.1 of the INTS Contract and an argument that Martinus was contractually responsible for the works the subject of CN-420.
In the September judgment, the primary judge stated:
[136] Consideration of Qube’s submissions: There is nothing in the Adjudicator’s reasons which demonstrates affirmatively that he considered the submissions in Qube’s response to Martinus’ claim (or the supporting evidence referred to in those submissions). The question is whether I can infer from this that he did not in fact consider those submissions. This is essentially a factual question. In answering it, I must consider alternative possibilities which might explain why, having considered the submissions, he nevertheless did not refer to them.
[137] In this regard, the tight timetables under which adjudications normally operate are relevant. Counsel for Qube emphasised, however, that in the present case the Adjudicator had 19 weeks to consider the application, and, having regard to the fees he charged, he can have done little else over that period. Counsel submitted that in the circumstances, this factor was of little weight.
[138] Counsel for Martinus did not agree. They argued that the content of the obligation of natural justice in the particular case was to be determined by reference to the Act, and not the circumstances of the particular case.
[139] I do not accept this argument. The nature of the obligation is, I accept, constrained by the terms of the Act. But this does not go very far. While in general the Act provides for tight timetables, it also provides for extensions.
[140] The true rule is that the degree to which consideration may be expected is constrained by the amount of time available. But for the purpose of drawing an inference about the facts of a particular case, it is necessary to have regard to the facts of that case. In my view, it would be absurd to suppose that the Court would take the same approach to the drawing of the relevant inference where an adjudicator was dealing with a single claim involving a single issue as it would if that same issue arose in another adjudication involving twenty other claims each involving multiple issues.
[141] In the present case, there were no doubt many claims and issues for consideration. But the issue currently in question was an important one. I see no reason to think that the time pressures on the Adjudicator were so extreme as to prevent him from dealing with Qube’s submissions or explaining why he did not consider it necessary to do so.
[143] Another possibility suggested is that a submission may not have been referred to because the adjudicator considered that it did not justify a response or that it did not, because of other findings or conclusions, arise. But the plausibility of that explanation depends upon the nature of the submission. The more extensive the submission is, and the weightier it appears to be, the less likely the explanation becomes.
An assessment of how “weighty” Qube’s submission in its Adjudication Response was constituted an error. The weight to be accorded to a submission is a matter for the adjudicator. An attempt on judicial review limited to jurisdictional error to assign “weight” to submissions made to an adjudicator is to invite impermissible merits review by the Court opining whether the arguments are, in the opinion of the Court and based on the Court’s construction of the issues, of “substance”. An attempt by a Court to assign relative “weight” to submissions made to an adjudicator runs the risk of applying an intensity of review of decisions made by adjudicators under the SOP Act inconsistent with the decisions of this Court I have summarised above.
The two arguments that the primary judge found had not been considered by the adjudicator were set out as follows in the September judgment:
[144] The Adjudicator effectively accepted that cl 36.3A was not available; it was unnecessary to go into Qube’s submissions in any detail on that point. But that was not so for the argument about cl 36.1, or for the argument that Martinus was contractually responsible for the works the subject of the claim.
[145] In my view, these arguments from Qube were arguments of apparent substance. In particular, Martinus’ proposition that a “Variation Order” could be created for the purposes of cl 36.1 without the Superintendent signing a formal order under the Contract was a surprising one. Qube’s arguments were relevant to issues which the Adjudicator addressed in his reasons. I find it difficult to accept that the Adjudicator would, if he had considered those arguments, felt that they were so inconsequential that they did not call for mention.
[146] Of particular significance, in my view, is what the Adjudicator said at [1372]. Even if it was correct to say that there was no supporting evidence in the payment schedule, there was in the adjudication response. It was not suggested that Qube’s submissions in the response were not “duly made”. Similarly, Qube’s response submissions did go into the contractual position, contrary to the point the Adjudicator seems to have been making in [1375]. I agree with counsel for Qube that it is highly unlikely that the Adjudicator would have expressed himself in this way if he had considered the submissions.
I do not agree that the primary judge’s conclusion about Qube’s argument being of “apparent substance” told in favour of a finding of jurisdictional error. As I explained in Ceerose, a Court on judicial review assessing arguments for their “apparent substance” invites an impermissible merits review. It bears repeating that the scheme of the SOP Act provides that an adjudicator’s findings with respect to matters of fact are within jurisdiction and unreviewable. Further, there being no review for errors of law on the face of the record, an adjudicator’s determination of legal issues will also be unreviewable unless jurisdictional error is established.
The primary judge’s ultimate conclusion about CN-420 was expressed thus:
[147] Naturally I have hesitated, when the Adjudicator was required to consider Qube’s submissions, to draw the inference that he did not do so. Nevertheless I find myself driven to that conclusion. It is the most straightforward explanation for why the submissions were not referred to in the Adjudicator’s reasons and, in my opinion, the most probable.
The adjudicator did not fall into jurisdictional error. This is for two reasons. First, even assuming that there was no reference to the matters identified by Qube in the adjudicator’s decision, I am not satisfied that it was established that the adjudicator failed to consider any submission he regarded as “duly made”. Jurisdictional error was not established. Secondly, the arguments actually made by Qube in the Payment Schedule were in fact addressed by the adjudicator.
The adjudicator correctly identified CN-420 as a claim by Martinus under both cll 32.1 and 36.1 of the INTS Contract. The adjudicator found that Qube had issued directions under cl 32.1 and found that Martinus had a separate and distinct right to payment under that clause.
[1357] I am persuaded that the Respondent’s directions of 10 October 2022, 30 March 2023 and instances of further directions changing the dates for access to parts of the site identified in the Claimant’s notice dated 31 August 2023 were directions given under clause 32.1 of the Contract.
[1358] Upon giving a direction under clause 32.1, the Respondent became liable for the Claimant’s additional costs if compliance with any such directions caused the Claimant to incur more or less cost than otherwise would have been incurred had the Claimant not been given the direction.
This conclusion might be incorrect as a matter of law, but that is not to the point in a judicial review alleging jurisdictional error. The correct construction of the contract was a matter for the adjudicator. The adjudicator’s decision is valid even if he misconstrued the contract.
Contrary to the conclusion of the primary judge that the adjudicator had failed to consider Qube’s argument about cl 36.1, the adjudicator found that Qube had issued variation orders (“VO”s) for the purposes of cl 36.1:
[1359] The Claimant also argues that the Directions to Re-sequence the Works given by the Respondent were also directions under clause 36.1 of the Contract.
[1360] Clause 36.1 of the Contract states;
*“*36.1 Directing variations
The Contractor shall not vary WUC except as directed in writing by the issue of a variation order.
The Superintendent, before the date of commissioning completion, may direct the Contractor to vary WUC by any one or more of the following which is nevertheless of a character and extent contemplated by, and capable of being carried out under, the provisions of the Contract (‘variation’**):
a) increase, decrease or omit any part;
b) change the character or quality;
c) change the levels, lines, positions or dimensions;
d) carry out additional work;
e) demolish or remove material or work no longer required by the Principal
A variation may involve the omission of any part or parts of WUC and the Contractor acknowledges and agrees that the Principal may engage others to carry out that part or parts so omitted. The Contractor further acknowledges that any one or more omission will not constitute a basis to allege that the Principal has repudiated the Contract notwithstanding the extent or timing of the omission.
[1361] The Respondent’s directions of 10 October 2022, 30 March 2023 and instances of further directions changing the dates for access to parts of the site identified in the Claimant’s notice dated 31 August 2023 were directions and compliance with that direction, required the Claimant to carry out additional work.
[1362] Accordingly, I accept the argument that the Directions to Re-sequence the Works given in writing by the Respondent under clause 32.1, required the Claimant to perform additional work and were variation orders under clause 36.1 for all intents and purposes.
Findings about these issues were a matter for the adjudicator. It may be, on a correct understanding of the INTS Contract, the adjudicator’s conclusions were incorrect. It may be, properly analysed, that the adjudicator misunderstood some of the legal submissions made to him. It does not follow that Qube established that the adjudicator failed to consider a submission duly made and thus fell into jurisdictional error.
Critically, the adjudicator considered and dealt with every reason in the Payment Schedule that Qube advanced to reject the Payment Claim. I do not accept that a failure to refer expressly to a particular submission drawn from the Adjudication Response provided a sufficient basis to conclude that the adjudicator had fallen into jurisdictional error. As I explained at some length in Ceerose, the fact that a particular submission was not referred to, at best, might raise a question about what inference should be drawn from that matter. This case is far removed from the type of case I was referring to in Ceerose where jurisdictional error may be inferred. That is because the adjudicator in this case expressly dealt with every matter raised by Qube in the Payment Schedule. The adjudicator was obliged to deal with Qube’s reasons included in its Payment Schedule. This he did. If a submission travelled outside the matters raised in the Payment Schedule, it was irrelevant and inadmissible: s 20(2B) of the SOP Act.
Qube cannot, by pointing to the detail of a submission made in the Adjudication Response, elevate that submission above the identified reason for non-payment it gave in its Payment Schedule. That is, it cannot be correct that a new matter was properly raised in the Adjudication Response which has not been the subject of Qube’s Payment Schedule. If the adjudicator considered but failed to grasp the subtlety of a submission made in Qube’s Adjudication Response as falling within a reason advanced by the Payment Schedule, that was an error within the adjudicator’s jurisdiction.
It was not a jurisdictional error for the adjudicator to fail to repeat in his already lengthy adjudication every matter addressed in the Adjudication Response. It was a matter for the adjudicator to determine the extent to which specific submissions needed to be referred to. The adjudicator addressed each of the matters raised by Qube in its Payment Schedule. The adjudicator may or may not have been correct in his understanding of the relationship between the detail contained in the Adjudication Response and the reason for non-payment provided in the Payment Schedule. Any error, if there be error, was an error within jurisdiction.
Qube’s argument in the Adjudication Response at [10.111] that cl 36.1 of the contract applied such that a variation occurred only when the Superintendent issues a written direction takes the matter no further. The adjudicator found that there were written directions given by Qube at [1331]-[1332], [1346], [1351] and [1361]-[1362]. Those findings were sufficient to address Qube’s argument that cl 36.1 required written directions. Contrary to submissions made in this Court about the form a variation order must take, Qube did not make any submission to the adjudicator that a variation order must take a particular form. It was not an error, let alone a jurisdictional error, for the adjudicator to not set out any further detailed reasoning about the operation of cl 36.1.
As to Qube’s argument that the CN-420 works were part of the WUC on the proper construction of the contract, the adjudicator found that he was not satisfied that those works were within the contractual scope:
[1375] Further, I cannot find anything in the Contract that says that construction of all haul roads that may be required throughout the course of the works is included in the Claimant’s preliminaries regardless of whether the work is part of the original lump sum or a variation to the Contract. Accordingly, I do not accept the Respondent’s argument for withholding payment on this point.
It may or may not be correct that Martinus was contractually responsible for the works the subject of CN-420. That is not to the point. Any error, assuming there be an error, was not a jurisdictional error. It was a matter for the adjudicator to determine whether the CN-420 works were part of the WUC. This task the adjudicator undertook. Jurisdictional error was not established.
In concluding at [1372] that “the respondent provides no further explanation in the Payment Schedule [nor] provides any reference to the part of the contract that supports that assertion” (being the assertion that CN- 420 works form part of the WUC), the adjudicator was correct. It was not an error, let alone a jurisdictional error for the adjudicator so to conclude. As I have explained, the adjudicator was correct to focus on the content of Qube’s Payment Schedule. Qube was not permitted to add reasons for withholding payment in its Adjudication Response beyond those given in its Payment Schedule. The conclusion of the primary judge at [146] of the September judgment that it was of “particular significance” for the adjudicator to conclude as he did, was an error.
The onus of establishing jurisdictional error was on Qube. Qube was required to establish that the adjudicator had, in fact, failed to consider submissions he found were duly made. The absence of specific reference in the adjudicator’s reasons to a particular submission in the Adjudication Response does not establish that those submissions were not considered.
The adjudicator dealt with all of the matters raised by Qube in the Payment Schedule and that it was appropriate in those circumstances for the adjudicator not to address additional reasons which, as a matter of law, could not travel beyond the reasons given in the Payment Schedule, each of which was squarely addressed.
Finally, there was a clear independent basis for the adjudicator’s decision. That was that CN-420 should be allowed under cl 32.1. Qube did not in its Payment Schedule respond to Martinus’s claim under cl 32.1. The adjudicator may or may not have been correct about the construction of cl 32.1 and its effects in this case. The construction of the contract, however, was a matter for the adjudicator. Even if the construction adopted was not correct, it was not a jurisdictional error for the adjudicator so to conclude. It follows that even if the adjudicator had fallen into error, that error was not material as there was an unchallenged independent basis for the adjudicator’s decision.
I reject Qube’s submission, made in this Court, that cl 32.1 was not relied upon by the adjudicator as an independent basis for Martinus’s claim. As I have found, the adjudicator plainly did so rely. A resequencing direction causing additional cost can properly be described as “variation”. In any event, the proper understanding of the INTS Contract was a matter for the adjudicator. Qube advanced no argument to the adjudicator in its Payment Schedule that characterisation of the work as WUC bore upon the cl 32.1 claim. I reject the submission made in this Court to the contrary. As to the extent to which a mark-up was applied to cl 32.1 claims, that was a matter for the adjudicator to determine. I reject Qube’s submission that the adjudicator’s conclusion “sits uneasily” with the application of the mark-up to “variations”. Whether or not that observation is correct, it was within the adjudicator’s jurisdiction to decide whether a mark-up should be applied to cl 32.1 claims and the quantum of that mark-up.
I do not agree with the primary judge at [149] of the September judgment that the adjudicator ran together his reasoning on cll 32.1 and 36.1 in such a way as to cast doubt on the adjudicator’s conclusion that cl 32.1 was an independent basis that Martinus was entitled to succeed on CN-420. The primary judge’s reasoning at [150] of the September judgment about temporary works was a proposition not advanced by Qube. It was not an error, let alone a jurisdictional error, for the adjudicator to reach the conclusion that he did.
For these reasons, I would allow ground 1 of the appeal.
By notice of contention ground 1, Qube asserts that the primary judge’s conclusion about CN-420 was correct for the additional reason that the adjudicator’s decision was made in circumstances where there was a denial of procedural fairness, in that no argument was ever put forward by Martinus that the relevant directions were “deemed to be variation orders” or were variation orders “for all intents and purposes”.
Qube’s complaint should be rejected. The adjudicator did not rely upon a “deeming” of something to be a variation order as Qube’s submitted. Reading the adjudicator’s reasons fairly, as the cases make clear should be the approach adopted, the adjudicator concluded that Qube’s resequencing directions were variation orders within the meaning of cl 36.1:
[1362] Accordingly, I accept the argument that the Directions to Re-sequence the Works given in writing by the Respondent under clause 32.1, required the Claimant to perform additional work and were variation orders under clause 36.1 for all intents and purposes.
The adjudicator’s subsequent reference to “deemed variation orders” at [1367] is plainly a reference to what the adjudicator had already concluded at [1362]. As Demex makes clear, only if there has been a substantial denial of procedural fairness by an adjudicator will there be jurisdictional error under the SOP Act. The SOP Act provides for a “rough and ready” process (Chase Oyster Bar at [208]), not intended readily to be held invalid on judicial review.
Martinus had, from the beginning, advanced the submission that the directions given by Qube were variation orders within the meaning of cl 36.1. Whether they were or were not was a matter within the jurisdiction of the adjudicator to determine. I reject Qube’s submission that there was any denial of procedural farness.
I would reject ground 1 of the notice of contention.
Ground 2 of the notice of appeal, to the extent it refers to CN-420, contains an error. The parties were content to address this ground on the basis that it was intended to address CN-277.5.
Item 2B of the INTS Payment Claim claimed extension of time delay costs for an Extension of Time (“EOT”) identified as EOT 34. The claim was identified as CN-277.5. The basis of the claim was identified at “ItemRef4” and “Appendix 8” of the Payment Claim.
The contractual basis for this claim was cl 34.9 of the INTS Contract which addressed an entitlement to costs incurred by Martinus as a direct result of delay the subject of an extension of time (subject to a daily cap of $80,000). In the INTS Payment Schedule, these claims were disputed by Qube (in Appendix 4 and Appendix D). In Appendix D, at 1.8 Qube asserted that the costs claimed by Martinus were inconsistent across its supporting documentation and that Martinus had not demonstrated its costs because the INTS Contract had already been terminated and Martinus paid most of its entitlements.
Martinus addressed the EOT 34 claim CN-277.5 in [804]-[876] of its Adjudication Application. Martinus addressed each of the reasons advanced by Qube in the Payment Schedule for not paying Martinus’s claim. In its Adjudication Response at [857]-[870] Qube contended that Martinus had not established that it had actually incurred costs as a result of the delay and advanced a range of reasons for non-payment which were not contained in Qube’s Payment Schedule.
The adjudicator addressed this claim at [1990]-[2021] and addressed quantum issues at [2017]-[2020]:
[2017] I am persuaded the Claimant is entitled to delay costs pursuant to Item 26 of Part A of the Annexure and clause 34.9 of the Contract at the rate of $80,000 per day because the Pavements, Drainage and Utilities were underway at the time of Termination and the Claimant was at peak manning levels and which the Claimant explained in Appendix C of its CN - 277.5 claim that forms a part of the Payment Claim.
[2018] I acknowledge the Respondent’s assertions about having made certain payments for preliminaries. That is, however, not relevant in determining whether the Claimant is entitled to an extension of time and delay costs under the Contract.
[2019] If the Respondent has made an overpayment, and as all payments are on account of the final payment, it is for the Respondent to exercise its rights of certifying the appropriate amount accounting for any overpayments it may have made.
[2020] I have, therefore, determined that the Claimant is entitled to an extension of time of 13 days and to associated Delay Costs of $80,000 per day, which amount to $1,040,000 for Claim for EOT (EOT 34 Update 2) and Delay Damages CN – 277.5.
[193] Quantum issue: Qube’s challenge here covers a different type of alleged jurisdictional error, namely a failure to consider submissions made by Qube. In considering this ground I will follow the same approach as I did when considering the challenge to the decision on variation CN-420.
[194] It is of course clear that the Adjudicator was obliged, if he was to uphold the claim, to find that Martinus had incurred additional costs attributable to the relevant delaying event for each of the days for which the EOT was allowed, and that each day’s costs exceeded $80,000. It was not enough simply to identify the existence of some ongoing effect. It is equally clear that, so far as Qube was concerned, this was in dispute, and had been addressed by Qube in their submissions to the Adjudicator.
[195] The Adjudicator did not refer to those submissions in his reasons. Again, the question is whether that justifies an inference that he did not consider them.
[196] Again, counsel for Martinus did not, in my view, advance any persuasive reason for declining to draw the inference. On the face of it, the submissions were relevant. The amount involved was significant in absolute terms, if not large in a relevant sense. I do not think that I should infer that the Adjudicator had no time to deal with it. If he thought that for some reason he did not have to, he could readily have said so.
[197] Again, I draw what seems to me to be the natural and straightforward inference on the probabilities, namely that for some reason the Adjudicator overlooked Qube’s submissions. I did not understand materiality to be in dispute. In my view, jurisdictional error is established.
The submissions made by Qube allegedly not referred to are obscure. Qube in its submissions in this Court refers to Appendix D. In the relevant part of Appendix D under the heading “lack of substantiation of costs claimed” Qube asserted that Martinus’s claimed costs were inconsistent across its supporting documentation (1.8.2) and that Martinus had not demonstrated its costs as the INTS Contract had been terminated and most preliminaries already paid (1.8.4). The adjudicator dealt with these submissions.
I am unable to accept that the adjudicator fell into error in making the findings he did, much less that any error was a jurisdictional error. The inference I draw is that the adjudicator, having considered all the material relevant to CN-277.5, was persuaded by Martinus’s explanation contained in Appendix 8 of its CN-277.5 claim as to proof of its delay costs. The adjudicator plainly rejected, as he was entitled to, Qube’s contention that there was a “lack of substantiation of costs claimed”. It was not necessary for the adjudicator specifically to record Qube’s submission in any greater detail. Whether the adjudicator was satisfied that Martinus had substantiated the costs it claimed was a matter for the adjudicator and not the Court on judicial review for jurisdictional error.
No breach of the obligation to consider submissions “duly made” provided by s 22(2) of the SOP Act was established. It follows that ground 2 of the notice of appeal should be allowed.
Notice of contention ground 2 asserts that the primary judge should have concluded that the adjudicator’s decision about CN-277.5 was legally unreasonable. I do not agree. Qube does not address the fundamental principle that legal unreasonableness must be judged by reference to the scheme of the statute under which the decision was made: Li at [67].
The essence of the adjudicator’s determination was that the INTS Contract was terminated on 25 September 2023: at [2003]. Prior to termination of the contract, a condition precedent for an EOT was that it was notified within 14 days. That time bar did not survive termination. For delay events occurring after about 11 September 2023, no time bar was applicable. By reason of s 13(4)(b) of the SOP Act, Martinus was entitled to make a claim for delay damages after termination: at [2010]-[2013].
That construction may have been “contestable” as the primary judge observed, but his Honour correctly found that the adjudicator’s reasoning was not “in some way alien to the Act”. It was a matter for the adjudicator to construe the contract and apply the SOP Act, including s 13(4)(b).
Finally, to the extent it was pressed, I reject Qube’s attempt to recharacterise this question as a jurisdictional fact. It is not correct that the validity of a Payment Claim turns on whether the correct amount is calculated. Authority has long held that an adjudicator does not commit a jurisdictional error by misapplying ss 9 and10 of the SOP Act. In John Holland, Hodgson JA (with whom Beazley JA agreed) said at [39] that the adjudicator’s jurisdiction is to determine the amount of the progress payment in accordance with ss 9 and 10 of the Act. In Transgrid v Siemens Ltd (2004) 61 NSWLR 521; [2004] NSWCA 395 at [34] (Hodgson JA, Mason P and Giles JA agreeing), this Court said even if the “amount calculated in accordance with the terms of the contract” were, on the true construction of s 9(a) and of the contract, the amount certified by the Superintendent, a decision to the contrary by the adjudicator would be a mere error of law, and not such as to render the determination invalid. If it be the case that, on the true construction of the contract, there could be no entitlement to a progress payment in respect of a variation not approved in writing by the Superintendent, the inclusion of such a progress payment would likewise be an error of law, and not a matter which would render the determination invalid.
I would reject notice of contention ground 2.
At the outset of consideration of this ground it should be acknowledged that Mr Giles SC, who appeared in this Court for Qube, accepted in his oral submissions that the primary judge had fallen into the errors Martinus alleged in relation to this ground. Qube’s written and oral submission in this Court were thus directed to their notice of contention.
Despite that concession, given that this issue is by far the largest in terms of quantum, I will nevertheless explain this aspect of the dispute between the parties. Ground 3 addressed the issue of whether Qube had validly terminated for cause (as Qube asserted) or, instead, had terminated for convenience (as Martinus asserted). If the adjudicator concluded that Qube terminated for convenience, Martinus had a contractual entitlement to payments such as demobilisation costs and other wasted costs. Martinus pursued these costs in its Payment Claim as CN-522.
Qube asserted in the Payment Schedule that Martinus had no entitlement to these payments because Qube had terminated for cause. This question depended principally on the validity of one of two show cause notices which, in turn, depended on whether there was a “substantial breach” of contract within the meaning of cl 39.2 of the INTS Contract.
The critical show cause notice was described by the primary judge as the “Directions Show Cause” Notice. The Directions Show Cause Notice was founded on an alleged failure to comply with directions issued by the Superintendent under cl 20 of the INTS Contract. The primary judge found that the adjudicator failed to consider submissions made by Qube about what his Honour called the “construction question”: September judgment at [235] and [237].
Qube issued the Directions Show Cause Notice on 29 August 2023. The two asserted failures to comply with the Superintendent’s directions related to:
A direction given on 28 July 2023, in respect of supply and placement of bottom ballast; and
A direction given on 14 August 2023, in respect of the commencement of the pre-building of turnouts.
An initial problem with the primary judge’s finding that the adjudicator had fallen into jurisdictional error in failing to consider Qube’s submissions, is that the Directions Show Cause Notice had nothing whatever to do with what the primary judge described at [223] of the September judgment as a “direction to Martinus to remove its building materials from part of the site known as the LOGOS area” nor with “a direction to Martinus to provide details of its subcontracting arrangements”. These matters were not relied on by Qube in relation to its Directions Show Cause Notice case. Rather, these matters were relied upon only by Qube in submissions as evidence of an alleged repudiation at general law. As I have said, in this Court, Qube did not seek to defend the reasoning of the primary judge on this point.
In its Adjudication Response, Qube made submissions about a “Failure to Comply with Directions – Interface” 6.125-6/127. These submissions related to what the primary judge called the “LOGOS area direction” but did not relate to the Directions Show Cause Notice. The primary judge apparently misunderstood that. His Honour said:
[227] It is sufficient to refer to Qube’s submissions on the LOGOS area direction. The submissions stated (emphasis original):
6.125 Martinus states that it has not breached the Contracts by its failure to comply with a direction from the Superintendent relating to the use of a “laydown area” along the route. It is entirely unclear to Qube on what basis Martinus could maintain such a position. There is no dispute that, on 4 September 2023, the Superintendent directed Martinus to remove track rails from an area known as the “LOGOS Area”. Similarly, there is no dispute that Martinus failed to comply with that direction within the time requested by the Superintendent, or at all. As noted above, a disagreement as to the basis for the direction does not entitle Martinus to ignore a direction issued by the Superintendent, or otherwise excuse performance of its obligations under the Contracts.
6.126 If Martinus disagrees with a direction issued by the Superintendent, it is entitled to raise a dispute in respect of the direction, which is to be determined in accordance with the dispute resolution provisions set out in clause 42 of the Contracts. However, even if it disagrees with the basis of / premise for a direction issued by the Superintendent, Martinus is still obliged to comply with that direction and to do so promptly. A failure to do so constitutes a breach of the Contracts.
6.127 In response to the specific matters raised by Martinus, Qube says as follows:
…
6.127.5 Martinus’ access to [the LOGOS area] was specifically subject to the above-mentioned limitation [requiring Martinus to facilitate access to the area]. It had no right to use that area indefinitely and for its convenience. The right to access and use this area was always liable to be revoked upon request. Further, and more importantly, Qube is under no obligation to provide access to additional areas of land, outside of the project boundaries, by means of “assistance” to Martinus. In executing the Contracts. Martinus warranted that it had informed itself of the site constraints. It took all risks associated with performing the WUC within the confines of the site. It cannot now complain that it had nowhere to store trackwork materials. That was entirely a matter to be coordinated and managed by Martinus.
6.127.6 If it required additional land for the purposes of a “laydown area”, then it was obliged to make those arrangements itself. It cannot seek to shift responsibility for site logistics and materials storage onto Qube and/or the Superintendent. The Superintendent was under no obligation to propose some alternative location for the storage of such materials, and so Martinus’ complaints in this regard are misconceived and go nowhere.
6.127.7 Martinus does not say that it could not have complied with the direction. Instead, it says compliance with that direction would have required “double-handling”, and consequential impacts to other works along the route. The fact that the movement of such supplies would have resulted in some inconvenience to Martinus does not mean that it is entitled to completely disregard the direction.
6.127.8 Martinus has not disclosed any intelligible basis on which to defend this ground.
Qube did not make submissions to the effect that any failure to comply with the “LOGOS Area direction” was a “substantial breach” within the meaning of cl 39.2 of the INTS Contract. Qube did submit that “as noted above, a disagreement as to the basis for a direction does not entitle Martinus to ignore a direction issued by the Superintendent, or otherwise excuse performance of its obligations under the Contracts”. The primary judge interpreted those remarks as a reference back to an earlier part of Qube’s submissions where Qube had made submissions about the meaning of “substantial breach” within the meaning of cl 39.2 of the INTS Contract.
The construction question referred to in the September judgment directed attention to the meaning of cl 39.2 of the INTS Contract:
[235] So far as the Adjudicator’s actual decision is concerned, all that this discloses is an arguable error of law on the face of the record, which would not be jurisdictional. But (and this is the difference between the Directions Show Cause Notice and the Program Show Cause Notice) Qube made submissions on the construction question which are not referred to in the Adjudicator’s reasons on that question.
[1634] No direction under clause 29.3 was issued by the superintendent in relation to the show cause notices it issued under clause 39.3 in August and September 2023.
[1635] The Respondent argues the Claimant failed to comply with the directions of the superintendent given under clause 20 of the Contract, which provides;
*“*20 Superintendent
The Principal shall ensure that at all times there is a Superintendent. In the performance of its role and functions under:
a) the first paragraph only of subclause 34.5;
b) subclauses 37.2 and 37.4; and
c) subclause 41.5,
the Superintendent shall act independently.
Other than in respect of the role and functions referred to in the preceding paragraph of this clause 20, the Superintendent shall give directions and carry out its other functions under the Contract on and behalf of and as agent of the Principal and not as an independent certifier, assessor or valuer.
Except where the Contract otherwise provides, the Superintendent may give a direction orally but shall as soon as practicable confirm it in writing. If the Contractor in writing requests the Superintendent to confirm an oral direction, the Contractor shall not be bound to comply with the direction until the Superintendent does so.
The Contractor must promptly comply with any direction given by the Superintendent in connection with the Contract or WUC.
If the Contractor fails to comply with a direction of the Superintendent given under the Contract or fails to perform any of its obligations under the Contract. the Superintendent may issue a notice to the Contractor requiring such performance and specifying a reasonable time for performance. If the Contractor does not comply with the notice, then, in addition to any other rights of the Principal under the Contract or at law, the Principal may, by further notice to the Contractor, perform or have others perform that obligation. The Principal may recover the costs and expenses of it or others performing the obligation as a debt due to the Principal by the Contractor.
[1636] The failures to comply with directions relied upon by the Respondent in the Directions Show Cause Notices under clause 39.3 of the Contract, cannot be categorised as any of the substantial breaches of Contract listed in clause 39.2 of the Contract.
[1637] Further, clause 20 of the Contract sets out the Respondent’s remedies for a breach of a direction given under that clause by the superintendent. None of those remedies include a right to terminate the Contract under clause 39.4 of the Contract. In other words, a failure to comply with a proper direction given by the superintendent under clause 20 of the Contract is not a substantial breach of Contract.
It was within the adjudicator’s jurisdiction to construe the contract. The adjudicator concluded that:
the alleged failures to comply with directions identified by Qube in the Directions Show Cause notice could not be categorised as a substantial breach within the meaning of cl 39.2; and
breach of a direction given by a superintendent under cl 20 could not constitute a substantial breach within the meaning of cl 39.2 permitting termination.
There was no reason in those circumstances for the adjudicator to repeat submissions made by Qube about alleged breaches of other directions given by the Superintendent, or submissions about what in general may amount to “a substantial breach”, lest he fall into jurisdictional error.
The primary judge’s conclusion that the adjudicator had fallen into jurisdictional error was not correct. His Honour proceeded from the incorrect understanding that the Qube submissions allegedly not taken into account were relevant to the issue of the Directions Show Cause Notice. As Mr Giles SC accepted in oral address:
His Honour did make the error in his reasoning in thinking that we relied on those two matters as part of our contractual termination case.
The adjudicator’s construction of the INTS Contract rendered it unnecessary further to consider the meaning of “substantial breach”. On the adjudicator’s construction, a failure to comply with a direction given by the Superintendent cannot constitute a substantial breach. Whether that conclusion is correct or not as a matter of construction, it was not a jurisdictional error for the adjudicator so to conclude. Qube’s submissions pointing to other alleged substantial breaches by failure to comply with directions given by the Superintendent were irrelevant on the adjudicator’s construction of the INTS Contract. It was not an error, let alone a jurisdictional error, to fail to record each of those submissions.
The submissions relied upon by the primary judge to find jurisdictional error were not relied upon by Qube in respect of the Directions Show Cause Notice. The adjudicator was not compelled to interpret Qube’s submissions in the way the primary judge interpreted them, lest he fall onto jurisdictional error. The adjudicator discharged his statutory function. It was sufficient for the adjudicator to record his construction of the contract. He was not obliged to identify reasons for rejecting alternative constructions.
There was no breach of s 22(2) of the SOP Act giving rise to jurisdictional error. Notice of appeal ground 3 should be allowed.
Notice of contention ground 3 is dense, to the point of impenetrability. Notice of contention ground 3 contains five sub-grounds:
The first relates to a further allegation the adjudicator failed to consider submissions “duly made” in relation to substantial breaches relied upon by Qube;
The second complains about an alleged breach of procedural fairness by the adjudicator in making “an apparent finding” that the “Program Show Cause Notice” was not a valid notice;
The third complains that the adjudicator failed to consider submissions duly made by the first respondent with respect the limits of recovery under cl 40A of the Contracts;
The fourth complains that the adjudicator’s decision was unreasonable and irrational and thus infected by jurisdictional error, in that the adjudicator determined to treat the claim as a “variation” and thus apply a 45.31% mark up to the claimed costs;
The fifth is a further complaint of unreasonable and irrational decision making by the adjudicator determining that Martinus was entitled to amounts under cl 40A of the INTS Contract in respect of the costs of “unfixed materials” and failing thereafter to reconcile those claims with other amounts claimed and awarded in respect of related contract works items, leading, it was alleged to a situation where Martinus “practically” would be paid twice.
Despite the breadth of the notice of contention, Qube’s written and oral submissions were largely directed to a matter which was not the subject of any one of these five sub-grounds – an alleged failure by the adjudicator to address Qube’s alleged entitlement to terminate “for cause” at common law. No application was made by Qube to amend the notice of contention. Mr Giles SC also accepted that the primary judge failed to deal at all with Qube’s argument about an alleged entitlement to terminate “for cause” at common law in his reasons.
Qube’s submission about the Court’s function in these circumstances was encapsulated in the following exchange:
PAYNE JA: …What’s our authority or power to determine the issue in your favour on the assumption the trial judge is wrong?
GILES: Well, because your Honours have the authority under 75A [of the Supreme Court Act]. I have the problem that I have not got a notice of contention that quite grapples with the point.
I reject Qube’s submission. This point, error by the primary judge and the absence of any notice of contention, was clearly flagged by Martinus long prior to the two day appeal hearing in this Court. It is common ground that the primary judge did not determine the issue that Qube now wishes to agitate. In the absence of a notice of contention it is not open to Qube to submit in this Court that the “adjudicator simply dismissed each of Qube’s contentions as to termination pursuant to cl 39.4 and then proceeded to deal with the termination for convenience claim”, thereby ignoring Qube’s repudiation at general law case. Qube should not be permitted to rely in this Court on a contention that the primary judge should have upheld a complaint of jurisdictional error on the basis of an argument that his Honour did not deal with at all. To permit Qube to advance such an argument now would be unfair to Martinus.
Even if I am wrong about this conclusion, I am not persuaded that Qube established that the adjudicator failed to consider a submission duly made by Qube. This is because Qube accepts that the adjudicator considered Qube's case about each of the “show cause” notices at [1594]-[1641]. Qube accepts that the adjudicator accepted Martinus’s case about each of those notices. It appears that in so doing the adjudicator also addressed and rejected Qube's case that Martinus’s conduct gave rise to a repudiation at general law. For example, at [1639], when addressing the Directions Show Cause notice, the adjudicator found that he was not satisfied that a particular individual was empowered to “take any repudiatory conduct” on behalf of Martinus. I am not satisfied, even on the contingent basis I am dealing with this complaint, that the adjudicator failed to consider a submission duly made by Qube about repudiation at common law.
It is now necessary to consider each of the five sub-ground arguments raised by Qube under the ground 3 of the notice of contention.
As to the first sub-ground, Qube complains that the adjudicator erred in finding that the Program Show Cause Notices lack detail sufficient to enable Martinus to understand them. I do not agree. The adjudicator was entitled to come to the conclusion he did. It is, with respect, obvious that if Qube wished to rely upon a show cause notice to justify a termination for cause, Qube would need adequately to state the alleged breaches and give Martinus an opportunity to remedy those breaches. Martinus complained at some length about the absence of sufficient detail in the various notices. The adjudicator’s findings that the notices lacked sufficient detail were well open. No failure to consider submissions duly made has been shown.
As to the second sub-ground, Qube complains that the finding of a want of “examples or particulars” was not a point which was made by Martinus in the Adjudication Application. Since Martinus had not disputed the show cause notices on the basis that they were inadequate, Qube alleged that the adjudicator erred by deciding on that basis. This was said to give rise to an issue of procedural fairness. Again, I do not agree. Clause 39.3(b) requires that a show cause notice must “state” the “alleged substantial breach”. The notice must require Martinus to remedy the breach: cl 39.3(c). It was plainly open to the adjudicator to find that where Qube sought to rely on a show cause notice to justify a right of termination, he was entitled to consider whether the notice met the requirements of cl 39.3 and in particular, whether the notice adequately stated the breaches and afforded Martinus an opportunity to remedy the alleged breaches. In any case, Martinus had complained at length that the show cause notices lacked detail. It was open to the adjudicator to observe that the show cause notices lacked particulars. Qube was not denied procedural fairness by the adjudicator so concluding.
As to the third sub-ground, that “the adjudicator failed to consider submissions duly made by the first respondent with respect the limits of recovery under clause 40A of the Contracts”, Qube complains that the adjudicator did not reveal how he “squares the express right under cl 40A as somehow being a variation, the rights of which are specifically laid out in a different clause of the contract”. The alleged violence to the language of the contract was said to demonstrate legal unreasonableness.
Qube’s argument on this sub-ground is labyrinthine. Qube complains that the adjudicator found that Martinus was entitled to amounts under cl 40A in respect of the costs of “unfixed materials” where he did not thereafter reconcile those claims with other amounts claimed and awarded in respect of related contract works items.
I do not agree with Qube’s complaint. The construction adopted by the adjudicator may be incorrect, but he was not required to “square” to Qube’s satisfaction the various rights under the Contract lest he fall into jurisdictional error. I am not satisfied that the adjudicator’s reasoning was in some way legally unreasonable.
As to the fourth sub-ground, the adjudicator’s conclusion that Martinus was entitled to apply a margin of 45.31% to works consequential on Qube’s termination was not legally unreasonable. The adjudicator was entitled to characterise the work as a variation to the initial scope caused by Qube’s conduct. The adjudicator accepted, as he was entitled to, Martinus’s argument at [1670] that post termination work was outside the scope of the contract.
As to the fifth sub-ground, in respect of unfixed materials, the adjudicator accepted Martinus’s claim on the basis that no valid reason was given by Qube in the Payment Schedule for withholding payment:
[1825] In relation to the Ballast, the Respondent has made no submissions about how it calculated the scheduled amount, which is different from the claimed amount for the Claimant’s supply of unfixed material in Schedule 2 to Appendix E of the Payment Schedule or in section “Subclause 40A(d)(iv)” in Appendix E of the Payment Schedule. That amounts to an unsupported assertion which is not a valid reason for withholding payment that the Claimant could consider.
[1826] The consequences of the Respondent failing to provide a reason for withholding means the adjudicator may accept the claimed amount set out by the Claimant as set out above at paragraph 622), it is clear from Insite Construction Services Pty Ltd v Daniels Civil Pty Ltd & Anor [2023] QSC 33 that where the Respondent fails to provide its assessment of quantum, it is open to the adjudicator to accept the Claimant’s valuation of the corresponding claimed item in the Payment Claim.
[1827] Accordingly, I have decided the Claimant is entitled to the claimed amounts of $2,575,389.38 for unfixed material (Ballast).
The conclusion reached by the adjudicator was not legally unreasonable. If it were necessary to decide, the adjudicator was also entitled to conclude that it followed from Qube’s own assessment that there was still ballast onsite which needed to be taken from the stockpile post termination. That reasoning was not inconsistent with a conclusion that Martinus had achieved a completion of over 100% in the supply of ballast.
I reject notice of contention ground 3.
Under the INTS Contract, Qube held security in the form of unconditional bank guarantees. On the same day as the Payment Claim was made, Qube called on and converted security in a total of $7,029,849.50. Martinus did not make a claim in relation to the bank guarantees in its Payment Claim. In the Payment Schedule, however, Qube deployed the converted security of $7,029,849.50 by adding $7,029,849.50, derived from the call on the bank guarantees, to the adjusted contract price, which it called the “Superintendent’s revised contract value”. The amount of $7,029,849.50 was then applied by Qube to effect claimed set-offs in section 6 of the INTS Payment Schedule. The primary judge explained [241] that Qube calculated the “set offs” by first claiming $5.4 million in payments it had made to contractors who had replaced Martinus on site, on the basis that Qube (having terminated for cause) was entitled to recoup those amounts. Secondly, Qube “set off” $2.1 million which it had paid on account.
In the adjudication application, Martinus accepted that the $2.1 payment on account should be deducted by the adjudicator from the amounts determined to be payable but disputed claims for payments totalling $5.4 million made by Qube for:
amounts claimed by Qube associated with John Holland;
amounts claimed by Qube associated with Vaughan Civil;
amounts claimed by Qube associated with Mainland Civils;
amounts claimed by Qube related to Reversal of an account payment; and
amounts claimed by Qube associated with Additional consultants.
In Qube’s Payment Schedule, the alleged “set-offs” totalled $7,493,553.26. Once the security was applied against these claims, the residual of the claims asserted by Qube against Martinus in the Payment Schedule was $463,703.76; that is, despite Qube receiving security in the sum of $7,029,849.50, by reason of these additional claims (framed as “set-offs”), Qube was asserting it was entitled to $7,493,553.26 from Martinus and that even after the amount of the guarantee was accounted for, Qube was entitled to an additional $463,703.76 from Martinus. Qube referred to this amount as an additional deduction under Item 4A of its Payment Schedule.
The adjudicator addressed the bank guarantee issue at [2042]-[2090]. The adjudicator rejected Qube’s argument that he lacked jurisdiction to determine whether this was properly before him. In the adjudicator’s view:
Qube had elected to account for the proceeds of the bank guarantees as an amount added to the adjusted contract sum by the Payment Schedule:
[2077] The Respondent’s has elected to account for the proceeds of the Bank Guarantees at item 6.4.1 of the Payment Schedule as an amount that is added to the adjusted Contract sum.
[2078] The fact that it appears under the heading “Deductions I Recovery” is of no consequence.
[2079] The relevant fact is that the Respondent has assessed and scheduled for payment in the Payment Schedule an amount that is equivalent to the redeemed value of the Bank Guarantee to which it had recourse on 8 February 2023. That amount of course is a positive amount from which appropriate deductions could be made.
…
[2086] On the basis of my determination of the Payment Claim including the determination of the claimed “Deductions / Recovery” in the Payment Schedule, the Respondent is not entitled to retain the proceeds of the redeemed securities because the Claimant does not owe the Respondent any amount under the Contract.
[2051] I have determined above that the Claimant terminated for its convenience under clause 40A and following that determination, the Claimant accrued a right to claim for the return of any security held by the Respondent pursuant to clause 40A(e) of the Contract.
[2052] I have also determined below that the Respondent is not entitled to payment for “deduction I recovery” items referenced items 6.1, 6.2, 6.3 and 6.4.3 in the Payment Schedule.
[2053] In those circumstances, the Contract requires the Respondent return any security held by the Respondent. Security is defined by clause 1 of the Contract and includes cash.
…
[2084] I determined that claim above and found that the Respondent terminated for its convenience under clause 40A on 25 September 2024 pursuant to its notice so given.
[2089] In any event, I do not consider that any “accounting” or “reversal” other than that provided by the Respondent in the Payment Schedule is required.
[2090] Accordingly, I will consider the amount scheduled in the Payment Schedule as indicated by the Respondent at section 6.4.1 of the Payment Schedule.
The adjudicator did not allow a claim for the reversal of the call on the bank guarantee. Rather, the adjudicator recognised that in its Payment Schedule Qube had identified an “adjusted contract price” and had added as a positive integer the sum of $7,029,849.50 being the amount of the call on the guarantees.
The primary judge concluded there were two distinct jurisdictional errors. First, his Honour found that the adjudicator had fallen into jurisdictional error by awarding to Martinus a sum by way of restitution of the proceeds of the bank guarantees when no such claim had been included in Martinus’s Payment Claim. Secondly, the primary judge found that the adjudicator fell into jurisdictional error by not considering Qube’s submissions “duly made”.
Qube contends that the primary judge was correct to construe what it had done in its Payment Schedule as he did in the September judgment:
[279] Scope of adjudication: The Adjudicator’s reasons show that he awarded to Martinus a sum by way of restitution of the proceeds of the bank guarantees on the ground that, as a consequence of his finding on the termination issue, Qube had no right to retain that sum. The problem is that, as the Adjudicator repeatedly acknowledged, no such claim had been included in Martinus’ payment claim.
[280] Contrary to the Adjudicator’s statements at [2065] and following, Qube did not, in its payment schedule, add the bank guarantee proceeds to the amount for which it was liable under Martinus’ payment claim. What Qube actually did was to claim a set-off of $500,000. The credit for the bank guarantee proceeds was a credit allowed by Qube in calculating the amount of the set-off claimed. It was in no way an acknowledgment of some freestanding liability to Martinus.
…
[288] As to whether judicial review is available, I agree that the facts of Icon are distinguishable. The Court of Appeal’s decision proceeds on the basis that the “backcharges” were claims by the principal against the contractor introduced by the principal by way of set-off. In the present case, the bank guarantee proceeds were a separate credit allowed by the principal against its set-off claim. The distinction is, I think, effectively recognised in Icon at [25].
Qube submitted that this approach cohered with what Basten JA had said in Icon at [25]. Qube contended that the present case does not involve any error of the kind which this Court found in Icon. I do not agree.
As I have explained at 61-64] by reference to the decision in Icon, in the present case Qube introduced the converted security in a total of $7,029,849.50 by deploying it in the Payment Schedule as an amount added to the adjusted contract sum. In doing so, Qube introduced to the dispute to be resolved by the adjudicator an issue about the calculation of the value of the work claimed by Martinus in the Payment Claim. It is not to the point that Martinus did not make a claim in restitution for $7,029,849.50 in its Payment Claim. Qube was the party who was asserting that the value of Martinus’s claim should be reduced by reason of “set-offs” greater than the sum of the value of the guarantees. Further, and contrary to Qube’s case, the adjudicator did not award any amount by way of restitution, rather, the adjudicator resolved a dispute about the value of the claim Martinus had made. The adjudicator did so by taking onto account the “adjusted contract price” introduced to the dispute by Qube in its Payment Schedule.
The “dispute propounded by the parties” which the adjudicator was empowered by the SOP Act to determine was that which arises after both the Payment Claim and the Payment Schedule have been considered.
In Ceerose, this Court explained that the position taken by the respondent in its Payment Schedule necessarily affected the adjudicator’s task. There is nothing in the SOP Act which expressly or impliedly prohibits an adjudicator from recognising the fact that in a Payment Schedule the contract price could be adjusted upwards even if that upwards adjustment was not the subject of the Payment Claim. So much follows from the terms of ss 13 and 14 of the SOP Act which I have set out at the outset. Further, there is nothing in the SOP Act which prohibits the adjudicator from accepting or rejecting deductions claimed in a Payment Schedule. It is well established that an adjudicator can consider accepting or rejecting such deductions even if they are not the subject of a Payment Claim: see Icon at [33], [35] and [36]. Even if the adjudicator was incorrect, the scope of the dispute identified by the Payment Claim and Payment Schedule was a matter for the adjudicator. The decision of this Court in Icon is governing. The meaning of the Payment Claim and the Payment Schedule were matters falling within the jurisdiction of the adjudicator.
The second jurisdictional error found by the primary judge in relation to the bank guarantees was an alleged failure to consider Qube’s submissions about the first instance decision in Australia Avenue and the “point about the form of the Schedule”:
[297] Again, the starting point is that the Adjudicator did not say anything in his reasons which indicated that he considered Qube’s submissions. In particular, there was no reference to Icon. And there was no reference to the point about the form of the schedule.
The first instance decision in Australia Avenue was overruled in Icon. No jurisdictional error was established in allegedly failing to consider that overruled first instance decision. In respect of the form of the Payment Schedule, I have earlier rejected the primary judge’s characterisation of what the adjudicator did and was entitled to do. It is an impermissible incursion into the role of the adjudicator to construe the Payment Schedule as having “only set off” $463,703.76. The adjudicator was entitled to act on his understanding that Qube itself had added $7,029,849.50, derived from the call on the bank guarantees to the adjusted contract price, which Qube called the “Superintendent’s revised contract value”, before allegedly applying “set-offs” (being additional claims made by Qube) in a greater amount. There was no error in the adjudicator so concluding. Much less was any jurisdictional error established.
I would uphold ground 4 of the notice of appeal.
This issue concerned Martinus’s claim for what the INTS Contract defined as “preliminaries”. The INTS Contract set out a contract price for preliminaries of $31,405,498.73, but did not identify when that amount became payable. There had been a dispute between the parties in a prior adjudication as to when preliminaries were to become payable, which had been resolved essentially on the basis that preliminaries should become payable “from day to day, on a ‘straight line’ basis, from the beginning of the contract to the original date for practical completion”: November judgment at [9].
The INTS Payment Claim included a claim for preliminaries of $30,334,965.30. This was a claim for 96.59% of the total contract price for this item: see INTS Determination at [203].
In the INTS Payment Schedule, Qube said the following under the heading “Preliminaries (Qube)”:
The Superintendent has valued preliminaries by applying the following pro-rata formula for time based activities. Any activities that are not time based have been valued as they are complete:
1. PC Date less Contract Date = 484 days;
2. Termination date less Contract date = 465 days;
3. Termination date progress = 465 days / 484 days;
4. Total % complete = 96%.
The Superintendent acknowledges the Adjudicator’s Determination in respect of the cumulative percentage for Preliminaries. However, the Superintendent does not agree with the methodology, as it is the incorrect approach considering numerous Extension of Time claims have been claimed (for Preliminaries) and included within the Adjudicator’s Determination.
In the INTS Payment Schedule, Qube also addressed specific sub-items in respect of the Preliminaries claim. The primary judge focused on four of these items: 1.1.4, 1.2.1, 1.2.2 and 1.7.3. The relevant parts of the Payment Schedule are set out in the November judgment at [12]. One of the items objected to (1.2.1) set out the following: “Time based calculation, please refer to column AJ-AL, row 13-18”. The reference to a “time based calculation” was understood by the primary judge to be a reference to the question of whether these preliminaries should be valued on a straight line basis. Item 1.2.1 was of some significance for the primary judge because in the INTS Adjudication Application Martinus asserted that a time-based method was not appropriate: see November judgment at [13].
It is important to first note the adjudicator’s observation at [154]. Having referred to this Court’s decision in Dualcorp Pty Ltd v Remo Constructions Pty Ltd (2009) 74 NSWLR 190; [2009] NSWCA 69 (which held that adjudication determinations attracted the doctrine of issue estoppel), the adjudicator said:
[154] Accordingly, if any dispute about contractual entitlement has been resolved by an adjudication determination, I am required to follow that contractual interpretation in this Adjudication Application.
[200] I accept the Respondent’s method of calculating the amount of Item 1 Preliminaries to which the Claimant is entitled. …
…
[203] The Respondent’s method for calculating the value of completed Item 1 Preliminaries indicates the Claimant is entitled to 96.07% of the total amount for Preliminaries.
[204] Therefore, the Claimant is entitled to claim 96.07% of the Contract Sum for this item (being; $41,405,498.730), which amounts $31,171,262.63).
[208] The Respondent has provided no reasons for withholding payment save for providing its method of calculating the value of the Preliminaries, which I accept.
Qube’s case was that this reasoning disclosed a failure to deal with the “dispute between the parties”: November judgment at [18]. The primary judge effectively accepted that argument, concluding that this reasoning involved error, being a “fail[ure] to deal with the four items in question” (being items 1.1.4, 1.2.1, 1.2.2 and 1.7.3) and a failure to “consider Qube’s objections to them”: November judgment at [31]. The primary judge treated the scope of the “dispute” between the parties as if it was a matter for objective determination by the Court.
What the adjudicator was required to consider, however, was, relevantly, the Payment Claim and Payment Schedule as interpreted by him. The adjudicator interpreted the Payment Schedule as asserting that preliminaries should be valued at 96.07% complete (rather than the figure of 96.59% complete asserted by Martinus). The interpretation of the Payment Schedule was a matter for the adjudicator. Having so interpreted the Payment Schedule, the adjudicator accepted what he understood to be Qube’s position i.e. that preliminaries should be valued at 96.07% complete. The adjudicator interpreted the Payment Schedule as not advancing any other reason for withholding payment in respect of preliminaries. That was a conclusion open to the adjudicator.
The reasons excerpted by the adjudicator appeared under the heading “Preliminaries (Qube)” and were plainly understood by the adjudicator to be Qube’s sole reasons for rejecting Martinus’s Payment Claim in respect of preliminaries.
The reasons which his Honour concluded that the adjudicator overlooked were inconsistent with the previous adjudicator’s determination. The previous adjudicator had held that preliminaries were to be valued on a straight line basis. In the items relied on by his Honour, Qube was seeking to contend that the items should be valued on a different basis. The adjudicator found that he was bound to adopt the conclusions of the previous adjudicator because of, inter alia, Dualcorp in this Court. There was no reason to expect the adjudicator would or should in those circumstances say any more about Qube’s argument that various items should be valued on a different basis.
The primary judge also found that there was a “simple arithmetical” error in the adjudication and this was a jurisdictional error because it “cannot have been intended that an award would be binding if affected by such an error”: November judgment at [49]-[51]. His Honour characterised this as having “no reason” to award the amount which was awarded: November judgment at [51].
The proposition that a mathematical error is jurisdictional is not correct. A mathematical computation is a finding of fact. Findings of fact are matters for the adjudicator: Icon at [13]-[15] (Basten JA, Meagher JA agreeing at [35], Leeming JA agreeing at [36]); Iskra v MMIR Pty Ltd [2019] NSWCA 126 at [39]-[40] (Gleeson JA, Bathurst CJ agreeing at [1], Payne JA agreeing at [55]).
The mathematical error was incorrectly characterised as an absence of a “reason”, when, at most, it was an incorrect reason.
I would uphold ground 6 of the notice of appeal.
By notice of contention ground 5, Qube contends that the finding the subject of appeal ground 6 also involved a denial of procedural fairness or was legally unreasonable.
As to the alleged claim of legal unreasonableness, it is no doubt correct, as Qube says, that the decision of an adjudicator is not “unreviewable” for jurisdictional error. This conclusion does not assist Qube here. The adjudicator’s interpretation of the Payment Claim and Payment Schedule was clearly open to him. It was a decision far removed from one affected by jurisdictional error as being legally unreasonable.
As to the alleged denial of procedural fairness, it is no doubt correct that the adjudicator accepted that he was bound to act in accordance with authority which the adjudicator understood to include Dualcorp. It was not a denial of procedural fairness for the adjudicator to act upon his understanding of the law. The adjudicator here was not bound to raise with Qube whether it wished to challenge any binding authority of this Court, including Dualcorp, before acting upon that authority. It would be antithetical to the objects of the SOP Act to require adjudicators so to act and to provide, in effect, a running commentary on the legal conclusions they proposed to draw. There was no denial of procedural fairness.
I would reject notice of contention ground 5.
This issue concerned a claim for additional design management resources (CN-421) because of a failure on the part of Qube to provide designs adequately and promptly. In the INTS Payment Claim, Martinus claimed $6,127,988.62. Qube scheduled $0 in its Payment Schedule. The adjudicator ultimately allowed $2,932,040.48.
The primary judge concluded that the adjudicator erred by failing to consider “parts of the Payment Schedule and submissions where [certain] quantum objections were identified and developed”: November judgment at [65].
The precise material referred to appears to be sections of a document entitled “CN-421 – Additional Design Management Resources” (“CN-421 Document”), which appeared about 500 pages into Qube’s INTS Payment Schedule: see November judgment at [57]-[58]. The primary judge inferred that the material was not considered by the adjudicator. This was because the adjudicator said that Qube had not provided an explanation as to why it disputed certain design and commercial manager resources claimed by Martinus, whereas the primary judge considered that, at paragraph 2.28 of the CN-421 Document, criticism was made of the claim for design resources.
Jurisdictional error was not established in this instance. The adjudicator correctly recorded what appeared in Qube’s INTS Payment Schedule under the heading “Reasons for Withholding Payment” in respect of CN-421. Those reasons did not include a specific objection to the claim for the three designers. There was thus no error in the adjudicator’s statement that there had been no explanation by Qube about why it was not paying these claims. The adjudicator understood the entirety of Qube’s reasons for withholding payment in respect of CN-421 to be those set out at [1401]:
[1401] The Respondent provided the following reasons for withholding payment;
“CN 421 relates to a claimed variation for additional design management resources fo**r work which the Contractor was required to carry out as result of post-IFC design changes directed by VO-054 and VO-061. The Superintendent rejects the principal and quantum of CN 421.
*Further details of the Superintendent’*s response to CN 421 are provided at Appendix C.2 to INTS and ISRA Payment Schedule 15.
In summary, the Superintendent notes that:
• the additional design management resources which are subject of CN 421 do not constitute a variation to the WUC or additional works under the Contract. The costs claimed are time-related costs for additional preliminary costs arising from post-IFC design changes directed by VO 054 and VO 061;
• the Contractor has been compensated for additional time-related costs for the extended duration of design management resources on site within the VO 054 remeasure for post-IFC design changes up to 16 June 2023 (RAILPSPL-VARN-000060) which has been used by the Superintendent to value VO-054 works claimed, assessed and paid;
• further, the additional design resources would be covered by the Contractor’s application of the 45.31% mark-up determined by Alan Stapleton in adjudication determinations #525 and #526 (on an interim basis and until finally determined by arbitration) applied to the works subject of CN 521 – inclusive of design changes arising from VO 054, VO 055 and VO 061;
• to the extent that further design management resources were required (beyond those accounted for within the valuation of VO 054 and the 45% mark-up applied to costs claimed for varied works which are the subject of VO 054 and VO 061):
o the costs claimed are preliminary time-related costs and are not direct costs of a variation to which the determined 45% markup applies;
o the Superintendent instructed Currie & Brown to undertake an independent benchmarking exercise of the Contractor*’s rates, including* fo**r additional design management resources. The results of this benchmarking exercise confirm that the rates applied by the Contractor are Sell Rates, which are already inclusive of overheads and profit;
o *the additional resources claimed include resources f**or non-*design related works; and
o the Contractor has failed to substantiate or provide evidence of the costs allegedly incurred
• to the extent that the claimed costs constitute a variation (which is denied*), the Contractor failed to submit CN 421 in accordance with clause 36.3A of the Contract and therefore has no entitlement to claim* for any additional time or cost arising out of alleged “additional design management resources” arising from VO 054 or VO 061
The adjudicator was entitled to understand the complaint at 2.28 of the CN-421 Document to be directed to a different issue – entitlement – because it challenged whether there was an entitlement to additional designers at all. The adjudicator concluded that there was an entitlement to additional designers at [1439]. The primary judge did not perceive error in the adjudicator’s determination of entitlement (as distinct from quantum).
It may be that the adjudicator misunderstood the CN-421 Document and the scope of any additional reasons given by Qube beyond those he quoted at [1401]. I do not, however, infer that the adjudicator had not considered Qube’s submission. This is because he excerpted large portions of it at [1402]. Even assuming the adjudicator misunderstood the document, he considered it. That is not jurisdictional error.
I would allow ground 7 of the appeal.
This issue concerned a claim for certain additional labour costs arising from delayed and deficient signal design. Martinus claimed $672,217.54. Qube scheduled $0 in its Payment Scheule. The adjudicator allowed the claimed amount.
His Honour concluded that the adjudicator fell into jurisdictional error in that he did not consider the two objections to this claim set out in the INTS Payment Schedule:
that Martinus has failed to substantiate or provide evidence of the costs allegedly incurred; and
that Martinus has used incorrect rates in its calculations.
The primary judge found that Qube’s reasons for scheduling $0 in respect of this claim in the Payment Schedule should have been understood as being contained in a document located approximately 500 pages into the Payment Schedule which repeated a contention that there had been a failure to substantiate costs and also said that “the costs claimed are preliminary time-related costs and are not direct costs of a variation to which the 45.31% markup applies”: see November judgment at [69].
I do not agree that jurisdictional error was established. Qube’s objections were each set out at [1458], where the adjudicator explained that Qube provided the following reasons for withholding payment:
“CN 422 relates to a claimed variation fo**r additional signalling design management required as a result of post-IFC design changes directed by VO 055.
*Further details of the Superintendent’*s response to CN 422 are provided at Appendix C.3 to the INTS and ISRA Payment Schedule 15.
The Superintendent rejects the principal and quantum of CN 422. In summary, the Superintendent notes that:
1. the additional signalling design management resources which are subject of CN 422 do not constitute a variation to the WUC or additional works under the Contract:
2. the costs claimed were indirect job costs which should have been and/or were included as part of the Contractor’s original tender price;
3. The costs claimed are time-related and relate to the cost of Martinus engaging a signalling manager for 47 weeks in circumstances where it had originally allowed for a duration o f17 weeks. The costs claimed are therefore additional preliminary costs arising from post-IFC design changes directed by and valued as part of VO 055.
4. The Contractor’s preliminaries include an allowance for a Senior Project Engineer (signals), a Project Engineer (signals), a Grad Engineer (Signals) and a Trainee Engineer (signals) (as per the Tender Org Chart for the preliminaries base contained in the PMP). In fact, the Contractor has only provided one Signalling Manager as per the September 2023 Org Chart and although it has identified the role of a signalling engineer, that role has never been filled;
5. to the extent that additional signalling design management resources were required (beyond those accounted for within the valuation of VO 055 and the 4 5% mark-up determined by Alan Stapleton in adjudication determinations #525 and #526 (on an interim basis and until finally determined by arbitration) applied to costs claimed for varied works which are the subject of VO 055):
6. the costs claimed are preliminary time-related costs for the extended involvement of the Signalling Design Manager and are not direct costs of a variation to which the 45% mark-up applies;
7. the Contractor has failed to substantiate or provide evidence of the costs allegedly incurred; and
8. the Contractor has used incorrect rates in its calculations;
9. to the extent that the claimed costs constitute a variation (which is denied), the Contractor failed to submit CN 422 in accordance with clause 36.3A of the Contract and therefore has no entitlement to claim fo**r any additional time or cost arising out of alleged “additional design management resources” arising from VO 055.
The adjudicator plainly understood that he had dealt with all of Qube’s reasons for withholding payment in respect of CN 422.
The first reason referred to at [1458] found by the primary judge not to have been considered was that there was a failure to substantiate the claim. The adjudicator in fact dealt with this issue at [1471]. The adjudicator found that a “sufficient breakdown” was provided by Martinus to Qube. That, in context, was a finding that there was substantiation of Martinus’s claim, and a rejection of Qube’s submission.
I reject Qube’s submission, made in this Court, that it was an error, let alone a jurisdictional error, for the adjudicator to fail to understand the difference between a “sufficient breakdown” of costs claimed and a “substantiation” of costs claimed. To read an adjudicator’s reasons as Qube suggests is to do so with an eye attuned to error. That approach to judicial review of the decision of an adjudicator under the SOP Act has repeatedly been rejected.
The second reason referred to at [1458] (also relied on by the primary judge) was that Martinus had used incorrect rates. Qube’s complaint was apparently that Martinus had claimed direct costs, when it should only have claimed time-related costs. That contention was expressly considered and rejected by the adjudicator at [1470].
I reject Qube’s submission, made in this Court, that jurisdictional error in failing to consider a submission “duly made” may be discerned by comparing the adjudicator’s finding at [1470] with that made at [1466]. It may that the adjudicator considered but failed to appreciate some complexity in Qube’s arguments, now repeated in in this Court. Such an error, if be an error, was not jurisdictional.
In neither instance was it correct to conclude that it was established that the adjudicator had failed to consider a submission “duly made” by Qube.
I would allow ground 8 of the notice of appeal.
This was a claim for additional costs arising from wet weather, CN-451. In respect of this item, Martinus claimed $73,263.83. Qube scheduled $0. The adjudicator allowed the claimed amount.
It is clear from [1523]-[1525] of the adjudicator’s determination that the adjudicator’s reasons for allowing the claimed amount were that, first, in the INTS Payment Schedule Qube’s reasons for withholding payment in respect of CN-451 were directed to a different claim, CN-437. Secondly, Qube did not provide any reasons for withholding payment for the purposes of the SOP Act.
The primary judge stated that Qube’s Adjudication Response (cf the Payment Schedule) contained reasons regarding CN-451 that the adjudicator was obliged to consider. The primary judge inferred that the adjudicator did not do so: November judgment at [96]-[100].
I am unable to agree with this conclusion. It was a matter for the adjudicator to construe Qube’s Payment Schedule and, having construed it, to form a view as to what (if any) valid “reasons” for withholding payment were given by Qube in that Payment Schedule. If the adjudicator was of the view that no valid reasons for withholding payment were given in the Payment Schedule, the adjudicator was obliged to decline to consider any further submissions about CN-451 contained in the Adjudication Response: s 20(2B) of the SOP Act.
Qube failed, in terms, to respond to CN-451 in the INTS Payment Schedule. It was not an error, let alone a jurisdictional error, for the adjudicator to conclude as he did. I reject Qube’s submission, made in this Court, that despite the absence of any reference in Qube’s Payment Schedule to CN-451, the adjudicator was required to interpret the Payment Schedule by reference to a large number of “contextual matters” found outside Qube’s Payment Schedule, and to conclude that reasons for Qube not paying CN-451 were to be found in Qube’s Payment Schedule response to another claim, CN-437. The error in the primary judge’s reasoning was to proceed on the basis that it was for the Court to interpret the Payment Schedule and to conclude what submissions were “duly made”. These were matters for the adjudicator.
I would allow ground 9 of the appeal.
By notice of contention ground 6, Qube submitted that it was legally unreasonable for the adjudicator to treat “obvious typographical errors in the Payment Schedule as entitling him to disregard the first respondent’s adjudication response”. Qube contended that the adjudicator was required to overlook the errors made by Qube in its Payment Schedule.
I reject Qube’s submission. I have set out the principles for determining legal unreasonableness in the context of the SOP Act above at [75]-[80]. The adjudicator’s decision was not legally unreasonable. The adjudicator was not required to fix mistakes made by Qube in its Payment Schedule, lest he fall into jurisdictional error.
Qube also submitted that the way that the adjudicator dealt with the submissions involved a denial of procedural fairness. I disagree. I have addressed the principles relating to procedural fairness in the context of the SOP Act above at [71]-[75]. There is no procedural unfairness in reading Qube’s Payment Schedule in the terms in which it was expressed. There was no denial of procedural fairness.
I would reject ground 6 of the notice of contention.
This ground raises essentially the same issue as was raised by ground 9. This issue involved a claim for additional costs incurred in addressing stormwater pit design cost issues arising from design changes issued by Qube. The claim was identified by Martinus as CN-299. Martinus claimed $96,842.89. Qube’s Payment Schedule referred to a different claim, CN-377, and scheduled $0 as owing. Qube gave no reasons in the Payment Schedule for disallowing CN-299. The adjudicator allowed the claimed amount.
The primary judge found that the adjudicator, having concluded that Qube’s Payment Schedule did not give valid reasons (because it responded to CN-367 rather than CN-299), should nevertheless have gone on to consider the contents of the Adjudication Response:
[132] In my view, it was plain from the adjudication application and Qube’s adjudication response that Qube was objecting to CN-299 on the same basis on which it had (successfully) objected to CN-267. That being so, the same conclusions follow as for CN-451 and the challenge succeeds.
[746] As to the Respondent’s rejection of CN 367, that has nothing to do with the assessment of the Claimant’s claim CN-299 and I will not consider the reasons for withholding payment further in this section.
Ground 7 of the notice of contention should be rejected, for essentially the same reasons as notice of contention ground 6:
The adjudicator’s decision was not legally unreasonable. The adjudicator was not required to fix mistakes made by Qube in its Payment Schedule, lest he fall into jurisdictional error.
There is no procedural unfairness in reading Qube’s Payment Schedule in the terms in which it was expressed. There was no relevant denial of procedural fairness.
This issue involved a claim for costs associated with termination of intertrack drainage. Martinus claimed $70,760.13 in the ISRA Payment Claim – CN-353. Qube scheduled $24,744.82. In the Adjudication Application, Martinus reduced this claim to $35,956.70: see ISRA Adjudication Application at [711].
The adjudicator understood that Martinus had in fact only reduced its claim to $60,701.52, being the sum of the claimed amount ($35,956.70) and the scheduled amount ($24,744.82): ISRA Determination at [771]. The adjudicator awarded that amount: ISRA Determination at [776].
The primary judge appears to have concluded in the November judgment that there was jurisdictional error either on the basis that the adjudicator had awarded more than the claimed amount or on the basis that there was a mathematical error:
[136] The Adjudicator’s reasoning followed the same pattern as for other claims where the 45% mark-up was in issue. He upheld Martinus’ entitlement to charge a mark-up at that level, and therefore concluded that its claim succeeded in full. Using the figure given in earlier in his reasons, he awarded Martinus $61,000.
…
[139] Counsel for Martinus characterised any error which may have been made by the Adjudicator as an error in his understanding of Martinus’ adjudication application. Counsel submitted that any such error was not a jurisdictional one. Counsel did not accept that any error, to the extent it was a mathematical error, gave rise to “legal unreasonableness”. Counsel submitted that such an error “might” be capable of being dealt with under s 22(5), but not by way of judicial review proceedings.
I do not agree:
As to the first possible basis for the finding of jurisdictional error, the interpretation of the Payment Claim and the Adjudication Application were matters for the adjudicator. Errors of the kind made here were errors within jurisdiction.
As to the second possible basis for the finding of jurisdictional error, a mistake in calculation of the kind made by an adjudicator is an error of fact and not a jurisdictional error.
I would allow appeal ground 11.
Ground 8 of the notice of contention should be rejected. It was not contended by Qube that the amount here in issue (a little more than $24,000) was outside the amount claimed by Martinus in the ISRA Payment Claim. Whilst the adjudicator misunderstood the detail of the claim, it was not a denial of procedural fairness for the adjudicator to determine that the sum claimed was derived by the addition of two amounts identified in the submissions he considered were “duly made”. The adjudicator’s error was an error within jurisdiction.
Further, it was not legally unreasonable for the adjudicator to determine that the sum claimed was the derived by the addition of two amounts identified in the submissions “duly made”. This approach reflects the fact that the SOP Act provides for a “rough and ready” process (Chase Oyster Bar at [208]), not intended readily to be held invalid on judicial review.
I would reject notice of contention ground 8.
I will deal with ground 5 of the appeal and ground 4 of the notice of contention, which address the issue of costs, together and out of order.
The adjudicator required Qube to pay the whole of the costs of the INTS Adjudication and the ISRA Adjudication. The adjudicator had a discretion to determine the apportionment of costs between Qube and Martinus: s 29(3) of the SOP Act. The adjudicator apportioned 100% of the costs to Qube.
Where there is jurisdictional error in the determination of an adjudicated amount, s 32A of the SOP Act gives the court the power to set aside a determination of costs: Ceerose at [187]. Section 32A is a remedial power which arises once jurisdictional error has been found. Section 32A assumes that parts of a determination have been “affected” by jurisdictional error and parts not so “affected”.
Naturally enough, given that his Honour had found jurisdictional error in a number of respects, his Honour understood that he was exercising the power given by s 32A of the SOP Act. As I have found, however, the adjudicator did not fall into jurisdictional error in any of the respects identified. It follows that the s 32A(2) power was not enlivened. No separate complaint was made by Qube about alleged jurisdictional error in the costs determination. Accordingly, I would uphold ground 5 of the notice of appeal.
Cross-appeal ground 1, relating to the INTS adjudication, arose out of design variations made by Qube. Variation orders were issued by the Superintendent which specified figures which the Superintendent considered Martinus was entitled on account of the design variations.
Martinus claimed to be entitled to a greater amount and made a Payment Claim (CN-521) for the value of work allegedly attributable to the variation. The total amount to which Martinus claimed to be entitled was $20.5 million, but in the Payment Claim, Martinus acknowledged credits for allowances which had already been made.
The content of the dispute was explained in the following paragraphs in Martinus’s Adjudication Application:
603. The dispute regarding the design change variation is about quantum. In the Payment Schedule, Qube relies on a competing assessment by Currie & Brown of the design change under VO-54, VO-55, and VO-61.
604. In broad terms, the dispute between the parties relates to:
(a) whether the design change is to be administered as a “remeasurement” (per Qube’s / RPS’/ Currie & Brown’s position) or as a variation (Martinus’ position);
(b) how new or changed items of work are to be reflected as part of the valuation of the design change; and
(c) the rates to be applied to the work.
605. In the Payment Schedule, Qube states that Martinus has:
(a) attempted to change the rates/prices “beyond the scope of remeasurement exercise for variations”;
(b) not substantiated what the design changes are;
(c) not substantiated the rates applied by Martinus; and
(d) changed previously agreed quantities.
The adjudicator found Qube’s Payment Schedule to be “incomprehensible”.
CN-521 was included in the INTS Payment Claim in the amount of $23,528,069.85. The INTS Payment Claim incorporated by reference three further documents setting out the basis of the claim: “INTS_VO54, VO55 & VO61 Summary”, “MITD_INTS – Design Change Variation Detailed Cost Breakdown & Claimed Progress” and “Appendix 1 – Progress Mark Ups”.
Qube’s INTS Payment Schedule addressed CN-521 in several places. The Payment Claim had a line item addressing CN-521, which stated:
CN-521 relates to additional works associated with the post-IFC design changes directed by the Superintendent pursuant to VO 054, VO 055 and VO 061. The quantum claimed by the Contractor for VO 054, VO 055 and VO 061 is disputed.
The Contractor has cumulatively claimed the following amounts for CN-521 submitted on 8 February 2024 under the heading ‘The Contractor Claim for Design Change Variation Scope – VO054 & VO061’ with its payment claims for INTS and ISRA:
• INTS Payment Claim 15 (INTS PC 15)): $23,528,069.85 (exc. GST)
• ISRA Payment Claim 15 (ISRA PC 15)): $4,286,019.84 (exc. GST)
The Superintendent has assessed the value of CN-521 within its certification of the cumulative amounts certified for INTS and ISRA works within INTS and ISRA Payment Schedule 15. Further details of the Superintendent’s approach to the assessment of works which are the subject of CN-521 (inclusive of post-IFC design changes up to 30 September 2023 directed by VO 054, VO 055 and VO 61) are contained in the Superintendent’s response to CN-521 at Appendix C.5 to INTSA and ISRA PS 15.
A similar point was made by Qube in other parts of the INTS Payment Schedule.
Qube did not provide, in relation to CN-521, any document which directly responded to Martinus’s claim. Rather, Qube asserted that Martinus’s claim should be measured against “INTS and ISRA works within INTS and ISRA Payment Schedule 15”.
Of course, Qube was free to adopt whatever methodology and format it wished to adopt in its Payment Schedule responding to Martinus’s Payment Claim. Having chosen, however, to rely on a non-responsive and confusing array of cross-references in the Payment Schedule (including references to both the INTS and ISRA Contracts), Qube cannot now reasonably complain that the adjudicator found the Payment Schedule to be incomprehensible. I have concluded that the adjudicator’s description of the Payment Schedule was a fair one.
Qube’s approach was to respond to a Payment Claim made about an aspect of the INTS Contract by assessing it partly under the INTS Contract and partly under the ISRA Contract. Qube’s choice to address both contracts in this way made the Payment Schedule difficult, if not impossible, to understand properly.
In a separate part of Qube’s Payment Schedule, Qube included by cross-reference a lengthy spreadsheet. The spreadsheet contained a column entitled “Valuation of VO-54, 055 and 063 (Changes in Quantities and Rates)”. The spreadsheet contained no discernible or intelligible means of reconciling anything in the spreadsheet directly against Martinus’s claim in CN-521. Despite the assistance of experienced Senior Counsel on this appeal, Qube’s real case on this issue remains elusive.
[615] With respect to the scheduled amount, as Martinus explained, it was difficult to identify exactly what was scheduled in response to CN521 because of Qube’s use of a blended schedule which combines both contract scope and variation scope. Martinus has carried out its own calculation of what Qube has scheduled in response to what was claimed by Martinus in CN521 in the reconciled version of the Payment Schedule which is referred to in section G.2 above.
[616] Martinus’ calculation is that the cumulative amount scheduled by Qube for the design change work under the INTS Contract is $12,143,133.08.
[568] As Martinus will explain in further detail below, in the Payment Schedule, rather than assess Martinus’ contract scope claim separately to Martinus’ design change / variation scope claim, Qube / RPS has returned to assessing the contract scope and variation scope as part of a blended schedule.
[569] To use a degree of understatement, Qube’s decision with respect to the format of the Payment Schedule has made it difficult for Martinus to understand what exactly Qube has scheduled against what was claimed by Martinus, and what remains in dispute.
[639] However, in the Payment Schedule, Qube and RPS have returned to the blended schedule format. The reasons given by Qube for doing so are incoherent. Qube said that it revised its approach to “ensure that no items have [been] missed, to make the assessment more user friendly and to avoid confusion between the Contract Works and the measured variation works”. Qube has achieved the complete opposite of what it apparently set out to achieve.
Qube’s contention that it was an error for the adjudicator to observe that Martinus “asserts that it does not understand the Respondent’s assessment of CN-521” must be rejected. Martinus expressly submitted that Qube’s approach “made it difficult for Martinus to understand” Qube’s assessments (at [569]) and caused “confusion” (at [639]).
It was clearly open to the adjudicator to find that the INTS Payment Schedule was not comprehensible.
In the Adjudication Application, Martinus also separately addressed an assertion by Qube that it had approached the manner of assessment in the way that it had because the proper analysis of CN-521 was that it comprised a claim for a “remeasurement” rather than a claim for a “variation”: see [621]-[633].
Echoing the confusing way Qube addressed CN-521 in the Payment Schedule, in the Adjudication Response, Qube made a number of seemingly internally inconsistent claims:
At [3.3] and [3.20], Qube contended that CN-521 was beyond the scope of the Payment Claim, an assertion which is of no continuing relevance (being one of a handful of issues not sought to be relitigated by Qube on appeal).
At [10.3], Qube identified CN-521 as a “variation” claim for $23,528,069.85. This presentation of the issue was contrary to Qube’s Payment Schedule allegation that CN-521 should, in some way, be allocated across various contract works, and not treated as a variation.
At [10.59]-[10.96], under the heading “IFC Design Changes and the Design Change Variation”, Qube advanced a submission that Martinus had miscalculated the amount scheduled in respect of CN-521. According to this claim by Qube, the correct scheduled amount was $14,500,650.55, of which $12,130,541.36 was attributable to the INTS Contract: see at [10.64]. In support of that contention, Qube referred to “the Final Payment Schedules” (at [10.64]), but gave no reference to any part of the Payment Schedules where that figure was identified.
At [10.64], Qube submitted that its Payment Schedules were not difficult to understand or misleading. Clearly, Qube understood that Martinus was submitting that Qube’s INTS Payment Schedule was difficult to comprehend. I reject Qube’s submission that there was any denial of procedural fairness involved in the adjudicator’s finding that the Payment Schedules were difficult to understand and misleading.
The adjudicator addressed CN-521 at [1543]-[1575]. The adjudicator analysed the key parts of the INTS Payment Claim, the INTS Payment Schedule, the INTS Adjudication Application and the INTS Adjudication Response at [1543]-[1548].
The adjudicator noted that, although on the face of the INTS Payment Schedule Qube scheduled $0 against CN-521, by reference to the INTS Adjudication Response, Qube had apparently scheduled $12,543,894.84 against CN-521, albeit apportioned amongst various other items:
[1549] The Respondent, actually, scheduled $12,543,894.84 for payment for work carried out under VO 054 and VO 061 in the Payment Schedule but it apportioned the amount scheduled relating to this claim for a variation under various parts of the claims for the Contract works. Those amounts were recorded in the Payment Schedule as such.
[1555] The Respondent explained its methodology of assessing claim CN – 521 but has not provided any reasons for withholding payment by explaining the quantities it has determined or the rates it has applied for each part of that claim where the scheduled amount was less than the claimed amount set out in CN – 521 in the Payment Schedule.
[1556] The Respondent has made an assessment of the claims against VO 54, VO 55 and VO 61, however save for a total amount assessed for that claim, the Respondent did not provide a break-up directly responding to the amounts claim in CN -521 of the Payment Schedule.
[1557] The Respondent has broken down the assessment of the claims against VO 54, VO 55 and VO 61 for each item in a way that cannot be directly compared to the amounts claimed by the Claimant.
[1558] The Respondent also applied rates (apparently determined by its consultant, Currie & Brown) and quantities that differ from those claimed by the Claimant in its claim CN- 521 in the Payment Claim without any explanation of how those quantities were measured or those rates determined.
….
[1560] As the scheduled amounts are not referable to the amounts claim in CN – 521 of the Payment Claim, I am not persuaded that the Respondent has satisfied its obligations under section 14 of the Act and the Contract because it failed to provide reasons for withholding payment against each claimed item to which the Claimant could respond either accepting or disputing the amount scheduled.
…
[1564] The Respondent’s approach is uncertain as it cannot be compared to the claim. Further, the Respondent provides no explanation of each quantity or rate that it applied that was different to those claimed in the Payment Claim by the Claimant. That explanation, if it had been provided would have constituted a reason for withholding payment as required under clause 37.2 of the Contract and under section 14(3) of the Act.
[1572] The Respondent has not, therefore, complied with s 14(3) of the Act because it failed to provide reasons for withholding payment that the Claimant could consider and to which it could respond if it chose to do so.
The essential parts of the adjudicator’s reasoning were:
The INTS Contract was not a remeasurable contract, and it was appropriate to separate contract works from variations, as Martinus had done: at [1552]-[1554].
Qube’s approach had led to uncertainty because the items in Qube’s INTS Payment Schedule could not be compared to, and were not directly referable to, Martinus’s Payment Claim: at [1560] and [1564].
Qube had not provided an explanation about how the quantities and rates applied to each separate component of the contract works against which CN-521 had been apportioned had been determined: at [1558], [1560] and [1564].
Properly understood, Qube’s the INTS Payment Schedule did not supply “reasons for withholding payment” in response to the claimed item within the meaning of s 14(3): at [1572].
The primary judge considered Qube’s complaints in respect of CN-521 in the November judgment at [159]-[178]. At that time, Qube’s sole complaint was that CN-521 was affected by legal unreasonableness. As the primary judge correctly found, the threshold for finding that a decision was legally unreasonable is high. I have earlier addressed legal unreasonableness at [75]-[80].
The primary judge concluded that the adjudicator’s interpretation of the Payment Schedule was a matter within the adjudicator’s jurisdiction and was not legally unreasonable:
[177] It may be accepted that, like any other decision of the Adjudicator on the merits, there is a possibility that a decision by an adjudicator of this type could be subject to review on the grounds of “legal unreasonableness”. But I do not think that this has been demonstrated in the present case. Qube’s allegation is simply an allegation of an ordinary error in reasoning. It is not an allegation of decision-making alien to an adjudicator’s function under the Act.
[178] It may be that the Adjudicator failed to address, or address fully, the grounds of rejection advanced in Qube’s payment schedule. But if so, that still gave him an unreviewable justification for not addressing consequential submissions by Qube and meant that there was no jurisdictional error in failing to address such submissions. This challenge fails.
Qube puts its case in cross-appeal ground 1 about jurisdictional error in three ways. Two are complaints about an alleged denial of procedural fairness and the third is legal unreasonableness. Each is, in substance, a different label for the same complaint, arising from Qube’s contention about the adjudicator’s interpretation of the INTS Payment Schedule and conclusion that it did not relevantly set out “reasons” within the meaning of s 14(3) of the SOP Act.
I reject Qube’s contention that the adjudicator reached a decision on a basis not put by the parties. What the adjudicator found was that Qube’s approach was “uncertain as it cannot be compared to the claim”: at [1564]. That was what Martinus had submitted in the INTS Adjudication Application at [568]-[569], [615]-[616], and [649]. Qube was not denied procedural fairness. The point Qube complains about was clearly taken by Martinus.
Qube adopted an approach in its Payment Schedule where it did not respond directly to the Payment Claim, but instead used its own format and methodology. The differences between the amount claimed and the amount that Qube proposed to be paid could not readily be understood. Qube ought reasonably to have been aware that that adjudicator might conclude that Qube’s Payment Schedule could not readily be comprehended. Qube both had, and availed itself of, an opportunity to deal with that point in its Adjudication Response. There was no denial of procedural fairness.
Qube also contends that the adjudicator constructively failed to exercise jurisdiction because the adjudicator failed to resolve the dispute raised by the parties’ submissions. The phrase “constructive failure to exercise jurisdiction” is, of course, a label which is merely descriptive of jurisdictional error: Ceerose at [46] and the cases there referred to. The substance of Qube’s complaint is that there was a denial of procedural fairness because of the failure to consider a substantial, clearly articulated argument. There is a risk with this type of argument that claims about failure to address matters can shade into claims about arguments being resolved incorrectly because misunderstood, or not really grappled with, which tends towards merits or appellate review: M1 v R1 [2024] NSWCA 256 at [65] (Mitchelmore JA, Leeming JA agreeing at [1], Price AJA agreeing at [122]); see also Secretary, Department of Education v Dawking [2024] NSWCA 4 at [90]-[97] (Gleeson JA, Mitchelmore JA agreeing at [100], Kirk JA agreeing at [101]).
Qube’s argument is simply another way of contending that the adjudicator’s construction of the Payment Schedule was erroneous. That argument fails. At the risk of repetition, it is for an adjudicator to decide the dispute which he or she understands has been propounded by the parties. An adjudicator’s decision is not affected by jurisdictional error because a Court, for itself, concludes that a different dispute had been propounded by the partes. If this were not so, it would subvert clear authority arising under the SOP Act that an adjudicator can decide whether submissions are “duly made”. Qube’s complaint is premised upon an assertion that certain submissions were “duly made”, in circumstances where the determination of which submissions were “duly made” was a matter for the adjudicator. I would reject this second aspect of Qube’s complaint.
Finally, Qube contended that the adjudicator’s conclusion was legally unreasonable. I reject Qube’s assertion that legal unreasonableness has been established. The adjudicator’s understanding of the dispute was open to him. The primary judge correctly rejected this complaint.
Cross-appeal ground 1 should be rejected.
Cross-appeal ground 2 concerned contract works variations 2.1-2.6, 2.8-2.9, 2.11, 2.14-2.15 and 2.17. These components of the adjudication concerned twelve contract works items for which Martinus claimed to be entitled to variation payments. The adjudicator allowed the claim but applied some deductions. The primary judge explained that because the adjudicator adopted the same reasoning to deal with the claims as he adopted for CN-521 (cross- appeal ground 1), the complaint made by Qube could be rejected on the same basis. Qube accepts that ground 2 should fail if it fails on ground 1. Qube’s acceptance that this ground falls with ground 1 is sufficient to dispose of this ground.
The reasons why Qube’s case should be rejected can be exposed by taking item 2.1 as an example. The Payment Claim addressed item 2.1 under four line items, 2.1, 2.1.1, 2.1.2 and 2.1.3. In respect of item 2.1, Qube said in its Payment Schedule:
The Superintendent notes there has been minimal design change since the Quantity Surveyors determination within VO-054. All conduit configurations are unchanged and the only change to pits has been the relocation of S14A by approximately 1 metre. As such, this has been valued using rates set out by the Quantity Surveyor within VO-054.
[226] The Claimant indicates that it has claimed 99.07% of the adjustment for VO-054, 055 and 061 (changes in quantities and rates)”) and the “budget transfer” under its claim for CN - 521 “Claim for design change variation scope VO 054 and VO 061”. I have accepted the percentages claimed for the adjustment for VO- 054, 055 and 061 (changes in quantities and rates)”) and the “budget transfer” to determine that part of the scheduled amount to be transferred to the scheduled amount for CN - 521 “Claim for design change variation scope VO 054 and VO 061.”
[227] In order to compare the scheduled amount to the claimed amount for Item 2.1 - Service Zones, I will transfer 99.07% of the scheduled amount relating to VO 054, VO 055 and VO 061 and “budget transfer” from Item 2.1 - Service Zones in the Payment Schedule to the Respondent’s scheduled amount relating to the claim relating to CN - 521 “Claim for design change variation scope VO 054 and VO061.”
[7.8] The suggestion that Qube’s approach to valuation of the contract works ought to be rejected because it has not been undertaken in accordance with the Contracts, is rejected. The reference to a remeasurement in the context of clause 36 is explained in section 10 below.
The adjudicator addressed this claim at [214]-[236]. The adjudicator concluded that:
Qube’s Payment Schedule did not “respond” or “directly respond” to Martinus’s Payment Claim: at [217] and [225].
the INTS Payment Schedule did not “provid[e] sufficient explanation of each of the new items”: at [217].
Qube had not “provided sufficient explanation for [him] to understand how each of the … new entries relate to any claimed item in the [INTS] Payment Claim”: at [219].
Qube had not “explained why the scheduled amount is less than the claimed amount”: at [229].
These were each correct statements of fact. They do not disclose error, let alone jurisdictional error. The problems which Qube introduced into the INTS Payment Schedule in respect of CN-521 repeated themselves throughout. Qube did not clearly respond to the INTS Payment Claim. Qube introduced multiple new line items. Qube failed to give any intelligible explanation about those new line items. It was open for the adjudicator, within the proper exercise of his jurisdiction, to reach the conclusions he did.
His Honour addressed these claims as follows in the September judgment:
Contract works variations 2.1-2.6, 2.8-2.9, 2.11, 2.14-2.15 and 2.17
[179] These components of the adjudication concerned twelve contract works items for which Martinus claimed to be entitled to variation payments. The Adjudicator allowed the full amounts claimed but again applied some deductions.
[180] In each case, the Adjudicator adopted the same reasoning to deal with the claims as he adopted for CN-521. Indeed, the same paragraphs (including quotations from the case law) appear to have been copied and pasted into the relevant parts of the adjudication.
[181] In oral submissions, counsel for Qube indicated that the determinations were challenged on the same grounds as the CN-521 determination and did not address the items individually. In these circumstances, I proceed on the basis that the reasons I have given for rejection of the challenge concerning CN-521 apply equally to these claims.
No error has been shown in the primary judge’s conclusions about this issue.
Qube determined to reply to Martinus’s Payment Claim in a non-responsive way. Respectfully, after a full hearing in the Court of Appeal with experienced Senior Counsel on both sides, I remain unsure of the points Qube was seeking to make. Much less am I critical of the adjudicator for allegedly misunderstanding Qube’s reasons for rejecting Martinus’s claim.
Qube was aware that Martinus was asserting that Qube’s Payment Schedule was difficult to understand. It was a matter for the adjudicator to accept or reject the parties’ contentions on that issue. The primary judge’s reasons for rejecting the substance of ground 1 apply equally to ground 2.
The outcome of the cross-appeal in respect of the INTS Determination should equally apply to the analogous claims that arose in respect of the ISRA Determination, being each of the claims entitled “Contract Works” and enumerated 1 to 9 (inclusive) in the Amended List Statement. These claims were variously dealt with by the adjudicator at [200]-[611] of the ISRA Determination by applying substantively the same reasoning as that applied to the analogous claims in the INTS Determination.
I would reject ground 2 of the cross-appeal.
Qube applied for a stay of the proceedings pending a final determination of the arbitration referred to at [23]. The primary judge refused to grant that stay. Qube seeks leave to appeal from the decision of the primary judge.
The essential debate between the parties was whether Qube was entitled to a stay given what it submitted were financial difficulties faced by Martinus, such that there was a risk that if Qube was successful in the final arbitration, Martinus could not repay the sum it obtained under the SOP Act. The primary judge said in the September judgment:
[354] Indeed, up to a point, the more financial difficulty the contractor is in, the less reason there is for granting a stay, as the more likely it will be that the grant of such a stay will result in the contractor being deprived of the cashflow which is needed to sustain its operations. It is only when insolvency becomes inevitable, or at least highly probable, that the dynamics reverse because of the possibility that an interim payment will effectively become final. No doubt it was considerations such as this which caused Payne JA, in Shade Systems Pty Ltd v Probuild Constructions (Aust) Pty Ltd [2018] NSWCA 33, to refuse a stay in a case where the contractor’s financial position was “precarious”.
[355] Nothing like that is present here. I have been troubled by the fact that Martinus has failed to produce any updated accounts, and it is unclear what effect the partial failure of its claims in the adjudication proceedings, coupled with a reversal of any judgment which is enforced, would have on Martinus’ balance sheet. But the arbitration proceedings have not even begun, and it is not suggested that they will fall to be determined this year, or perhaps even next year.
As the High Court explained in Shade Systems, the policy of SOP Act is to ensure that any person who undertakes to carry out construction work (or who undertakes to supply related goods and services) under a construction contract is entitled to receive, and is able to recover, progress payments for carrying out that work and supplying those goods and services. The SOP Act is intended to provide a speedy and effective means of ensuring cash flow to builders and trade subcontractors from the parties with whom they contract. The SOP Act creates an entitlement that is to be determined informally, summarily and quickly, and then summarily enforced without prejudice to the common law rights of both parties which can be determined in due course.
The risk that a contractor might not be able to refund moneys ultimately found to be due to a developer after a successful civil action by the developer under the contract is a risk which, as a matter of policy in the SOP Act’s commercial context, has, prima facie, been assigned to the developer: see R J Neller approved in Shade Systems and followed on numerous occasions in this Court.
As the High Court further explained in Shade Systems at [51] (per Kiefel CJ, Bell, Keane, Nettle and Gordon JJ) about circumstances where contractual proceedings contemplated by s 32 of the SOP Act conclude that a payment made pursuant to the SOP Act should, on the correct construction of the contract, not have been made if necessary, a restitutionary order can be sought. The risk that the party placed at an advantage by an underpayment or overpayment may later become incapable of meeting such an order is a risk that is assigned to the other party.
The conclusion that the policy of the Act is to place the risk of insolvency on the developer/principal contractor is further underlined by s 32B which was introduced in 2018:
32B Application of Part to a claimant in liquidation
(1) A corporation in liquidation cannot serve a payment claim on a person under this Part or take action under this Part to enforce a payment claim (including by making an application for adjudication of the claim) or an adjudication determination.
(2) If a corporation in liquidation has made an adjudication application that is not finally determined immediately before the day on which it commenced to be in liquidation, the application is taken to have been withdrawn on that day.
[96] The stated prime objective of keeping cash flowing in the contracting chain by enforcing timely payments cannot be construed as supporting any construction of the SOP Act that limits or qualifies its operation more generally to companies under external administration or that are the subject of a DOCA. Further, any weight that might be given to that prime objective in exercising a discretion to extend convening periods for the second creditors’ meetings must necessarily have regard to the text and operation of the SOP Act. The text of s 32B makes clear that the legislature has chosen the liquidation of a corporation as the relevant event for excluding a person from taking any action under the SOP Act to enforce a payment claim, not the appointment of external administrators or entry into a DOCA.
These matters lend weight to the conclusion that there is a heavy burden on a party who seeks injunctive relief or a stay pending the outcome of proceedings contemplated by s 32 on the basis that a payment may become unrecoverable due to the possible or even likely insolvency of the payee at a later date. Considerable caution should attend the grant of such an injunction or a stay, as to do so may detract from the primary purpose of the SOP Act.
In the present case, Qube sought closely to analyse financial statements and management accounts produced by Martinus. Qube complained that the primary judge had wrongly failed to draw inferences adverse to Martinus by reason of what was an asserted lack of explanation of how the amount claimed by Martinus “was recorded in the accounts”. Secondly, Qube complained that the primary judge “wrongly thought that Martinus was profitable. Thirdly, Qube complained that Martinus’s financial position meant that this “put Qube at considerable risk of non-recovery, so as to render any interim payment one which was, in practical terms, final”. Fourthly, Qube complained that the primary judge wrongly discounted the evidence of Qube’s expert, Mr Cairns, as addressed to the wrong question. Qube submitted that the primary judge should have considered what Mr Cairns “sought to extract from the underlying financial information”. Fifthly, Qube submitted that the sum of money it was required to pay, compared to other cases in which a stay had been refused, meant that “the quantum of the amount which is required to be paid if a stay is not granted is a material integer when the discretion of the Court falls to be exercised”. Finally, Qube submitted that the significance of the purposes of the SOP Act “do not loom large in the same way as in many of the cases”, because Qube had already terminated the Contracts.
I would refuse leave to appeal. My reasons for rejecting the detail of Qube’s submissions may be summarised as follows:
Qube contends that that “Martinus had already accounted for, at least, a significant part of the amounts the subject of the adjudication applications”. That proposition was not established by the evidence. Qube analysed the FY 23 audited accounts of Martinus and asserted they showed that “there were real doubts about Martinus’s profitability”. “Real doubts” about Martinus’s profitability do not establish a proper basis for the stay sought by Qube. The onus was on Qube to establish that a stay should be granted, and the onus was a heavy one. It was not for Martinus to establish that it was profitable. Thus, even if it were correct as Qube submits that it was “clear that the notion that Martinus was profitable is wrong, or at least not established”, it would not follow that the primary judge erred in refusing to grant a stay.
Qube’s second point largely overlaps with its first. The gist of the submission is that, although the primary judge concluded at [355] that Martinus was “trading profitably at present”, if one assumed that Qube did not owe any money at all to Martinus under the relevant contracts, then Martinus would not be profitable. The primary judge’s observation at [356] was a statement of fact. Martinus is trading profitably. Qube does not establish that a finding of fact is wrong by asserting that if the facts were different the finding of fact would have been different.
Qube’s third point was that Martinus’s evidence demonstrated that it “had experienced difficulty in making payments of less than $1 million”. That submission should be rejected. What the relevant witness for Martinus, Mr Brunsdon, said was that Martinus had elected to spread redundancies over a period as, if they were all paid at once, “that would have a significant detrimental effect on Martinus’s cashflow”. That is a statement of the obvious. Attempts to manage cash flow do not establish an inability at some point in the future to provide restitution, should restitution be ordered.
Qube’s fourth point was that their expert, Mr Cairns, had allegedly identified a “trend” whereby Martinus “increased its indebtedness over time and was borrowing in order to fund its operations”. There was no error in the primary judge assessing Qube’s expert evidence by reference to “the question which confronted the Court when considering whether to grant a stay”. His Honour correctly concluded that Mr Cairns’ evidence did not establish a sufficient risk of inability to provide restitution in the future. The height of Mr Cairns’ evidence was that he was unable to say whether Martinus was presently at “risk of insolvency”.
Qube’s fifth point was that the primary judge failed to take into account that, as a result of his Honour’s rulings, Martinus would be entitled to an interim payment of around $30 million. The risk of prejudice to Qube was said to be “affected by the quantum of money the subject of the adjudication determination”. That submission is without merit. The primary judge’s reasoning was expressly directed to whether payment by Qube to Martinus now would convert the interim payment to Martinus into a final one. Qube did not establish a sufficient risk that any payments it is required to make to Martinus under the SOP Act would be rendered final regardless of any future order for restitution in Qube’s favour.
Qube’s sixth point was that the fact that the contracts had been terminated prior to the Payment Claims meant that the statutory policy of the SOP Act was less important. I do not agree. The purpose of the SOP Act is to ensure cashflow to contractors, whether or not they remain parties to an existing construction contract. Seymour Whyte Constructions Pty Ltd v Ostwald Bros Pty Ltd (in liq) (2019) 99 NSWLR 317; [2019] NSWCA 11 stands for the proposition that there is an entitlement to a progress payment under the SOP Act even if there is no expectation of future performance under the relevant construction contract. If Qube’s position was correct, it would subvert the policy of the SOP Act. A company in Qube’s position could immunise itself from a Payment Claim by terminating the contract. The SOP Act gives an express right to serve a Payment Claim after termination: see s 13(1C). In this case, there is no less need for cashflow because time has passed since the work was done, and the SOP Act expressly permits claims to be served within 12 months of work being completed: s 13(4) of the SOP Act.
The primary judge did not ask the wrong question, nor did his Honour apply the wrong test. His Honour correctly identified the relevant legal principles and appreciated that a balancing exercise was called for. In that balancing exercise, it was permissible to consider whether final rights would be frustrated, as his Honour did. The primary judge did not find that a stay was available only when insolvency has been demonstrated. It is clear that a mere risk of insolvency is ordinarily insufficient to justify a stay. No House v The King error was shown.
Finally, even if House v the King error had been established, and I were called upon to re-exercise the discretion, I would refuse a stay.
The stay sought is contrary to the policy of the SOP Act. There is no basis for concluding that there is a sufficient risk that Qube will be unable to recover from Martinus any amounts ordered to be paid as restitution following a final award. The fact that the sums are relatively large does not change this conclusion. The highest Qube puts it is that there is “significant doubt” about Martinus’s ability to repay. “Significant doubt” does not justify a stay of the kind sought.
The relevant jurisdiction engaged is the interlocutory power of the Court to prevent frustration of a future award (or judgment). The statutory policy of the SOP Act is that a contractor has a right to immediate cash flow, to be used in the ordinary course of business, despite the risk that a future award (or judgment) may not be satisfied. In this respect, it is important to note, as this Court has said, that s 32 is concerned with the legal rights of the parties, and “does not speak to the practical effect upon them”: TFM Epping Land Pty Ltd v Decon Australia Pty Ltd [2020] NSWCA 118 at [84] (Bell P, Macfarlan and Leeming JJA). Section 32B now also makes it clear that, while a company in liquidation lacks rights under Pt 3 of SOP Act, there is no intention that companies otherwise proven to be in financial distress lack such rights. Once the nature of the jurisdiction invoked is properly identified, and the policy of the SOP Act clearly understood, it is clear that a “significant doubt” about the ability to meet an award in the future is insufficient to award a stay.
Leave to appeal should be refused.
For the foregoing reasons I propose the following orders:
Appeal allowed.
Cross-appeal dismissed.
Summons seeking leave to appeal dismissed.
Set aside:
(a) orders 1, 2, and 3 of the orders made on 26 September 2024 and orders 1, 2, 3, 4 and 7 of the orders made on 15 November 2024 in proceedings 2024/286961; and (b) order 3 of the orders made on 26 September 2024 and order 2 of the orders made on 15 November 2024 in proceedings 2024/278963; and (c) order 2 of the orders made on 15 November 2024 in proceedings 2024/278984.
Vary order 6 of the orders made on 26 September 2024 (as varied by order 5 made on 15 November 2024) in proceedings 2024/286961 by deleting the words on and from the words “on terms” in that order.
Vacate order 7 of the orders made on 26 September 2024 (as varied by order 6 made on 15 November 2024) in proceedings 2024/286961 (interlocutory regime pending appeal).
Order that Qube’s summons filed 5 August 2024 in proceedings 2024/286961 is dismissed with costs.
Order Qube to pay Martinus’s costs of the appeal, the cross-appeal and the application for leave to appeal.
GRIFFITHS AJA: I agree with Payne JA.
**********
Martinus Rail Pty Ltd
Qube RE Services
(1990) 170 CLR 1
(2004) 61 NSWLR 42
(2023) 112 NSWLR 225
(2010) 78 NSWLR 393
(2023) 113 NSWLR 282
(2007) 69 NSWLR 72
(2009) 74 NSWLR 190
(2018) 264 CLR 123
(1936) 55 CLR 499
(2024) 98 ALJR 196
(1997) 190 CLR 1
(2024) 98 ALJR 610
(2020) 271 CLR 550
(2018) 264 CLR 541
(2013) 249 CLR 332
(2009) 83 ALJR 1123
(1999) 197 CLR 611
(2018) 264 CLR 1
(2019) 99 NSWLR 317
(2004) 61 NSWLR 521
(2002) 209 CLR 597
(2003) 145 FCR 1
(1909) 10 CLR 114
(2021) 272 CLR 33
(2021) 273 CLR 21
(2010) 239 CLR 531
(2019) 264 CLR 421
(2001) 206 CLR 323
(2015) 257 CLR 22
(1995) 184 CLR 163
(1998) 194 CLR 355
(2023) 276 CLR 136
(2021) 273 CLR 506
(2022) 276 CLR 80
(1944) 69 CLR 407
(2000) 199 CLR 135
(1945) 69 CLR 613
(1965) 113 CLR 177
(1976) 136 CLR 1
(2001) 205 CLR 507