Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Works despite quirks: liability cap upheld by TCC notwithstanding difficult language

In Drax Energy Solutions Limited v Wipro Limited [2023], the TCC upheld a contractual clause said to impose a single liability cap for all claims arising out of a master services agreement.

The Background to the Case

Drax entered into a master services agreement with Wipro for the provision of software services.

Wipro was engaged to carry out the Services for a 5-year period through a number of statements of work which would be entered in to on specific ‘go-live’ dates for pre-agreed charges.

Following a number of missed milestones, and delayed deliveries, responsibility for which is disputed, Drax terminated the agreement alleging repudiatory breach of contract.

Drax subsequently issued proceedings against Wipro claiming damages for misrepresentation, quality defects, delay and losses flowing from the termination. Wipro counterclaimed for wrongful termination, prolongation costs and unpaid invoices.

Drax argued clause 33.2 of the agreement imposed a separate liability cap on each of its claims/causes of action. In contrast, Wipro contended that clause 33.2 imposed a single cap for all claims.

What did the Court Decide?

Applying the principles summarised in the well-known case of Triple Point Technology v PTT [2021], the TCC found that despite some “linguistic quirks” clause 33.2 imposed a single aggregate cap on Wipro’s liability for Drax’s claim.

Conclusion

This case provides a useful reminder that limitation clauses should be drafted carefully and without ambiguity.

Where a party intends a cap on liability to apply to multiple causes of action, this needs to be expressly stated. The courts will not be sympathetic to parties who fail to draft their contracts with sufficient specificity, especially in cases like this where the parties are large corporations and had sought professional advice when drafting the contract.

To read our full bulletin, please follow this link.

For more information contact:

David Spires 

Partner

E-mail: DSpires@hklegal.co.uk