e-discovery 2.0

Much of the business and personal productivity that comes in the digital world  is from email and its unique abilities. Email allows us to communicate in a way that helps us associate context to our discussions, namely in its ability to be chained into a sequential thread when email users reply to or forward emails they previously received. This accomplishes two important tasks: 1) it allows the person sending the reply or forward to get an understanding of the issues so he/she can craft a meaningful response, and 2) it allows the person receiving the response to understand that response in the context of other on-going discussions. Email programs such as Microsoft Outlook, Eudora, and Gmail help by automatically including content from prior emails, thus producing a long chain of reference.

It is no coincidence that emails thus constitute key evidentiary value in the context of litigation. The inherent value captured in emails is what makes email productions central to pre-trial disclosures and the electronic discovery that precedes it. Courts have long recognized that emails are a business record and subject to discovery. Establishing who said what in the context of a matter in dispute is greatly facilitated by examining the thread of emails recorded in email repositories. With respect to electronic discovery, however, email threading presents several unique challenges. The area of greatest confusion and uncertainty has been the determination of privilege when emails are exchanged with in-house counsel and attorneys and whether such emails are protected by attorney-client privilege or not. A central issue is the composition of privilege logs under these circumstances.

There are several legal opinions on the matter of intermingling privileged and non-privileged communications in an email chain. These opinions have left the matter with little clarity, especially regarding whether the entire email thread is privileged or whether individual emails must be separated out and classified as privileged, with a privilege log listing them. Typically, the most recent email in a thread contains all other emails in that thread. Separating out individual emails (i.e., the contained emails) from the containing email would allow for treatment of just the portions of the email thread that may have privilege. When such separation is permitted, some contained emails may be assessed as privileged while others may not. However, it is entirely possible that the contained email is also present as an independent email under possession of the same custodian or another custodian. When it is present, one could argue that the contained email can just be ignored, and if the corresponding email is responsive, one can ignore the contained email. But rarely does a collection include a complete set of custodians, so the question of whether the privilege log should include the contained item in question still remains. In terms of management of review, and for constructing a privilege log, treating the most recent email and all its contained emails as a single entity is less expensive and cleaner than separating and determining privilege status of each contained email.

Another complicating factor is simply a determination of privilege. Does the mere fact that an attorney was listed as a courtesy CC recipient make the entire email privileged? And, when such emails are then forwarded only to an attorney involved in the case, with a legal strategy discussed in the containing email, is only the new content added to the containing email privileged, or does the privilege determination extend to the other contained emails?  Let’s examine a few opinions for guidance.

With respect to privilege there is a significant body of opinions that would suggest that only communications that explicitly seek legal advice are privileged.

“With respect to internal communications involving in-house counsel, a party “must make a ‘clear showing’ that the ‘speaker’ made the communications for the express purpose of obtaining or providing legal advice”, Chevron Texaco Corp., 241 F. supp 2d) at 1076 (quoting In Re Sealed Case, 737 F.2d 94 (D.C. Cir. 1984)). If the legal and business advice are inextricably intertwined, “the legal advice must predominate over the business advice, and not be merely incidental, for the communications to be protected under attorney client privilege.” Evidently, attempts to include an incidental attorney in a thread would not offer privilege protections. However, the issue is complicated if the most recent containing email is indeed a genuine attempt to seek such guidance. Here again, there are two opinions. In United States v. Chevron Texaco Corp., 241 F. supp. 2d 1065, 1074 n.6 (N.D. Cal. 2002), we note that:

“With respect to each series of emails for which Chevron asserts protection under privilege, Chevron breaks the series into each discrete message. In our view, such a representation of the document is misleading. Each email/communication consists of the text of the sender’s message as well as all of the prior emails attached to it. Therefore, Chevron’s assertion that each separate email stands as an independent communication is inaccurate.”The above would have you prepare a single entity with the most recent containing email and all other quoted emails treated as a single unit. On the other hand, we see the opposite opinion in Universal Service Fund Telephone Billing Practices Litigation, 232 F.R.D. 669, 674 (D. Kan. 2005) where “the court strongly encourages counsel, in the preparation of future privilege logs, to list each email within a strand as a separate entry”. In a related ruling, the court notes: “Obviously, a sufficient (i.e., reasonably detailed) privilege log is vital if litigants and judges are to determine whether documents have been properly withheld from discovery.” As mentioned earlier, this can be much more expensive from a review and production standpoint.

In Chemtech Royalty Assoc., L.P. v. United States, Nos. 05-cv-00944, 06-cv-00258, 07-cv-00405, at (M.D. La. Mar. 30, 2009), we get another perspective: “Asserting privilege for an entire email thread in the privilege log, but only describing the last message in the thread is deficient.”

In Baxter Healthcare Corp. v. Fresenius Med. Care Holding, Inc., No. 07-cv-01359, 2008 BL 229777 at (N.D. Cal. Oct 10, 2008), the defendants are ordered to produce a privilege log that “separately identifies the author, recipient(s), copyee(s), and blind carbon copyee(s) for each logged email communication regardless of whether the communication is part of an email string”. The court directive is: “Each email is a separate communication, for which a privilege may or may not be applicable. Defendants cannot justify aggregating authors and recipients for all emails in a string and then claiming privilege for the aggregated emails.”

Thus, the contained emails must be treated as separate privilege log entries.

In Vioxx Products Liability Litigation, 501 F. Supp. 2d 789, 812 (E.D. La 2007) the court notes:

“Email threads in which attorneys are ultimately involved were usually listed on the privilege log as one message.”  Further, “Simply because technology has made it possible to physically link these separate communications (which in the past would have been separate memoranda) does not justify treating them as one communication and denying party a fair opportunity to evaluate privilege claims raised by the producing party.”

Again, the preference has been to separate out individual contained emails as independent emails with corresponding privilege log.

In C.T.  v.  Liberal School District, Nos. 06-cv-02093, 06-cv-02360, 06-cv-02359, 2007 BL 21826 at (D. Kan. May 24, 2007), the court orders the plaintiff to submit an amended privilege log that listed email in a string as a separate entry.

In Se. Pa. Transport Authority v. Caremark PCS Health, L.P., 254 F.R.D., 253, 264-65 (E.D., Pa 2008) court recommends “analyzing emails in chain separately to rule on defendant’s privilege claims”.

Another significant opinion is found in Muro v. Target Corp., 250 F.R.D. 350 (N.D. Ill. 2007). In addition to at least four motions, an in camera review  was requested for identifying the privilege status of eighty nine documents. Here, the court ruled that FRCP Rule 26(b)(5)(A)  does not require that all contained emails be separated out. However, the court sustains Target’s objection to the Magistrate Judge’s ruling that its privilege log was inadequate for failure to separately itemize each individual email quoted in an email string. In Muro, though, you are allowed to treat an entire email as a single entity only if the non-privileged communications in that chain are otherwise disclosed. Hence, if you wish to treat an email as a single unit, you are required to either disclose the individual contained emails from other custodians, or to list them as Derived Emails (see below).

Another important case is the Rhoads Industries Inc. v. Building Materials Corp. of America et al 2008, WL 5082993 (E.D. Pa Nov. 26, 2008), where the court rendered the opposite opinion:

“Each version of an email string (i.e., a forward or reply of a previous email message) must be considered a separate, unique document, and therefore each message of the string which is privileged must be separately logged in order to claim privilege in that particular document.”

Of course, the context of the Rhoades opinion is the statement: “In the world of electronic communications, a series of email messages, among people employed by the client, but working in different locations, can replace the meeting with an attorney and subsequent letter.” However, this opinion is very debatable.

