Hexagon Housing Association Limited v Providence Building Services Limited [2026] UKSC 1.¹

Intro

This case note explores the recent Supreme Court decision in Hexagon Housing Association Limited v Providence Building Services Limited [2026] UKSC 1. The facts are relatively simple, and the law deceitfully uncontroversial. Yet a single clause buried within standardised construction contracts warranted judicial attention from the highest court.

It will be argued that the Supreme Court adopted a textually faithful approach to construction of the termination clause within the JCT contract. Although the majority judgment reasoning, given by Lord Burrows, relies in part on construing the clause through ‘business common sense’, the result can be explained wholly by reading the text of the clause.

This note is as much a review of how to understand words, syntax, structure, and meaning as it is a case note. I do not propose to set out a thesis on how construction of a commercial clause ought to be, although in this regard see the excellent book by Ryan Catterwell.² I merely hope to engage the reader’s linguistic nous. Treat this note like an adapted version of The Times Crossword: read the relevant termination clause yourself and form your view as to how it should be construed; then cross-reference your reasoning with that of the Court of Appeal and the Supreme Court.

Facts

The essential background behind the dispute relates to Hexagon Housing Association Limited (‘Hexagon’) repeatedly failing to pay Providence Building Services Limited (‘Providence’) on time.

Hexagon, as ‘Employer’, contracted with Providence as ‘Contractor’ for the building of residential homes in Purley, South London.

First Default

Hexagon failed to pay £264,242 by the deadline of 15 December.

Providence then on 16 December issued a ‘Notice of Specified Default’ warning Hexagon of its non-payment under Clause 8.9.1.

Hexagon remedied this default by paying the full amount on 29 December.

Second Default

Five months later, in May 2023, Hexagon failed to pay £365,812 by the deadline of 17 May.

Providence, rather than warning Hexagon under Clause 8.9.1 like they did for the non-payment in December, exercised the nuclear option of a “Notice of Termination” under Clause 8.9.4, the next day on 18 May.

Hexagon argued that this ‘Notice of Termination’ by Providence was itself unlawful and constituted a repudiatory breach.³

The dispute can thus be aptly summarised: did the contract allow Providence to immediately terminate the contract upon Hexagon’s repeated default, if the initial default had been cured before a right to terminate had accrued?

The Termination Clause

It is best that I publish the relevant clause in full:⁴

Default by Employer

8.9.1 If the Employer:

.1 does not pay by the final date for payment the amount due to the Contractor in accordance with clause 4.9 and/or any VAT properly chargeable on that amount...

...

the Contractor may give to the Employer a notice specifying the default or defaults (a "specified" default or defaults).

.2 ...

.3 If a specified default or a specified suspension event continues for 28 days from the receipt of notice under clause 8.9.1 or 8.9.2, the Contractor may on, or within 21 days from, the expiry of that 28 day period by a further notice to the Employer terminate the Contractor's employment under this Contract.

.4 If the Contractor for any reason does not give the further notice referred to in clause 8.9.3, but (whether previously repeated or not):

.1 the Employer repeats a specified default; ...

then, upon or within 28 days after such repetition, the Contractor may by notice to the Employer terminate the Contractor's employment under this Contract.

An Exercise in Construction

Remember to refer to the facts above before trying to interpret the clause yourself.

The Contractor is Providence; the Employer is Hexagon.

The question before the court was whether Providence needed to have accrued a right to termination under Clause 8.9.3 before being able to terminate the contract for Hexagon’s repeat default under Clause 8.9.4.

Reading the relevant clauses — Clause 8.9.1.1, Clause 8.9.3, and Clause 8.9.4.1 — together, what do you think?

Here is my take before I embark upon analysing both rival constructions:

1. Hexagon’s non-payment on both 15 December and 17 May 2023 clearly engages Clause 8.9.1.1. Namely, Hexagon “does not pay by the final date for payment the amount due to” Providence.
2. Providence then has a choice as to whether it serves a notice about non-payment, evidenced by the language “may give... notice specifying default” as per the bottom of Clause 8.9.1.
3. To be able to terminate under Clause 8.9.3, this specified default notice must have been issued. Providence then must wait for a 28-day curing period before it can further act, as per the language of Clause 8.9.3, which makes that further termination notice conditionally dependent on whether “a specified default continues for 28 days from the receipt of notice under Clause 8.9.1.” Only if this condition precedent is satisfied can Providence “by a further notice to the Employer (Hexagon) terminate the Contractor’s employment (Providence’s own contract)”, as per Clause 8.9.3. Critically, the right to terminate only accrues if the default has not been cured, not whether notice has been served or not.
4. Clause 8.9.4 is therefore only engaged where, despite Providence having accrued a right to terminate under Clause 8.9.3, it has chosen not to terminate. This is evidenced by the language, “if [Providence] for any reason does not give the further notice referred to in clause 8.9.3”, then upon Hexagon repeating a specified default Providence “may by notice... terminate... this contract” under Clause 8.9.4. Crucially, this does not mean that where the right to terminate has not accrued under Clause 8.9.3, because for instance Hexagon had cured the first specified default, Providence can still immediately terminate for a repeat default under Clause 8.9.4. Indeed, the wording of Clause 8.9.4 in my view presupposes that the right to terminate has arisen under Clause 8.9.3, but that “for any reason” Providence “does not give further notice” at the time of the first default, this does not preclude Providence from immediately terminating upon a later repeat of such default.

Rival Constructions

Providence’s interpretation

Providence’s central submission is that the words in Clause 8.9.4, “if [Providence] for any reason”, cover the situation where Providence does not give the further notice referred to in Clause 8.9.3 to terminate for the first specified default because the circumstances associated with the specified default do not give rise to an accrued right to terminate.

In other words, where there has been a repetition of a specified default, there is no requirement that the right to terminate has previously accrued under Clause 8.9.3.⁵

On this view, Providence was entitled to terminate under Clause 8.9.4 because in May there had been a repetition by Hexagon of late payment in a situation where there had been an earlier late payment in December for which a specified default notice had been served. Providence was thus entitled to immediately terminate for the second late payment a day after the payment was due and was not required to wait for 28 days to see if Hexagon could cure the default.⁶ It did not matter that no right to terminate accrued for the first default.

Indeed, this broad interpretation was accepted by the Court of Appeal. Stuart-Smith LJ found that the words “for any reason” were “broad enough to catch a case where the reason why the further notice may not be given is that there is no accrued right to give it.”⁷

The Court of Appeal’s literal construction saw that “the conditional words of Clause 8.9.3 are satisfied even where the Contractor had no accrued right to give the further notice referred to in Clause 8.9.3”.

Hexagon’s interpretation

By contrast, Hexagon argued that before a termination notice can be validly served by Providence for a repeat specified default under Clause 8.9.4, Providence must previously have accrued a right to serve a termination notice under Clause 8.9.3.⁸

It follows that, where an earlier specified default was cured within 28 days, no termination notice can be immediately served despite the repetition of a specified default. On the facts, Providence was thus not entitled to terminate under Clause 8.9.4 in respect of the second late payment, as despite it being a repeat of a specified default from the first late payment, the fact Hexagon cured the first default within 28 days prevented Providence from having accrued a right to terminate under Clause 8.9.3.

The Supreme Court’s Decision

The Supreme Court ultimately favoured Hexagon’s interpretation.

Lord Burrows, giving the judgment, focused on how Clause 8.9.4 is “parasitic” on Clause 8.9.3, rather than being “independent of it”. Indeed, his Lordship found that the words “if the contractor for any reason does not give the further notice referred to in clause 8.9.3” at the start of Clause 8.9.4 show the dependency of the clause on the preceding Clause 8.9.3.

Lord Burrows endorsed counsel’s articulation that Clause 8.9.3 was a “gateway” into Clause 8.9.4. Namely, if the specified default is cured by Hexagon within 28 days, then Providence’s ability to serve a termination notice under Clause 8.9.3 never arises, and in turn Clause 8.9.4 never bites.

In my view this construction is cogent as a matter of linguistics and syntax.

Clause 8.9.4 uses the definite article of “the” when it says “the further notice”, rather than “a further notice”. “The” is a specific identifier, referring to a particular type of notice that only comes into existence once the 28-day cure period has expired without payment. If Hexagon pays within the 28 days, the right to that “further notice” is never born. Moreover, every word must have a purpose, and there is a presumption against linguistic redundancy.⁹ Why bother with a 28-day cure period in Clause 8.9.3 for a first default, if Clause 8.9.4 allows you to bypass the cure logic entirely the second time a payment was late. The phrase “referred to in clause 8.9.3” is a linguistic bridge; you must cross 8.9.3 to get into 8.9.4.

