e-discovery 2.0

Recently, I attended the Sedona Conference’s annual meeting in Atlanta and, amongst other interesting topics, was the discussion of local rules developments and in particular the Seventh Circuit’s new Electronic Discovery Pilot Program (“Pilot Program”).  The Pilot Program was launched October 1, 2009 and seems to be a model for collaboration, since it was developed by eliciting input from a number of disparate groups:

“(a) continuing comments by business leaders and practicing attorneys, regarding the need for reform of the civil justice pretrial discovery process in the United States, (b) the release of the March 11, 2009 Final Report on the Joint Project of the American College of Trial Lawyers Task Force on Discovery (“Task Force”) and the Institute for the advancement of the American Legal System at the University of Denver (“IAALS”), and (c) The Sedona Conference® Cooperation Proclamation.”

The impetus of the Pilot Program was the “broken” nature of the electronic discovery process with the belief that better collaboration and cooperation would certain help remediate the situation.

“The goal of the Principles is to incentivize early and informal information exchange on commonly encountered issues relating to evidence preservation and discovery, paper and electronic, as required by Rule 26(f)(2). Too often these exchanges begin with unhelpful demands for the preservation of all data, which often are followed by exhaustive lists of types of storage devices. Such generic demands lead to generic objections that similarly fail to identify specific issues concerning evidence preservation and discovery that could productively be discussed and resolved early in the case by agreement or order of the court. As a result, the parties often fail to focus on identifying specific sources of evidence that are likely to be sought in discovery but that may be problematic or unduly burdensome or costly to preserve or produce.”

What I really like about the Pilot Program is that it strives to be both prescriptive and practical, which should hopefully avoid the type of ambiguity often exploited by obstreperous counsel.  For example, there is an entire section on early case assessment (ECA) principles, which require discussion of:

• Production issues
• Identification of electronically stored information (ESI)
• The scope of preservation
• The meet & confer process

There’s also the relatively novel requirement that counsel designate an e-discovery “liaison” to work with the parties to coordinate and flesh out germane e-discovery issues.  Regardless of whether the e-discovery liaison is an attorney, a third party consultant, or an employee of the party, the e-discovery liaison(s) must:

“(a) be prepared to participate in e-discovery dispute resolution;

(b) be knowledgeable about the party’s e-discovery efforts;

(c) be, or have reasonable access to those who are, familiar with the party’s electronic systems and capabilities in order to explain those systems and answer relevant questions; and

(d) be, or have reasonable access to those who are, knowledgeable about the technical aspects of e-discovery, including electronic document storage, organization, and format issues, and relevant information retrieval technology, including search methodology.”

Needless to say, this requirement alone should make marked improvements in the e-discovery dialogue, which unfortunately seems like it’s occurring (literally) among participants who both speak different languages and don’t realize it.

Finally, what makes the Pilot Program unique is that its Principles will be subjected to testing during the phases of the Pilot Program, which is scheduled to end on May 1, 2010 (for the first phase).

This project certainly seems like it’s on the right track and pending feedback from the bench and bar, it could serve as a model for local jurisdiction everywhere.

On of August 14, 2009, the California Judicial Counsel amended their Rules of Court to augment discussion of electronic discovery issues during the meet and confer process.

Rule of Court 3.724 was amended to require discussion of “Any issues relating to the discovery of electronically stored information” no later than 30 calendar days before the date set for the initial case management conference.  The broad language (i.e., “any”) was augmented by eight specific categories that must be expressly discussed:

(A) Issues relating to the preservation of discoverable electronically stored information;

(B) The form or forms in which information will be produced;

(C) The time within which the information will be produced;

(D) The scope of discovery of the information;

(E) The method for asserting or preserving claims of privilege or attorney work product, including whether such claims may be asserted after production;

(F) The method for asserting or preserving the confidentiality, privacy, trade secrets, or proprietary status of information relating to a party or person not a party to the civil proceedings;

(G) How the cost of production of electronically stored information is to be allocated among the parties;

(H) Any other issues relating to the discovery of electronically stored information, including developing a proposed plan relating to the discovery of the information;

Many of these issues track FRCP language (including forms of production, preservation, privilege issues, etc.).  However, section G seems somewhat novel given the historical “American Rule” where the producing party is required to bear all necessary costs of production.

