• GL
Choose your location?
  • Global Global
  • Australian flag Australia
  • French flag France
  • German flag Germany
  • Irish flag Ireland
  • Italian flag Italy
  • Polish flag Poland
  • Qatar flag Qatar
  • Spanish flag Spain
  • UAE flag UAE
  • UK flag UK
Navigating Interesting Times

Navigating Interesting Times

Risk Matters: The DWF insurance podcast | Ep04
In this episode of Risk Matters you will hear about two recent court judgments of note to the insurance community. 
Our hosts Jennifer Kleisner, Senior Associate and Simon Cooper, Consultant from the Global Risks team at DWF will be specifically discussing the decisions of two recent court judgements (1) Scotbeef v. D&S Storage and (2) Technip Saudi Arabia v. The Mediterranean & Gulf Insurance & Reinsurance Co.

*This podcast is a continuation of our recent article "Navigating: 'Interesting Times': Challenges and Opportunities for the Insurance Industry in 2024"

Listen to the podcast

 

Subscribe to Risk Matters via Apple Podcasts and Spotify

Audio Transcripts

Episode 4
1
00:00:00,020 --> 00:00:03,940
Welcome to Risk Matters, the insurance podcast brought to you by DWF and your

2
00:00:03,940 --> 00:00:07,660
global guide to the latest trends and issues in the insurance and reinsurance industry.

3
00:00:08,260 --> 00:00:12,200
Join us as we explore topical issues, emerging technologies and the innovative

4
00:00:12,200 --> 00:00:14,760
strategies that are shaping the global future of insurance.

5
00:00:16,760 --> 00:00:21,880
Welcome to the next episode of our DWF Risk Matters podcast series titled We

6
00:00:21,880 --> 00:00:25,820
Live in Interesting Times, where myself, Jennifer Kleiser, will be talking with

7
00:00:25,820 --> 00:00:29,180
Simon Herman Cooper, about two recent court judgments of note to the insurance community.

8
00:00:30,000 --> 00:00:34,120
And this is a community that's seen shifting sands of late, facing fresh challenges

9
00:00:34,120 --> 00:00:37,760
and evaluating risk in view of global warming, increased global conflict and

10
00:00:37,760 --> 00:00:39,440
political instability, with

11
00:00:39,440 --> 00:00:42,640
around half of the world's population voting in elections during 2024.

12
00:00:43,100 --> 00:00:46,980
And it's important to remember the contract wording will always be the starting

13
00:00:46,980 --> 00:00:50,060
point for what terms have been agreed between insurers and insured,

14
00:00:50,120 --> 00:00:52,100
and what risk insurers have agreed to accept.

15
00:00:52,100 --> 00:00:57,360
Yes, although insurers are operating in a dynamic environment as far as risk

16
00:00:57,360 --> 00:01:00,760
is concerned, the terms of the policy remain key.

17
00:01:01,020 --> 00:01:06,260
And it's these contractual terms which are often central when a dispute gains traction.

18
00:01:06,800 --> 00:01:10,760
And two recent court decisions have been apt reminders of this.

19
00:01:11,680 --> 00:01:14,940
So I understand Simon will be looking today at the two decisions,

20
00:01:15,180 --> 00:01:19,940
Scott Beef against DNS Storage and Technip Saudi Arabia against the Mediterranean

21
00:01:19,940 --> 00:01:22,140
and Gulf Insurance and Reinsurance Company.

22
00:01:22,540 --> 00:01:27,920
Yes, that's right. The Scott Beef case is not only a reminder of the rules of construction,

23
00:01:28,800 --> 00:01:32,720
but it's also a great example of the way in which the Insurance Act of 2015,

24
00:01:33,340 --> 00:01:37,040
has changed the approach to warranties in an insurance contract,

25
00:01:37,040 --> 00:01:41,680
as well as the sort of evidence that insurers need their underwriters to demonstrate,

26
00:01:42,220 --> 00:01:46,100
if they want to argue that they would have written the risk on a different basis

27
00:01:46,100 --> 00:01:48,840
if a fair presentation had been made.

28
00:01:50,550 --> 00:01:54,470
Judgements applying the Act have been few and far between since 2016,

29
00:01:54,910 --> 00:02:00,050
and it's important to learn the lessons we can from cases like Scott Beef.

30
00:02:01,590 --> 00:02:07,270
Our second case today, the Technic case, focuses on the importance of policy definitions.

31
00:02:08,050 --> 00:02:10,770
Lawyers do love a definition. Yeah, we do.

32
00:02:10,950 --> 00:02:15,410
And it's interesting about this case that it highlights that just because a

33
00:02:15,410 --> 00:02:20,290
wording is a market standard wording, it doesn't mean it's perfect and arguments

34
00:02:20,290 --> 00:02:23,550
about its correct interpretation can still gain traction.

35
00:02:24,910 --> 00:02:29,510
And the case also contained some interesting commentary on insurance exclusions

36
00:02:29,510 --> 00:02:34,410
and on clauses requiring consent to settlement in the reinsurance context.

37
00:02:35,310 --> 00:02:40,270
So taking the Scott Beef case first, this judgment might come as something of

