07.08.2013 Views

Misrepresentation, Non-Disclosure and Breach ... - Law Commission

Misrepresentation, Non-Disclosure and Breach ... - Law Commission

Misrepresentation, Non-Disclosure and Breach ... - Law Commission

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

10.40 The issue here is slightly different from the case in which the consumer honestly<br />

believed what they said to be true. In the Newsholme situation, the consumer<br />

usually accepts that what was written on the form is incorrect; the point is that<br />

they did not realise that it was on the form at all. However, we think the same<br />

approach should apply. If the consumer acted only negligently, or even without<br />

negligence, the insurer’s remedies should be limited appropriately. Thus the<br />

proposer’s signature should no longer be treated as conclusive evidence that the<br />

consumer knew or adopted the statements on the form filled out by the<br />

intermediary.<br />

10.41 However, the policyholder’s signature should provide strong evidence that they<br />

made or adopted the representations on the form. Further, in considering whether<br />

the consumer has been negligent, we would expect the court or ombudsman to<br />

take heed of any warnings on the form. Suppose, for example, the consumer had<br />

signed a declaration stating that they understood the need to check the form<br />

carefully <strong>and</strong> that they had done so, but it later emerged that they had signed the<br />

form without reading it. This would suggest negligence. In O’Connor v Kirby the<br />

Court of Appeal held that the insured was negligent in failing to check the form. 10<br />

The insured applied for car insurance through an independent intermediary, who<br />

made a mistake filling in the form. The intermediary then h<strong>and</strong>ed him the form<br />

<strong>and</strong> asked him to check through it. The insured did this rapidly <strong>and</strong> failed to<br />

notice the mistake. The court found that the insured had been negligent in failing<br />

to check the form <strong>and</strong> had caused the loss.<br />

10.42 However, there may be contrary evidence. Suppose that the insurer’s<br />

representative had told the consumer that the form contained precisely the<br />

(correct) information the proposer had given <strong>and</strong> that the proposer did not need<br />

to read it. The intermediary may even have presented the form to the proposer in<br />

such a way that they did not see the written warning. In such a case we do not<br />

think the signature should be taken to be conclusive evidence of negligence. We<br />

all regularly sign documents that we have not read carefully; but most of us think<br />

that in our private lives this is excusable when the other party knows “what we<br />

meant” or “what the true position is”. When coupled with a general impression<br />

that the intermediary represents the insurer, the failure to check may be<br />

excusable.<br />

10.43 The policyholder may also claim that the answers were incorrect because the<br />

intermediary had given them misleading advice as to how to answer. In this case<br />

the proposer knows what is written on the form, <strong>and</strong> claims he was misled into<br />

making that statement. The signed declaration does not address the issue at<br />

stake. Nor would a signature help the court or ombudsman decide a case where<br />

the policyholder argued that they genuinely thought their answer was correct.<br />

10.44 We provisionally propose that a consumer insured’s signature on a<br />

proposal form that has been completed incorrectly by a third person should<br />

not be regarded as conclusive evidence that the insured knew of or<br />

adopted what was written on the form.<br />

10<br />

[1972] 1 QB 90.<br />

258

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!