Curiously missing, in comparison with FRCP 26 B(2)(b), is the need to discuss the handling of “inaccessible” ESI, although this could easily be subsumed in the “any other issues” language of section H.  Also missing is a discussion about proposed searching and/culling protocols (aka “keyword negotiations”) which are often part of the core meet and confer topics in Federal court.

Nevertheless, the scope is broad enough to require *a* discussion of all likely relevant electronic discovery issues, which was often lacking historically.  Once that discussion starts, reasonably savvy counsel should be able to flesh out most of the significant issues.  And, given this broad language a judge would presumably give them a hard time for any material omissions.

David Isom and I have collaborated a number of times over the years on a variety of electronic discovery presentations and articles.  So, when I saw that California was proposing new state electronic discovery rules that had some interesting variances vis-à-vis the FRCP, I thought David might be able to give us the benefit of his unique and sage perspective.

1. David, as the author of the definitive piece about inaccessibility under the Federal Rules of Civil Procedure (The Burden of Discovering Inaccessible Electronically Stored Information: Rules 26(b)(2)(B)& 45(d)(1)(D)), how many litigators do you think really understand and use these provisions?

I sense that litigators with a basic understanding of the new electronic discovery rules know that the inaccessibility rule exists and provides some protection for parties against unduly burdensome discovery.  Few seem to have noticed that Rule 45 contains an inaccessibility provision whose language is similar to the Rule 26(b)(2)(B) inaccessibility protection for parties, but whose protections as applied to subpoenaed nonparties are greater than the protections for parties.  Here are the three most basic and exciting (or excruciating, depending upon your side of the fence) impacts of the new inaccessibility rules:

(1) The inaccessibility rule has completely changed a nonparty’s leverage to narrow subpoenas seeking electronically stored information (ESI).  Subpoenaed nonparties now have protection against fishing expedition subpoenas that did not exist before — to narrow subpoenas, or to require the payment of costs and attorney fees in responding to broad subpoenas.

(2) Cost-shifting, for parties as well as nonparties, is now controlled by the inaccessibility rules.  Several federal courts have recently held that discovery cost-shifting is allowed only if these inaccessibility rules provide for cost-shifting under the circumstances.

(3)  The inaccessibility rules must be asserted and asserted timely if they are to provide protection.  For example, after counsel for nonparty Office of Federal Housing Enterprise Oversight spent $6 million of our money responding to a subpoena in In re Fannie Mae Securities Litigation, 552 F. 3d 814 (D.C. Cir. 2009), counsel tried to recover the money on an inaccessibility cost-shifting argument.  To which the United States District Court and the Court of Appeals for the District of Columbia said, in essence:  you might have had a good idea, and saved your client $6 million, had you raised the arguments before agreeing to produce the documents and spending all that money.  But you agreed to produce the ESI and cannot come back now and get any protection.  You should have studied the inaccessibility rule.

2. So, assuming we’re still early in the learning curve, do you think these FRCP provisions are really gaining traction either in practice or in the case law?

Judging by the number of reported decisions, the inaccessibility rules are receiving as much attention as the other new features of the federal electronic discovery rules.  Which, I suppose, is damnation by faint praise — a large percentage of the reported cases are about what should happen because lawyers didn’t understand or apply the rules properly. Cason-Merenda v. Detroit Medical Center, 2008 U.S. Dist. LEXIS 51962 (E.D. Mich. July 7, 2008) is a good example.  There, defendant’s counsel produced ESI without any objection and without pre-identifying the ESI as inaccessible.  After production, counsel tried to get their opponents to share the cost of producing the allegedly inaccessible ESI.  The court correctly held that the ESI must be identified as inaccessible in advance of the production to give the seeking party the option to decide whether the discovery is really worth the candle, especially given the prospect that the cost of production might be shifted to the seeking party.

3. What are your thoughts on the new California state provisions regarding “inaccessible” ESI where they’re proposing a different treatment and slightly different burden?  And, will this approach ultimately weaken responding parties abilities to make “inaccessible” claims successfully?