38
00:02:40,270 --> 00:02:41,710
an unpleasant surprise to insurers.

39
00:02:41,710 --> 00:02:44,510
Yeah, I think so, because the court found

40
00:02:44,510 --> 00:02:48,790
that the effect of the Insurance Act was such that a condition precedent to

41
00:02:48,790 --> 00:02:53,930
liability written into the policy concerning the insured's trading conditions

42
00:02:53,930 --> 00:02:59,650
was unenforceable as a contractual condition precedent and should instead be

43
00:02:59,650 --> 00:03:01,770
treated as a pre-contractual representation,

44
00:03:02,030 --> 00:03:08,770
which could only operate, if at all, as a warranty subject to the new rules set out in the Act.

45
00:03:10,820 --> 00:03:14,960
The background to the case was that DNS Storage, who is the plaintiff,

46
00:03:16,000 --> 00:03:18,560
that's wrong actually, can I go back?

47
00:03:19,560 --> 00:03:24,020
The background to the case was that DNS Storage provided warehousing facilities

48
00:03:24,020 --> 00:03:26,780
for meat processing companies in Scotland.

49
00:03:27,240 --> 00:03:32,200
It contracted with its clients on the basis of industry standard terms,

50
00:03:32,420 --> 00:03:38,320
known as the UKWA terms, and subsequently the FSDF terms.

51
00:03:38,760 --> 00:03:43,140
That's a lot of acronyms. Yeah, we love our acronyms as well as our definitions, don't we?

52
00:03:43,700 --> 00:03:50,000
So, DNS purchased Warehouse Keepers Liability Insurance from Lonham, the insurance company.

53
00:03:50,960 --> 00:03:56,860
And the policy noted that the insured's trading conditions were FSDF terms and conditions.

54
00:03:57,460 --> 00:04:03,300
And the policy also contained a duty of assured clause, which is at the heart of this dispute.

55
00:04:04,220 --> 00:04:08,860
Okay, so this is where the all-important so-called condition precedent comes into play.

56
00:04:08,860 --> 00:04:12,900
So the duty of assured clause provided, I understand, that it was a condition

57
00:04:12,900 --> 00:04:17,340
precedent to the liability of insurers, that the insured would firstly make

58
00:04:17,340 --> 00:04:20,820
a full declaration of all current trading conditions at inception,

59
00:04:21,060 --> 00:04:25,740
during the currency of the policy, continuously trade under the conditions they

60
00:04:25,740 --> 00:04:28,500
had declared and had been approved by insurers in writing,

61
00:04:28,700 --> 00:04:32,960
and take all reasonable and practical steps to ensure that their trading conditions

62
00:04:32,960 --> 00:04:36,500
were incorporated in all contracts that the insured entered into,

63
00:04:36,600 --> 00:04:38,560
presumably for the duration of the policy.

64
00:04:38,860 --> 00:04:41,780
I mean, that seems fairly clear drafting to me.

65
00:04:42,140 --> 00:04:46,000
Yes, and the clause seemed to provide a bit of a get-out at the end as well,

66
00:04:46,160 --> 00:04:49,300
because it said that if a claim under the policy arose,

67
00:04:50,220 --> 00:04:54,980
and it concerned an underlying contract where the insured had failed to incorporate the conditions,

68
00:04:55,320 --> 00:04:59,880
the insured's right to indemnity would not be prejudiced if they could show

69
00:04:59,880 --> 00:05:04,460
that they'd taken all reasonable and practicable steps to incorporate the conditions

70
00:05:04,460 --> 00:05:05,920
into the relevant contract.

71
00:05:07,000 --> 00:05:10,960
The difficulty arose because there was a clause later in the wording,

72
00:05:11,060 --> 00:05:15,460
I think it was a couple of pages further on, that set out the effect of a breach

73
00:05:15,460 --> 00:05:16,860
of this condition precedent,

74
00:05:17,280 --> 00:05:21,880
and it said that if insurers could identify a breach of condition precedent,

75
00:05:22,240 --> 00:05:25,800
then they'd be entitled to avoid the claim in its entirety.

76
00:05:27,240 --> 00:05:31,460
And how did the claim that was the subject of this dispute arise? What were the facts?

77
00:05:31,780 --> 00:05:36,320
Well, DNS made a claim following allegations against it by Scott Beef,

78
00:05:36,520 --> 00:05:40,380
which was a red meat product provider, as its name might suggest.

79
00:05:40,700 --> 00:05:46,200
And Scott Beef alleged that meat had been inadequately stored in the DNS warehouses

80
00:05:46,200 --> 00:05:48,340
and had therefore become damaged.

81
00:05:48,880 --> 00:05:52,720
And whilst the claim was being investigated by the insurers,

82
00:05:53,100 --> 00:05:59,140
it transpired that DNS's contract with Scott Beef was not on the SFDF terms

83
00:05:59,140 --> 00:06:02,860
and conditions as had been required by the insurance contract.

84
00:06:04,080 --> 00:06:08,080
And on that basis, insurers rejected the claim and they said there had been

85
00:06:08,080 --> 00:06:12,060
a breach of the condition precedent set out in the duty of assured clause.

