<?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: What to Do When the Other Side Wants to Change Your MSCD-Compliant Language</title>
	<atom:link href="http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/</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: AdamsDrafting &#187; Blog Archive &#187; More on Prospects for Change: Getting Outside Counsel to Cooperate</title>
		<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/comment-page-1/#comment-79853</link>
		<dc:creator>AdamsDrafting &#187; Blog Archive &#187; More on Prospects for Change: Getting Outside Counsel to Cooperate</dc:creator>
		<pubDate>Tue, 27 Jan 2009 18:53:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/#comment-79853</guid>
		<description>[...] This post earlier this month considered how to ensure that people on the other side of a deal don&#8217;t balk at MSCD-compliant language. But what if it&#8217;s your outside counsel that&#8217;s not playing along? [...]</description>
		<content:encoded><![CDATA[<p>[...] This post earlier this month considered how to ensure that people on the other side of a deal don&#8217;t balk at MSCD-compliant language. But what if it&#8217;s your outside counsel that&#8217;s not playing along? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AdamsDrafting &#187; Blog Archive &#187; Prospects for Change</title>
		<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/comment-page-1/#comment-79517</link>
		<dc:creator>AdamsDrafting &#187; Blog Archive &#187; Prospects for Change</dc:creator>
		<pubDate>Sat, 24 Jan 2009 17:52:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/#comment-79517</guid>
		<description>[...] couple of recent posts (this one and this one) prompted some gnashing of teeth and rending of clothes by commenters frustrated at the pushback [...]</description>
		<content:encoded><![CDATA[<p>[...] couple of recent posts (this one and this one) prompted some gnashing of teeth and rending of clothes by commenters frustrated at the pushback [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art</title>
		<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/comment-page-1/#comment-78812</link>
		<dc:creator>Art</dc:creator>
		<pubDate>Mon, 19 Jan 2009 19:56:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/#comment-78812</guid>
		<description>I agree with the attitude that a lawyer should be responsible for their document, but I can also imagine the view from a firm&#039;s management. It is no good to them, if a breach occurs, to say that the lawyer responsible just was too dumb - the firm is held responsible, and the management are responsible for the firm, so by that point it&#039;s too late. If you are in a firm with 1000 lawyers, management aren&#039;t going to look at it on a personal level anyway, and the chances of a breach increase proportionately to headcount.

I don&#039;t like being nannied, but so goes the world...</description>
		<content:encoded><![CDATA[<p>I agree with the attitude that a lawyer should be responsible for their document, but I can also imagine the view from a firm&#8217;s management. It is no good to them, if a breach occurs, to say that the lawyer responsible just was too dumb &#8211; the firm is held responsible, and the management are responsible for the firm, so by that point it&#8217;s too late. If you are in a firm with 1000 lawyers, management aren&#8217;t going to look at it on a personal level anyway, and the chances of a breach increase proportionately to headcount.</p>
<p>I don&#8217;t like being nannied, but so goes the world&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sol Irvine</title>
		<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/comment-page-1/#comment-77903</link>
		<dc:creator>Sol Irvine</dc:creator>
		<pubDate>Tue, 13 Jan 2009 14:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/#comment-77903</guid>
		<description>I find the best solution to this problem is to incorporate only the substantive changes from the other side into the subsequent draft.  

This forces the other side to justify everything else.

Also, re Art&#039;s comment on track changes, I&#039;m aware that many firms discourage its use for the reasons you mention.  My opinion is that lawyers are responsible for understanding their documents, and that includes the use of metadata.  Track changes is an incredibly powerful tool.  To disallow it because there is a chance someone might not be bright enough to use it properly is wrong-headed.  Baby/bathwater, etc.</description>
		<content:encoded><![CDATA[<p>I find the best solution to this problem is to incorporate only the substantive changes from the other side into the subsequent draft.  </p>
<p>This forces the other side to justify everything else.</p>
<p>Also, re Art&#8217;s comment on track changes, I&#8217;m aware that many firms discourage its use for the reasons you mention.  My opinion is that lawyers are responsible for understanding their documents, and that includes the use of metadata.  Track changes is an incredibly powerful tool.  To disallow it because there is a chance someone might not be bright enough to use it properly is wrong-headed.  Baby/bathwater, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art</title>
		<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/comment-page-1/#comment-77788</link>
		<dc:creator>Art</dc:creator>
		<pubDate>Mon, 12 Jan 2009 13:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/#comment-77788</guid>
		<description>Track changes also have a risk of accidental disclosure of data. Where changes or comments are hidden, internal comments can potentially be sent accidentally to people who should not be seeing them.

At our law firm we are told not to use them for exactly this reason. An example is cited of a firm (I don&#039;t know which) sending a draft document to a client which, when track changes were revealed, showed the precedent used - i.e. another client&#039;s document.

This also happened (in a political context) to ex-UK Home Secretary Charles Clarke, who once sent his internal comments on a terrorism document to the opposition party in error.

I use Workshare to show changes, and either write comments in the text in bold (and highlighted, depending on the client), or put them in the accompanying email.</description>
		<content:encoded><![CDATA[<p>Track changes also have a risk of accidental disclosure of data. Where changes or comments are hidden, internal comments can potentially be sent accidentally to people who should not be seeing them.</p>
<p>At our law firm we are told not to use them for exactly this reason. An example is cited of a firm (I don&#8217;t know which) sending a draft document to a client which, when track changes were revealed, showed the precedent used &#8211; i.e. another client&#8217;s document.</p>
<p>This also happened (in a political context) to ex-UK Home Secretary Charles Clarke, who once sent his internal comments on a terrorism document to the opposition party in error.</p>
<p>I use Workshare to show changes, and either write comments in the text in bold (and highlighted, depending on the client), or put them in the accompanying email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lemens</title>
		<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/comment-page-1/#comment-77383</link>
		<dc:creator>Chris Lemens</dc:creator>
		<pubDate>Thu, 08 Jan 2009 16:03:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/#comment-77383</guid>
		<description>D.C. @ 4:15
I don&#039;t like comments. Being general counsel for my company, I mostly do commercial deals, not corporate ones. A business person sees every deal, but there are a lot of different business people seeing different deals. Many of them are very unsophisticated about Word. Getting them all to make sure they look for and read the comments would be a struggle. I can&#039;t count the number of times where I&#039;ve asked the business people what our response to a comment was and they were totally unaware of the comment&#039;s existence.

I&#039;d be afraid of that happening on the other side, too, if I put my remarks in comments. With footnotes, they are highly visible. It avoids the risk that the other side, in a big deal, took positions not realizing that we had issues in comments. The only way they can save face in that situation is for us to give on some of the issues in our comments. And, as we seasoned negotiators know, saving face is sadly huge for a lot of people.

I can, of course, solve that problem by spending more time on each deal, making sure that the relevant business people (on both sides!) have read the comments, and so on. But my business is the mass-production of deals. I don&#039;t want to spend the extra 10 minutes on each turn of each deal to make sure that everyone has read everything. That would have too high a cost in foregone business.

I&#039;m not sure whether you are saying that deleting footnotes was to hard or too easy, but I find deleting the footnotes is easy (either one at a time or all at once). To delete all at once in Word 2003, select any footnote; from the menu bar, select Format, then Styles and Formatting; at the top of the Styles and Formatting pane to the right, click on the Select All button below the Footnote Reference drop-down box; then hit the delete key. Poof! All the footnotes are gone.

If your business is mainly corporate, I can see how using comments would work. You have the chance to introduce yourself to the opposing counsel before the first turn of the draft and can discuss the logistics. In the commercial deals that I do daily, there is usually no counsel assigned on the other side until they receive my first re-draft of their form. Persuasive footnotes, highly visible to the business people, may even induce them to decide they don&#039;t need legal counsel if they feel that our position is fair. That&#039;s a good thing.

Chris</description>
		<content:encoded><![CDATA[<p>D.C. @ 4:15<br />
I don&#8217;t like comments. Being general counsel for my company, I mostly do commercial deals, not corporate ones. A business person sees every deal, but there are a lot of different business people seeing different deals. Many of them are very unsophisticated about Word. Getting them all to make sure they look for and read the comments would be a struggle. I can&#8217;t count the number of times where I&#8217;ve asked the business people what our response to a comment was and they were totally unaware of the comment&#8217;s existence.</p>
<p>I&#8217;d be afraid of that happening on the other side, too, if I put my remarks in comments. With footnotes, they are highly visible. It avoids the risk that the other side, in a big deal, took positions not realizing that we had issues in comments. The only way they can save face in that situation is for us to give on some of the issues in our comments. And, as we seasoned negotiators know, saving face is sadly huge for a lot of people.</p>
<p>I can, of course, solve that problem by spending more time on each deal, making sure that the relevant business people (on both sides!) have read the comments, and so on. But my business is the mass-production of deals. I don&#8217;t want to spend the extra 10 minutes on each turn of each deal to make sure that everyone has read everything. That would have too high a cost in foregone business.</p>
<p>I&#8217;m not sure whether you are saying that deleting footnotes was to hard or too easy, but I find deleting the footnotes is easy (either one at a time or all at once). To delete all at once in Word 2003, select any footnote; from the menu bar, select Format, then Styles and Formatting; at the top of the Styles and Formatting pane to the right, click on the Select All button below the Footnote Reference drop-down box; then hit the delete key. Poof! All the footnotes are gone.</p>
<p>If your business is mainly corporate, I can see how using comments would work. You have the chance to introduce yourself to the opposing counsel before the first turn of the draft and can discuss the logistics. In the commercial deals that I do daily, there is usually no counsel assigned on the other side until they receive my first re-draft of their form. Persuasive footnotes, highly visible to the business people, may even induce them to decide they don&#8217;t need legal counsel if they feel that our position is fair. That&#8217;s a good thing.</p>
<p>Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D. C. Toedt</title>
		<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/comment-page-1/#comment-77293</link>
		<dc:creator>D. C. Toedt</dc:creator>
		<pubDate>Wed, 07 Jan 2009 23:15:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/#comment-77293</guid>
		<description>Chris @ 3:35 p.m., I&#039;ve had the same favorable experience as you when I explain why I make changes.  

I&#039;ve found it helpful, though, to use Word comments instead of footnotes.  The former are (normally) tagged with the author&#039;s initials and a serial number. That allows them to remain in the draft without confusing people.  They can be deleted all at once with a single comment.  (I used to use footnotes instead of comments because comments couldn&#039;t be deleted en masse like that.)

I&#039;ve also found it helpful to put in a comment for every non-trivial change I make&#160;&#8212; that way, when the lawyers do get on the phone to discuss the markup, we can just proceed seriatim through the (numbered) comments and their associated changes.</description>
		<content:encoded><![CDATA[<p>Chris @ 3:35 p.m., I&#8217;ve had the same favorable experience as you when I explain why I make changes.  </p>
<p>I&#8217;ve found it helpful, though, to use Word comments instead of footnotes.  The former are (normally) tagged with the author&#8217;s initials and a serial number. That allows them to remain in the draft without confusing people.  They can be deleted all at once with a single comment.  (I used to use footnotes instead of comments because comments couldn&#8217;t be deleted en masse like that.)</p>
<p>I&#8217;ve also found it helpful to put in a comment for every non-trivial change I make&nbsp;&mdash; that way, when the lawyers do get on the phone to discuss the markup, we can just proceed seriatim through the (numbered) comments and their associated changes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lemens</title>
		<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/comment-page-1/#comment-77290</link>
		<dc:creator>Chris Lemens</dc:creator>
		<pubDate>Wed, 07 Jan 2009 22:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/#comment-77290</guid>
		<description>I took up a suggestion from a seminar I attended. On turning the first draft of larger commercial deals, I now usually add a footnote explaining the rationale for each change I make. After having done this several times now, I noticed the following effects:

(1) I am less likely to make changes that are stylistic, unless I identify specific reasons to do so (like ambiguity). For example, I won&#039;t change:
&lt;blockquote&gt;This Services Agreement (this &quot;Agreement&quot;)&lt;/blockquote&gt;

(2) I had way fewer changes come back to me than I usually encounter. I think this is partly because I am self-editing and partly because it is easier for the other side to consider our viewpoint outside of the confines of a telephone negotiating session.

(3) The logistics of the back-and-forth drafts worked better, especially when I included something like this as my first footnote:
&lt;blockquote&gt;This is [my company] draft dated [date]. We have used footnotes throughout to state the reasons for our changes. For the next draft, we would appreciate it if, using Microsoft Word&#039;s “Track Changes” features, you would reject all of our footnotes (so they don’t show up in the next draft), then accept all our other changes and make your own changes with “Track Changes” turned on (so that only your changes show up in the next draft). We’ve included a clean draft that does that, for your convenience.&lt;/blockquote&gt;

(4) I&#039;ve found that words of authority are the biggest stylistic change I make consistently. So, I use something like this footnote the first time I do that:
&lt;blockquote&gt;For words of authority (such as shall, must, may, will, and should), we have used the American Rule consistently, as detailed in Kenneth A. Adams’ &lt;i&gt;A Manual of Style of Contract Drafting&lt;/i&gt; (ABA 2008).&lt;/blockquote&gt;

Interestingly, on the last such deal, the very bright lawyer on the other side noted that he had the first edition on his desk and reads this blog. (Hi, Chris!) I think that was a very easy deal to close partly because we shared a perspective.

Chris</description>
		<content:encoded><![CDATA[<p>I took up a suggestion from a seminar I attended. On turning the first draft of larger commercial deals, I now usually add a footnote explaining the rationale for each change I make. After having done this several times now, I noticed the following effects:</p>
<p>(1) I am less likely to make changes that are stylistic, unless I identify specific reasons to do so (like ambiguity). For example, I won&#8217;t change:</p>
<blockquote><p>This Services Agreement (this &#8220;Agreement&#8221;)</p></blockquote>
<p>(2) I had way fewer changes come back to me than I usually encounter. I think this is partly because I am self-editing and partly because it is easier for the other side to consider our viewpoint outside of the confines of a telephone negotiating session.</p>
<p>(3) The logistics of the back-and-forth drafts worked better, especially when I included something like this as my first footnote:</p>
<blockquote><p>This is [my company] draft dated [date]. We have used footnotes throughout to state the reasons for our changes. For the next draft, we would appreciate it if, using Microsoft Word&#8217;s “Track Changes” features, you would reject all of our footnotes (so they don’t show up in the next draft), then accept all our other changes and make your own changes with “Track Changes” turned on (so that only your changes show up in the next draft). We’ve included a clean draft that does that, for your convenience.</p></blockquote>
<p>(4) I&#8217;ve found that words of authority are the biggest stylistic change I make consistently. So, I use something like this footnote the first time I do that:</p>
<blockquote><p>For words of authority (such as shall, must, may, will, and should), we have used the American Rule consistently, as detailed in Kenneth A. Adams’ <i>A Manual of Style of Contract Drafting</i> (ABA 2008).</p></blockquote>
<p>Interestingly, on the last such deal, the very bright lawyer on the other side noted that he had the first edition on his desk and reads this blog. (Hi, Chris!) I think that was a very easy deal to close partly because we shared a perspective.</p>
<p>Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art</title>
		<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/comment-page-1/#comment-77247</link>
		<dc:creator>Art</dc:creator>
		<pubDate>Wed, 07 Jan 2009 14:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/#comment-77247</guid>
		<description>I think Ken&#039;s first suggestion is the best, and even if your client is &quot;hot to do the deal&quot;, I think the following is still a good bet:

&quot;Dear X,

Thank you for your comments, all of which prove your unimpeachable genius as a deal lawyer (or words to that effect). I have incoporated all the substantive comments into the current draft, though in the interests of time I have not included all the cosmetic changes.&quot;

In this way you can demonstrate that you are focussed on time and cost, while maintaining the good drafting. If they insist on their comments, you can be sterner, and still invoke time/costs as perfectly valid reasons for ignoring their points.

Of course, there may come a point where you should give in - some people are beyond help.

Art</description>
		<content:encoded><![CDATA[<p>I think Ken&#8217;s first suggestion is the best, and even if your client is &#8220;hot to do the deal&#8221;, I think the following is still a good bet:</p>
<p>&#8220;Dear X,</p>
<p>Thank you for your comments, all of which prove your unimpeachable genius as a deal lawyer (or words to that effect). I have incoporated all the substantive comments into the current draft, though in the interests of time I have not included all the cosmetic changes.&#8221;</p>
<p>In this way you can demonstrate that you are focussed on time and cost, while maintaining the good drafting. If they insist on their comments, you can be sterner, and still invoke time/costs as perfectly valid reasons for ignoring their points.</p>
<p>Of course, there may come a point where you should give in &#8211; some people are beyond help.</p>
<p>Art</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/comment-page-1/#comment-77165</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 06 Jan 2009 23:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2009/01/06/change-mscd-compliant-language/#comment-77165</guid>
		<description>Vance: By all means drop my name, but you should keep the indefinite article in the title.

More to the point, I&#039;d love it if you were to try these positions out and report back.

Ken</description>
		<content:encoded><![CDATA[<p>Vance: By all means drop my name, but you should keep the indefinite article in the title.</p>
<p>More to the point, I&#8217;d love it if you were to try these positions out and report back.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
</channel>
</rss>