I am not an expert on California law, but am keenly interested in what the states are doing with electronic discovery.  As of this writing (May 2009), it appears that California Assembly Bill No. 5 has not yet been enacted.  Yet, here are some thoughts about how the inaccessibility provisions of this bill, if enacted, would compare to the federal rules of inaccessibility.  The bottom line is that the California bill is remarkably similar to the federal rules on inaccessibility issues.

Under the federal rules, a party seeking protection for inaccessibility initiates the process by “simply” (so far, the courts have tolerated fairly sparse identifications as satisfying this requirement) identifying the sources of information claimed to be not reasonably accessible because of undue burden or cost.  The subpoenaed nonparty seeking protecting can initiate by identifying the ESI sought as not reasonably accessible in an objection, motion to quash or motion for protective order.  In the federal system, either the seeking party or the protecting party or nonparty can move to test the issue (one by a motion to compel, the other by a motion for protective order).

The California bill is nearly identical to the federal process.  The bill provides that a person resisting a subpoena for ESI on inaccessibility grounds may “oppose” the subpoena.  If this means that such a person can either object or move to quash or move for a protective order, it appears to be the same as the federal rule.  The California bill specifies that a party resisting a production request on inaccessibility grounds initiates protection by identifying the types or categories of sources of electronically stored information that it asserts are not reasonably accessible.  This is similar to the federal rule, whose text requires identification of “sources”, but whose committee notes clarify that merely “types or categories of sources” of inaccessible, responsive ESI need be identified.  The California’s Legislative Counsel’s Digest indicates that the process for protecting inaccessible ESI, apparently for both parties and subpoenaed nonparties, can be initiated by moving for a protective order, or by opposing or objecting to the subpoena or request.

Even if there are any distinctions in the above processes, the two processes appear to merge thereafter.  In both systems, the motions to test inaccessibility must be preceded by a conference of counsel to attempt in good faith to resolve the issue, together with a certificate that such an attempt has been made.  In both, the person seeking protection has the burden of proving inaccessibility (this is even true in the federal system where the process is initiated by the seeker’s motion to compel).  In both systems, if the holding party proves inaccessibility, the burden shifts to the seeking party to show good cause for producing the ESI, despite its inaccessibility.

And in both, if good cause is shown, the court may still impose conditions upon production, including cost-shifting.  In both, the factors that the courts are to consider in determining good cause are similar — more accessible, less burdensome sources; cumulativeness of the discovery; whether the burden or expense of the discovery would outweigh the likely benefit of the discovery, considering such things as the importance of the issues, the amount in controversy and the resources of the parties.  One possible difference between the California bill and the federal rules on good cause is that the California bill requires the court to limit discovery if any of the listed factors exists, where the federal rules and committee notes seem to envision a pure balancing.

In sum, the California bill essentially adopts the federal approach.

Some confusion has arisen because California commentators have drawn a distinction between the California bill and a misinterpretation of the federal rules.  One commentator, for example, stated that “under the federal rules, if ESI is inaccessible, the responding party simply doesn’t need to produce such documents.”  This ignores the affirmative identification duty that I discussed above.

4. With the rapid advancements in ESI restoration technologies, which the Comments to the Rule anticipated, are backup tapes in your mind still “inaccessible”?

The rules make it clear that inaccessibility cannot be measured by technology category alone.  The test does not depend upon the type of technology involved, but upon the balancing of need, technology, importance, spoliation, relevance, alternative sources and potential benefit against overbreadth, burden and cost.  So, if backup tapes are the only source available for important, relevant information because more accessible relevant sources have been spoliated, backup tapes will not be deemed inaccessible.  Without spoliation, if relevant ESI is available on active sources, backup tapes may not be discoverable.

Perhaps the main reason that categories of technology cannot be deemed per se accessible or inaccessible is that the technology is changing so fast.  Many search tasks that were expensive and difficult five years ago are much more doable now.

5. Finally, what do you think the future holds for these FRCP sections?

The inaccessibility rules will continue to be the main battleground where the great debates about the value and cost of electronic discovery will be fought, since these rules are specifically tailored to balance all of the interests in that debate.

