Thank You Judge John Facciola

facciola2

Thanksgiving time is one for reflection. I have been thinking about Judge John Facciola’s impact on the world of eDiscovery with his upcoming retirement. I am very thankful we had such a dedicated judge who has been such a leader in electronic discovery.

Judge Facciola had his share big cases, but the important ones are the cases that give a nuts and bolts framework on how to actually litigate issues surrounding electronically stored information.

Judge Facciola excelled at these cases and showed a profound willingness to be hands on in solving issues, from search term efficiency to hosted repositories. The Judge’s commanding use of language is second to none, with many memorable quotes.

The good Judge is a profoundly thoughtful individual, whose interests include sailing, baseball, history, and a strong dedication to our justice system. I wanted to share a couple of stories I had with the Judge over the years.

First Time I Met the Judge

I met Judge Facciola on Super Tuesday 2008 in Washington, DC. I was in DC for a conference and had a webinar planned with him later in the month. I wanted to take the opportunity to meet him in person since I was in town.

After going through security at the Federal Courthouse, I eventually found the waiting room for his department’s chambers. Observing large format photos of boats on the wall (one was a dory) and magazine on the America’s Cup, I thought, “Cool, we can talk about sailing.”

The Judge greeted me in one of his signature bow ties. Ironically, I did not know he wore bow ties at that time. My react was simply, “Awesome.”

We had lunch in the judges’ dining room that overlooks the US Capital Building. It is still surreal to remember, seeing other judges eating lunch and discussing matters of importance. To this date it is still one of the most memorable events in my career so far.

Judge Facciola and I discussed search terms and discovery requests. I shared with him my concern that “text speak” such as “LOL” type acronyms should be included when conducting searches of text messages and instant messages. He actually sat-up and said, “I had not thought of that.”

After leaving the Courthouse, I met up with some attorney friends. We watched the Super Tuesday results at different campaign parties at some of DC’s more entertaining pubs, but that adventure is another story.

An Evening at the Cosmos Club

I visited DC in 2013 for a business trip. I contacted the Judge if he had time to meet for lunch or coffee while I was in town. He offered to meet for dinner at the Cosmos Club.

I am normally well versed in history, but I had to look up the Cosmos Club. The Club was founded in 1878 dedicated to the advancement of art, science, and literature. Its members included Alexander Graham Bell, Woodrow Wilson, and virtually every Secretary of State.

There is no question the Cosmos Club was the most regal institution I have ever entered. For me, it represented those dedicated to knowledge with a true sense of class. The library was simply majestic, where one could be lost for hours in study.

The Judge and I enjoyed a good meal, discussing the law, film, boats, and of course US History. At a prior dinner before Legal Tech 2009, we discussed the sinking of the USS Indianapolis and the unfair court martial of Captain Charles McVay III, leaving the others looking at us in respectful confusion.

While we were discussing topics from eDiscovery to President Garfield, another dinner party walked by our table. The person in the lead looked familiar, but I could not identify the dinner guest.

Once the other party was seated, the Judge said, “That’s General Petraeus.”

A True Statesman

Jessica Mederson and I invited Judge Facciola to record an Independence Day podcast for our blog The Legal Geeks. Judge Facciola truly loves the United States. The Judge shared his thoughts on the 4th of July, the meaning of Independence, and the role of the Judiciary in upholding the promise of the Declaration of Independence. Jess and I were clearly in awe of what the Judge had to say about our country and freedom.

Legacy on the Court

Judge Facciola leaves a powerful legacy of civic duty, honor, and a strong work ethic. I wish him well in his future adventures, whether they are out sailing or well-earned time with family. Thank you for your service, Your Honor.

Moreover, thank you for the tip about Beau Ties Ltd of Vermont. Wonderful collection of bow ties.

An Unsung Hero on the Form of Production

scales-303388_1280Magistrate Judge Paul Cherry is a great jurist whose opinions on the form of production should be taught in first year Civil Procedure classes.

The Judge clearly explains the Federal Rules of Civil Procedure and applies the rules to the case at bar in very concise analysis.

