Preservation

eDiscovery Trends: Google “Vaults” Into eDiscovery Preservation

 

Yesterday, Google announced the launch of an eDiscovery tool named Vault for its Google Apps business customers.  Google Apps Vault is an add-on which preserves electronically stored information (ESI), including Gmail, chats and other correspondence to help users meet preservation obligations for litigation, regulation and compliance laws.

Jack Halprin, Head of eDiscovery at Google posted the following to the Google blog yesterday:

“Today we’re announcing the availability of Google Apps Vault (Vault) for Google Apps for Business customers. Vault is an easy-to-use and cost-effective solution for managing information critical to your business and preserving important data. It can reduce the costs of litigation, regulatory investigation and compliance actions.

Businesses of all sizes need to be prepared for the unexpected. In today’s environment, using Vault to manage, archive and preserve your data can help protect your business. Litigation costs can really take a toll on a business when minor lawsuits can run up to many thousands of dollars, and larger lawsuits can cost even more. Significant litigation costs come from having to search and find relevant data, which is also known as electronic discovery (eDiscovery).

E-discovery can be part of virtually any litigation and requires you to search, find and preserve your electronic information such as email. Vault helps protect your business with easy-to-use search so you can quickly find and preserve data to respond to unexpected customer claims, lawsuits or investigations. With an instant-on functionality and availability of your data a few clicks away, Vault provides access to all of your Gmail and on-the-record chats and can provide significant savings to your business over the traditional costs of litigation and eDiscovery.

Additionally, Vault gives Google Apps customers the extended management and information governance capabilities to proactively archive, retain and preserve Gmail and on-the-record chats. With the ability to search and manage data based on terms, dates, senders, recipients and labels, Vault helps you find the information you need, when you need it. Vault gives management, IT, legal and compliance users a systemized, repeatable and defensible platform that will reduce the costs and risks of doing business. With just a few clicks, the business can access a service designed for security and providing auditable access to critical information.

Vault is built on the same modern, 100% web-based architecture as Google Apps. Unlike traditional solutions, it does not require a complex and costly IT environment, and can be deployed in a matter of minutes. Vault brings the security, ease-of-use and reliability of Google Apps to information governance. It can help meet the sophisticated requirements of large organizations and makes these advanced capabilities available to business of all sizes.”

Vault is available to Google Apps customers for $5 per user per month.

So, what do you think?  Do you think that Google has the financial resources to make a splash with Vault?  Just kidding.  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Best Practices: Issuing the Hold is Just the Beginning

Yesterday, we discussed identifying custodians, preparing a written litigation hold, issuing the hold and tracking responses.  Today, we’ll discuss interviewing hold notice recipients, follow up on notices, releasing holds when the obligation to preserve is removed and tracking all holds within an organization.  Here are the rest of the best practices for implementing a litigation hold.

Interviewing Hold Notice Recipients: Depending on the case, follow-up interviews (with at least the key custodians) are generally accepted as a best practice and may be necessary to ensure defensibility of the notice.  The point of these interviews is to repeat the duty to preserve, provide a detailed explanation of the requirements of the hold, answer the recipient’s questions (if any), and confirm that the recipient understands and agrees to adhere to the notice. You should keep written records of each of these interviews and document the reasoning for determining which individuals to interview.

Follow-Up on Hold Notices: For a litigation hold plan to be successful and defensible, it needs to include periodic follow-up reminders to recipients of the notices to inform them that the data in question remains under hold until the case concludes. Follow-up reminders could simply be a retransmission of the original notice or they could be a summary of all of the notices the individual has received, if there are multiple cases with holds for that individual. There is no specific requirement on how often the reminders should be sent, but it’s best to send them at least quarterly.  For some cases, it may be necessary to send them monthly.

Release the Hold: Not to be confused with “release the hounds”, it is just as important to inform people when the duty to preserve the data expires (typically, when the case is completed) as it is to notify them when the duty to preserve begins.  Releasing the hold is key to ensure that information doesn’t continue to be preserved outside of the organization’s document retention policies – if it is, it may then become subject to litigation holds in other litigations unnecessarily.  Releasing the hold also helps keep custodians from being overwhelmed with multiple retention notices, which could cause them to take the notices less seriously.  However, the release notification should be clear with regard to the fact that data subject to hold in another matter should continue to be preserved to meet discovery obligations in that matter.

