<?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>AdamsDrafting &#187; Front and Back of the Contract</title>
	<atom:link href="http://www.adamsdrafting.com/category/front-and-back-of-the-contract/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com</link>
	<description></description>
	<lastBuildDate>Sun, 25 Dec 2011 14:20:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>One Person Signing for More than One Party?</title>
		<link>http://www.adamsdrafting.com/2010/07/03/one-person-signing-for-more-than-one-party/</link>
		<comments>http://www.adamsdrafting.com/2010/07/03/one-person-signing-for-more-than-one-party/#comments</comments>
		<pubDate>Sat, 03 Jul 2010 21:02:14 +0000</pubDate>
		<dc:creator>Ken Adams</dc:creator>
				<category><![CDATA[Front and Back of the Contract]]></category>

		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2892</guid>
		<description><![CDATA[A reader recently asked as follows: If someone is signing a contract on behalf of more than one party, and that person serves each party in the same capacity, would it be OK to use just one signature block, as in the following example? ACME HOLDINGS, LLC ACME ACQUISITIONS, LLC ACME INVESTMENTS, LLC By:     ______________________ [...]]]></description>
			<content:encoded><![CDATA[<p>A reader recently asked as follows: If someone is signing a contract on behalf of more than one party, and that person serves each party in the same capacity, would it be OK to use just one signature block, as in the following example?</p>
<blockquote><p>ACME HOLDINGS, LLC<br />
ACME ACQUISITIONS, LLC<br />
ACME INVESTMENTS, LLC</p>
<p>By:     ______________________<br />
          Richard Roe<br />
          President</p></blockquote>
<p>I responded that I&#8217;d feel more comfortable with the above arrangement if you added the notation &#8220;on behalf of each of the three above-named entities,&#8221; or some such. But saving a bit of space and sparing the signatory the ordeal of signing a couple of extra times seem negligible benefits. I have no plans to use such a three-for-one arrangement. But what if one person was signing for, say, six or more parties? Hmmm. Does that ever happen? If anyone can point to a publicly available contract that uses this technique, please post a link or email me a pdf.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamsdrafting.com/2010/07/03/one-person-signing-for-more-than-one-party/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>When What&#8217;s In the Contract Is Inconsistent with the Signature Block</title>
		<link>http://www.adamsdrafting.com/2010/07/03/when-whats-in-the-contract-is-inconsistent-with-the-signature-block/</link>
		<comments>http://www.adamsdrafting.com/2010/07/03/when-whats-in-the-contract-is-inconsistent-with-the-signature-block/#comments</comments>
		<pubDate>Sat, 03 Jul 2010 20:48:46 +0000</pubDate>
		<dc:creator>Ken Adams</dc:creator>
				<category><![CDATA[Front and Back of the Contract]]></category>

		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2889</guid>
		<description><![CDATA[What happens if a contract says that someone is personally liable for an obligation, but that person signs the contract not in their individual capacity, but as an officer of a limited liability company? In this newsletter article, Doug Batey of Stoel Rives considers a recent Washington Court of Appeals opinion that addressed exactly that [...]]]></description>
			<content:encoded><![CDATA[<p>What happens if a contract says that someone is personally liable for an obligation, but that person signs the contract not in their individual capacity, but as an officer of a limited liability company?</p>
<p>In <a href="http://www.llclawmonitor.com/2010/06/articles/piercing-the-veil/sometimes-an-llcs-signature-on-a-contract-can-result-in-a-members-personal-liability/#page=1">this newsletter article</a>, <a href="http://www.stoel.com/showbio.aspx?Show=270">Doug Batey</a> of Stoel Rives considers a recent Washington Court of Appeals opinion that addressed exactly that issue. Here, from Doug&#8217;s article, are the facts (citations omitted):</p>
<blockquote><p>William and Teresa Grover formed Grover International, LLC in 2005 and shortly thereafter acquired a business. In connection with the acquisition they received an assignment of the seller’s real estate lease. Their LLC signed the assignment using a conventional corporate style of signature, as “Grover International, LLC by William Grover member.”</p>
<p>So far so good. But the lease assignment said that the lease was assigned to “William and Teresa Grover as individuals, dba Grover International, LLC” (“dba” of course being the customary abbreviation for “doing business as”). The lease assignment in fact referred five different times to the assignee as “William and Teresa Grover as individuals, dba Grover International, LLC.”</p>
<p>In 2006 the Grovers sold their business, and the new buyer later defaulted on the lease. The owner of the real estate sued the Grovers, the LLC, their seller and their buyer. The trial court ruled on summary judgment that all defendants were liable jointly and severally, including William and Teresa Grover individually.</p></blockquote>
<p>The Court of Appeals held that the language in the contract trumped the signature block, and that if the signatory in question “did not want to be personally bound on the assignment, he should have insisted on the elimination of the language within the agreement that designated the assignee as ‘William and Teresa Glover as individuals.’”</p>
<p>Doug expresses surprise that the court didn&#8217;t treat the inconsistent language as an ambiguity capable of being resolved by means of extrinsic evidence. He also points out that the contract wasn&#8217;t entirely clear that personal liability was intended:</p>
<blockquote><p>The contract language did not refer simply to the Grovers individually, but to the Grovers doing business as Grover International, LLC, which at the time was an existing LLC. The phrase “doing business as” is usually used only for situations where a corporation or LLC does business under an alternate name. In Losh, however, the dba referred to an existing and separate entity, not just an alternate name for the Grovers.</p></blockquote>
<p>But for drafters, the moral of the story is a simple one: Don&#8217;t introduce this sort of inconsistency into your contracts!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamsdrafting.com/2010/07/03/when-whats-in-the-contract-is-inconsistent-with-the-signature-block/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Tacking an Acknowledgment on to the End of a Contract</title>
		<link>http://www.adamsdrafting.com/2010/03/05/tacking-an-acknowledgment-on-to-the-end-of-a-contract/</link>
		<comments>http://www.adamsdrafting.com/2010/03/05/tacking-an-acknowledgment-on-to-the-end-of-a-contract/#comments</comments>
		<pubDate>Fri, 05 Mar 2010 21:38:21 +0000</pubDate>
		<dc:creator>Ken Adams</dc:creator>
				<category><![CDATA[Front and Back of the Contract]]></category>

		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2346</guid>
		<description><![CDATA[You sometimes see a contract that has a paragraph entitled &#8220;Acknowledgement&#8221; added at the end, after the party signatures. For example, a search on the SEC&#8217;s EDGAR system quickly retrieved this document, a &#8220;forebearance agreement and amendment to indenture&#8221; between Gulfstream International Group, Inc. and Shelter Island Opportunity Fund, LLC. Here&#8217;s what came after their [...]]]></description>
			<content:encoded><![CDATA[<p>You sometimes see a contract that has a paragraph entitled &#8220;Acknowledgement&#8221; added at the end, after the party signatures.</p>
<p>For example, a search on the SEC&#8217;s EDGAR system quickly retrieved <a href="http://www.sec.gov/Archives/edgar/data/1405419/000135448810000630/gia_ex107.htm">this document</a>, a &#8220;forebearance agreement and amendment to indenture&#8221; between Gulfstream International Group, Inc. and Shelter Island Opportunity Fund, LLC. Here&#8217;s what came after their signature blocks:</p>
<blockquote><p>ACKNOWLEDGMENT AND AGREEMENT OF GUARANTORS The undersigned, each a guarantor of the indebtedness of Gulfstream International Group, Inc., a Delaware corporation ( Company ) to Shelter Island Opportunity Fund, LLC ( Holder ), pursuant to the separate Guaranty of each dated as of August 21, 2008 (each, as amended from time to time, a Guaranty ), hereby (i) acknowledges receipt of the foregoing Forbearance Agreement and Amendment to Securities Purchase Agreement and Debenture (the Agreement ); (ii) consents to the terms and execution thereof; (iii) reaffirms all obligations to Holder pursuant to the terms of the Guaranty; and (iv) acknowledges that Holder may amend, restate, extend, renew or otherwise modify the Transaction Documents and any indebtedness or agreement of Company, or enter into any agreement or extend additional or other credit accommodations, without notifying or obtaining the consent of the undersigned and without impairing the liability of the undersigned under the Guaranty for all of Companys present and future indebtedness to Holder.</p>
<p>[Signature blocks omitted.]</p></blockquote>
<p>I haven&#8217;t previously given any thought to the practice of tacking acknowledgements on to the end of a contract. I invite you to suggest whether or not that practice makes sense and, if it does, when it&#8217;s appropriate to use it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamsdrafting.com/2010/03/05/tacking-an-acknowledgment-on-to-the-end-of-a-contract/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>A Reminder that Contracts Under Seal Are, Sadly, Still Relevant</title>
		<link>http://www.adamsdrafting.com/2010/02/19/reminder-that-contracts-under-seal-are-sadly-still-relevant/</link>
		<comments>http://www.adamsdrafting.com/2010/02/19/reminder-that-contracts-under-seal-are-sadly-still-relevant/#comments</comments>
		<pubDate>Sat, 20 Feb 2010 03:24:30 +0000</pubDate>
		<dc:creator>Ken Adams</dc:creator>
				<category><![CDATA[Front and Back of the Contract]]></category>

		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2283</guid>
		<description><![CDATA[In this January 2008 blog post I noted that the requirements for what constitutes a &#8220;contract under seal&#8221; have been relaxed to the point of ludicrousness. But I also noted that in some states whether a contract is under seal has a bearing on which statute of limitations applies. From @Richards1000&#8216;s prolific Twitter outpouring I [...]]]></description>
			<content:encoded><![CDATA[<p>In <a href="http://www.adamsdrafting.com/2008/01/11/contracts-under-seal/">this January 2008 blog post</a> I noted that the requirements for what constitutes a &#8220;contract under seal&#8221; have been relaxed to the point of ludicrousness. But I also noted that in some states whether a contract is under seal has a bearing on which statute of limitations applies.</p>
<p>From<a href="http://twitter.com/richards1000"> @Richards1000</a>&#8216;s prolific Twitter outpouring I learned today of <a href="http://www.delawarelitigation.com/2010/02/articles/chancery-court-updates/chancery-court-applies-20year-statute-of-limitations-for-contracts-under-seal-rejects-laches-defense-defines-inquiry-notice/">this post</a> by the Delaware Corporate and Commercial Litigation Blog noting that in a recent opinion in a long-running lawsuit, the Delaware Chancery Court applied the twenty-year statute of limitations for contracts under seal.</p>
<p>Contract drafters should take into account external irrationality of this sort. For a given contract, check whether by statute the governing-law jurisdiction still recognizes contracts under seal and applies a different statute of limitations to contracts under seal. If it does, you may want to revise the contract in question so as to make it *rolls eyes* a contract under seal.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamsdrafting.com/2010/02/19/reminder-that-contracts-under-seal-are-sadly-still-relevant/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>When Is an Amendment Not an Amendment?</title>
		<link>http://www.adamsdrafting.com/2010/01/28/when-is-an-amendment-not-an-amendment/</link>
		<comments>http://www.adamsdrafting.com/2010/01/28/when-is-an-amendment-not-an-amendment/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 15:22:06 +0000</pubDate>
		<dc:creator>Ken Adams</dc:creator>
				<category><![CDATA[Front and Back of the Contract]]></category>

		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=2150</guid>
		<description><![CDATA[The following oddity from a reader: When is an amendment not an amendment? When it&#8217;s a separate agreement! From the introductory paragraph of a supplier&#8217;s attachment to another agreement: IMPLEMENTATION ASSISTANCE AMENDMENT NUMBER ONE TO BASIC LICENSE AGREEMENT NUMBER [redacted] CUSTOMER: [redacted] This Amendment, together with the terms and conditions contained int he Basic License [...]]]></description>
			<content:encoded><![CDATA[<p>The following oddity from a reader:</p>
<blockquote><p>When is an amendment not an amendment? When it&#8217;s a separate agreement!</p>
<p>From the introductory paragraph of a supplier&#8217;s attachment to another agreement:</p>
<blockquote><p><strong>IMPLEMENTATION ASSISTANCE AMENDMENT NUMBER ONE TO BASIC LICENSE AGREEMENT NUMBER [redacted] CUSTOMER: [redacted]</strong></p>
<p>This Amendment, together with the terms and conditions contained int he Basic License Agreement, dated January ___, 2010 shall constitute a separate and distinct Agreement between the parties. All the terms and conditions of said Basic License Agreement continue in full force and effect and shall control this Amendment unless specifically modified hereby.</p></blockquote>
<p>I&#8217;m not entirely sure what this means. From what I gather, what they really intend is for this &#8220;Amendment&#8221; not to <em>amend</em> anything, but to use the &#8220;Basic License Agreement&#8221; as a master set of terms and to add additional terms to address &#8220;implementation assistance&#8221; services. Sort of like an addendum with additional legal terms. Nevertheless, I wonder whether its prudent under any circumstance to refer to something as an &#8220;amendment&#8221; when you don&#8217;t intend it to modify the agreement to which it is attached.</p>
<p>From the world of bizzaro-drafting!</p></blockquote>
<p>I agree: don&#8217;t give anything in a contract a misleading label, because someone—notably a judge—may take you at your word.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamsdrafting.com/2010/01/28/when-is-an-amendment-not-an-amendment/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Some Kinds of Backdating May Be Permissible, But that Doesn&#8217;t Make It a Good Idea</title>
		<link>http://www.adamsdrafting.com/2009/09/20/backdating-permissible-doesnt-make-it-a-good-idea/</link>
		<comments>http://www.adamsdrafting.com/2009/09/20/backdating-permissible-doesnt-make-it-a-good-idea/#comments</comments>
		<pubDate>Sun, 20 Sep 2009 16:20:14 +0000</pubDate>
		<dc:creator>Ken Adams</dc:creator>
				<category><![CDATA[Front and Back of the Contract]]></category>

		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=1456</guid>
		<description><![CDATA[On the website of the state bar of Wisconsin I came across an article entitled &#8220;Backdating Documents: Not Necessarily the Stuff of Scandal.&#8221; It contains the following passage: Drafting and executing a document after an event occurs, but in a manner that accurately reflects the date on which the event transpired, is a permissible form [...]]]></description>
			<content:encoded><![CDATA[<p>On the website of the state bar of Wisconsin I came across an article entitled &#8220;<a href="http://www.wisbar.org/AM/Template.cfm?Section=InsideTrack&amp;Template=/CustomSource/InsideTrack/contentDisplay.cfm&amp;ContentID=85477">Backdating Documents: Not Necessarily the Stuff of Scandal</a>.&#8221; It contains the following passage:</p>
<blockquote><p>Drafting and executing a document after an event occurs, but in a manner that accurately reflects the date on which the event transpired, is a permissible form of backdating. This is backdating that memorializes, something the United States Court of Appeals for the Seventh Circuit has recognized as a legitimate practice. For example, if parties clearly reach an agreement on Dec. 31, 2009, but do not execute a contract formalizing their agreement until Jan.3, 2010, the contract may be dated as of Dec. 31, 2009. This is simply the accurate memorialization of a past event, something that is essential to legal practice.</p></blockquote>
<p>But just because something might be permissible doesn&#8217;t mean that it&#8217;s a good idea. I recommend not backdating a contract. Here&#8217;s what I said in <a href="http://www.adamsdrafting.com/2009/05/07/contract-preceded-by-oral-agreement/">this May 2009 blog post</a>:</p>
<blockquote><p>Courts have certainly been willing to hold that a contract exists before a written contract has been finalized. See, for example, <a href="http://www.adamsdrafting.com/2007/06/24/saying-you-have-a-deal/">this June 2007 blog post</a>. But I’d still use as the date for a written contract the date it was signed. It’s likely that the written contract addresses many more issues than were covered by the oral agreement, making the written contract different from the oral agreement.</p>
<p>Furthermore, giving the written contract its own date simply reflects the reality of how the contract process unfolded, and it’s always good to have contracts track reality. If the date of the oral agreement was reached is somehow significant, then mention it in the recitals of the written contract.</p></blockquote>
<p>If having a contract accurately reflect how events transpired doesn&#8217;t work for you, you&#8217;ve got problems that will only be exacerbated if you try to engage in any sleight of hand over dating.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamsdrafting.com/2009/09/20/backdating-permissible-doesnt-make-it-a-good-idea/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Superfluous Recitals in Merger Agreements</title>
		<link>http://www.adamsdrafting.com/2009/09/11/superfluous-recitals-in-merger-agreements/</link>
		<comments>http://www.adamsdrafting.com/2009/09/11/superfluous-recitals-in-merger-agreements/#comments</comments>
		<pubDate>Fri, 11 Sep 2009 10:17:12 +0000</pubDate>
		<dc:creator>Ken Adams</dc:creator>
				<category><![CDATA[Front and Back of the Contract]]></category>

		<guid isPermaLink="false">http://www.adamsdrafting.com/?p=1380</guid>
		<description><![CDATA[Methinks that the recitals in the average big-time-M&#38;A merger agreement are bloated. By way of example, below are the recitals from the August 31, 2009, merger agreement for Disney&#8217;s acquisition of Marvel. I&#8217;ve noted some big-picture comments in bracketed italics; I&#8217;ll spare you my many micro-level objections. RECITALS WHEREAS, the parties intend that, subject to the terms [...]]]></description>
			<content:encoded><![CDATA[<p>Methinks that the recitals in the average big-time-M&amp;A merger agreement are bloated. By way of example, below are the recitals from the August 31, 2009, merger agreement for Disney&#8217;s acquisition of Marvel. I&#8217;ve noted some big-picture comments in bracketed italics; I&#8217;ll spare you my many micro-level objections.</p>
<blockquote>
<p style="text-align: center;">RECITALS</p>
<p>WHEREAS, the parties intend that, subject to the terms and conditions hereinafter set forth <em>["subject to" phrase occurs several times, but flawed logic—the intent precedes the contract, not the other way round]</em>, Merger Sub shall merge with and into the Company (the &#8220;Merger&#8221;) <em>[appropriate topic for recitals]</em>, on the terms and subject to the conditions of this Agreement and in accordance with the General Corporation Law of the State of Delaware (&#8220;DGCL&#8221;);</p>
<p>WHEREAS, the parties intend that the Merger shall be immediately followed by a merger of the Surviving Corporation (as defined below) with and into Merger LLC (the &#8221; Upstream Merger &#8220;) <em>[appropriate topic for recitals]</em>, on the terms and subject to the conditions of this Agreement and in accordance with the Delaware Limited Liability Company Act (the &#8221; LLC Act &#8220;);</p>
<p>WHEREAS, the parties intend that the Merger be mutually interdependent with and a condition precedent to the Upstream Merger and that the Upstream Merger shall, through the binding commitment evidenced by Section 5.18 , be effected immediately following the Effective Time (as defined below), on the terms and subject to the conditions of this Agreement and in accordance with the LLC Act, without further approval, authorization or direction from or by any of the parties hereto <em>[too much information for recitals, and anyway covered in the body of the contract]</em>;</p>
<p>WHEREAS, the Boards of Directors of Parent and the Company each have determined that a business combination between Parent and the Company is advisable and in the best interests of their respective companies and stockholders and accordingly have agreed to effect the Merger provided for herein upon the terms and subject to the conditions set forth herein <em>[standard feature of merger-agreement recitals, but is unnecessary, given that authorization is addressed in board consents and in representations in the merger agreement; if this is in effect PR intended for shareholders, that function is better served by the proxy statement]</em>;</p>
<p>WHEREAS, simultaneously with the execution and delivery of this Agreement and as a condition and inducement to Parent&#8217;s and Merger Sub&#8217;s willingness to enter into this Agreement, Parent is entering into a voting agreement with the Company and certain stockholders of the Company (the &#8220;Voting Agreement&#8221;) <em>[if this is a condition to entry into the merger agreement, I'd expect to see that stated in the body of the contract; simpler just to say in the recitals that the parties have entered into the voting agreement]</em>; and</p>
<p>WHEREAS, it is intended that the Merger and the Upstream Merger, considered together as a single integrated transaction for United States federal income Tax purposes along with the other transactions effected pursuant to this Agreement, shall qualify as a &#8220;reorganization&#8221; within the meaning of Section 368(a) of the Internal Revenue Code of 1986, as amended (the &#8221; Code &#8220;) <em>[omit, as (1) covered in the body of the contract, in obligations relating to tax treatment, and (2) is misleading, as I gather that it's settled law that intent of the parties doesn't control the tax consequences of their actions; instead, when referring to the merger for first time say that it's structured as a reorganization]</em>.</p>
<p>NOW, THEREFORE, in consideration of the representations, warranties, covenants and agreements contained herein and for other good and valuable consideration, the receipt and adequacy of which are hereby acknowledged, and subject to the conditions set forth herein, the parties hereto agree as follows <em>[as always, a joke]</em>:</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.adamsdrafting.com/2009/09/11/superfluous-recitals-in-merger-agreements/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Questionable Defense of the Month: &#8220;I Signed the Contract in the Wrong Place&#8221;</title>
		<link>http://www.adamsdrafting.com/2009/06/24/signed-contract-in-wrong-place/</link>
		<comments>http://www.adamsdrafting.com/2009/06/24/signed-contract-in-wrong-place/#comments</comments>
		<pubDate>Wed, 24 Jun 2009 12:54:17 +0000</pubDate>
		<dc:creator>Ken Adams</dc:creator>
				<category><![CDATA[Front and Back of the Contract]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://adamsdrafting.com/system/2009/06/24/signed-contract-in-wrong-place/</guid>
		<description><![CDATA[Today the Law Shucks blog posted this item about a former IBM executive, David L. Johnson, who is claiming that his noncompetition agreement with IBM is unenforceable. One element of his defense is that he signed the contract in the space where IBM was supposed to sign. According to Bloomberg: Johnson told Robinson he signed the [...]]]></description>
			<content:encoded><![CDATA[<p>Today the Law Shucks blog posted <a href="http://lawshucks.com/2009/06/lame-defense-in-non-compete-suit/">this item</a> about a former IBM executive, David L. Johnson, who is claiming that his noncompetition agreement with IBM is unenforceable. One element of his defense is that he signed the contract in the space where IBM was supposed to sign. According to <a href="http://www.bloomberg.com/apps/news?pid=newsarchive&amp;sid=aK5hnt04Z92Q">Bloomberg</a>:</p>
<blockquote><p>Johnson told Robinson he signed the agreement on the space where IBM was supposed to sign because he thought it would prevent the contract from taking effect. His lawyers said it was up to IBM’s human resources department to make him to sign the agreement or punish him—something that didn’t happen.</p>
<p>“The notion that Mr. Johnson intended to be bound by that agreement is absurd,” Johnson’s lawyer, Michael Banks, said at the hearing.</p></blockquote>
<p>In their post, Law Shucks said they hoped that I&#8217;d have something to say about this—and I heard the call!</p>
<p>If Johnson&#8217;s defense were limited to the fact that he had signed the contract in the wrong place, he would likely have a tough time getting any court to buy his defense. Here&#8217;s what 1-2 Corbin on Contracts § 2.10 has to say generally about such matters:</p>
<blockquote><p>A signature may be operative without respect to its position on the document, although it is customary to sign at the end of the writing and beneath the written provisions. There must be satisfactory evidence that the signature was affixed with intent to authenticate and express assent to the entire document.</p></blockquote>
<p>And in a few minutes of rooting around on Westlaw, I found a relevant case, <em>Karapanos v. Boardwalk Fries, Inc.</em>, 837 P.2d 576 (Utah App. 1992). Here&#8217;s the relevant language:</p>
<blockquote><p>Karapanos argues that because he signed in the wrong place, the agreement was never executed. We disagree. Black&#8217;s Law Dictionary defines &#8220;execute&#8221; as &#8220;[t]o perform all necessary formalities, as to make and sign a contract.&#8221; 509 (5th ed. 1979). In addition, &#8220;it is a general rule that a signature located anywhere on a contract is sufficient to authenticate the instrument if it was placed there with the intent to do so.&#8221; <em>Pio v. Gilliland Constr., Inc.</em>, 276 Or. 975, 560 P.2d 247, 250 (1976); see 1 Corbin on Contracts 122 § 31 (1950). Karapanos admits he intended and believed the agreement to be enforceable when he signed it. In fact, he assigned his interest under the agreement to Guardian State Bank to secure a loan. He also flew to Maryland to receive training from Boardwalk. Boardwalk similarly conducted itself as if the agreement were fully enforceable. Boardwalk gave Karapanos confidential and proprietary materials, including operation and training manuals, business plans, budgets, and equipment specifications. It was only after Karapanos began having doubts about his decision that he questioned the enforceability of the agreement. Therefore, we conclude the parties executed the agreement, and we will enforce the agreement as it is written.</p></blockquote>
<p>The lawyers for our former IBM executive would doubtless distinguish <em>Karapanos</em> by saying that Johnson never did anything to suggest that he thought the contract was enforceable. The problem is that the way you comply with a noncompetition agreement is by &#8230; doing nothing. So lack of any indication of assent other than Johnson&#8217;s signature wouldn&#8217;t seem to prove anything.</p>
<p>But there&#8217;s more to Johnson&#8217;s story that the fact that he signed in the wrong place. Apparently IBM never signed the contract and returned the original to Johnson, who refused requests to sign another. So the story is murkier than it seems at first glance.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamsdrafting.com/2009/06/24/signed-contract-in-wrong-place/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Playing Games With the Date Next to the Signature</title>
		<link>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/</link>
		<comments>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/#comments</comments>
		<pubDate>Thu, 21 May 2009 21:31:02 +0000</pubDate>
		<dc:creator>Ken Adams</dc:creator>
				<category><![CDATA[Front and Back of the Contract]]></category>

		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/</guid>
		<description><![CDATA[Having parties to a contract date their signatures makes sense when there&#8217;s a lag time between when the first party signs and the last party signs. And some auditors are requiring that their clients use dated signatures in all their contracts. But dating signatures can be a nuisance. As I noted in this November 2008 [...]]]></description>
			<content:encoded><![CDATA[<p>Having parties to a contract date their signatures makes sense when there&#8217;s a lag time between when the first party signs and the last party signs. And some auditors are requiring that their clients use dated signatures in all their contracts.</p>
<p>But dating signatures can be a nuisance. As I noted in <a href="http://www.adamsdrafting.com/2008/11/01/signature-date-omitted/">this November 2008 blog post</a>, one problem is that parties sometimes return signed signature pages without filling in the date next to the signature.</p>
<p>Here&#8217;s another potential problem: what if the person signing puts in a date other than the date when they signed? Or they sign and date the contract but wait a few days before returning it? In either case, the result could be that the contract is given a date that is different from the date that would have been used if the person signing had put in the actual date and promptly returned the signature page. This could be more of a nuisance than playing games with the date in the introductory clause—the date you use in the introductory clause is something the parties have to agree on, whereas someone signing a contract has unfettered discretion to give their signature whatever date they want.</p>
<p>I have no idea whether this is a real issue. But the simplest fix would be to use a signature-automation solution such as <a href="http://www.echosign.com/">EchoSign</a> or <a href="http://www.docusign.com/">DocuSign</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamsdrafting.com/2009/05/21/playing-games-with-date-next-to-signature/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Initialing Each Page of a Contract</title>
		<link>http://www.adamsdrafting.com/2009/05/05/intialing-each-page/</link>
		<comments>http://www.adamsdrafting.com/2009/05/05/intialing-each-page/#comments</comments>
		<pubDate>Tue, 05 May 2009 12:24:39 +0000</pubDate>
		<dc:creator>Ken Adams</dc:creator>
				<category><![CDATA[Front and Back of the Contract]]></category>

		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/05/05/intialing-each-page/</guid>
		<description><![CDATA[Here&#8217;s what I understand of the practice of having those signing a contract also initial each page of the contract: It&#8217;s commonplace in wills, apparently as a check against substitution of pages. It&#8217;s required by statute in the case of some contracts. For example, under Ohio Revised Code 1349.55, each page of a contract providing [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s what I understand of the practice of having those signing a contract also initial each page of the contract:</p>
<ul>
<li>It&#8217;s commonplace in wills, apparently as a check against substitution of pages.</li>
<li>It&#8217;s required by statute in the case of some contracts. For example, under Ohio Revised Code 1349.55, each page of a contract providing for a non-recourse civil litigation advance must be initialed by the consumer.</li>
<li>With respect to business contracts, in the U.S. it would be unusual for the parties to initial each page, except in the case of real-estate contracts.</li>
<li>In Europe, it&#8217;s commonplace for the parties to a business contract to initial each page.</li>
</ul>
<p>Readers, please tell me more, including with respect to jurisdictions outside the U.S. When do you have the parties initial each page, and why?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamsdrafting.com/2009/05/05/intialing-each-page/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
	</channel>
</rss>