A Plaintiff in a recent case sought consumer credit reports in native file format, which was produced as static images. Judge Cherry provided textbook case analysis which I summarized in my Everlaw Blog guest post Really Thinking Through the Form of Production. Please check it out for my thoughts on the form of production and document review.

Guest Post on Everlaw: Is An Attorney Responsible for Manually Reviewing Discovery Before Production?

Review-TeamI prepared a guest post for Everlaw’s blog on an attorney’s ethical duty to follow a client’s instruction to manually review documents prior to production.

Is expert testimony required to show a lawyer breached their standard of care or is this issue one a jury can decide on their own?

Check out the case summary and tips on document review at Everlaw:

What is an attorney’s Duty of Loyalty to review discovery documents before producing them to an opposing party? That issue recently arose in a summary judgment battle between a client and his former attorneys.

The Case:

The client claimed that the law firm had committed malpractice because the attorneys failed to review discovery responses before production to the opposing party – after being directed to do so by their client. Things really went wrong when the client was hit with sanctions, and the law firm denied knowledge of certain documents in court. Price Waicukauski & Riley v. Murray, 2014 U.S. Dist. LEXIS 130680 (S.D. Ind.Sept. 18, 2014).

 Continue reading at Is An Attorney Responsible for Manually Reviewing Documents?

Native Files & Protective Orders

What do parties do when they anticipate documents, testimony, or information containing or reflecting confidential, proprietary, trade secret, and/or commercially sensitive information are likely to be disclosed or produced during the course of discovery, initial disclosures, and supplemental disclosures in a case? Agreeing to a protective order is a the solution the parties sought in Farstone Tech., Inc. v. Apple Inc.

ConfidentialPaperClip

The protective order stated the following on native files:

Where electronic files and documents are produced in native electronic format, such electronic files and documents shall be designated for protection under this Order by appending to the file names or designators information indicating whether the file contains “CONFIDENTIAL,” “CONFIDENTIAL – ATTORNEYS’ EYES ONLY,” or “CONFIDENTIAL – OUTSIDE ATTORNEYS’ EYES ONLY – SOURCE CODE,” material, or shall use any other reasonable method for so designating Protected Materials produced in electronic format. When electronic files or documents are printed for use at deposition, in a court proceeding, or for provision in printed form to an expert or consultant pre-approved pursuant to paragraph 12, the party printing the electronic files or documents shall affix a legend to the printed document corresponding to the designation of the Designating Party and including the production number and designation associated with the native file. No one shall seek to use in this litigation a .tiff, .pdf or other image format version of a document produced in native file format without first (1) providing a copy of the image format version to the Producing Party so that the Producing Party can review the image to ensure that no information has been altered, and (2) obtaining the consent of the Producing Party, which consent shall not be unreasonably withheld.

Farstone Tech., Inc. v. Apple Inc., 2014 U.S. Dist. LEXIS 89604, 10-12 (C.D. Cal. June 24, 2014).

The section of depositions demonstrated a lot of forethought on behalf of the attorneys who prepared the stipulated protective order (or Judge) with the party printing the electronic files or documents shall affix a legend to the printed document corresponding to the designation of the Designating Party and including the production number and designation associated with the native file. The only way this could be stronger would be the legend also including a MD5 hash value for authentication (which it potentially would include) and the system file pathway.

The final sentence on allowing review of a static image to the opposing side for review also addresses a concern many attorneys have over native files converted to static images. There is the obvious method of reading the document to determine it is “identical,” but using near-de-duplication technology to verify the text is an exact match, assuming the static image is a searchable PDF. If it is a TIFF, then conducting a line by line comparison is the best option.

My compliments to the attorneys who drafted the stipulated protective. I hope the litigation avoids any discovery disputes and focuses on the merits.

Stuck in the Predictive Coding Pipeline

ExxonMobil Pipeline had a problem in discovery: their discovery responses were overdue. The requests for production was served in November 2013 and due after one extension in January 2014. The Plaintiffs rightly brought a motion to compel.