Hold Tracking System: It’s important to have a reliable “system” for tracking litigation holds across all matters within the organization. Depending on your needs, that could be a customized application or a simple database or spreadsheet to track the information.  You should keep historical tracking data even for completed matters as that information can be useful in guiding hold issuance on new matters (by helping to identify the correct custodians for new matters that are factually similar or related to current closed or open matters).  At a minimum, a tracking system should:

  • Track responses from individual custodians and identify those who have not yet responded,
  • Track periodic reminder notices and release notices,
  • Provide ability to report a list of people with a duty to preserve for a specific matter as well as all matters for which a person is under retention.

So, what do you think?  Do you have a solid “hold” on your hold process?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Best Practices: Hold It Right There!

 

When we reviewed key case decisions from last year related to eDiscovery, the most case law decisions were those related to sanctions and spoliation issues.  Most of the spoliation sanctions were due to untimely or inadequate preservation of the data for litigation.  As noted in Zubulake, Judge Shira Sheindlin ruled that parties in litigation have an obligation to preserve potentially relevant data as soon as there is a reasonable expectation that data may be relevant to future litigation.  However, even if the party reacts in a timely manner to take steps to preserve data through a litigation hold, but executes those steps poorly, data can be lost and sanctions can occur.  Here are some best practices for implementing a litigation hold.

The most effective litigation hold plans are created before actual litigation arises and applied consistently across all matters. While cases and jurisdictions vary and there are not many hard and fast rules on implementing litigation holds, there are generally accepted best practices for implementing holds.  Implementation of a litigation hold generally includes each of the steps identified below:

Identify Custodians: As we learned in Voom HD Holdings v. EchoStar Satellite LLC, 600292/08, It’s important to completely identify all potential custodians and suspend any automatic deletion policies that might result in deletion of data subject to litigation.  In this case, EchoStar put a litigation hold in place, instructing employees to save anything that they deemed potentially relevant to the litigation, but did not extend this hold to stopping automatic deletion of eMails from EchoStar's computers until four months later in June 2008.  As a result of their untimely and incomplete hold, EchoStar was given an adverse inference sanction (their second one!).

Custodians can be individuals or non-custodial (i.e., not held by a specific individual) sources such as IT and records management departments.  To determine a complete list of custodians, it’s generally best to conduct interviews of people identified as key players for the case, asking them to identify other individuals who are likely to have potentially relevant data in their possession.

Prepare Written Hold Notice: Hold notices should be in writing, and should typically be written in a standard format.  They should identify all types of data to be preserved and for what relevant period.  Sometimes, hold notices are customized depending on the types of custodians receiving them (e.g., IT department may receive a specific notice to suspend tape destruction or disable auto-deletion of emails).

Distribute Hold Notice: It is important to distribute the notice using a communication mechanism that is reliable and verifiable. Typically, this is via email. It’s rare to use paper notices anymore as they are more difficult to track. Distribution should occur only to the selected and specific individuals likely to have potentially relevant information, usually not company-wide, as not everyone will understand the parameters of the hold.  Notices with overly broad distributions have, in some cases, been deemed inadequate by courts.

Track Responses: It is advisable to require recipients of the litigation hold notice to confirm their receipt and understanding of the notice via a method that can be tracked.  Receipt and read notifications or voting buttons in emails could be used for this purpose, but they may not always be acceptable, since there is no guarantee that the recipient actually read or understood the notice.  Perhaps a better approach is to send each recipient an attached form that enables them to acknowledge each instruction within the hold notice to confirm a more complete understanding – these forms can even be set up as enterable PDF forms that even enable digital signatures so that no printing is required.

Tomorrow, we’ll discuss follow up on notices, releasing holds when the obligation to preserve is removed and tracking all holds within an organization.  Hasta la vista, baby!

So, what do you think?  Do you have a solid “hold” on your hold process?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Daily Is Eighteen! (Months Old, That Is)

 

Eighteen months ago yesterday, eDiscovery Daily was launched.  A lot has happened in the industry in eighteen months.  We thought we might be crazy to commit to a daily blog each business day.  We may be crazy indeed, but we still haven’t missed a business day yet.

The eDiscovery industry has grown quite a bit over the past eighteen months and is expected to continue to do so.   So, there has not been a shortage of topics to address; instead, the challenge has been selecting which topics to address.