86
00:06:12,900 --> 00:06:17,440
And given the drafting of that clause was pretty clear, how did the insured

87
00:06:17,440 --> 00:06:19,460
try and argue that the claim should still be paid?

88
00:06:20,040 --> 00:06:25,560
Well, DNS's case was that the requirements of the duty of assured clause were

89
00:06:25,560 --> 00:06:32,080
not on their true construction, conditions precedent, but instead were pre-contractual representations.

90
00:06:33,380 --> 00:06:35,240
And the court agreed with that argument.

91
00:06:35,740 --> 00:06:40,640
Looking at the requirements of the duty of assured clause, the court felt that

92
00:06:40,640 --> 00:06:44,500
although these were badged as conditions precedent, so insurers had described

93
00:06:44,500 --> 00:06:47,060
them as condition precedent in the actual contract,

94
00:06:47,420 --> 00:06:51,840
that wasn't conclusive and the clauses Causes could be properly interpreted

95
00:06:51,840 --> 00:06:58,340
as pre-contractual representations which had intended to be incorporated into the contract.

96
00:06:59,100 --> 00:07:05,420
That was partly because they represented promises by the insured about the situation

97
00:07:05,420 --> 00:07:12,900
at inception where they declared that all trading conditions then in use satisfied various criteria.

98
00:07:13,460 --> 00:07:18,420
And then they said that they would only trade under those conditions for the duration of the policy.

99
00:07:19,740 --> 00:07:23,900
Of course, if these requirements were indeed pre-contractual representations

100
00:07:23,900 --> 00:07:26,080
rather than conditions precedent,

101
00:07:26,440 --> 00:07:31,300
then the only way for them to be enforced once the contract had been entered

102
00:07:31,300 --> 00:07:37,100
into is for them to be treated of warranties by the insured for the purposes of the contract.

103
00:07:37,740 --> 00:07:42,300
But the Insurance Act has obviously changed the way warranties are treated in insurance contracts.

104
00:07:42,300 --> 00:07:47,620
Yes, that's right, because Section 9 of the Insurance Act states that a pre-contractual

105
00:07:47,620 --> 00:07:51,660
representation can't automatically be turned into a warranty,

106
00:07:51,700 --> 00:07:54,080
and any attempt to do so in the wording,

107
00:07:54,280 --> 00:07:58,500
for example by a basis of contract clause, will be unenforceable.

108
00:08:00,020 --> 00:08:03,020
There was a bit more of a debate about the third part of the clause,

109
00:08:03,060 --> 00:08:07,380
which requires the insured to take reasonable steps to ensure that conditions

110
00:08:07,380 --> 00:08:12,760
are incorporated into the contract the insurer has entered into on an ongoing basis,

111
00:08:13,160 --> 00:08:18,360
as well as in contracts that existed at the time that the policy was entered into. you.

112
00:08:19,460 --> 00:08:23,220
But the court held that this couldn't be relied upon as a freestanding condition

113
00:08:23,220 --> 00:08:25,740
precedent to liability, as

114
00:08:25,740 --> 00:08:29,980
it didn't comply with the transparency requirements of the Insurance Act.

115
00:08:30,580 --> 00:08:35,220
Ah yes, so where you have a clause that puts the insured in a worse position

116
00:08:35,220 --> 00:08:38,740
than would have been the case under the Act, you have to make sure the clause

117
00:08:38,740 --> 00:08:41,100
is drafted in a clear and unambiguous way,

118
00:08:41,260 --> 00:08:45,700
and also draw the attention of the insured specifically to the relevant clause

119
00:08:45,700 --> 00:08:47,940
prior to the policy being entered into.

120
00:08:48,200 --> 00:08:52,760
Yes, that's right. And none of those conditions had been satisfied here.

121
00:08:53,020 --> 00:08:58,040
And they needed to be because the third part of the duty of assured clause entitled

122
00:08:58,040 --> 00:09:03,400
insurers to reject a claim unless the insured took all reasonable and practicable

123
00:09:03,400 --> 00:09:09,760
steps to ensure that their trading conditions were incorporated into the contracts they entered into.

124
00:09:10,820 --> 00:09:16,140
If the wording was allowed to stand as is, the insured would be in a worse position

125
00:09:16,140 --> 00:09:21,300
than under the Act, which provides that insurers are only off-risk whilst the

126
00:09:21,300 --> 00:09:23,920
insured is in breach of any warranty,

127
00:09:24,600 --> 00:09:29,760
or condition precedent is in breach of any warranty, and a condition precedent

128
00:09:29,760 --> 00:09:32,700
is in breach of any warranty.

129
00:09:33,220 --> 00:09:36,940
And furthermore, breach of warranty or breach of a condition precedent...

130
00:09:36,940 --> 00:09:40,860
If you can also go through it, and then go before it.

131
00:09:41,060 --> 00:09:46,660
Okay, I'll start the whole thing again. If the wording was allowed to stand as is,

132
00:09:46,880 --> 00:09:49,900
the insured would be in a worse position than under the Act,