An entirely different approach is suggested in Apsley v. Boeing Co., No. 05-cv-01368, 2008 BL 12035 at (D. Kan. Jan 22, 2008), with the opinion “Although Boeing listed on its privilege log entire email strings, it redacted only the portion of the string that contained legal communications.” While this seems to be a perfectly reasonable approach, wouldn’t this compromise case strategy since the very fact that certain portions of the non-privileged, unredacted emails were being exchanged with in-house counsel and is therefore part of an attorney communication can be damaging?

Suffice it to say, the courts differ in their opinions on how to handle email threads and their privileged logs. It is in this context that the Clearwell E-Discovery Platform’s treatment of email threads is extremely helpful for preparing your litigation response. In fact, Clearwell has received two patents related to email threading, one for constructing email threads and its ranking and another for determining derived emails from other containing emails and de-duplication in the context of original emails. Clearwell has advanced email meta-data and content analytics to piece together all emails of a thread. Furthermore, its Derived Email feature separates out contained emails as complete emails, which are then de-duplicated against other emails that are not derived from a contained email. In situations where such a duplicate is not identified, the derived email is maintained in a special state. Also, the containing email’s thread is separated out in such a way that each individual email’s privilege status can be determined. One can apply either a single- or multiple-record policy satisfying whatever the prevailing opinion is from the bench. Also, Clearwell’s redaction capabilities and its ability to produce the same set of documents for multiple parties allow the case team to provide a quick turnaround if there is a motion to produce either a privilege log or the non-privileged snippets of emails. Such technology can be a lifesaver when it comes to meeting electronic discovery obligations.

Yesterday, Marsh & McLennan (M&M) announced the sale of Kroll, its investigative services division which last year generated $678 million in revenue. Kroll is being acquired by Altegrity, another investigative services company which is owned by Providence Equity. The acquisition price is $1.13 billion, below the $1.3 billion M&M was rumored to be asking, and the deal is financed by Apollo Investment Services and Goldman Sachs.

There are many aspects to this transaction, but I want to focus on just one: what does this mean for Kroll Ontrack, Kroll’s largest division with $250 million in revenue and a staggering 1,500 employees, making it by far the world’s largest e-discovery service provider?

To answer this question, I will first outline the strategic challenge facing Kroll Ontrack, before outlining two alternative strategies its new owners may adopt for addressing it.

Strategic Challenge: Kroll Ontrack Is The “Yahoo! Of E-Discovery”

Just as Yahoo was an internet pioneer in the 1990s, Kroll Ontrack was the pioneer of electronic discovery services. Like all pioneers, as the first to market, Kroll had to build everything itself. So Kroll Ontrack invested not only in recruiting and training its staff of skilled consultants, the company also developed its own suite of e-discovery tools and software. It offered this integrated package of services and software to the market and, justifiably, charged a price premium.

But as the industry matured, it disaggregated with more savvy customers and new companies focused on specific parts of the value chain. Customers became better educated and more confident making decisions, diminishing the value of Kroll’s “we-are-the-safe-choice” value proposition. These customers today have many more options for e-discovery than was the case in years gone by, primarily because of a generation of e-discovery software companies, such as Clearwell, Guidance, Exterro, and kCura/Relativity, which offer capabilities like collection, ECA (Early Case Assessment), litigation hold management, and linear review. These have been widely adopted by Kroll Ontrack’s competitors, negating Kroll’s technological advantage. Even worse, because Kroll Ontrack’s competitors do not need to invest in R&D, they have a substantially lower cost structure. As a result, they have undercut Kroll Ontrack on price, which has halted its growth and squeezed its margins.

In a directly analogous way, Yahoo! has seen its broad internet service to consumers eroded by a host of more focused competitors such as Google, Facebook, and Skype. Consumers today are much more familiar with the internet, and feel comfortable making separate choices for search, social networking, and messaging, without the need for an umbrella brand. That has left Yahoo! without a reason for being: even today, its CEO struggles to answer the fundamental question “what is Yahoo!?”