Thanks for noticing us!  We’ve more than doubled our readership since the first six month period, had two of our biggest “hit count” days in the last month and have more than quintupled our subscriber base since those first six months!  We appreciate the interest you’ve shown in the topics and will do our best to continue to provide interesting and useful eDiscovery news and analysis.  And, as always, please share any comments you might have or if you’d like to know more about a particular topic!

We also want to thank the blogs and publications that have linked to our posts and raised our public awareness, including Pinhawk, The Electronic Discovery Reading Room, Unfiltered Orange, Atkinson-Baker (depo.com), Litigation Support Technology & News, Next Generation eDiscovery Law & Tech Blog, InfoGovernance Engagement Area, Justia Blawg Search, Learn About E-Discovery, Ride the Lightning, Litigation Support Blog.com, ABA Journal, Law.com and any other publication that has picked up at least one of our posts for reference (sorry if I missed any!).  We really appreciate it!

As we’ve done in the past, we like to take a look back every six months at some of the important stories and topics during that time.  So, here are some posts over the last six months you may have missed.  Enjoy!

eDiscovery Trends: Is Email Still the Most Common Form of Requested ESI?

eDiscovery Trends: Sedona Conference Provides Guidance for Judges

eDiscovery Trends: Economy Woes Not Slowing eDiscovery Industry Growth

eDiscovery Law: Model Order Proposes to Limit eDiscovery in Patent Cases

eDiscovery Case Law: Court Rules 'Circumstantial Evidence' Must Support Authorship of Text Messages for Admissibility

eDiscovery Best Practices: Cluster Documents for More Effective Review

eDiscovery Best Practices: Could This Be the Most Expensive eDiscovery Mistake Ever?

eDiscovery 101: Simply Deleting a File Doesn’t Mean It’s Gone

eDiscovery Case Law: Facebook Spoliation Significantly Mitigates Plaintiff’s Win

eDiscovery Best Practices: Production is the “Ringo” of the eDiscovery Phases

eDiscovery Case Law: Court Grants Adverse Inference Sanctions Against BOTH Sides

eDiscovery Trends: ARMA International and EDRM Jointly Release Information Governance White Paper

eDiscovery Trends: The Sedona Conference International Principles

eDiscovery Trends: Sampling within eDiscovery Software

eDiscovery Trends: Small Cases Need Love Too!

eDiscovery Case Law: Court Rules Exact Search Terms Are Limited

eDiscovery Trends: DOJ Criminal Attorneys Now Have Their Own eDiscovery Protocols

eDiscovery Best Practices: Perspective on the Amount of Data Contained in 1 Gigabyte

eDiscovery Case Law: Computer Assisted Review Approved by Judge Peck in New York Case

eDiscovery Case Law: Not So Fast on Computer Assisted Review

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery History: A Look Back at Zubulake

 

Yesterday, we discussed a couple of cases within a month’s time where the New York Appellate Division has embraced the federal standards of Zubulake v. UBS Warburg LLC, 220 FRD 212.  Those of us who have been involved in litigation support and discovery management for years are fully aware of the significance of the Zubulake case and its huge impact on discovery of electronic data.  Even if you haven’t been in the industry for several years, you’ve probably heard of the case and understand that it’s a significant case.  But, do you understand just how many groundbreaking opinions resulted from that case?  For those who aren’t aware, let’s take a look back.

The plaintiff, Laura Zubulake, filed suit against her former employer UBS Warburg, alleging gender discrimination, failure to promote, and retaliation. Southern District of New York Judge Shira Sheindlin's rulings in this case are the most often cited in the area of electronic discovery, and were issued prior to the 2006 amendments to the Federal Rules of Civil Procedure. That’s somewhat like establishing laws before the Ten Commandments!  The important opinions related to eDiscovery are commonly known as Zubulake I, Zubulake III, Zubulake IV and Zubulake V.  Here is a summary of each of those opinions:

Zubulake v. UBS Warburg, 217 F.R.D. 309 (Zubulake I) and Zubulake v. UBS Warburg, 216 F.R.D. 280 (S.D.N.Y. 2003) (Zubulake III)

The plaintiff argued that key evidence was located in various emails exchanged among employees of UBS, the defendant. Initially, the defendant produced about 350 pages of documents, including approximately 100 pages of email, but the plaintiff produced approximately 450 pages of email correspondence on her own. To address the discrepancy, the plaintiff requested for UBS to locate the documents that existed in backup tapes and other archiving media.