133
00:09:50,060 --> 00:09:54,100
which provides that insurers will only be off risk for a breach of warranty

134
00:09:54,100 --> 00:09:59,680
while the insured is in breach and once the breach has been remedied, cover will be restored.

135
00:10:01,360 --> 00:10:05,160
And it's also the case under the new Act that a breach of warranty or a condition

136
00:10:05,160 --> 00:10:12,100
precedent can be disregarded altogether under Section 11 if the warranty is

137
00:10:12,100 --> 00:10:15,040
intended to reduce the risk of loss of a particular kind,

138
00:10:15,300 --> 00:10:18,700
in a particular place, or at a particular location,

139
00:10:19,020 --> 00:10:24,160
and if breach of the warranty didn't increase the likelihood of the loss which

140
00:10:24,160 --> 00:10:26,000
actually occurred occurring.

141
00:10:27,320 --> 00:10:32,240
So for the clause to be effective, the Section 17 transparency requirements

142
00:10:32,240 --> 00:10:36,040
had to be adhered to, and as the judge found, they hadn't been.

143
00:10:36,480 --> 00:10:40,760
So presumably that left insurers with only an argument for breach of the duty

144
00:10:40,760 --> 00:10:45,380
of fair presentation under Section 3, on the basis that the insured had misrepresented

145
00:10:45,380 --> 00:10:47,380
its trading practices during placement.

146
00:10:48,000 --> 00:10:58,700
Well, that's right. And as you know, if insurers want to argue that there's

147
00:10:58,700 --> 00:11:02,300
been a breach of the duty of fair presentation, they have two choices.

148
00:11:02,700 --> 00:11:06,700
They can either try and make an argument that the breach was deliberate or reckless.

149
00:11:07,180 --> 00:11:12,300
And if they do that, they'd be entitled to avoid the policy from inception and keep the premium.

150
00:11:13,680 --> 00:11:16,440
Alternatively as here they can argue that

151
00:11:16,440 --> 00:11:19,840
the breach was not deliberate or reckless and

152
00:11:19,840 --> 00:11:24,760
in those circumstances their remedy will depend on what the actual underwriter

153
00:11:24,760 --> 00:11:29,720
would have done if he or she had received a fair presentation of the risk at

154
00:11:29,720 --> 00:11:34,600
placement so for example if the actual underwriter says that he or she would

155
00:11:34,600 --> 00:11:38,740
not have written the risk and can establish that on the balance of probabilities,

156
00:11:39,260 --> 00:11:41,860
then the contract will be treated as void.

157
00:11:42,640 --> 00:11:46,080
Alternatively, if the underwriter's evidence is that they would have written

158
00:11:46,080 --> 00:11:50,820
the risk on different terms, then those terms will be incorporated into the

159
00:11:50,820 --> 00:11:51,960
contract from inception.

160
00:11:53,880 --> 00:11:57,800
But in order to prove what the underwriter would have done under different circumstances,

161
00:11:58,320 --> 00:12:04,580
insurers will, if possible, need evidence from that underwriter because it's a subjective test.

162
00:12:05,020 --> 00:12:09,360
And if that underwriter isn't available, as unfortunately for insurers was the

163
00:12:09,360 --> 00:12:14,040
case here, then they'll need evidence such as applicable underwriting guidelines,

164
00:12:14,580 --> 00:12:19,380
evidence of corporate practice from more senior underwriters of the class in

165
00:12:19,380 --> 00:12:24,420
question, or evidence from someone with previous experience of the account.

166
00:12:25,360 --> 00:12:30,320
In this case, as I say, the original underwriter wasn't available to give evidence

167
00:12:30,320 --> 00:12:35,800
and so insurers relied on evidence from the underwriter who'd been responsible

168
00:12:35,800 --> 00:12:38,160
for writing the risk in previous years.

169
00:12:39,160 --> 00:12:44,460
That underwriter claimed that insurers had always based their underwriting decisions

170
00:12:44,460 --> 00:12:49,860
for this risk on the assumption that the standard terms would apply to the contract

171
00:12:49,860 --> 00:12:51,980
between the insured and its customers.

172
00:12:53,340 --> 00:12:57,560
And her case was that if insurers had been told that the insured was not always

173
00:12:57,560 --> 00:13:02,160
applying those standard terms, insurers would have declined the risk completely.

174
00:13:03,780 --> 00:13:07,800
It seems like quite a lot rests on that evidence that you put forward as to

175
00:13:07,800 --> 00:13:09,620
what the underwriter's decision would have been.

176
00:13:10,080 --> 00:13:13,680
How did the court receive the evidence in this matter? Well, you're right,

177
00:13:13,800 --> 00:13:18,120
and this is a big change from the position under the old Marine Insurance Act,

178
00:13:18,220 --> 00:13:23,100
because now the underwriter has to prove on the balance of probabilities what

179
00:13:23,100 --> 00:13:26,320
would have happened if a fair presentation had been made.

180
00:13:26,320 --> 00:13:31,920
And in this case, the underwriter accepted under cross-examination that important

181
00:13:31,920 --> 00:13:34,220
provisions of the standard terms,

182
00:13:34,440 --> 00:13:38,880
and particularly the provisions relating to limits of liability in the original