Solution: Sell It Or Fix It

As Kroll Ontrack’s new owner, Altegrity has a simple choice. It could sell Kroll Ontrack, making the strategic challenge someone else’s problem; or Altegrity could fix it, by adopting a fundamentally different strategy.

Let’s consider each in turn:

Sell It: Most sensible people would find it funny to think about selling something right after you bought it. But in this case, it could make a lot of sense. Altegrity is a leading provider of investigative services, not e-discovery, making the “non-Ontrack” part of Kroll’s business a much better fit. So why not sell Kroll Ontrack, pay down debt, and focus on the services business which it understands? This would be especially attractive if, as Vivian Tero at IDC suggests, there are willing buyers such as ECM or storage software companies which like Kroll Ontrack but do not want the services business.

Fix It: Mike Cherkasky, Altegrity’s CEO, is a former head of Kroll, and so is perhaps uniquely well placed to bring about a change in direction. To do so, he must decide what Kroll Ontrack wants to be. If its goal is to be the leading e-discovery service provider, then it should kill its internal software development efforts and focus on providing customers the absolute best service using industry leading tools. If it wants to be an e-discovery software company, which would be a much harder transition, then it needs to exit the services business and make its technology available every litigation support company.

Either way, it will take time and a lot of painful decisions for Kroll Ontrack to recover its momentum. But if any encouragement is needed, the Altegrity and the Kroll Ontrack teams need only look at what’s happening to Fios, another of the industry’s early pioneers. So far, Fios has refused to decide what it wants to be, abandoning its internal review platform for Relativity but keeping its proprietary processing software. The result? It’s had three different CEOs in the past 12 months, and competitors continue to steal market share.

Jason R. Baron was a keynote speaker at a recent electronic discovery summit and he mentioned an electronic data discovery topic that “ought to be blogged about.”  So, with that kind of softball I had to take a swing, particularly because it’s been a topic we (at e-discovery 2.0) have been discussing lately.

The genesis of this blog (per Jason) is the recent “skepticism” evidenced by the bench regarding the defensibility of custodian based collections.  ARMA has a good piece on this very topic, entitled “Is ‘Manual’ Collection of ESI Defensible?”  The core notion is that the tried and true practice of custodian based ESI collection is now under fire by courts, which appear to be looking at this practice with an increasing level of distrust.

“While it is common for companies to use automated data-collection software and hardware, some corporate litigants opt for more informal, “manual” collection methods (i.e., searches performed by individual records custodians) when responding to ESI requests. Companies may choose the manual collection of ESI to reduce costs, particularly if they have limited levels of litigation or lower risk levels posed by the litigation itself.”

While there’s no dispute that the “automated” collection methods available in litigation software referenced above have a number of features that make this approach more efficient, the question is whether a “manual” (i.e., custodian based) collection process is somehow less defensible.  If this is truly the case, then many midsized companies without the budget to purchase such e-discovery applications will inherently be found deficient – which is a daunting notion.

Take the recent case of Ford Motor Co. v. Edgewood Properties Inc., 257 F.R.D. 418 (D.N.J. 2009) where the dispute arose out of the demolition of a Ford assembly plant in New Jersey.  Ford and Edgewood entered into a contract whereby Ford agreed to provide 50,000 cubic yards of concrete to Edgewood in exchange for Edgewood removing it from the site.  When the concrete turned out to be contaminated, the dispute started in earnest.

The crux of Edgewood’s complaint was that it was unhappy with Ford’s production and somehow suspected that the dearth of documents was due to the electronic data collection process.  Edgewood sought to “’confirm the adequacy of Ford’s manual document collection process’ by using a third-party vendor to perform keyword searches on documents not in the existing repository of ESI, but instead, documents within the possession of certain Ford custodians.”

To reconcile the dispute the court looked to the Sedona Conference’s work in the area:

“In The Sedona Conference Best Practices Commentary on the Use of Search and Information Retrieval Methods in E-Discovery, Practice Point 1 states that “[i]n many settings involving electronically stored information, reliance solely on a manual search process for the purpose of finding responsive documents may be infeasible or unwarranted. In such cases, the use of automated search methods should be viewed as reasonable, valuable, and even necessary.”(emphasis added). Once again, the Court confronts this peculiar situation insofar as Edgewood has a point that the document collection method used by Ford is not necessarily contemplated under the Sedona Principles, but that agreement by the parties at the outset as to the mode of collection would have been the proper and efficacious course of action.  However, “[a]bsen[t] agreement, a [responding] party has the presumption, under Sedona Principle 6, that it is in the best position to choose an appropriate method of searching and culling data.”

Accordingly, the court found that the lack of agreement coupled with Ford being in the best position to make a call about the methodology, was a deciding factor in generally upholding Ford’s manual collection process.

“It would be improvident at this juncture to grant Edgewood the relief it seeks when it has not shown any indicia of bad faith on the part of Ford. To countenance such a holding would unreasonably put the shoe on the other foot and require a producing party to go to herculean and costly lengths (especially in a document-heavy case such as this) in the face of mere accusation to rebut a claim of withholding. This scenario is not contemplated by the Federal Rules.”

While Ford wasn’t penalized for its manual collection, this practice has come under fire in several other opinions.  In the highly controversial case of Phillip M. Adams & Assoc., LLC v. Dell, Inc., 621 F. Supp. 2d 1173 (D. Utah 2009) custodian based collection/preservation policies were similarly under fire.

“ASUS’ practices invite the abuse of rights of others, because the practices tend toward loss of data. The practices place operations-level employees in the position of deciding what information is relevant to the enterprise and its data retention needs. ASUS alone bears responsibility for the absence of evidence it would be expected to possess. While Adams has not shown ASUS mounted a destructive effort aimed at evidence affecting Adams or at evidence of ASUS’ wrongful use of intellectual property, it is clear that ASUS’ lack of a retention policy and irresponsible data retention practices are responsible for the loss of significant data.”

Adams was in fact cited by Judge Scheindlin in her latest opus – Pension Comm. of the Univ. of Montreal Pension Plan v. Banc of America Sec. LLC, No. 05 Civ. 9016, 2010 U.S. Dist. Lexis 4546, at *1 (S.D.N.Y. Jan. 15, 2010), where she found fault with the Plaintiff’s reliance on manual collections:

“This instruction does not meet the standard for a litigation hold. It does not direct employees to preserve all relevant records–both paper and electronic-nor does it create a mechanism for collecting the preserved records so that they can be searched by someone other than the employee.  Rather, the directive places total reliance on the employee to search and select what that employee believed to be responsive records without any supervision from Counsel.

From the foregoing, it’s probably too early to call the skepticism over manual collection a trend per se.  Certainly, lobbing a preservation notice over the proverbial wall to custodians without the requisite level of supervision is a recipe for disaster.  Education (about the matter and the required tasks), compliance (with the preservation instructions) and ongoing monitoring (to ensure that compliance continues over time) are all critical responsibilities that must be thoughtfully undertaken by counsel for a defensible ediscovery process.

The question then becomes, is the problem here really about the “manual” collection efforts by the custodians or more simply the fact that they aren’t supervised with the requisite degree of care?  If this is the case, which I’d opine that it is, then “properly executed” manual collections should be fine (i.e., defensible).

But, as Ford indicates, if your company is going to rely upon a manual collection modus operandi, then it may be advisable to let the opposition in on the use of this tactic.  This approach may be mandated by local rule or it may just be the type of transparent cooperation that’s all the rage these days.

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.