The defendant, arguing undue burden and expense, requested the court to shift the cost of production to the plaintiff, citing Rowe Entertainment v. The William Morris Agency, 205 F.R.D. 421 (S.D.N.Y. 2002). In May 2003, the court ruled stating that whether the production of documents is unduly burdensome or expensive "turns primarily on whether it is kept in an accessible or inaccessible format". The court determined that the issue of accessibility depends on the media on which data are stored. It described five categories of electronic media, as follows:

  1. Online data, including hard disks;
  2. Near-line data, including optical disks;
  3. Offline storage, such as magnetic tapes;
  4. Backup tapes;
  5. Fragmented, erased and damaged data.

The last two categories were considered inaccessible as they were not readily available and thus subject to cost-shifting. Discussing the Rowe decision, the court concluded that it needed modification and created a new seven factor balance test for cost-shifting:

  1. The extent to which the request is specifically tailored to discover relevant information;
  2. The availability of such information from other sources;
  3. The total cost of production, compared to the amount in controversy;
  4. The total cost of production, compared to the resources available to each party;
  5. The relative ability of each party to control costs and its incentive to do so;
  6. The importance of the issues at stake in the litigation; and
  7. The relative benefits to the parties of obtaining the information.

The defendant was ordered to produce, at its own expense, all responsive email existing on its servers, optical disks, and five backup tapes as selected by the plaintiff. The court would only conduct a cost-shifting analysis after the review of the contents of the backup tapes.

In July 2003, Zubulake III applied the cost-shifting test outlined in Zubulake I based on the sample recovery of data from five backup tapes.  After the results of the sample restoration, both parties wanted the other to fully pay for the remaining backup email. The sample cost the defendant about $19,003 for restoration but the estimated costs for production was $273,649, including attorney and paralegal review costs. After applying the seven factor test, it determined that the defendant should account for 75 percent of the restoration and searching costs, excluding attorney review costs.

Zubulake v. UBS Warburg, 220 F.R.D. 212 (S.D.N.Y. 2003) (Zubulake IV)

During the restoration effort, the parties discovered that some backup tapes were no longer available. The parties also concluded that relevant emails created after the initial proceedings had been deleted from UBS's email system and were only accessible on backup tapes. The plaintiff then sought an order requiring UBS to pay for the total costs of restoring the remaining backup tapes and also sought an adverse inference instruction against UBS and the costs for re-deposing some individuals required because of the destruction of evidence.

In October 2003, Judge Scheindlin found that the defendant had a duty to preserve evidence since it should have known that it would be relevant for future litigation. However, at the time, she concluded that the plaintiff failed to demonstrate that the lost evidence supported the adverse inference instruction claim. But, she did order the defendant to cover the costs as claimed by the plaintiff.

Zubulake v. UBS Warburg, 2004 WL 1620866 (S.D.N.Y. July 20, 2004) (Zubulake V)

In July 2004, Judge Scheindlin ruled that UBS had failed to take all necessary steps to guarantee that relevant data was both preserved and produced, and granted the plaintiff's motion for adverse inference instruction sanctions, sought in Zubulake IV, due to the deleted evidence (emails and tapes) and inability to recover key documents during the course of the case.

The court also indicated that defense counsel was partly to blame for the document destruction because it had failed in its duty to locate and preserve relevant information. In addressing the role of counsel in litigation, the court stated that "[c]ounsel must take affirmative steps to monitor compliance so that all sources of discoverable information are identified and searched" by ensuring all relevant documents are discovered, retained, and produced and that litigators must guarantee that relevant documents are preserved by instituting a litigation hold on key data, and safeguarding archival media.

In the final instructions to the jury Judge Scheindlin instructed in part, "[i]f you find that UBS could have produced this evidence, the evidence was within its control, and the evidence would have been material in deciding facts in dispute in this case, you are permitted, but not required, to infer that the evidence would have been unfavorable to UBS." In addition, monetary sanctions were awarded to the plaintiff for reimbursement of costs of additional re-depositions and of the motion leading to this opinion, including attorney fees. The jury found in the plaintiff’s favor on both claims awarding compensatory and punitive awards totaling $29.2 million.