183
00:13:38,880 --> 00:13:41,320
contract between the insured and its customers,

184
00:13:41,600 --> 00:13:44,880
could have been incorporated into the insurance itself.

185
00:13:45,900 --> 00:13:49,300
But nonetheless, she still maintained that the risk would not have been written

186
00:13:49,300 --> 00:13:54,540
without the representation by the insured that standard terms were being applied.

187
00:13:54,540 --> 00:13:59,960
But the judge couldn't accept that, and the reasons for that were first of all

188
00:13:59,960 --> 00:14:07,180
that the FSDF terms were not in fact industry standard, as had been argued by the insurers,

189
00:14:07,500 --> 00:14:12,320
and furthermore, and perhaps even more damningly, insurers didn't even know

190
00:14:12,320 --> 00:14:16,680
what was in the FSDF terms when they wrote the risk in the first place.

191
00:14:16,680 --> 00:14:21,180
And finally, as the underwriter conceded in cross-examination,

192
00:14:21,460 --> 00:14:26,340
the judge found that important provisions of the FSDF terms could have been

193
00:14:26,340 --> 00:14:32,240
incorporated into the insurance had insurers actually considered them to be

194
00:14:32,240 --> 00:14:34,000
important and they hadn't done that.

195
00:14:34,000 --> 00:14:39,280
And all of that undermined the case that underwriters' decision to participate

196
00:14:39,280 --> 00:14:44,860
in the risk was determined by the insurer's representation that they would always

197
00:14:44,860 --> 00:14:47,560
incorporate these terms into their underlying contract.

198
00:14:48,420 --> 00:14:53,880
And on that basis, then, the judge found that insurers had failed to show that

199
00:14:53,880 --> 00:14:57,720
they wouldn't have written the contract at all had a fair presentation been

200
00:14:57,720 --> 00:15:03,060
made, and they therefore weren't entitled to avoid the risk and had to pay the underlying loss.

201
00:15:04,880 --> 00:15:08,420
So I think this shows the real importance of the evidence of the underwriter

202
00:15:08,420 --> 00:15:12,320
and the importance of having anything that will back that up as well as the

203
00:15:12,320 --> 00:15:15,760
individual's testimony, such as underwriting records, things like that.

204
00:15:16,400 --> 00:15:21,120
Yeah, I agree. And it's an important reminder of the significance of maintaining

205
00:15:21,120 --> 00:15:27,320
clear underwriting records and internal underwriting guidelines so that insurers

206
00:15:27,320 --> 00:15:31,860
are in a strong position to prove what it is that they would have done had a

207
00:15:31,860 --> 00:15:33,340
fair presentation been May.

208
00:15:33,600 --> 00:15:37,960
Often, they may be required to give that evidence some years down the line.

209
00:15:38,040 --> 00:15:43,340
If it's not supported by documentation, obviously, that can be difficult. Okay.

210
00:15:44,400 --> 00:15:48,060
Let's move on then to our second case we're discussing in this podcast,

211
00:15:48,400 --> 00:15:54,520
the Technip Saudi Arabia against the Mediterranean and Gulf insurance and reinsurance company MATA.

212
00:15:54,940 --> 00:15:58,560
Just looking at the facts of this one, Technip, which was the insured,

213
00:15:58,660 --> 00:16:03,500
contracted to carry out work on offshore assets, which were owned by a joint venture company.

214
00:16:03,880 --> 00:16:07,860
And I understand that as part of the transaction, Technit entered into a standard

215
00:16:07,860 --> 00:16:12,460
form all risks insurance policy covering offshore construction in the form of

216
00:16:12,460 --> 00:16:17,020
an amended Wellcar 2001 offshore construction project policy.

217
00:16:17,200 --> 00:16:19,240
So kind of a standard term policy.

218
00:16:19,660 --> 00:16:24,400
And the JV company and the other contractors were also insured under this same policy.

219
00:16:25,220 --> 00:16:28,680
Now, in terms of the facts that led to the loss, So whilst the offshore works

220
00:16:28,680 --> 00:16:33,120
were underway, a vessel that Technip had charted collided with an unmanned offshore

221
00:16:33,120 --> 00:16:35,620
wellhead that was owned by the JV company.

222
00:16:36,320 --> 00:16:40,560
Technip claimed on the policy, but I understand insurers rejected liability.

223
00:16:40,980 --> 00:16:46,280
And on that basis, they advised Technip to act as a prudent uninsured in their

224
00:16:46,280 --> 00:16:49,100
discussions with the JV company about the loss.

225
00:16:49,260 --> 00:16:54,040
And Technip, you know, accordingly went on to do just that and negotiate a settlement

226
00:16:54,040 --> 00:16:56,220
of 25 million US dollars.

227
00:16:57,660 --> 00:17:01,680
Once that settlement had been agreed, the insured once again approached insurers

228
00:17:01,680 --> 00:17:05,560
for indemnity under the policy and cover was once more rejected,

229
00:17:05,700 --> 00:17:08,780
this time on the basis that the loss was excluded.