The Defendants had enough discovery to give most eDiscovery attorneys a migraine with a nosebleed: 16 separate lawsuits, with 165 discovery requests in one case, a total of 392 requests in all the related cases, and 83 custodians with approximately 2.7 million electronic documents. Other discovery going back to 1988 had over 63,000 paper documents that were scanned and to be searched with keywords. Additionally, there were approximately 630,000-800,000 documents that had to be reviewed for responsiveness, confidentiality, and privilege. The Defendants had produced 53,253 documents consisting of over 191,994 pages. United States v. ExxonMobil Pipeline Co., 2014 U.S. Dist. LEXIS 81607, 5-8 (E.D. Ark. June 9, 2014).

pipeline

The Defendants suggested using predictive coding in light of the large volume of discovery, but the Plaintiff the United States did not agree with the use of predictive coding (at least since the filing of the motions). ExxonMobil Pipeline, at *6. Moreover, the parties did not seek relief from the Court on the use of predictive coding, other than to order the parties meet and confer. ExxonMobil Pipeline, at *6-7.

The Defendants explained that using traditional review with 50 attorneys that document review could be completed by the end of June 24 and production by the end of August 2014. ExxonMobil Pipeline, at *6.

The United States disagreed with the Defendants assumption of lawyers only reviewing 250 documents/files a day. Moreover, the Defendants did not raise concerns about document review when they entered an agreed upon scheduling order in October 2013. ExxonMobil Pipeline, at *6-7.

The Court acknowledged that the Defendants had a large volume of discovery to review. Moreover, it was unclear if the parties had agreed to a review methodology before the Court issued its order. Regardless, the Court ordered the Defendants to complete their review and production by July 10, 2014, absent good cause. ExxonMobil Pipeline, at *7-8.

Bow Tie Thoughts

Most attorneys do not think about document review strategies at the beginning of a case. They should. Discovery is the backbone of civil litigation. Unless you know the information you have to review, strategies to maximize efficiency, and reviewing for claims or defenses, document review can be a nightmare experience.

This case does not go into why the Defendants sought agreement from the Plaintiff on the use of predictive coding. I do not agree with that strategy, unless a specific review protocol was ordered at the Rule 16 conference that the producing party wanted to change.

The issue with a document production is whether or not the production is adequate. Lawyers should agree to the subject matter of the case, custodians, data ranges, and other objective information that goes to the merits of the lawsuit. When lawyers start asking each other for permission on whether they can use predictive coding, visual analytics, clustering, email threading, or any other technology, civil litigation becomes uncivil. Case in point: the Plaintiffs argued the Defendants could review more than 250 documents a day in this case. Such disputes turn into an academic fight over how much lawyers can read and analyze in a 9-hour workday. The end result of such motion practice would be a Judge ordering lawyers to read faster.

My advice is to focus on the merits and not derail the case with a fight over what review technology can be used. Fight over whether the production is adequate, not what whether you can use predictive coding.

Arkansas Bar Association Annual Meeting

I had the honor of speaking at the 2014 Arkansas State Bar Annual meeting on eDiscovery Ethics and new trends in eDiscovery in Hot Springs, Arkansas. I had an amazing time and greatly appreciated the hospitality of the Arkansas Bar Association.

Arkansas_Ethics-Presentation

My new Ethics seminar is a Star Trek themed presentation based on the Ingenuity 12 LLC v Doe case, that also covered the evolving rules of attorney and judicial ethics on social media; how to conduct a reasonable inquiry with ESI; the duty of candor to the Court; compliance with Rule 11 in an age of Terabytes; Production obligations under FRCP 26(g); and the duty of confidentiality and computer security. It was also a ton of fun.

MirrorSpock-Agonizer

My two sessions were attended by 150-200 attorneys in the convention center exhibit hall. We also covered the proposed California ethics opinion on eDiscovery competency, which will require attorneys to be competent in the following areas:

Initially assess eDiscovery needs and issues, if any;

Implement appropriate ESI preservation procedures, including the obligation to advise a client of the legal requirement to take actions to preserve evidence, like electronic information, potentially relevant to the issues raised in the litigation;

Analyze and understand a client’s ESI systems and storage;

Identify custodians of relevant ESI;

Perform appropriate searches;