Judge Scheindlin’s opinions in Zubulake, including definitions of accessible and inaccessible data, the seven factor balance test for cost shifting and definition of counsel’s obligation for preserving data, have been referenced in numerous cases since and have provided guidance to organizations preparing for litigation.  For any of you who may not have fully understood the significance of the case, I hope this look back was helpful.

So, what do you think?  Did you learn something new about Zubulake?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Case Law: The Zubulake Rules of Civil Procedure

 

As noted in Law Technology News (N.Y. Appellate Division Continues to Press 'Zubulake' EDD Standard) recently, the New York Appellate Division has embraced the federal standards of Zubulake v. UBS Warburg LLC, 220 FRD 212 in two case rulings within a month’s time.

In Voom HD Holdings v. EchoStar Satellite LLC, 600292/08, the decision, written by Justice Sallie Manzanet-Daniels, was the first by a New York state appellate court to apply the standard for spoliation of electronic evidence applied by Judge Shira Scheindlin in Zubulake in 2003.  As defined by Judge Scheindlin, the Zubulake standard asserts that "once a party reasonably anticipates litigation, it must suspend its routine document retention/destruction policy and put in place a 'litigation hold' to ensure the preservation of relevant documents."

The case relates to a 2005 contract dispute between EchoStar and Cablevision subsidiary Voom HD Holdings, within which Voom agreed to provide EchoStar rights to broadcast Voom's programming.  Once the case was filed by Voom in February 2008, EchoStar put a litigation hold in place, instructing employees to save anything that they deemed potentially relevant to the litigation, but did not extend this hold to stopping automatic deletion of eMails from EchoStar's computers until four months later in June 2008.

Voom moved for spoliation sanctions against EchoStar for failing to preserve its eMails and Manhattan Supreme Court Justice Richard Lowe granted the motion, citing Zubulake, finding that EchoStar should have put in place a litigation hold (including a stop to automatic deletion of e-mails) in June 2007, when its corporate counsel sent Voom a letter containing a notice of breach, a demand and an explicit reservation of rights (i.e., reasonably anticipated litigation).  Therefore, EchoStar was given an adverse inference sanction (they had also received a similar sanction in 2005 in Broccoli v. EchoStar Communications Corp., 229 FRD 506).

EchoStar appealed and requested the appellate court to adopt a rule that a company must preserve documents when litigation is pending or when it has "notice of a specific claim."  However, that argument was rejected by The First Department, which ruled that “EchoStar and amicus's approach would encourage parties who actually anticipate litigation, but do not yet have notice of a 'specific claim' to destroy their documents with impunity” and upheld the sanction.

In U.S. Bank National Association v. GreenPoint Mortgage Funding Inc., 600352/09, the First Department held that the producing party should bear the initial costs of "searching for, retrieving and producing discovery," but that lower courts may permit cost shifting based on the factors set forth in Zubulake.  The case was filed by U.S. Bank, NA (indenture trustee for the insurers and holders of the mortgage-backed notes issued by GreenPoint Mortgage Funding Inc., a now defunct mortgage lender specializing in "no-doc" and "low-doc" loans) against GreenPoint.

U.S. Bank served its first document production request on GreenPoint along with its original complaint; however, GreenPoint did not produce the requested documents.  Instead, they moved for a protective order arguing that U.S. Bank should pay the costs associated with its document requests including the cost of attorney review time for confidentiality and privilege assertions.  The court upheld GreenPoint's argument that the "party seeking discovery bears the costs incurred in its production" but rejected GreenPoint's request for U.S. Bank to also bear the attorney costs for privilege and confidentiality determinations.

Upon appeal, the First Department reversed the lower court's conclusion that the requesting party bear the cost of production, finding that, per the Federal Rules of Civil Procedure and Zubulake, the producing party should “bear the cost of the searching for, retrieving, and producing documents, including electronically stored information.”  In the February 28 ruling, Justice Rolando Acosta wrote that the court was “persuaded that Zubulake should be the rule in this Department.”  However, the court also ruled that the lower court could order cost shifting under CPLR Article 31 between the parties by considering the seven factors set forth in Zubulake.

What are those seven factors?  Tune in tomorrow, when we will provide a refresher to the Zubulake case and its various opinions!

So, what do you think?  Is the Zubulake standard appropriate for these two cases?  Is it appropriate for cases in general?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Best Practices: Who’s On Your Team?

 