230
00:17:09,480 --> 00:17:13,360
But they also raised the argument that Technip had failed to obtain insurer's

231
00:17:13,360 --> 00:17:18,140
consent to the settlement, which I understand was a requirement of the policy.

232
00:17:18,800 --> 00:17:22,140
So let's have a look at the exclusion point in the first instance.

233
00:17:23,240 --> 00:17:27,020
Yeah, so and this is where our all important definitions become relevant.

234
00:17:27,660 --> 00:17:33,600
Because the relevant exclusion carved out any claim for damages to any property

235
00:17:33,600 --> 00:17:41,120
which the principal assured, with an A, owned that was not otherwise provided for in the policy.

236
00:17:41,980 --> 00:17:45,400
But the policy didn't define a principal assured,

237
00:17:45,720 --> 00:17:51,580
what it did was define principal insured, and the principal insured,

238
00:17:51,660 --> 00:17:56,960
with an I, was defined in a way that included both Technic and the JV company,

239
00:17:57,160 --> 00:17:59,600
which of course had owned the damaged wellhead.

240
00:18:00,060 --> 00:18:05,600
Okay, so slightly different terminology, principal insured versus principal

241
00:18:05,600 --> 00:18:09,580
assured, where only principal insured is defined.

242
00:18:10,160 --> 00:18:18,340
That's right. And the policy furthermore distinguished between principal insureds and other insureds,

243
00:18:18,340 --> 00:18:23,180
which was also a defined term in the policy and referred to another category

244
00:18:23,180 --> 00:18:25,920
of insureds who were covered by the policy,

245
00:18:26,000 --> 00:18:31,420
presumably to a lesser extent or for lesser covers or lesser amounts.

246
00:18:31,940 --> 00:18:37,560
So the insurers argued that the principal assured in the exclusion should have

247
00:18:37,560 --> 00:18:41,680
the same meaning as the defined term principal insureds.

248
00:18:41,680 --> 00:18:46,100
And that meant, of course, that the exclusion would bite because the property

249
00:18:46,100 --> 00:18:51,100
which had been damaged was the property owned by one of the principal ashwards

250
00:18:51,100 --> 00:18:52,940
– in other words, the JV company.

251
00:18:54,870 --> 00:18:59,630
Technic's position, on the other hand, was that the term principal assured in

252
00:18:59,630 --> 00:19:04,790
the exclusion should be read as applying only to the principal insured making

253
00:19:04,790 --> 00:19:06,590
the claim, in other words, Technic.

254
00:19:06,830 --> 00:19:14,050
And where the property forming the subject of the claim was not the property

255
00:19:14,050 --> 00:19:16,810
of Technic, the exclusion didn't bite.

256
00:19:17,490 --> 00:19:23,610
So all of this turns on whether you use an A or an I, which is the sort of point

257
00:19:23,610 --> 00:19:27,130
that lawyers love and everyone else thinks is probably rather silly.

258
00:19:27,250 --> 00:19:32,110
But nonetheless, £25 million or US dollars turned on this one issue. you.

259
00:19:33,470 --> 00:19:38,150
Teknik also tried to make the argument that because the policy was a composite policy,

260
00:19:38,470 --> 00:19:42,830
in other words, it covered a number of different insureds, under which insured

261
00:19:42,830 --> 00:19:49,170
party should be treated as a separate distinct insured, when considering the exclusion,

262
00:19:49,630 --> 00:19:55,110
the court should consider the term as if there was only one insured.

263
00:19:56,310 --> 00:19:59,810
Okay, but am I right that Teknik lost at first instance.

264
00:19:59,970 --> 00:20:04,510
Yeah, despite all those arguments, Technic did indeed lose at first instance

265
00:20:04,510 --> 00:20:10,110
and the court found for insurers holding that the exclusion applied and the

266
00:20:10,110 --> 00:20:12,550
court then went, or the case then went to appeal,

267
00:20:12,830 --> 00:20:16,910
but unfortunately for Technic, they lost again in the court of appeal.

268
00:20:17,910 --> 00:20:22,930
And it's at the court of appeal where the issues surrounding the principles

269
00:20:22,930 --> 00:20:27,790
of construction were really addressed in detail because the court of appeal.

270
00:20:29,630 --> 00:20:35,390
If you start from the beginning okay yeah

271
00:20:35,390 --> 00:20:38,250
so the court found for insurers they found

272
00:20:38,250 --> 00:20:41,410
that the exclusion applied but the case then

273
00:20:41,410 --> 00:20:44,410
went to appeal at the court of appeal but nonetheless

274
00:20:44,410 --> 00:20:50,110
the court of appeal also found in favor of insurers and technic lost once again

275
00:20:50,110 --> 00:20:55,710
and it was at the court appeal level that the issue of construction interpretation

276
00:20:55,710 --> 00:21:01,410
of the policy was set out in terms of basic principles and basic rules.

277
00:21:01,990 --> 00:21:06,750
And what the Court of Appeal reminded everybody of is that the words of the

278
00:21:06,750 --> 00:21:12,470
contract have to be given their natural and ordinary meaning as far as possible.

279
00:21:12,650 --> 00:21:18,110
And that's the natural and ordinary meaning that would be understood by an objective