Collect responsive ESI in a manner that preserves the integrity of that ESI;

Advise the client as to available options for collection and preservation of ESI;

Engage in competent and meaningful meet and confer with opposing counsel concerning an eDiscovery plan; and

Produce responsive ESI in a recognized and appropriate manner.

Proposed Formal Opinion Interim No. 11-0004 (ESI and Discovery Requests) (State Bar of California).

Khan-FormofProduction

This proposed opinion has teeth, because lawyers who are not competent in eDiscovery should either learn how to handle eDiscovery issues, associate with those who are, which can be retaining an expert, or decline representation. Given the fact virtually all civil litigation has data of some kind in it, the third option could end careers.

ESI-Tribbles

“Tweeting Discovery,” my second session, explored recent social media/eDiscovery issues. The material also covered two of the new and proposed statutes limiting the use of Drones by law enforcement. The Drone limitations would prohibit law enforcement to use Drones to gather evidence, images, sounds, or data. The key exceptions would be in a high risk of terrorist attack, finding a mission person, preventing imminent loss of life, or a search warrant (limited in scope to only person subject to the search), and data retention rules. See, 2013 ILL. ALS 569 and 2013 Bill Text NC H.B. 312.

I want to thank the Arkansas Bar Association for their hospitality. I had a corner suite in the Arlington Hotel, which included a Washington, DC, theme, complete with a large sitting room and conference room. Truly a lot of fun. I even took a moment to enjoy the suite and record this promo video for The Legal Geeks submission to the Geekie Awards:

 

Don’t Forget to Produce Email Attachments

Thank You Litigation World! This article won the LitigationWorld Pick of the Week award. The editors of LitigationWorld, a free weekly email newsletter for litigators and others who work in litigation, give this award to one article every week that they feel is a must-read for this audience.litigationworld-800

A defendant law firm in a fee dispute were ordered to produce specific email communications. The law firm produced email messages in PDF format without attachments. The Defendants claimed in a meet and confer they could not produce attachments from the server, but did not explain why. Skepnek v. Roper & Twardowsky, LLC, 2014 U.S. Dist. LEXIS 11894, at *3-4 (D. Kan. Jan. 27, 2014)

LeslieCrystal_Really_EmailIt is never good to have a Judge state, “It is unclear why defendants claim that it is impossible to include every attachment to the produced e-mails but somehow, they are able to produce specific attachments upon request.” Skepnek, at *4.

The Defendants attempted to make the case about the Plaintiffs not stating the form of production in their request.

The Judge did not take the bait and focused on the real issue in the case: the failure to produce the responsive files. Skepnek, at *6.

The Court ordered the production of the attachments, explaining its order as follows:

Defendants offer no excuse for their failure to produce responsive documents except that plaintiffs never requested the documents in native format. Plaintiffs simply want the documents that the court ordered defendants to produce, regardless of format. Because plaintiffs failed to specify a form for producing the electronically stored e-mails and attachments, defendants were required under Rule 34(b)(2)(E)(ii) either to produce the e-mails and attachments in the form (1) in which they are ordinarily maintained, or (2) “in a reasonably usable form.” Defendants failed to produce the attachments at all. Defendants also failed to show PDF format is the form in which their e-mails and attachments are ordinarily maintained.

Skepnek, at *6.

Bow Tie Thoughts

Lawyers often get into trouble with the production of electronically stored information because they do not retain anyone to handle the collection, processing or production of data. Many think their client’s IT staff can somehow “just do it” and avoid the cost of hiring a service provider.

Problem with that logic: You’re doing it wrong.

That is a lot like thinking an auto mechanic charges too much for a break job, so just have your 10 year old do it instead. Since the kid made a great Pinewood Derby car, he should be able to fix the Audi. What could possibly go wrong?

The duty of competency requires lawyers to hire experts to solve technical issues. The collection of ESI and processing are two such areas. Moreover, the technology is constantly advancing. I have watched very impressive product demonstrations of many software applications. Producing email with attachments is something service providers have been doing for over a decade. There are even YouTube videos showing how the technology works. There really is not an excuse from a technological perspective on why email was not produced with attachments in native file format.