When beginning a new eDiscovery project, a good place so start is to estimate the various tasks that will need to be performed and identify the type of personnel that will be needed. Every project is different and unique, so the requirements of each project must be assessed. As the project unfolds, the tasks required to complete it may change – not just in terms of tasks added, but also tasks removed if the work is deemed to be unnecessary.  So, it is important to revisit the project tasks and assignments to determine whether additional personnel are needed or if you can cut back. Here are the types of roles that could be associated with a typical eDiscovery project:

Client Contact(s): It’s important for the client to be involved in the process, so the team should include at least one client representative that can serve as the link between the internal and external teams, providing guidance on internal company workings and contact personnel. Typically, the client contact is from the in-house legal department, usually either a paralegal (to handle routine tasks) or an attorney (to discuss issues and coordinate decision making).  When preservation and collection are required, the client contact(s) generally assist with litigation hold procedures, locating and collecting ESI, and conducting interviews of custodians. It is up to the client contact(s) to involve key managers and custodians as needed to provide guidance during this process.

IT Personnel: When responding to requests for ESI, let’s face it – you need your trusty geek.  Or geeks.  It’s important to include personnel who understand technical details about the client’s various computer systems and data.  Depending on the case, you need one or more individuals who understand any and all of the above: email and email archiving, storage of employee ESI, servers, clients, intranets, and databases. It’s typical for IT personnel in larger organizations to specialize; for example, to have one or more that is more knowledgeable about structured data (i.e. database programs) while others may understand and have access to email systems. 

IT personnel should be involved in all issues related to the technology for the responding party to increase efficiency and optimize the approach to each new case. For many corporations, this is typically one or more individuals already employed as a member of the IT staff.  It’s important for IT personnel to have at least a basic understanding of the legal processes and requirements of discovery.  If they don’t have that, it may be necessary to provide some training before a case arises or employ an outside consultant.

Forensic Collection Personnel: In some cases, it’s necessary to perform forensic analysis on various types of ESI (or at least collect the ESI in a forensic manner in the event that’s required). Examples of cases that may require forensic collection of electronic data include internal integrity investigations, situations where fraud and data deletion are suspected (such as trade secret cases) and government civil or criminal investigations. To enable the forensic specialist to testify (if required) to the work that was performed and exactly how it was done, companies often use a vendor not employed by the company or by the outside law firm.

See at least one critical team component missing?  Tomorrow, we’ll talk about the rest of the team.  Same bat time, same bat channel!

So, what do you think?  Do you estimate the team members needed for your project before it begins?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Humor: And Now For Something Completely Different…

 

Every now and then, it’s nice to take a break from the regular case law updates, emerging trends reports and best practices tutorials and just have a laugh.  We recently published a two part interview series from LegalTech New York with Ralph Losey, who always has interesting and educational thoughts to share regarding eDiscovery.  Ralph recently published a video post on his excellent blog, e-Discovery Team® entitled How Not to Cooperate in an E-Discovery Conference.

Based on the watermark, it appears that Ralph used XtraNormal to make the video.  XtraNormal enables you to make an animated movie by selecting your animated “actors”, type or record your dialogue, and select a background.  The “actors” sound a bit robotic if you type the dialogue, but that just adds to the humor as the pronunciations and inflections are rather humorous.  Sometimes, they put the emPHASis on the wrong sylLABle.  And, it’s funny to hear them try to pronounce words like “chutzpah”.  🙂

Ralph’s video depicts opposing parties negotiating terms of eDiscovery production, and his attorney representing the producing party is particularly uncooperative.  Complete with applause and a laugh track, the four minute video is guaranteed to amuse anybody that has dealt with discovery negotiations or even works in discovery or litigation support.

Ralph has posted several other videos to YouTube, some of which are educational and others of which (while possibly also being educational) are also fun, including a Star Trek Meets e-Discovery series.

So, what do you think?  Did you get a laugh?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine Discovery. eDiscoveryDaily is made available by CloudNine Discovery solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

eDiscovery Trends: Craig Ball of Craig D. Ball, P.C., Part Two

 

This is the seventh (and final) of the 2012 LegalTech New York (LTNY) Thought Leader Interview series.  eDiscoveryDaily interviewed several thought leaders at LTNY this year and generally asked each of them the following questions:

  1. What do you consider to be the emerging trends in eDiscovery that will have the greatest impact in 2012?
  2. Which trend(s), if any, haven’t emerged to this point like you thought they would?
  3. What are your general observations about LTNY this year and how it fits into emerging trends?
  4. What are you working on that you’d like our readers to know about?