Syntactically, by beginning 8.9.4 with a reference to the action in 8.9.3, the former clause makes the latter a condition precedent. If the syntax were meant to be independent, it would have been drafted as “Notwithstanding Clause 8.9.3, if a specified default is repeated...”. Rather, Clause 8.9.4 is tethered to the specific failure to act upon a right created in the previous Clause 8.9.3.

Commercial Sensibility?

Finally, it is worth just noting the role of ‘commercial sensibility’ in interpreting commercial clauses.

It is trite law that you start first with the textual language, and then you move onto which rival construction coheres most with business common sense.¹⁰

For what it is worth, the Court of Appeal was right to eschew any focus on commercial sensibility as unlocking the interpretive gateway to this case.¹¹

Hexagon argued that commercially it made sense to require an accrued right to serve further notice, otherwise Providence could pull the plug on the whole construction project if Hexagon was even a day late on paying, provided such late payment was a repeat specified default. In other words, despite a late payment being cured for December, the very fact this late payment event reared its head again in May was enough for Providence to walk away immediately. This would be so even before Hexagon had a chance to cure it.

By contrast, Providence argued that commercially a serious defaulter should face consequences, otherwise Hexagon could wait until the 27th day for every payment round until paying. This means a bad faith Employer could deliberately disrupt the Contractor’s cash flow by paying late but just in time, every time, and the Contractor would have no recourse to pull the plug under the termination clause.

Lord Burrows tentatively reinforced his conclusion on construction of the clause, by noting how his interpretation would encompass a ‘less-extreme outcome’.¹² This, in my view, is a thinly disguised attempt to appeal to ‘commercial sensibility’ that both the High Court and Court of Appeal distanced themselves from. Indeed, Lord Burrows found that Providence’s construction lacked commercial sense:

It would mean that any breach by late payment (provided a specified notice of default were given by the Contractor), if repeated by any subsequent late payment, would entitle the Contractor to terminate the contract. For example, if the Employer made two late payments, each being made one day late, the Contractor, on this interpretation, would be entitled to serve a notice terminating the contract (provided a specified default notice had been served in respect of the first late payment). That might be thought to provide a sledgehammer to crack a nut.

As this note has argued, the result of this case can be done wholly by recourse to textual analysis. Commercial sensibility in my view is not compelling in such circumstances.

Concluding Remarks

I hope you have managed to stick with me through this note. And I hope you managed to find at least one of the views convincing.

The Supreme Court, in my view, arrived at the correct construction. This was largely informed by a close textual analysis, faithful to the words, structure, meaning and syntax of the clause. Commercial sensibility served only to reaffirm the conclusion on the textual analysis, but should never be a substitute nor override what the plain ordinary meaning of a clause is.

Whether the UK’s highest court will be confronted again in having to construe a single clause in a contract remains to be seen.

But for now, this case note is a reminder that words, structure, meaning, and syntax are the only interpretive tools one ought to need when construing a contract.

Finley Hewitt
BCL (Oxon); BA (Oxon).

Endnotes

1. Hexagon Housing Association, recent completed developments. Image of the relevant residential developments subject to the JCT contract. Back
2. Ryan Catterwell, A Unified Approach to Contract Interpretation (Hart Publishing 2020). Back
3. Providence Building Services Ltd v Hexagon Housing Association Ltd [2024] EWCA Civ 962 [10]-[13]. Back
4. The strike-outs reflect amendments made by the parties to the original standardised termination clause in most JCT contracts. Back
5. UK Supreme Court, ‘Press Summary: Providence Building Services Ltd v Hexagon Housing Association Ltd [2026] UKSC 1’ (15 January 2026). Back
6. Ibid. Back
7. Providence Building Services Ltd v Hexagon Housing Association Ltd [2024] EWCA Civ 962 [30]. Back
8. Hexagon Housing Association Limited v Providence Building Services Limited [2026] UKSC 1 [16]. Back
9. Dimes v Proprietors of the Grand Junction Canal (1852) 3 HL Cas 759. Back
10. Wood v Capita Insurance Services Ltd [2017] UKSC 24. Back
11. Stuart-Smith LJ in the Court of Appeal, at [35]. Back
12. Hexagon Housing Association Limited v Providence Building Services Limited [2026] UKSC 1, Lord Burrows [35]. Back