<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Recharacterizing Representations and Pre-closing Obligations as Conditions</title>
	<atom:link href="http://www.adamsdrafting.com/2010/01/08/recharacterizing-representations-and-pre-closing-obligations-as-conditions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2010/01/08/recharacterizing-representations-and-pre-closing-obligations-as-conditions/</link>
	<description></description>
	<lastBuildDate>Tue, 31 Jan 2012 01:23:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Michael</title>
		<link>http://www.adamsdrafting.com/2010/01/08/recharacterizing-representations-and-pre-closing-obligations-as-conditions/comment-page-1/#comment-95374</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Fri, 21 May 2010 17:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2083#comment-95374</guid>
		<description>I forgot about this. 
 
I certainly didn&#039;t mean to suggest that at all.  I don&#039;t think that same awkwardness is at play with conditions.  What I meant was that, sure, you can do this with conditions (&quot;If the price happens to be this, then [these rights/obligations follow]&quot;), but -- unfortunately -- this boils down to that I believe you can also avoid the awkwardness with warranties.  What isn&#039;t unfortunate is that this all amounts to basically the same thing.  I can state something as a warranty (or a representation, or a banana) and then suggest certain ramifications for its failure -- e.g., provide a condition to closing that the warranty (or representation or banana) is true as of the closing.  We can state the whole thing within a condition to closing.  In terms of avoiding the obligation to close for failure of a certain promise, this works all the same.   </description>
		<content:encoded><![CDATA[<p>I forgot about this. </p>
<p>I certainly didn&#39;t mean to suggest that at all.  I don&#39;t think that same awkwardness is at play with conditions.  What I meant was that, sure, you can do this with conditions (&quot;If the price happens to be this, then [these rights/obligations follow]&quot;), but &#8212; unfortunately &#8212; this boils down to that I believe you can also avoid the awkwardness with warranties.  What isn&#39;t unfortunate is that this all amounts to basically the same thing.  I can state something as a warranty (or a representation, or a banana) and then suggest certain ramifications for its failure &#8212; e.g., provide a condition to closing that the warranty (or representation or banana) is true as of the closing.  We can state the whole thing within a condition to closing.  In terms of avoiding the obligation to close for failure of a certain promise, this works all the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2010/01/08/recharacterizing-representations-and-pre-closing-obligations-as-conditions/comment-page-1/#comment-95284</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Thu, 29 Apr 2010 23:02:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2083#comment-95284</guid>
		<description>Michael: You suggest that the awkwardness of having a party undertake to do that which isn&#039;t within its control, or make representations regarding that which isn&#039;t within its control, would also appear in conditions regarding matters that aren&#039;t within a party&#039;s control. But nothing about conditions requires that they concern matters that are under the control of a party; in fact, it&#039;s quite the opposite. 
 
And I&#039;m afraid I don&#039;t have the stamina to wade into the representation v. warranties business again. The bottom line is that the elements of an action for misrepresentation and an action for breach of warranty are issues that apply only when a contract dispute arises. They have no bearing on how the parties articulate the deal, except where required by statute (for example, as regards waiver of warranties). 
 
And regarding &quot;At Closing the market price of unobtanium will be at least $10,000 per gram,&quot; addressing this issue in a representation suggests that it&#039;s something that&#039;s under the control of the party in question. It would be clearer to phrase it as the risk-allocation mechanism that it is: &quot;If at Closing the market price of unobtanium is less than $10,000 per gram, Acme shall ....&quot; 
 
Ken </description>
		<content:encoded><![CDATA[<p>Michael: You suggest that the awkwardness of having a party undertake to do that which isn&#039;t within its control, or make representations regarding that which isn&#039;t within its control, would also appear in conditions regarding matters that aren&#039;t within a party&#039;s control. But nothing about conditions requires that they concern matters that are under the control of a party; in fact, it&#039;s quite the opposite. </p>
<p>And I&#039;m afraid I don&#039;t have the stamina to wade into the representation v. warranties business again. The bottom line is that the elements of an action for misrepresentation and an action for breach of warranty are issues that apply only when a contract dispute arises. They have no bearing on how the parties articulate the deal, except where required by statute (for example, as regards waiver of warranties). </p>
<p>And regarding &quot;At Closing the market price of unobtanium will be at least $10,000 per gram,&quot; addressing this issue in a representation suggests that it&#039;s something that&#039;s under the control of the party in question. It would be clearer to phrase it as the risk-allocation mechanism that it is: &quot;If at Closing the market price of unobtanium is less than $10,000 per gram, Acme shall &#8230;.&quot; </p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.adamsdrafting.com/2010/01/08/recharacterizing-representations-and-pre-closing-obligations-as-conditions/comment-page-1/#comment-95263</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 26 Apr 2010 01:40:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2083#comment-95263</guid>
		<description>Ken:  I, too, am delighted to be a part of the conversation.  This is fun. 
 
So, I agree that it&#039;s a bit odd that a seller would covenant to do something it cannot do, but, inasmuch as the seller has agreed to do as much, I don&#039;t see why we would forgive this bargained-for obligation.  Now, if circumstances change to make the the obligation impracticable or its purpose frustrated or otherwise to excuse performance (e.g., under a force majeure clause), then that&#039;s a different story.  But, to my mind, the doctrine of excuse suggests that where impossible promises are made with eyes wide open (and, again, especially by sophisticated parties), then a party should be held to such promises.  I agree that it is an awkward situation and perhaps suggestive that a party did not actually manifest assent. 
 
I guess it depends on what you&#039;re defining as &quot;the issue.&quot;  WIth a condition, whatever rights that followed the satisfaction of the condition would be forfeited by the party&#039;s failure to perform the impossible.  This may still be an issue for some parties/courts.  I think you mean the cognitive dissonance involved with promising to do the impossible as opposed to agreeing that one&#039;s rights are conditioned upon the happening of something outside the party&#039;s control.  But, again, I don&#039;t think that conditions are the special mechanism for relieving this awkwardness -- indeed, I think the awkwardness is peculiar to covenants and representations.  It is awkward to promise to do the impossible.  It is awkward to assert as fact the unknown.  (I think a slightly separate conversation is the upshot of this &quot;illogicalness&quot; or &quot;awkwardness&quot; -- to my mind, the real questions are whether the parties will have a harder time negotiating with the terms so framed, will they understand how to &quot;use&quot; this document as a going concern, will a judge interpret these terms differently than intended by the parties or not enforce the provision altogether.) 
 
I disagree that representations and warranties are at all the same thing.  (I am new to this site; so, forgive my unfamiliarity with past discussion on this.  I will be sure to read up when I get the chance.)  Representations are assertions of fact made with the intention of inducing reliance.  Warranties are promises that certain assertions are true and/or will be true (depending on whether the warranty is stated as ongoing or as of a point in time).  Perhaps it is awkward to represent a fact about which one has no knowledge or control (e.g., to represent a future price: &quot;At Closing the market price of unobtanium will be at least $10,000 per gram.&quot;).  I think one may still go ahead and assert the unknown as fact; however, I think it&#039;s likely that any attempt to sue on that representation for misrepresentation will be unsuccessful.  However, there is nothing awkward about warranting the truth of a fact about which one has no knowledge (e.g., to warrant a future price).  This is the essential function of warranties (at least after Ziff-Davis) -- to shift the risk of the occurrence or non-occurrence of something.  This is not the essential function of representations, which are mere factual assertions upon which others may rely. 
 
Michael 
 
 </description>
		<content:encoded><![CDATA[<p>Ken:  I, too, am delighted to be a part of the conversation.  This is fun. </p>
<p>So, I agree that it&#39;s a bit odd that a seller would covenant to do something it cannot do, but, inasmuch as the seller has agreed to do as much, I don&#39;t see why we would forgive this bargained-for obligation.  Now, if circumstances change to make the the obligation impracticable or its purpose frustrated or otherwise to excuse performance (e.g., under a force majeure clause), then that&#39;s a different story.  But, to my mind, the doctrine of excuse suggests that where impossible promises are made with eyes wide open (and, again, especially by sophisticated parties), then a party should be held to such promises.  I agree that it is an awkward situation and perhaps suggestive that a party did not actually manifest assent. </p>
<p>I guess it depends on what you&#39;re defining as &quot;the issue.&quot;  WIth a condition, whatever rights that followed the satisfaction of the condition would be forfeited by the party&#39;s failure to perform the impossible.  This may still be an issue for some parties/courts.  I think you mean the cognitive dissonance involved with promising to do the impossible as opposed to agreeing that one&#39;s rights are conditioned upon the happening of something outside the party&#39;s control.  But, again, I don&#39;t think that conditions are the special mechanism for relieving this awkwardness &#8212; indeed, I think the awkwardness is peculiar to covenants and representations.  It is awkward to promise to do the impossible.  It is awkward to assert as fact the unknown.  (I think a slightly separate conversation is the upshot of this &quot;illogicalness&quot; or &quot;awkwardness&quot; &#8212; to my mind, the real questions are whether the parties will have a harder time negotiating with the terms so framed, will they understand how to &quot;use&quot; this document as a going concern, will a judge interpret these terms differently than intended by the parties or not enforce the provision altogether.) </p>
<p>I disagree that representations and warranties are at all the same thing.  (I am new to this site; so, forgive my unfamiliarity with past discussion on this.  I will be sure to read up when I get the chance.)  Representations are assertions of fact made with the intention of inducing reliance.  Warranties are promises that certain assertions are true and/or will be true (depending on whether the warranty is stated as ongoing or as of a point in time).  Perhaps it is awkward to represent a fact about which one has no knowledge or control (e.g., to represent a future price: &quot;At Closing the market price of unobtanium will be at least $10,000 per gram.&quot;).  I think one may still go ahead and assert the unknown as fact; however, I think it&#39;s likely that any attempt to sue on that representation for misrepresentation will be unsuccessful.  However, there is nothing awkward about warranting the truth of a fact about which one has no knowledge (e.g., to warrant a future price).  This is the essential function of warranties (at least after Ziff-Davis) &#8212; to shift the risk of the occurrence or non-occurrence of something.  This is not the essential function of representations, which are mere factual assertions upon which others may rely. </p>
<p>Michael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2010/01/08/recharacterizing-representations-and-pre-closing-obligations-as-conditions/comment-page-1/#comment-95261</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Sun, 25 Apr 2010 02:54:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2083#comment-95261</guid>
		<description>Michael: I&#039;m delighted to have someone take me up on this! 
 
When you use an obligation to address something that isn&#039;t under the control of the seller, in theory the buyer would be entitled to seek damages if the obligation isn&#039;t performed. In other words, you&#039;re penalizing the seller for not doing something even though the seller had no control over it. That doesn&#039;t make much sense. If you want to shift risk, it would be clearer for you to do so explicitly. 
 
That issue wouldn&#039;t arise if the matter were addressed as a condition. You wouldn&#039;t be requiring the seller to do the impossible and control whether X happens. Instead, you&#039;d be saying that you wouldn&#039;t want to proceed if X doesn&#039;t happen. 
 
I agree that when in doubt, a court will characterize something as an obligation rather than a condition. But generally the language in question relates to matters that are under the control of the party in question. 
 
And yes, you understand correctly what I mean by &quot;recharacterize.&quot; 
 
I&#039;m not sure what you mean regarding &quot;warranty. Contracts contain factual assertions. As a matter of convenience, it&#039;s simplest in a contract to refer to any such factual assertions as &quot;representations.&quot; (If you run a search on this blog for &quot;represents and warrants,&quot; you&#039;ll find more than you&#039;d ever want to know!) If any such factual assertion is inaccurate, you might be able to bring an action for misrepresentation, an action for breach of warranty, or both. But what kind of remedy you can bring doesn&#039;t affect the category of contract language of the factual statement, which is language of representation. 
 
Ken </description>
		<content:encoded><![CDATA[<p>Michael: I&#039;m delighted to have someone take me up on this! </p>
<p>When you use an obligation to address something that isn&#039;t under the control of the seller, in theory the buyer would be entitled to seek damages if the obligation isn&#039;t performed. In other words, you&#039;re penalizing the seller for not doing something even though the seller had no control over it. That doesn&#039;t make much sense. If you want to shift risk, it would be clearer for you to do so explicitly. </p>
<p>That issue wouldn&#039;t arise if the matter were addressed as a condition. You wouldn&#039;t be requiring the seller to do the impossible and control whether X happens. Instead, you&#039;d be saying that you wouldn&#039;t want to proceed if X doesn&#039;t happen. </p>
<p>I agree that when in doubt, a court will characterize something as an obligation rather than a condition. But generally the language in question relates to matters that are under the control of the party in question. </p>
<p>And yes, you understand correctly what I mean by &quot;recharacterize.&quot; </p>
<p>I&#039;m not sure what you mean regarding &quot;warranty. Contracts contain factual assertions. As a matter of convenience, it&#039;s simplest in a contract to refer to any such factual assertions as &quot;representations.&quot; (If you run a search on this blog for &quot;represents and warrants,&quot; you&#039;ll find more than you&#039;d ever want to know!) If any such factual assertion is inaccurate, you might be able to bring an action for misrepresentation, an action for breach of warranty, or both. But what kind of remedy you can bring doesn&#039;t affect the category of contract language of the factual statement, which is language of representation. </p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.adamsdrafting.com/2010/01/08/recharacterizing-representations-and-pre-closing-obligations-as-conditions/comment-page-1/#comment-95260</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sat, 24 Apr 2010 22:18:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2083#comment-95260</guid>
		<description>I agree that the representation doesn&#039;t do the trick -- because a buyer would have a hard time proving that it had reasonably relied on a representation by the seller about something clearly outside the seller&#039;s knowledge and control. 
 
I suppose it could be phrased as an obligation/covenant.  I don&#039;t see why this wouldn&#039;t be enforceable -- the seller is free to promise to do something difficult or seemingly outside its control.  Courts will start from the proposition that parties (especially the sophisticated) are free to promise as they like.  I suppose perhaps the more ridiculous, the more likely a court is to find the provision unconscionable, but I don&#039;t see why this would any more true for a covenant than a condition. 
 
Courts abhor conditions and will often do back flips to characterize a condition as a mere covenant (and not the other way around) -- because conditions must be strictly complied with to trigger any subsequent rights/obligations, whereas regular obligations need only be substantially performed to keep the other party on the hook for performance.  So, I would be surprised if you were to a find too many courts &quot;recharacterizing&quot; anything as a condition.  I&#039;m also a bit confused by the question -- by &quot;recharacterize,&quot; do you mean whether the court would allow the provision to operate *only* as a condition to closing through the &quot;bringdown&quot; clause and not allow the provision to have any effect as a separate representation or covenant? 
 
I think the appropriate contractual tool you&#039;re searching for is a warranty.  We can warrant anything will be true or not true for any period of time regardless of a party&#039;s ability to control -- this is just a means of allocating the risk of its truth/falsity between the parties.  This would give the receiving party the breach of warranty/contract claim in addition to any other rights as provided in the contract (e.g., the bringdown provision you mention, through which the content of the warranty would also amount to a condition to closing). </description>
		<content:encoded><![CDATA[<p>I agree that the representation doesn&#039;t do the trick &#8212; because a buyer would have a hard time proving that it had reasonably relied on a representation by the seller about something clearly outside the seller&#039;s knowledge and control. </p>
<p>I suppose it could be phrased as an obligation/covenant.  I don&#039;t see why this wouldn&#039;t be enforceable &#8212; the seller is free to promise to do something difficult or seemingly outside its control.  Courts will start from the proposition that parties (especially the sophisticated) are free to promise as they like.  I suppose perhaps the more ridiculous, the more likely a court is to find the provision unconscionable, but I don&#039;t see why this would any more true for a covenant than a condition. </p>
<p>Courts abhor conditions and will often do back flips to characterize a condition as a mere covenant (and not the other way around) &#8212; because conditions must be strictly complied with to trigger any subsequent rights/obligations, whereas regular obligations need only be substantially performed to keep the other party on the hook for performance.  So, I would be surprised if you were to a find too many courts &quot;recharacterizing&quot; anything as a condition.  I&#039;m also a bit confused by the question &#8212; by &quot;recharacterize,&quot; do you mean whether the court would allow the provision to operate *only* as a condition to closing through the &quot;bringdown&quot; clause and not allow the provision to have any effect as a separate representation or covenant? </p>
<p>I think the appropriate contractual tool you&#039;re searching for is a warranty.  We can warrant anything will be true or not true for any period of time regardless of a party&#039;s ability to control &#8212; this is just a means of allocating the risk of its truth/falsity between the parties.  This would give the receiving party the breach of warranty/contract claim in addition to any other rights as provided in the contract (e.g., the bringdown provision you mention, through which the content of the warranty would also amount to a condition to closing).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Anderson</title>
		<link>http://www.adamsdrafting.com/2010/01/08/recharacterizing-representations-and-pre-closing-obligations-as-conditions/comment-page-1/#comment-94640</link>
		<dc:creator>Mark Anderson</dc:creator>
		<pubDate>Fri, 08 Jan 2010 17:02:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2083#comment-94640</guid>
		<description>From an English law perspective, my first reaction is that it is unlikely that a court would recharacterise (using conventional English contract terminology) a warranty or representation as a condition precedent.

It is not uncommon, in my experience, for hard-nosed financial institutions to argue for warranties or representations not on the basis of what is reasonable or within the knowledge or control of the warrantor, but on the basis that there is a risk out there, perhaps in neither party&#039;s control, someone needs to bear that risk, and it should be the other party.  You use the word logical, and I agree that it is illogical to promise something that you can&#039;t control, but it seems to be quite common practice.

However, I don&#039;t have any case citations - sorry!</description>
		<content:encoded><![CDATA[<p>From an English law perspective, my first reaction is that it is unlikely that a court would recharacterise (using conventional English contract terminology) a warranty or representation as a condition precedent.</p>
<p>It is not uncommon, in my experience, for hard-nosed financial institutions to argue for warranties or representations not on the basis of what is reasonable or within the knowledge or control of the warrantor, but on the basis that there is a risk out there, perhaps in neither party&#8217;s control, someone needs to bear that risk, and it should be the other party.  You use the word logical, and I agree that it is illogical to promise something that you can&#8217;t control, but it seems to be quite common practice.</p>
<p>However, I don&#8217;t have any case citations &#8211; sorry!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