280
00:21:18,110 --> 00:21:21,710
person in the position of the parties to the contract.

281
00:21:21,890 --> 00:21:26,490
It's not something that would be understood by a lawyer's undertaking a microscopic

282
00:21:26,490 --> 00:21:30,370
examination of the wording, looking at the I's and A's and so on.

283
00:21:30,470 --> 00:21:36,250
What we're looking for is the natural and ordinary meaning of the words on an objective basis.

284
00:21:38,150 --> 00:21:43,010
The court acknowledged that the drafted clause was a market standard wording,

285
00:21:43,210 --> 00:21:46,710
but nonetheless they said that it's not a model of clear drafting,

286
00:21:46,810 --> 00:21:51,070
and so the first lesson for us here, I think, is that just because the wording

287
00:21:51,070 --> 00:21:55,370
is a market standard doesn't necessarily mean it's going to be clear.

288
00:21:56,090 --> 00:22:01,270
But nonetheless, the Court of Appeal found that insurers' interpretation of the exclusion,

289
00:22:01,630 --> 00:22:06,990
which involved reading principal insureds instead of principal assureds,

290
00:22:06,990 --> 00:22:12,970
did much less violence, as they put it, to the wording than the approach suggested by Technic.

291
00:22:13,850 --> 00:22:17,750
Technic's approach involved adding extra words to the clause,

292
00:22:17,910 --> 00:22:21,410
which was always, I think, probably going to be an uphill battle.

293
00:22:21,730 --> 00:22:27,550
Because what they said was that the court should effectively agree to amend

294
00:22:27,550 --> 00:22:33,310
the exclusion to refer not to any claim for damages to any property which the

295
00:22:33,310 --> 00:22:34,990
principal assured owned,

296
00:22:35,490 --> 00:22:44,710
but instead to any claim for damage to any property which the principal assured making the claim owned.

297
00:22:44,810 --> 00:22:49,550
So you see they wanted to add in some extra words and the court said that that

298
00:22:49,550 --> 00:22:55,890
did more violence, as they put it, to the wording than the interpretation suggested by the insurers.

299
00:22:57,170 --> 00:23:01,450
And it was also a factor, looking more broadly at the policy wording,

300
00:23:01,670 --> 00:23:06,530
that Technic's interpretation wouldn't work in the event of a claim by one of

301
00:23:06,530 --> 00:23:11,770
the other insureds who didn't, of course, actually own any property covered by the policy.

302
00:23:12,070 --> 00:23:15,650
Okay, so in that scenario, there wouldn't be any property which the principal

303
00:23:15,650 --> 00:23:21,570
assured making the claim owned because another insured would be making the claim. Yeah, exactly.

304
00:23:22,450 --> 00:23:25,870
So did the fact that this was, you mentioned earlier, it's a composite policy,

305
00:23:26,090 --> 00:23:28,890
it covers a number of named insureds, as we discussed earlier,

306
00:23:29,050 --> 00:23:32,270
but each should be treated distinctly. Did that argument hold any sway?

307
00:23:32,510 --> 00:23:36,450
No, it didn't. I mean, that was an argument that the technique tried to make,

308
00:23:36,450 --> 00:23:40,290
as you know, but the approach to the exclusion would be the same,

309
00:23:40,350 --> 00:23:42,710
whether this was a composite policy or not.

310
00:23:43,990 --> 00:23:48,270
And what about the consent to settlement point? Yeah, the relevant clause in

311
00:23:48,270 --> 00:23:53,070
the policy provided that insurers would only be liable to indemnify the insured

312
00:23:53,070 --> 00:23:58,430
in respect of damage where the insurers had consented to the underlying settlement.

313
00:23:58,530 --> 00:24:03,810
And in this case, they hadn't consented to the underlying settlement between Technic and the JV.

314
00:24:04,090 --> 00:24:07,570
But insurers had rejected the claim, if I remember correctly,

315
00:24:07,830 --> 00:24:12,490
and then told Technic to behave as a prudent uninsured. Can they really rely

316
00:24:12,490 --> 00:24:16,250
on a consent to settle clause in those circumstances? Well, the answer to that is no.

317
00:24:16,990 --> 00:24:21,750
The court found that insurers had either waived their right to rely on the consent

318
00:24:21,750 --> 00:24:28,010
to settle clause or stopped from doing so because of their denial of coverage earlier.

319
00:24:28,170 --> 00:24:31,250
So insurers couldn't effectively have their cake and eat it.

320
00:24:31,770 --> 00:24:35,890
And do these findings about the consent to settle clause still apply where the

321
00:24:35,890 --> 00:24:38,790
case had already been resolved on the basis of the exclusion?

322
00:24:38,810 --> 00:24:40,270
There was no cover anyway. way?

323
00:24:40,470 --> 00:24:44,750
Well, strictly speaking, the judge's comments on the point are non-binding on

324
00:24:44,750 --> 00:24:49,610
other judges, but they're still certainly persuasive and they'll be taken into

325
00:24:49,610 --> 00:24:52,490
account by courts facing similar issues in the future.