Some groups are claiming that electronic discovery is wasteful and expensive, and that the new rules exacerbate the problem.  Of course, the federal rules ought always to be analyzed for problems and need for improvement, but I haven’t heard informed, thoughtful, helpful suggestions for improvements to the federal rules in the recent debate.  Overall, I see the adoption of the federal rules as having helped reduce the cost of electronic discovery, not increased the cost.

There’s a lot of excitement (and corresponding uncertainty) about the recent passing of Federal Rule of Evidence 502 (FRE 502), which was signed into law on Sept 19th.  The main reason that the legal community is excited about FRE 502 is because of the potential for cost savings by reducing the amount of money associated with the e-discovery review process, which is routinely viewed as the most expensive area in the entire e-discovery process.

In combination with the codification of a national standard to determine when a privilege has been waived, FRE 502 is primarily designed to make the use of claw-back agreements a truly viable prospect when doing e-discovery privilege review.  It should provide some panacea (ideally) for rapidly escalating e-discovery costs.  Or, at least that was the impetus behind the rule’s creation – according to the Comments:

“The proposed new rule facilitates discovery and reduces privilege-review costs by limiting the circumstances under which the privilege or protection is forfeited, which may happen if the privileged or protected information or material is produced in discovery. The burden and cost of steps to preserve the privileged status of attorney-client information and trial preparation materials can be enormous. Under present practices, lawyers and firms must thoroughly review everything in a client’s possession before responding to discovery requests. Otherwise they risk waiving the privileged status not only of the individual item disclosed but of all other items dealing with the same subject matter. This burden is particularly onerous when the discovery consists of massive amounts of electronically stored information.”

In short, FRE 502 is designed to establish uniform, nationwide standards for waiver of attorney-client privilege and work product protection, with the main goal being to protect producing parties against the inadvertent disclosure of privileged materials or work product in either federal or state proceedings.  The salient section is subsection (b) which states that when a disclosure of privileged information is made in a federal proceeding or to a federal agency, the disclosure does not constitute a waiver if:

1. the disclosure is inadvertent;
2. the holder of the privilege or protection took reasonable steps to prevent disclosure; and
3. the holder promptly took reasonable steps to rectify the error, including (if applicable) following Federal Rule of Civil Procedure 26(b)(5)(B).

The end game here is presumably to increasingly leverage automated review methodologies to save costs.  But, in order to facilitate this type of review methodology without taking on unhealthy levels of risk means that claw-back provisions must be as airtight at possible to prevent inadvertent electronically stored information (ESI) productions.  And yet, exactly how FRE 502 will work in practice is up to debate since there isn’t any case law interpreting it yet.

One area that’s top of mind is how this new Rule will impact the recent decisions on e-discovery search, including the Victor Stanley case authored by Chief Magistrate Judge Grimm.  Since FRE 502 contains a core “reasonableness” prong in section (b) it’s likely that Grimm’s proclamation about e-discovery search will still be controlling.  Grimm fundamentally had to evaluate whether the producing party’s search protocols and procedures were in fact reasonable.

“Defendants, who bear the burden of proving that their conduct was reasonable for purposes of assessing whether they waived attorney-client privilege by producing the 165 documents to the Plaintiff, have failed to provide the court with information regarding: the keywords used; the rationale for their selection; the qualifications of M. Pappas and his attorneys to design an effective and reliable search and information retrieval method; whether the search was a simple keyword search, or a more sophisticated one, such as one employing Boolean proximity operators; or whether they analyzed the results of the search to assess its reliability, appropriateness for the task, and the quality of its implementation.” (footnotes omitted).

In Victor Stanley, the producing party wasn’t able to demonstrate reasonableness because they didn’t strategically craft out their strategy nor conduct any sampling to make sure that the e-discovery search worked as designed.  This type of analysis would still seem to come into play under FRE 502 and so, as Grimm states, the use of either a best practices or collaborative approach to e-discovery would seem to be as important as ever.

Given that backdrop it’s just as important as ever that parties “show their work” when it comes to e-discovery search.   Whether FRE 502 will really make parties feel safe enough to use automated review processes (thereby reducing costs) will remain to be seen.  But, this first step which unifies standards and expectations is at least a very positive step.

There have been several recent press releases from enterprise software companies proclaiming FRCP “compliance,” which certainly sounds appealing.  But, the use of that term begs the question:  how does a litigation support software search technology (or methodology) become FRCP “compliant” and is that goal even possible?