“Large storage vendor buys small electronic discovery software company to round-out broader corporate initiative.” That was the story in December 2007, when Seagate bought e-discovery company Metalincs for its i365 solution; and, it’s the same story today as EMC announced its acquisition of Kazeon for its SourceOne archiving solution. The terms of the EMC-Kazeon deal were not disclosed, but sources with knowledge of the transaction tell me that the acquisition price is approximately $75 million. That’s slightly less than what Seagate paid for Metalincs ($82 million), and less than what FTI Consulting paid for Attenex ($88 million). But it’s well within the usual range of $50-100 million that most acquirers pay for technology that has not yet matured into a business.

The deal will come as a relief to Kazeon’s long-suffering shareholders. The company was founded in 2003 and, over the past 6 years, it raised over $60 million in equity financing, double the amount it usually takes successful software companies to reach profitability. But despite all that investment, revenue has been hard to come by. According to former Kazeon employees, the company’s revenue totaled only $7 million over the past 12 months. Perhaps as a result, there’s been a lot of management turnover, and last year the board retained a recruiter to find a new CEO. In light of all that, selling the company for $75 million, or 10 times trailing revenue, is a great outcome for Kazeon’s shareholders. It also provides some level of job security for Kazeon’s employees, many of whom have been offered retention bonuses to stick around.

On the other side of the coin, the deal also makes sense for EMC, which needed to flesh out SourceOne, its recent re-branding of the Email Extender archive. In launching SourceOne in April 2009, EMC described it as an integrated portfolio of products: SourceOne Email Management for email archiving; Discovery Manager for legal holds of email; Celerra and Centera for storage; and Discovery Collector for identifying and collecting data from desktops and file shares. EMC owned all of those products except one: Discovery Collector, which instead was to come from EMC Select Partner, StoredIQ. It is widely known that EMC tried repeatedly to acquire StoredIQ but was rebuffed. So instead, it purchased Kazeon (i.e., the Kazeon Information Server) so that it now owns all aspects of SourceOne and does not have to rely on partners.

Will this eDiscovery deal be successful? We will have to wait and see, but Seagate’s experience is not encouraging. A year after it acquired Metalincs, Seagate laid off most of the staff and hired UBS to help it sell what was left of the electronic discovery company. There have not been any takers.

I was recently asked: “what are the first things you do when your client calls you about a case requiring e-discovery?”  So, for the benefit of all, I’ll post my answer.

My first caveat to the advice was context.  Since, while a lot of attorneys have attended CLEs or have read about e-discovery, it’s not the same in the real world.  As the old Spanish Proverb goes:

It’s not the same to talk of bulls as to be in the bullring.

Keeping in mind that reality may differ significantly from academics, here are some things to consider when the next e-discovery case comes up.   Please also keep in mind that these steps (like the EDRM workflow) aren’t linear and may in fact occur cyclically or in parallel:

1. Preserve, preserve, preserve

Nothing is more important than meeting the initial preservation obligation, which begins when litigation is “reasonably likely” – as opposed to just when the complaint is filed.  This first step in the long journey can easily be a trap for the unwary/unprepared.

The challenge once you’re past the trigger issue is to then identify the boundaries of the duty to preserve, i.e., what evidence must be preserved?   This inquiry is often initially comprised of identifying key players, date ranges and data types.

Another significant challenge in this step is to monitor and update the legal hold process.  And, given that litigation more often than not spans years, it’s easy to initially succeed at the preservation effort, but then later fail on execution.  The best way to minimize risk in this step is to move quickly from preservation to collection.  See Is Preservation in E-Discovery Overrated?

2. Work backwards

Once preservation (and ideally collection) is adequately covered, the next step is to start thinking about the end of the process and what success (or lack of failure) looks like.  The exposure and profile of the matter are important to consider when you embark upon an e-discovery project since it’s critical to scale discovery efforts appropriately.

One thing, in particular, that is very important to consider early in the process is the type of production format that will be preferred by reviewing counsel and the opposition.  TIFF-based image productions (which are historically well accepted) are often pitted against native file ESI reviews.  Either format may or may not be acceptable given the situation and the applicability of FRCP Rule 34.