326
00:24:52,710 --> 00:24:58,590
And quite frankly, in my view anyway, it's so blindingly obvious that that is

327
00:24:58,590 --> 00:25:02,190
the right interpretation that I wouldn't want to be in the position of trying

328
00:25:02,190 --> 00:25:03,450
to argue something different.

329
00:25:04,570 --> 00:25:09,790
So just in terms of kind of takeaways from those two cases and some Some of

330
00:25:09,790 --> 00:25:13,210
these, I think, are reminders of things we already know, but just have been

331
00:25:13,210 --> 00:25:14,410
hammered home by the court again.

332
00:25:15,030 --> 00:25:19,930
So make sure a clause has the effect that you want it to based on the drafting.

333
00:25:20,090 --> 00:25:25,090
So labelling a condition precedent doesn't by itself make the clause a condition precedent.

334
00:25:25,230 --> 00:25:28,550
You know, it's the substance rather than the label, that old story.

335
00:25:28,990 --> 00:25:33,090
And I think this is also a salutary reminder about the transparency requirements

336
00:25:33,090 --> 00:25:37,230
under the Act. If you want the clause to do something more than the act itself

337
00:25:37,230 --> 00:25:41,370
allows, just make sure you're ticking those section 16 and 17 boxes.

338
00:25:42,170 --> 00:25:46,130
As I understand it, we talked about this earlier, keep clear underwriting records.

339
00:25:46,230 --> 00:25:49,770
It's one of those things that probably seems like another job at the time.

340
00:25:49,790 --> 00:25:53,350
But if you do find yourself, as you said, potentially years later,

341
00:25:53,450 --> 00:25:57,050
wanting to make out a breach of fair presentation argument, you're going to

342
00:25:57,050 --> 00:25:58,850
need to have that evidence to back it up.

343
00:25:59,740 --> 00:26:03,800
And finally, if you do, as many policies do, have a consent to settle clause,

344
00:26:04,020 --> 00:26:07,700
give careful thought as to how any rejection of coverage,

345
00:26:07,960 --> 00:26:12,180
kind of email or letter is worded, if actually the coverage position is still

346
00:26:12,180 --> 00:26:16,520
a bit uncertain, so that you can preserve your entitlement to rely on that consent

347
00:26:16,520 --> 00:26:18,120
to settlement clause down the line.

348
00:26:18,600 --> 00:26:23,420
Yeah, I agree with all of that. And I think more generally, these cases illustrate

349
00:26:23,420 --> 00:26:28,600
that wordings are dynamic or should be considered a dynamic because the nature

350
00:26:28,600 --> 00:26:30,700
of risk is always changing,

351
00:26:30,980 --> 00:26:34,180
because the legal and commercial background is evolving.

352
00:26:34,400 --> 00:26:38,280
So we've seen, for example, in our first case, the Scott Beef case,

353
00:26:38,460 --> 00:26:45,620
a failure by insurers to respond properly, arguably to the effects of the Insurance Act.

354
00:26:45,820 --> 00:26:49,880
And one needs to bear in mind, therefore, that the legal background to your

355
00:26:49,880 --> 00:26:51,200
wordings is always ways evolving.

356
00:26:51,880 --> 00:26:57,300
And it's important on that basis to review existing wordings regularly to ensure

357
00:26:57,300 --> 00:27:00,080
they remain up to date and fit for purpose.

358
00:27:00,360 --> 00:27:05,540
And that is the position whether they're market standard clauses or other bespoke

359
00:27:05,540 --> 00:27:10,500
products, because it's interesting here that in our second case, the Technic case,

360
00:27:10,740 --> 00:27:15,040
the court was concerned with a market standard wording, but nonetheless found

361
00:27:15,040 --> 00:27:22,820
it to be poorly drafted and in many ways not really fit for purpose in the circumstances of this loss.

362
00:27:23,460 --> 00:27:28,780
So new wordings and clauses should be prepared on the basis of existing circumstances

363
00:27:28,780 --> 00:27:31,340
and not just on what's gone before.

364
00:27:32,360 --> 00:27:37,320
Interesting times indeed. So thanks to anyone who's listening and please do

365
00:27:37,320 --> 00:27:40,820
join us for the next episode in our Risk Matters podcast series.

366
00:27:42,180 --> 00:27:45,900
Thank you for listening to Risk Matters, the DWF insurance podcast.

367
00:27:46,260 --> 00:27:49,480
We hope you join us again soon for future podcasts in our series.

Previous episodes

Cyber Incident Response
In the next two episodes of Risk Matters, we delve into the intricate world of cyber incident response. Cyber threats have evolved in sophistication, necessitating a robust, multi-faceted response mechanism. Our discussion will be split into two parts to explore this evolution, highlighting the complexities and advancements in cyber incident response.
 
Ukraine: Insurance, commerce and what comes next
In this episode of Risk Matters we explore how insurers are responding to the ongoing conflict in Ukraine and the role insurance can play in helping support the Ukrainian economy.
 
Renewable energy and insurance: the challenges and opportunities
In this episode of Risk Matters we explore the insurance industry’s relationship with renewable energy markets.
 

Further Reading