<?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: Deal Proof—A Document-Analysis and Proofreading Tool</title>
	<atom:link href="http://www.adamsdrafting.com/2008/06/23/deal-proof/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2008/06/23/deal-proof/</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; Proofreading Tips?</title>
		<link>http://www.adamsdrafting.com/2008/06/23/deal-proof/comment-page-1/#comment-77104</link>
		<dc:creator>AdamsDrafting &#187; Blog Archive &#187; Proofreading Tips?</dc:creator>
		<pubDate>Tue, 06 Jan 2009 13:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/06/23/deal-proof/#comment-77104</guid>
		<description>[...] using another information-technology checking tool such as DealProof or [...]</description>
		<content:encoded><![CDATA[<p>[...] using another information-technology checking tool such as DealProof or [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2008/06/23/deal-proof/comment-page-1/#comment-62445</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 09 Sep 2008 18:15:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/06/23/deal-proof/#comment-62445</guid>
		<description>marcp: Have you seen &lt;a href=&quot;http://www.adamsdrafting.com/2008/04/23/lexicon/&quot; rel=&quot;nofollow&quot;&gt;my post on Lexicon&lt;/a&gt; ? I suspect that Lexicon would be more to your liking. Ken</description>
		<content:encoded><![CDATA[<p>marcp: Have you seen <a href="http://www.adamsdrafting.com/2008/04/23/lexicon/" rel="nofollow">my post on Lexicon</a> ? I suspect that Lexicon would be more to your liking. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marcp</title>
		<link>http://www.adamsdrafting.com/2008/06/23/deal-proof/comment-page-1/#comment-62259</link>
		<dc:creator>marcp</dc:creator>
		<pubDate>Mon, 08 Sep 2008 20:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/06/23/deal-proof/#comment-62259</guid>
		<description>I cannot find the price for West&#039;s Deal Proof.  The website only refers me to a sales rep.  I assume this means three things: the product is expensive due to the added cost of the sales rep; the product is so expensive that West is embarrassed to say how much it costs; and the sales rep is supposed to try to cross-sell me to other West products. I am not interested in any of that.

This is a small utility program for MS Word.  Tell me the price, let me do a demo (by myself, with the full version) and don&#039;t waste my billable time with sales reps. Sorry, West.</description>
		<content:encoded><![CDATA[<p>I cannot find the price for West&#8217;s Deal Proof.  The website only refers me to a sales rep.  I assume this means three things: the product is expensive due to the added cost of the sales rep; the product is so expensive that West is embarrassed to say how much it costs; and the sales rep is supposed to try to cross-sell me to other West products. I am not interested in any of that.</p>
<p>This is a small utility program for MS Word.  Tell me the price, let me do a demo (by myself, with the full version) and don&#8217;t waste my billable time with sales reps. Sorry, West.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandy Burge</title>
		<link>http://www.adamsdrafting.com/2008/06/23/deal-proof/comment-page-1/#comment-54680</link>
		<dc:creator>Sandy Burge</dc:creator>
		<pubDate>Thu, 10 Jul 2008 15:14:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/06/23/deal-proof/#comment-54680</guid>
		<description>Based on your blog, we asked our West representative to come do a demo of the product for us.  Gov&#039;t agencies, such as ours, were not aware of this tool.  I think it would be a great tool to use in drafting our 300 page managed care contracts, or even some of our non-contract documents with similar features.  I love the cite checking ability, as our contracts are rife with federal and state laws and regulations. That&#039;s a chore that takes hours to do by hand.</description>
		<content:encoded><![CDATA[<p>Based on your blog, we asked our West representative to come do a demo of the product for us.  Gov&#8217;t agencies, such as ours, were not aware of this tool.  I think it would be a great tool to use in drafting our 300 page managed care contracts, or even some of our non-contract documents with similar features.  I love the cite checking ability, as our contracts are rife with federal and state laws and regulations. That&#8217;s a chore that takes hours to do by hand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Munn</title>
		<link>http://www.adamsdrafting.com/2008/06/23/deal-proof/comment-page-1/#comment-54541</link>
		<dc:creator>David Munn</dc:creator>
		<pubDate>Tue, 08 Jul 2008 16:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/06/23/deal-proof/#comment-54541</guid>
		<description>I have looked at Deal Proof in the past and I agree with Fred that it can be a valuable tool. I&#039;m not aware of any other tool that does what Deal Proof does. 

It can help to catch some of the errors (e.g., cross-references and numbering) that tend to creep into a contract draft as it goes through the negotiation and editing processes. Since many lawyers don&#039;t use automatic numbering, and few lawyers use automatic cross references, these kinds of errors are introduced all the time, and they are often overlooked in the haste to get a deal done. Deal Proof would catch many of them. 

The other place where I think Deal Proof can add value is in reviewing a contract that was drafted by someone else. It doesn&#039;t take the place of manual proofreading, but it can catch many of the little things that are easy to overlook when you&#039;re trying to understand a lengthy contract you&#039;ve never seen before. Something like inconsistent use of definitions can be hard to spot in a long document, and Deal Proof does a decent job of finding those kinds of errors. 

The biggest problem I see with Deal Proof is not a problem with the software itself. It&#039;s that it&#039;s one more software tool that people have to take the time to learn and then take the time to use it routinely. In my experience, most lawyers are simply not going to spend the time to adopt another software tool, even if it would save them time in the long run. 

You could give Deal Proof to an assistant and let them use if for a first pass at proofreading, but much of the value of the tool would be lost since someone will still have to make a judgment call on many of the issues Deal Proof will spot.  

I applaud Fred for using Deal Proof to help in improving the quality of his firm&#039;s contracts, but I don&#039;t think most lawyers will adopt anything like this until, like spell check, it&#039;s completely integrated with word processing or a contract assembly tool.</description>
		<content:encoded><![CDATA[<p>I have looked at Deal Proof in the past and I agree with Fred that it can be a valuable tool. I&#8217;m not aware of any other tool that does what Deal Proof does. </p>
<p>It can help to catch some of the errors (e.g., cross-references and numbering) that tend to creep into a contract draft as it goes through the negotiation and editing processes. Since many lawyers don&#8217;t use automatic numbering, and few lawyers use automatic cross references, these kinds of errors are introduced all the time, and they are often overlooked in the haste to get a deal done. Deal Proof would catch many of them. </p>
<p>The other place where I think Deal Proof can add value is in reviewing a contract that was drafted by someone else. It doesn&#8217;t take the place of manual proofreading, but it can catch many of the little things that are easy to overlook when you&#8217;re trying to understand a lengthy contract you&#8217;ve never seen before. Something like inconsistent use of definitions can be hard to spot in a long document, and Deal Proof does a decent job of finding those kinds of errors. </p>
<p>The biggest problem I see with Deal Proof is not a problem with the software itself. It&#8217;s that it&#8217;s one more software tool that people have to take the time to learn and then take the time to use it routinely. In my experience, most lawyers are simply not going to spend the time to adopt another software tool, even if it would save them time in the long run. </p>
<p>You could give Deal Proof to an assistant and let them use if for a first pass at proofreading, but much of the value of the tool would be lost since someone will still have to make a judgment call on many of the issues Deal Proof will spot.  </p>
<p>I applaud Fred for using Deal Proof to help in improving the quality of his firm&#8217;s contracts, but I don&#8217;t think most lawyers will adopt anything like this until, like spell check, it&#8217;s completely integrated with word processing or a contract assembly tool.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