Today’s thought leader is Craig Ball.  A frequent court appointed special master in electronic evidence, Craig is a prolific contributor to continuing legal and professional education programs throughout the United States, having delivered over 750 presentations and papers.  Craig’s articles on forensic technology and electronic discovery frequently appear in the national media, and he writes a monthly column on computer forensics and eDiscovery for Law Technology News called Ball in your Court, as well as blogs on those topics at ballinyourcourt.com

Our interview with Craig had so much good information in it, we couldn’t fit it all into a single post.  Yesterday, we published part one.  Enjoy the rest of the interview!

What are your general observations about LTNY this year and how it fits into emerging trends?

Well, I've been coming to Legal Tech for well over a dozen years and ,each year, I think it couldn't possibly become more an eDiscovery conference (as opposed to a general forensic technology conference).  Then, next year, the aisles seem to grow longer and deeper with people providing eDiscovery solutions

So I'm just blown away.  I used to toil in this fairly obscure corner of the practice, and it’s now, literally, this whole event.  Walk down these aisles with me, and you'll see it's just one person after another after another offering some kind of eDiscovery tool or service or related product.  That’s also true of the educational sessions – some of which I guiltily helped plan, so the focus on eDiscovery does not come as much of a surprise.  But, remember that the vendors who sponsor these tracks have a hand in the content as well, and they’re the ones insisting, “We want to talk about eDiscovery.  We want to talk about technology-assisted review.”

It's not just because of what they're selling, although, certainly that’s a driver.  It's also what they want to hear about.  It's what their customers want to know more about. 

So, is it inconsistent that I'm saying there's not enough education about eDiscovery, and yet here, they talk of little else?  Other than LegalTech, and a few other events, the need remains to go longer and deeper.  Understanding information technology is a necessity for litigators.  That’s where the evidence lives.  IT is a discipline as broad, deep and complex in its way as the law.  Why then do we expect it should require so much less a dedication of time and effort to become even minimally proficient in information technology than it was to learn the law?

What are you working on that you’d like our readers to know about?

For me, this is the year of trying to offer an earlier acquaintance in information technology to lawyers.  I've spent almost thirty years teaching lawyers and judges about forensic technology and helping them get their arms around it.  This year, I returned to teaching law students.  My e-discovery course is offered at the University of Texas School of Law and I’m trying to help the students appreciate that in a very difficult job market, entering the profession with a practical understanding of how to attack an eDiscovery effort is a distinguishing factor in trying to find and keep employment.  It's a crucial skill set, and it's not one they can expect will be handed down to them from older lawyers.

There's just simply no lore to hand down where eDiscovery is concerned, at least not much useful lore.  And so I'm gratified for the challenge, and it's very hard work.  It's much harder to teach law students than it is to teach lawyers for a host of reasons.  The challenge in teaching law students versus lawyers is giving them the crucial context.  Most haven’t much exposure to law practice, so you have to give them more information and explain much more of what you take for granted with lawyers. 

Moving forward this year, I'm also trying to find ways to do more testing of new tools and refine mechanisms for reducing the volume of electronic information, to help lawyers master strategies that will make it easier for them to hit the ground running and take advantage of some of the economies that are within easy reach.  The key is to educate them on “methods” more than “shortcuts”.  I want to show them techniques that they can apply with confidence to speed the process of identification and preservation, as well as help them apply a better and more precise working vocabulary to enable them to communicate with clarity and confidence about ESI.  Competent communication, even more than cooperation, will prove a major contributor to eliminating headaches in eDiscovery.

Thanks, Craig, for participating in the interview!

And to the readers, as always, please share any comments you might have or if you’d like to know more about a particular topic!

eDiscovery Trends: Craig Ball of Craig D. Ball, P.C.

 

This is the seventh (and final) of the 2012 LegalTech New York (LTNY) Thought Leader Interview series.  eDiscoveryDaily interviewed several thought leaders at LTNY this year and generally asked each of them the following questions:

  1. What do you consider to be the emerging trends in eDiscovery that will have the greatest impact in 2012?
  2. Which trend(s), if any, haven’t emerged to this point like you thought they would?
  3. What are your general observations about LTNY this year and how it fits into emerging trends?
  4. What are you working on that you’d like our readers to know about?

