UK: Duty To Comply With Claims Cooperation Clause Where Insurer Has Denied Liability/Proving Quantum

Last Updated: 6 January 2015
Article by Jon Turnbull and Michelle M. Radom

After Eder J held, as a preliminary issue, that the insurance policy in question did cover theft by employees, despite the insured's non-selection of a "Theft by Employees Section" (and so the insurer couldn't reject the claim on that basis), the insured proceeded to bring a claim for business interruption losses. This was an unusual BI claim, because such claims are normally based on a single adverse event, such as a fire or flood or major burglary which is immediately known to the insured and which causes major losses of profit clearly reflected in the insured's accounts. By contrast, here the alleged thefts took place more than 500 times over more than five years (and spanning some five policy years) before discovery in December 2008, and the allegations of loss were founded not on accounts but instead on calculations based on various assumptions. Although the case is fact-specific, some general points of interest arose:

1) Complying with a Claims Cooperation Clause ("CCC"): the policy contained a claims condition that (inter alia), "in the event of a claim being made", the insured would provide particulars of its claim within 30 days after expiry of the Indemnity period, and deliver accounts and other "documents proofs information explanation and other evidence as may be reasonably required" by the insurer to investigate the claim. It was also provided that "if the terms of this condition have not been complied with, no claims under this Section shall be payable", and the term was accepted to be a condition precedent.

The insured argued that no claim could be made here until after discovery of the theft in December 2008, and hence there was no obligation to deliver particulars of the claim before that time. That argument was rejected by the judge. It did not matter that the insured did not discover the thefts until 30 days after the indemnity periods had expired under earlier policies. Particulars had not been sent until 17 February 2009 and so the insured had breached this requirement in respect of all thefts prior to 18 January 2008. However, although the judge accepted that insurers could have "pulled the shutters down" in relation to those thefts, he found that they had not done so on the facts.

Eder J also approved textbook commentary to the effect that "full particulars" means "the best particulars the assured can reasonably give", and (unless the policy states otherwise) further particulars can be supplied later on.

The judge did not decide the "very difficult issue of law which has never properly been considered by an English Court" as to whether an insured must comply with claims conditions if an insurer wrongly rejects a claim (and if that constitutes a repudiation of the insurance policy). Instead, he focused attention on the meaning of what was "reasonably" required.

The judge was prepared to find that the list of various documents required by the insurers had been "reasonably" required "in an abstract sense". However, he went on to hold that "it does not seem to me that this is necessarily so in circumstances where insurers in effect (wrongly) deny liability in principle or even (wrongly) refuse to admit that "employee theft" was an insured peril, as they did in the present case. I should emphasise that I fully accept that, generally speaking, it may be perfectly "reasonable" for insurers to reserve their position pending receipt of further documents/ information and that a requirement by insurers that the insured should deliver such documents/information may be entirely "reasonable" because a review of such documents/information by insurers is necessary in order to decide, for example, whether cover exists or not. In my view, that is a statement of the obvious but it is not this case. I should also make plain that I fully accept as a matter of the general law of contract that a repudiation is a thing "writ in water" and that, unless it is accepted by the innocent party, the latter will generally continue to be bound by the contract and, in particular, continue to be bound to perform that party's continuing obligations under the contract. That is, indeed, trite law. However, here the focus is one of construction of the contract and, in particular, what information may be "reasonably required" by insurers in the particular circumstances of the present case; and unless and until the defendants were prepared to confirm at the very least that "employee theft" was an insured peril, the requirement to deliver the other

categories of documents ... was, in my judgment, not "reasonable" having regard, in particular, to the time and expense that would have to be incurred by [the insured] in complying with such requirement".

The judge did, however, find that the insured had breached the claims cooperation clause by failing to provide profit and loss and management accounts from 2005 to 2008, it being common ground that a request for such accounts is routine for commercial claims and hence were "reasonably required". Although certain issues had been "parked" pending agreement on the question of liability, no additional costs would have had to be incurred in order for the insured to send the accounts.

Furthermore, there had not been unequivocal representation from the insurers that the insured was not required to deliver the accounts (and hence no waiver by estoppel). It did not matter that the insured thought or assumed that they did not have to deliver the accounts – that did not result from any agreement by the insurers. Accordingly, the claim failed because a breach of the CCC.

Eder J also said that it was "difficult" to say the insurer had breached its duty of good faith because it ought to have warned the insured that it was committing a breach of a condition precedent. The judge agreed that that the insurer was under no duty positively to warn the insured that it needed to comply with policy terms, and there was also no evidence to support the suggestion that it should be inferred that the insurer's silence was deliberate.

2) Proving quantum: an insured must establish on a balance of probabilities that a relevant event has been caused by an insured peril. Here, the insured faced difficulty in meeting that burden and proving that thefts had even taken place, and the judge accepted that "there may be different ways of satisfying the legal burden and standard of proof other than by direct evidence". However, here, although certain thefts (below the policy excess) had been proven, there was no evidence that an assumption made by the insured about the employee's thieving activities during the relevant period was correct. Indeed, the employee would most likely have tried to keep the number of incidents of theft to a minimum in order to avoid the risk of detection.

COMMENT: As mentioned above, this case does not resolve the issue of whether an insured must comply with a policy condition even if the insurer has (wrongfully) rejected a claim. In Diab v Regent Insurance Co Ltd [2006] UKPC 29 the Privy Council held that a claims provision remained binding even where insurers had told the insured they would not pay the claim (and the case was followed in Lexington Insurance Co v Multinacional de Seguros SA [2008] EWHC 1170 (Comm)), but there is textbook commentary doubting that approach in non-liability or reinsurance cases (see Colinvaux's Law of Insurance, 9th edn, para 9-018) and Eder J was not strictly bound to follow either Diab or Lexington. Instead, this case focuses on what an insurer can "reasonably" require from the insured following the rejection of a claim, if the policy contains that wording (and even if the clause does not contain that wording, Napier v UNUM Ltd (formerly NEL Permanent Health Insurance Ltd) [1996] 2 Lloyd's Rep 550 is authority for the view that the courts will imply a reasonableness test into any requirement for the insured to provide information to the insurer about its claim).

However, it might be said that by focusing the inquiry on the policy wording, the judge did implicitly accept that the insured was still bound to comply with a claims provision even though insurers had rejected the claim (even if he did not expressly say that was his conclusion). It is also noteworthy that the judge linked the issue of "reasonableness" in the policy condition to the insurer's conduct regarding the claim in general: in short, where a claim has not been accepted, an insurer cannot reasonably request information which it will be costly or timely to produce (and query how much time and expense will result in a request not being reasonable).

Ted Baker Plc v Axa Insurance UK Plc [2014] EWHC 3548 (Comm)

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

Jon Turnbull
Michelle M. Radom
In association with
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.