<?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: &#8220;Consecutive Months&#8221;</title>
	<atom:link href="http://www.adamsdrafting.com/2008/09/28/consecutive-months/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2008/09/28/consecutive-months/</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: Gregory Harris</title>
		<link>http://www.adamsdrafting.com/2008/09/28/consecutive-months/comment-page-1/#comment-71310</link>
		<dc:creator>Gregory Harris</dc:creator>
		<pubDate>Fri, 21 Nov 2008 04:00:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/09/28/consecutive-months/#comment-71310</guid>
		<description>I don&#039;t see many posts or comments about provisions relating to time, so I&#039;m putting my comment here in the most nearly related thread.

In my office, when periods of time such as appeal periods are in question, we often talk about &quot;day zero&quot; and &quot;day one,&quot; as in &quot;the date of issuance of the decision is day zero. The next day is day one of the appeal period.&quot;

I wonder whether this vernacular might have a useful place in contracts. For example:

&quot;Doe shall give Roe not less than 20 days Notice of a proposed sale of a Lot. The date of the proposed sale will be [deemed] day zero, and the date of mailing Notice will be [deemed] day 21.&quot;

That example excludes both terminal days. The terminal days could be easily included by calling the mailing date &quot;day 20&quot; and the sale date &quot;day one.&quot; The point is, either way is pellucid.

It&#039;s also more compact than saying, &quot;For example, the last day for timely mailing of a Notice of a proposed October 31 sale of a Lot would be October 10.&quot;

Use of &quot;day zero&quot; nomenclature would make harmless otherwise potentially ambiguous formulations like &quot;no less than 20 days before&quot; or &quot;within 30 days after&quot; a date or event.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t see many posts or comments about provisions relating to time, so I&#8217;m putting my comment here in the most nearly related thread.</p>
<p>In my office, when periods of time such as appeal periods are in question, we often talk about &#8220;day zero&#8221; and &#8220;day one,&#8221; as in &#8220;the date of issuance of the decision is day zero. The next day is day one of the appeal period.&#8221;</p>
<p>I wonder whether this vernacular might have a useful place in contracts. For example:</p>
<p>&#8220;Doe shall give Roe not less than 20 days Notice of a proposed sale of a Lot. The date of the proposed sale will be [deemed] day zero, and the date of mailing Notice will be [deemed] day 21.&#8221;</p>
<p>That example excludes both terminal days. The terminal days could be easily included by calling the mailing date &#8220;day 20&#8243; and the sale date &#8220;day one.&#8221; The point is, either way is pellucid.</p>
<p>It&#8217;s also more compact than saying, &#8220;For example, the last day for timely mailing of a Notice of a proposed October 31 sale of a Lot would be October 10.&#8221;</p>
<p>Use of &#8220;day zero&#8221; nomenclature would make harmless otherwise potentially ambiguous formulations like &#8220;no less than 20 days before&#8221; or &#8220;within 30 days after&#8221; a date or event.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2008/09/28/consecutive-months/comment-page-1/#comment-66158</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Wed, 01 Oct 2008 14:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/09/28/consecutive-months/#comment-66158</guid>
		<description>Paul: In your example, I think that &quot;continues&quot; tells the reader that the provision applies only in the event of five days of uninterrupted interruption, if you see what I mean. But it&#039;s best not to leave such questions open to interpretation, so perhaps I&#039;d use &lt;em&gt;consecutive&lt;/em&gt;. Or I might restructure the provision; it&#039;s hard to say without seeing the entire provision. Ken</description>
		<content:encoded><![CDATA[<p>Paul: In your example, I think that &#8220;continues&#8221; tells the reader that the provision applies only in the event of five days of uninterrupted interruption, if you see what I mean. But it&#8217;s best not to leave such questions open to interpretation, so perhaps I&#8217;d use <em>consecutive</em>. Or I might restructure the provision; it&#8217;s hard to say without seeing the entire provision. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Comeaux</title>
		<link>http://www.adamsdrafting.com/2008/09/28/consecutive-months/comment-page-1/#comment-66157</link>
		<dc:creator>Paul Comeaux</dc:creator>
		<pubDate>Wed, 01 Oct 2008 14:17:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/09/28/consecutive-months/#comment-66157</guid>
		<description>Ken,

     I&#039;m not quite sure I agree with the statement &quot;if you’re referring to a period of time before or after a point in time, consecutive is redundant.&quot;

    Take this provision about interruption in building services in a lease:  &quot;If such interruption continues for more than five consecutive days, [Tenant may exercise remedies].&quot;

     I want to avoid the a tenant telling me that the power was out for 3 days, then came back for a day, then was out for 2 more days--so now they can exercise remedies.  This concerns me because if I were a tenant, it&#039;s exactly the argument I&#039;d make.  I might not make this argument if power were out 3 days in October and another 2 in December. But if the period between power outages were short, I&#039;d make this argument, even if I knew that it was more of an equitable than a technical argument--and a smart landlord would compromise with the tenant on this.  The word &quot;consecutive&quot; in this instance helps the landlord avoid this issue.

     Having said this, I agree with you about &quot;consecutive&quot; being redundant. I just think that after writing a clear, well written provision, it is sometimes appropriate to make a conscious decision to add a redundancy, if there is a compelling reason to do so.</description>
		<content:encoded><![CDATA[<p>Ken,</p>
<p>     I&#8217;m not quite sure I agree with the statement &#8220;if you’re referring to a period of time before or after a point in time, consecutive is redundant.&#8221;</p>
<p>    Take this provision about interruption in building services in a lease:  &#8220;If such interruption continues for more than five consecutive days, [Tenant may exercise remedies].&#8221;</p>
<p>     I want to avoid the a tenant telling me that the power was out for 3 days, then came back for a day, then was out for 2 more days&#8211;so now they can exercise remedies.  This concerns me because if I were a tenant, it&#8217;s exactly the argument I&#8217;d make.  I might not make this argument if power were out 3 days in October and another 2 in December. But if the period between power outages were short, I&#8217;d make this argument, even if I knew that it was more of an equitable than a technical argument&#8211;and a smart landlord would compromise with the tenant on this.  The word &#8220;consecutive&#8221; in this instance helps the landlord avoid this issue.</p>
<p>     Having said this, I agree with you about &#8220;consecutive&#8221; being redundant. I just think that after writing a clear, well written provision, it is sometimes appropriate to make a conscious decision to add a redundancy, if there is a compelling reason to do so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lemens</title>
		<link>http://www.adamsdrafting.com/2008/09/28/consecutive-months/comment-page-1/#comment-65864</link>
		<dc:creator>Chris Lemens</dc:creator>
		<pubDate>Mon, 29 Sep 2008 14:20:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/09/28/consecutive-months/#comment-65864</guid>
		<description>I hope that the only time I use &quot;consecutive months&quot; is in a service level description, where I set some payment or termination option based on something like &quot;failure in (a) any three months in any six-month period or (b) any two consecutive months.&quot; The point there is to emphasize the distinction between the two measurements.

Chris</description>
		<content:encoded><![CDATA[<p>I hope that the only time I use &#8220;consecutive months&#8221; is in a service level description, where I set some payment or termination option based on something like &#8220;failure in (a) any three months in any six-month period or (b) any two consecutive months.&#8221; The point there is to emphasize the distinction between the two measurements.</p>
<p>Chris</p>
]]></content:encoded>
	</item>
</channel>
</rss>

