Commentary

Andrew Conry Murray
 

Trial Lawyers: E-Discovery Too Expensive

Cases are being settled based on cost, not merit, according to results of a survey released today.

Cases are being settled based on cost, not merit, according to results of a survey released today.CIOs know that electronic discovery efforts are a financial drain. A new survey of trial lawyers shows that attorneys agree.

According to the survey (registration required), 85% of respondents believe the discovery process is too expensive. Seventy-five percent say electronic discovery is driving up overall discovery costs.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Eighty-three percent say litigation costs compel some cases to settle that could have been tried on merit. Almost 71% say that counsel uses discovery as a method to force a settlement.

Nearly 77% of trial lawyers also believe the courts don't realize how hard the e-discovery process is.

However, like countries armed with nuclear weapons, no one is ready to give up on e-discovery. More than half of the respondents say they had cases that raised e-discovery issues. Of those respondents, 86% agree that "the 2006 e-discovery amendments allow for efficient and cost-effective discovery of electronically stored information at least some of the time."

Also, trial lawyers aren't ready to overhaul the Federal Rules of Civil Procedure (FRCP), which provide the guidelines for e-discovery requirements. Only 35% agreed the rules needed to be reviewed and rewritten.

How to account for these contradictions? My guess is you could translate these results as "When e-discovery leads to an outcome that's good for me and my client, I'm all for it."

A total of 1,494 trial lawyers, all members of the American College of Trial Lawyers (ACTL), responded to the survey, which was conducted by the ACTL and the Institute for Advancement of the American Legal System at the University of Denver.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links