<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Re Risk &#187; Wasa</title>
	<atom:link href="http://www.rerisk.net/tag/wasa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rerisk.net</link>
	<description>Risk, Re-/Insurance and Future Thinking</description>
	<lastBuildDate>Wed, 23 Jun 2010 11:59:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Alistair Schaff on Wasa v Lexington</title>
		<link>http://www.rerisk.net/2009/09/04/alistair-schaff-on-wasa-v-lexington/</link>
		<comments>http://www.rerisk.net/2009/09/04/alistair-schaff-on-wasa-v-lexington/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 15:50:03 +0000</pubDate>
		<dc:creator>Jolyon</dc:creator>
				<category><![CDATA[Case Reports]]></category>
		<category><![CDATA[follow settlements]]></category>
		<category><![CDATA[Reinsurance]]></category>
		<category><![CDATA[Wasa]]></category>

		<guid isPermaLink="false">http://www.rerisk.net/?p=548</guid>
		<description><![CDATA[Alistair Schaff QC gave an illuminating talk on Wasa –v– Lexington at an impromptu BILA session in Lloyd’s Old Library today.
While Schaff represented the winning reinsurers he managed to convey an objective sense that the right decision had been reached.  I was in tune with that since I had always found the CA decision [...]


Related posts:<ol><li><a href='http://www.rerisk.net/2009/09/02/quiet-times/' rel='bookmark' title='Permanent Link: Quiet times'>Quiet times</a> <small> Well, yes, it has been pretty quiet here on...</small></li>
<li><a href='http://www.rerisk.net/2009/06/02/master-policies-%e2%80%93v%e2%80%93-local-policies-reinstatement/' rel='bookmark' title='Permanent Link: Master policies –v– Local policies: reinstatement'>Master policies –v– Local policies: reinstatement</a> <small> In the very recent (20 May 2009) case of...</small></li>
<li><a href='http://www.rerisk.net/2008/11/14/authority-and-claims-co-operation/' rel='bookmark' title='Permanent Link: Authority and Claims Co-operation'>Authority and Claims Co-operation</a> <small> In the recent (24.10.08) case of Markel –v- Gothaer...</small></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p></p><p>Alistair Schaff QC gave an illuminating talk on <em>Wasa –v– Lexington</em> at an impromptu BILA session in Lloyd’s Old Library today.</p>
<p>While Schaff represented the winning reinsurers he managed to convey an objective sense that the right decision had been reached.  I was in tune with that since I had always found the CA decision oddly artificial and this judgment from the House of Lords strikes me as more commercially sensible.</p>
<p>An interesting point did arise, though.  Supposing that the underlying law had always and explicitly been that of Pennsylvania – what then would have happened as regards the period of cover under the (UK law) reinsurance?  In other words, how would the Courts reconcile the clash between the unusual yet legally correct (under Pennsylvanian law) finding that Lexington were liable for all loss occurring from 1942 onwards as against the very plain words of the reinsurance contract’s period clause, i.e. that it only responded to losses occurring during the policy period (for 3 years from 1 July 1977)?  Schaff admitted that he did not know the answer but said that, while it would be a very close call, it was perhaps marginally more likely that reinsurers would still squeak home. He alluded to their Lordships’ comments that the period clause in the reinsurance wording was very plain, and also to the English reinsurance law position that an LOD clause is not at all far from being an express, specific provision that cover will only be available for losses occurring in that period.</p>
<p>Interesting.  The factual matrix in <em>Wasa</em> was unusual and unlikely to be repeated, but that second scenario (a foreign finding at odds with English reinsurance doctrine) is not at all uncommon and one can expect this to be tested before very long, I suspect.</p>
<p>Emphasising that the case was all about construction, Schaff also pointed out why the ‘follow settlements’ clause in <em>Wasa</em> didn’t help the cedent, namely, because the clause only operates if the risk is one to which the insurance and reinsurance respond.  Here, the reinsurance did not respond (because of the LOD provisions) and Lexington were thus unable to apply the follow clause.  </p>
<p>While it seems obvious, that’s a principle worth bearing in mind.  Too often, people see a follow settlements or Full Reinsurance wording and immediately conclude that cover must necessarily apply.  <em>Wasa</em> shows quite neatly why that is not always the case.</p>


<p>Related posts:<ol><li><a href='http://www.rerisk.net/2009/09/02/quiet-times/' rel='bookmark' title='Permanent Link: Quiet times'>Quiet times</a> <small> Well, yes, it has been pretty quiet here on...</small></li>
<li><a href='http://www.rerisk.net/2009/06/02/master-policies-%e2%80%93v%e2%80%93-local-policies-reinstatement/' rel='bookmark' title='Permanent Link: Master policies –v– Local policies: reinstatement'>Master policies –v– Local policies: reinstatement</a> <small> In the very recent (20 May 2009) case of...</small></li>
<li><a href='http://www.rerisk.net/2008/11/14/authority-and-claims-co-operation/' rel='bookmark' title='Permanent Link: Authority and Claims Co-operation'>Authority and Claims Co-operation</a> <small> In the recent (24.10.08) case of Markel –v- Gothaer...</small></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://www.rerisk.net/2009/09/04/alistair-schaff-on-wasa-v-lexington/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