Today’s thought leader is Craig Ball.  A frequent court appointed special master in electronic evidence, Craig is a prolific contributor to continuing legal and professional education programs throughout the United States, having delivered over 750 presentations and papers.  Craig’s articles on forensic technology and electronic discovery frequently appear in the national media, and he writes a monthly column on computer forensics and eDiscovery for Law Technology News called Ball in your Court, as well as blogs on those topics at ballinyourcourt.com

Our interview with Craig had so much good information in it, we couldn’t fit it all into a single post.  So, today is part one.  Part two will be published in the blog tomorrow!

What do you consider to be the emerging trends in eDiscovery that will have the greatest impact in 2012?

Well, I see several things happening.  I'm gratified that people are starting to become more resigned to the obligation to pursue eDiscovery.  I think we're seeing some better practices, particularly with respect to preservation.

The preservation message is hitting home.  Whether it’s a function of the outsize fear factor prompted by sanctions decisions or whether lawyers and businesses are becoming better informed by virtue of education and dialogue like that here at LegalTech is hard to say.  Regardless, I think the message is starting to seep through that there are  things you must do early on to identify electronically stored information and be sure that it's properly preserved.

As I walk around the show and listen to the programs, I'm amazed by all discussion of Technology Assisted Review or TAR—maybe the worst acronym that industry’s come up with since ECA.  But, they didn't choose Super Human Information Technology, so I guess we should be thankful for small blessings.  I'm sure we'll soon an article mentioning TAR and feathers.

Technology Assisted Review is the use of more sophisticated algorithms—math–and advanced analytic to take replace or supplement the individualized judgment of lawyers' respecting the responsiveness, non-responsiveness and privileged character of documents and data sets.  The notion behind TAR is that we don't need legions of young associates or contract lawyers in darkened rooms staring at screens; instead, the broad distinctions between what is most likely to be relevant and what is not will be handled robotically.  It’s floated as a more palatable, more affordable alternative to poorly-chosen key words thrown at massive data volumes–a more intelligent, more intuitive tool that does the job in a way that’s no worse than human beings, hopefully somewhat better, and in any case, for a lot less money.  That is the dream, and it’s coming closer to a reality..

But the realization out there is spotty.  Expectations are unrealistic and marketing is overheated, but we are seeing some enthusiasm amidst the skepticism.  And, I think that trend is certainly going to continue, at least as a marketing trend whether it continues as a successfully-integrated technology or not.  For the moment, it’s an option only for those with big budgets, not the rank and file firm.  No surprises there, as eDiscovery has yet to become a process lawyers know how to manage cost-effectively, But they will learn, in time.  Clients, courts and malpractice carriers will leave no option but to learn it.

Which trend(s), if any, haven’t emerged to this point like you thought they would?

Oh, that's an easy one.  That's education.  I am appalled at the dearth of high-caliber educational options available to lawyers in this crucial and very costly corner aspect of the practice.  E-discovery education is still afflicted by the scourge of the one-hour CLE.  You know, where some earnest person’s trotted out for 30, 45 minutes, maybe an hour of introduction to electronic discovery.  That continuing, repeated, cursory treatment of this challenging area is what’s supposed to make us confident and competent.  It doesn't even begin to scratch the surface.

Lawyers are still not learning enough about the information infrastructure of their clients.  They're picking up a few buzz words.  I’ll see it some meet-and-confers.  It's like watching a little kid use a curse word.  This sort of smile creeps across their face when they’ve managed to work the word “metadata” into the conversation.  As though using the term is a talisman–a substitute for actually knowing what they're talking about.

I don't mean to be so dismissive, but it's really gets almost that absurd sometimes.  We don't have enough education.  We don't have enough lawyers starting to get it.  Most channel their energy and ingenuity into look for reasons why they don’t need to know this stuff.  The handful that really do want to learn have precious few places to go short of self-instruction.  We need to change that.

We need a Manhattan Project in this country to help rescue the experienced lawyers and bring them up to speed.  We need a sort of reset, getting all trial lawyers talking about these topics in an intelligent, productive, and perhaps most importantly of all, cost-effective way.

Thanks, Craig, for participating in the interview!

To the readers, just a reminder to stay tuned for part two of our interview with Craig tomorrow!  And, as always, please share any comments you might have or if you’d like to know more about a particular topic!