<?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: Are Law-Firm Contract-Drafting Services a Commodity?</title>
	<atom:link href="http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/</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: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/comment-page-1/#comment-57396</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 05 Aug 2008 21:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/#comment-57396</guid>
		<description>Bart: Document assembly certainly does face other obstacles. I tried to limit this post to the point raised in Rees&#039;s post, which I think was limited to the issue of commoditization. My reference in the post to &quot;companies and law firms that otherwise would be good candidates for document assembly&quot; was my way of cryptically acknowledging that other factors come into play. I discuss those factors in the introduction to the second edition of my book. Ken</description>
		<content:encoded><![CDATA[<p>Bart: Document assembly certainly does face other obstacles. I tried to limit this post to the point raised in Rees&#8217;s post, which I think was limited to the issue of commoditization. My reference in the post to &#8220;companies and law firms that otherwise would be good candidates for document assembly&#8221; was my way of cryptically acknowledging that other factors come into play. I discuss those factors in the introduction to the second edition of my book. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bart Earle</title>
		<link>http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/comment-page-1/#comment-57392</link>
		<dc:creator>Bart Earle</dc:creator>
		<pubDate>Tue, 05 Aug 2008 19:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/#comment-57392</guid>
		<description>Less than optimal contract language is a barrier to implementing document assembly. Automating drafting requires that lawyers come face to face with the inadequacies in their existing forms. However, there are other formidable barriers, as well. These barriers, not shortcomings of technology, have been and continue to be the major impediment (we have had excellent techonology for many years).  At the top of the list I would put a lack of incentives for law firms to adopt document assembly. Lawyers are not facing the kind of pressure to change that would drive them to make the investment of time and money required. That&#039;s Rees&#039; point as well, I believe.</description>
		<content:encoded><![CDATA[<p>Less than optimal contract language is a barrier to implementing document assembly. Automating drafting requires that lawyers come face to face with the inadequacies in their existing forms. However, there are other formidable barriers, as well. These barriers, not shortcomings of technology, have been and continue to be the major impediment (we have had excellent techonology for many years).  At the top of the list I would put a lack of incentives for law firms to adopt document assembly. Lawyers are not facing the kind of pressure to change that would drive them to make the investment of time and money required. That&#8217;s Rees&#8217; point as well, I believe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art Markham</title>
		<link>http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/comment-page-1/#comment-57241</link>
		<dc:creator>Art Markham</dc:creator>
		<pubDate>Mon, 04 Aug 2008 09:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/#comment-57241</guid>
		<description>I also agree. Some contracts genuinely require no input other than the variables, and software that both reduces costs and produces safer and better drafted contracts is not hard to envisage. Given its non-prevalence, perhaps it is harder to execute than conceive.

In some areas where contracts are non-negotiated (e.g. contracts documenting repetitive intra-group financing in banks), in-house departments do already see contract drafting as commodotised, and expect (and receive) consistent, fixed fees to reflect it. However, there will always be some value on the working relationship and on the smoothness of service provided, so it is never entirely about cost. But I think this goes for any commodotised market to a greater or lesser degree, so law would not be unique in that regard.</description>
		<content:encoded><![CDATA[<p>I also agree. Some contracts genuinely require no input other than the variables, and software that both reduces costs and produces safer and better drafted contracts is not hard to envisage. Given its non-prevalence, perhaps it is harder to execute than conceive.</p>
<p>In some areas where contracts are non-negotiated (e.g. contracts documenting repetitive intra-group financing in banks), in-house departments do already see contract drafting as commodotised, and expect (and receive) consistent, fixed fees to reflect it. However, there will always be some value on the working relationship and on the smoothness of service provided, so it is never entirely about cost. But I think this goes for any commodotised market to a greater or lesser degree, so law would not be unique in that regard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terence Lee</title>
		<link>http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/comment-page-1/#comment-56922</link>
		<dc:creator>Terence Lee</dc:creator>
		<pubDate>Fri, 01 Aug 2008 18:42:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/#comment-56922</guid>
		<description>I agree with your argument. Document assembly should commoditize that which should be commoditized and allows attorneys to focus on that which should never be commoditized.</description>
		<content:encoded><![CDATA[<p>I agree with your argument. Document assembly should commoditize that which should be commoditized and allows attorneys to focus on that which should never be commoditized.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cheryl Stephens</title>
		<link>http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/comment-page-1/#comment-56818</link>
		<dc:creator>Cheryl Stephens</dc:creator>
		<pubDate>Fri, 01 Aug 2008 00:03:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/07/31/are-law-firm-contract-drafting-services-a-commodity/#comment-56818</guid>
		<description>I have been saying, for nearly 20 years, that you save time and money in converting to document assembly programs if you convert to plain language first. 

You can avoid having so many variables in document packages. You can simplify and make consistent the sentence structures. Simplify a document assembly by simplifying the documents themselves. 

Computerized plain-language precedent systems provide greater uniformity of service, confidence in the product and a greater sense of security.</description>
		<content:encoded><![CDATA[<p>I have been saying, for nearly 20 years, that you save time and money in converting to document assembly programs if you convert to plain language first. </p>
<p>You can avoid having so many variables in document packages. You can simplify and make consistent the sentence structures. Simplify a document assembly by simplifying the documents themselves. </p>
<p>Computerized plain-language precedent systems provide greater uniformity of service, confidence in the product and a greater sense of security.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