IBM launched the first salvo:

“The software will allow companies to move from scattered, point-solution approaches to a disciplined approach that controls electronic information, helps support Federal Rules of Civil Procedure (FRCP) compliance,…”

And, Autonomy quickly followed suit:

“The Autonomy pan-enterprise search platform automates the retrieval, processing, and management of all information throughout a global organization irrespective of languages, operating systems, and file types, avoiding non-FRCP compliant search techniques.”

I’m more than tolerant of both puffery and marketing-speak (though woe to those who forward such releases to Monica Bay), but this notion of “FRCP compliance” seems to take advantage of an already bombarded buying public, who have likely grown weary of FRCP articles, CLEs, and maybe even blogs posts.  Nevertheless, it seems useful to really tease out what the FRCP means and does not mean in relationship to e-discovery and enterprise search.

So, in an attempt to debunk this “compliance” myth, I thought I’d devote this blog post to demystifying some of the inaccurate notions about the FRCP.

Federal First

Initially, it’s important to note that the Rules only apply to litigation within the United States Federal court system.  State court litigation, international lawsuits, arbitrations and administrative actions (just to name a few) aren’t under the aegis of the Rules.  While it’s true that certain state courts (Minnesota for example) have selectively adopted the new discovery provisions, most have not.  So, the first step is to check your venue.  Then, assuming the Rules do apply because your organization is in Federal litigation, the impact, while still not crystal clear, does take on more definition.

Relevancy Filters

As a starting place, the discovery process (as part of litigation) is fundamentally limited by Rule 26 to information (electronic and otherwise) that is “relevant” to the case at hand (i.e., “relevant to the claim or defense of any party”).  This distinction is critical because for the most part it prevents the responding party from having to cast a company wide net for all data, a task envisioned by many content management systems.   Certainly, the ability of certain litigation support software systems to access all user created data is valuable when searching for relevant data, but there are many ways to skin that cat.

No Express Retention or Preservation Duties

Legions of articles proclaim that the amended Rules create wholly new duties to retain information in general, as well as infusing new duties to preserve electronic data once litigation is anticipated.  Instead however, the new Rules expressly disavow creating truly new retention or preservation duties.  While it is undoubtedly a good practice to have a retention policy, given the welter of statutes and regulations that do create retention duties, the Rules do not mandate that a company create one ahead of litigation.

What is true, however, is that the new Rules have powerful implications for preservation once litigation is likely because of the requirements to understand, negotiate and produce relevant information early in the litigation process.  Under the new Rules, it is critical to be able to identify and retain potentially relevant data once litigation is filed (or is “reasonably likely”).  And yet, the burden of placing a legal “hold” on data, while often significant, certainly can be achieved without a formal document retention/deletion policy.  Again, the litigation “trigger” is key.

“Records” Aren’t the Focus

Continuing on this theme, but in a slightly different vector, there are differing opinions about the impact that the Rules have on “business records.”  This issue is nebulous since during litigation discovery, it is easy to confuse potentially relevant data corresponding to litigation with “business records,” which are often used in two different contexts.  Initially, there is the “business records” exception to the hearsay rule, which is quite specific and affects the admissibility of evidence in court.

The second, broader definition applies to organizations as they attempt to define a records management program to meet the numerous state, local and Federal mandates.  Commonly, as part of this complex initiative, companies will create records retention programs that specifically define official “records,” unofficial “records,” “non-records,” as well as specific retention periods for certain types of records.  Once the company’s records protocol is put into place there may be some downstream nexus with the Rules, but it won’t manifest itself until Federal court litigation arises, as described above.   The most common intersection occurs when a records retention policy prescribes a deletion event that contradicts the legal “hold” requirements for a record that is likely to be relevant to litigation.

In sum, the foregoing describes the role the FRCP plays in Federal court litigation.  It should be clear that the important, yet relatively narrow, use cases do not include any general compliance mandate in the absence of specific litigation.  I think it’s important to separate myth from reality when it comes to understanding how and when the revised Rules really do come into play.  Failure to do so can create an unpleasant scenario where your organization will either under- or over-prepare for these important litigation guidelines.