3. Understand the technical landscape

Most attorneys, but for a rare few, aren’t capable of really comprehending technical nuances of the complex and interrelated IT systems found at most Fortune 2,500 enterprises.  Fortunately, they are quite adept at working with experts (either consulting or testifying) to help them get to the bottom of difficult to comprehend and explain issues.  The key is find the right technical people who understand IT systems and who can explain it to judges, juries, and attorneys alike, especially for some of the most common ESI repositories like: email servers, archival systems, shared network drives, instant messaging servers, archival repositories (e.g., tape libraries, real time back-up systems, etc.), records management systems, knowledge management systems, proprietary, but highly leveraged, internal applications, offsite repositories (e.g., hosted IT or email systems) and significant partner or subsidiary data stores.  In many instances it will make sense to leverage or create a map of the data universe so that nothing is missed and inaccessibility arguments can be cogently detailed.

4. Get your lingo straight

Assumptions, whether in e-discovery or not, are often dangerous.  In the complex undertaking where multiple parties are handling ESI it’s critical to make sure that everyone is on the same page especially since every company handles IT, records management, ILM and information security differently.  So, when working with these disparate constituents the outset of an engagement is the right time to make sure everyone is on the same page.  Therefore, standardize on a set of commonly used terms. Examples of potentially ambiguous topics include “imaging” ,“archive”, and “records.”

5. Don’t assume your client will really be helpful

I’ve been involved with hundreds of e-discovery engagements and I’ve found that almost universally the end client professes a profound willingness to help out.  And yet, actual “help” is relatively rare.  To qualify this, it may be prudent to ask several additional questions:

• Does the Client have the time to actually help?  Everyone at the client’s site has a day job that they’re tasked with above and beyond transient e-discovery needs.  So, while bandwidth generally is important, what’s more critical is the ability to comply with aggressive judicial deadlines.
• Are the people helping the ones you’d want to see on the stand?  It’s often not realistic to have internal folks (especially IT and Records Managers) stay isolated during the various pre-trial events – meet & confer conferences and potentially 30(b)(6) depositions so it’s important to evaluate how a given witness will fare when providing testimony.
• How likely is it that you client would throw you under the bus if things went wrong?  In my opinion, there is now more reason for outside counsel to manage the risks of an e-discovery project going awry.  See, Sullivan and Cromwell’s suit against EED.  Some will wisely bring in 3rd party consultants/experts to have a neutral, unbiased constituent in the process.

6. Build a budget and team (internal/external)

Everyone is probably now aware of how expensive e-discovery can be if managed improperly.  This makes it all that more imperative to work quickly to get a rough sense of the scope (which will lead to a budget) and the client’s willingness to absorb associated charges.  The most important step is to right-size the e-discovery effort with the risks inherent in the corresponding litigation/investigation.  Otherwise, there’s a high likelihood that e-discovery process will be over-engineered (too expensive) or under-scoped (cutting dangerous corners).

7. Figure out your risk profile

Similar to right-sizing the budget, it also makes sense to adopt a “horses for courses” approach to e-discovery since there is no singular way to handle a given matter.  For example, in one case you make take forensic images, restore backup tapes, capture instant messaging data, harness metadata, or decide to do an automated review with a with a “clawback” provision. In either case, the only mistake is to assume that an approach from another, dissimilar matter is warranted in the instant case.

8. Assume the opposition is better informed than you are

While this actually may not be the case, it’s a safer bet that assuming a level of naiveté that may not exist.  What is certain is that the Plaintiff’s bar is increasingly well informed and can be very aggressive.  They’ve seen the playbook that calls for baiting the opposition into a discovery misstep that can result in significant, case altering sanctions.  According to a recent survey, 63% of the polled attorneys said that e-discovery is being abused by counsel, so it’s important to be wary initially.

