GB Building Solutions Ltd v SFS Fire Services Ltd (t/a Central Fire Protection)

In construing a construction subcontract, the court must ascertain the objective meaning of the language used by reading the contract as a whole. It must balance textual indications, the factual and commercial context, and the consequences of competing constructions through a unitary and iterative process.

A capitalised contractual definition does not necessarily govern every use of a similar unc capitalised expression. The court must determine the scope of the definition in its contractual context. Where a subcontractor gives a clear notice under a deeming provision identifying the date of practical completion, and the contractor does not dissent in writing within the stipulated period, practical completion is deemed to have occurred on that date. The actual state of completion is then irrelevant, subject to genuine ambiguity in the notice.

The claimant, the design and build main contractor, sought to recover losses arising from a flood in the basement of an office building. The defendant was the design and build subcontractor responsible for the sprinkler system.

The preliminary issue was whether the flood occurred before or after the subcontract’s terminal date. That depended first on whether practical completion was defined by reference to the main contract certificate or was to be determined under clause 2.20. Secondly, if clause 2.20 applied, the court had to decide whether the defendant had served a valid notice of practical completion and whether the subcontract works were in fact complete.

1. Construction of the subcontract. The court applied the unitary and iterative approach to contractual interpretation. The modified definition of “Practical Completion” did not govern clause 6.1. Clause 6.1 required the terminal date to be determined under clause 2.20, which applied to practical completion of the subcontract works.

2. The capitalisation of “Practical Completion” mattered under clause 1.1. The definition was intended to apply for some purposes, including the release of retention, but not necessarily throughout the subcontract. There was no relevant inconsistency requiring the order-of-precedence clause to make the capitalised definition prevail.

3. Deeming notice. Clause 2.20.1 created contractual certainty. If the subcontractor notified the contractor of the date when, in its opinion, the subcontract works were practically complete, and the contractor did not dissent in writing with reasons within 14 days, practical completion was deemed to have occurred on the notified date. The actual state of completion, and compliance with the associated documentation obligations, was irrelevant once an effective notice had gone unchallenged.

4. The notice did not need to identify clause 2.20.1 formally. It had to convey clearly that the subcontractor considered the works practically complete and had to identify a specific date. The completion certificate issued on 26 October 2009, and alternatively the email and certificates sent on 1 December 2009, satisfied that requirement. The claimant did not dissent in time.

5. Alternative factual conclusion. Even if actual completion had been relevant, the works were practically complete by 9 December 2009. The remaining matters were outside the subcontract scope, minor, or did not prevent the sprinkler system from operating. Later proposed or instructed works did not retrospectively alter practical completion.

6. The flood occurred after the terminal date. The preliminary issue was therefore answered in favour of the claimant’s entitlement in principle to advance its claim under clause 6.6.1.