ADVERTISEMENT



Google       

Home -> Law Blog Directory -> Corporate & Securities Law Blogs -> AdamsDrafting

OR PHONE (866) 635-1838 for Bankruptcy Help, (866) 635-6190 for Divorce,
(866) 635-2689 for Personal Injury or (866) 635-9402 for Criminal Defense

Find a Local Lawyer

Bankruptcy (866) 635-1838
Divorce (866) 635-6190
Personal Injury (866) 635-2689
Criminal Defense (866) 635-9402

Bookmark

Corporate & Securities Law

: AdamsDrafting

Why No Contract-Process Value Challenge?

By Ken Adams

ADVERTISEMENTS

Legal OnRamp, the online forum for in-house counsel and invited outside lawyers and vendors, has announced the “FMC Technologies 1 Law Litigation Value Challenge.” It’s a beauty contest for law firms interested in doing FMC’s litigation work.

I suppose what distinguishes it from the run-of-the-mill beauty contest is that Legal OnRamp represents a particulary public platform. And for all I know, the three stages involved-public online, private online, in-person meetings-might also differ from the way such things are normally handled.

Jeffrey Carr, general counsel of FMC Technologies, is an advocate for change in how law departments operate and how they obtain the services of outside counsel. The Litigation Value Challenge evidently represents a push toward, in Carr’s words, “a more transparent, value-driven legal marketplace.”

But on reading about this, what crossed my one-track mind was, Why no Contract-Process Value Challenge? I can’t imagine that anyone would argue that the contract process isn’t essential to companies, as well as a significant drain on resources. And unlike litigation, it’s pretty much a fact of life at all big companies.

The simplest answer is that companies generally don’t farm out to law firms much work related to their sales or procurement contract process. When they outsource that work, it tends to be to high-volume, low-intricacy shops offshore, as I described in this NYLJ article.

Conceivably, for each forward-thinking litigation-related initiative such as FMC’s, there’s a company somewhere bringing to bear an internal initiative geared at assessing how it might improve its contract process. That seems unlikely, for the simple fact that it’s easier to scrutinize outsiders than to critique your own work. (That’s something I discuss in this recent NYLJ article on retooling your contract process.)

And the objective evidence would seem to back me up. The number of companies engaged in rigorous contract-automation is still a small fraction of those who would benefit from it. And very few companies seem to be giving their contract language close scrutiny.

Given that the contract-process isn’t conducive to beauty contests, I offer, to FMC Technologies and any other substantial company, an only-half-facetious challenge of my own, the AdamsDrafting Contract-Process Value Challenge. Are you confident that your contracts aren’t, in the words of a recent Dilbert cartoon, impenetrable gibberish? Send one of them to me-odds are that I’d be able to show you how to make it much shorter and vastly clearer. Are you eager to even out the kinks in your contract process? I can introduce you to the brave new world of contract automation.

Full post as published by AdamsDrafting on May 14, 2009 (boomark / email).

Bloggers, promote your law blog by nominating your blog for inclusion in USLaw.com's Law Blog Directory and RSS Reader. Benefits described.
Related Law Articles

Lawsuits and Settlements

Related Searches

























































































































US Law
#1 Online Legal Resource













Your Blog Subscriptions
Subscribe to blogs

10,000+ Law Job Listings
Lawyer . Police . Paralegal . Etc
Earn a law-related degree
Are you the author of this blog? Adding USLaw.com to your Blogroll increases relevance. You qualify to display a USLaw Network badge.
Suggest changes to this blog's description or nominate another for inclusion. Register for updates.


Practice Area
Zip Code:

Contact a Lawyer Now!






0.0164 secs (new cache)