It’s also important to consider the potential reciprocity of a given matter and adjust your position accordingly.  In many instances it’s easy to consider your role only as a producing party, but with cross/counter claims it may be possible to simultaneously be propounding discovery and in the opposition’s shoes.

9. Prepare for an early case assessment

A recent industry survey found that effective early case assessment (ECA) approaches reduced overall litigation in half of the cases evaluated, and resulted in favorable outcomes for 76 percent of the cases.   The key to this methodology is to use the available next generation case analysis solutions earlier in the process, not just to review data for relevancy and privilege, but to:

• Identify the key players. This is critical in order to have a defensible legal hold process
• Evaluate the posture of the case to determine how it looks on the merits
• Diagnose potential outliers in the e-discovery process to facilitate meet and confer discussions and help create “inaccessibility” arguments
• Conduct a search term analysis for keyword negotiations during meet and confer discussions.  Objectively demonstrating the results of proposed search queries can go a long way in speeding up keyword negotiations

10. Don’t take search for granted

For many attorneys, e-discovery search is just like Lexis or Google.  Unfortunately, that isn’t the case.  Instead, it’s become highly complex and is now receiving significant judicial scrutiny.  In Victor Stanley v. Creative Pipe Judge Grimm suggested that attorneys need to rethink how they’ve traditionally managed the search process:  “[F]or lawyers and judges to dare opine that a certain search term or terms would be more likely to produce information than the terms that were used is truly to go where angels fear to tread.”  It’s now important to devise (and share at early meet & confer conferences) a defensible search strategy that can withstand judicial scrutiny.

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.

Most large companies face a dilemma. Should they open up their products and invite others to build features on them, creating a “platform” or ecosystem around themselves? Or would that be inviting the proverbial fox into the hen-house, meaning they should instead prevent others from integrating with their product or leveraging it to create add-on functionality?

In the internet world, there is no doubt about the answer: throw open the doors via easy-to-use APIs (“application programming interfaces”) and let a thousand flowers bloom. That’s what FaceBook did a couple of weeks back with their announcement of the FaceBook Platform, and it has already led to hundreds of new applications for their users. It is what Skype did so effectively, creating a mini-industry around themselves of voicemail, skins, ring-tones, and more. Even eBay, which has jealously guarded its feedback ratings and has habitually crushed smaller companies in its cross-hairs, is embracing the open platform mantra, announcing this week that third-party companies can build features that work with eBay in new ways.

By contrast, telecom companies live in a world of closed standards. Even in the wireless industry, which is arguably the most competitive part of the telecom world, the carriers (Cingular, T-Mobile, Verizon, etc.) exact a heavy toll on any application trying to reach their handsets. As friends in the industry tell me, “There’s a reason why there has never been a billion dollar mobile application company.”

In e-discovery, the large technology vendors like EMC, HP, Symantec, and ZANTAZ face the same choice. Their email archiving products store huge amounts of data. Should they let 3^rd party e-discovery software analyze that data, giving their customers more choice? Or should they slam the door shut, and try to force customers to use their own proprietary e-discovery applications?

The answer, it seems, depends on what they want to be when they grow up. As the market leader, Symantec is confident enough to open its archive (Enterprise Vault) to 3^rd party applications while offering customers its own Discovery Accelerator for litigations holds and some document review. Similarly, perhaps because of its powerful brand, HP focuses on storage optimization with HP RISS and partners with e-discovery software, often with huge savings for its customers. On the other side of the coin, smaller companies like ZANTAZ and Mimosa see themselves as e-discovery companies: they seek to leverage their storage products to get customers to also buy their e-discovery applications.

In the long-run, my feeling is that any archive of any stature will have to adopt open standards. Customers will demand it, and (unlike telecom companies) the archive vendors do not have the market power to resist. Over time, they will also come to appreciate (as HP and Symantec do now) that enabling 3^rd party applications to analyze the data they store is to their advantage, since it creates a powerful, additional incentive to store more information in the archive.