Close
Enter your
text here

Production

Production is the “Ringo” of the eDiscovery Phases – Best of eDiscovery Daily
 

God Save the Queen!  Today is our last full day in London and we’re planning to visit Westminster Abbey, which is where all of England’s kings and queens are crowned.  For the next two weeks except for Jane Gennarelli’s Throwback Thursday series, we will be re-publishing some of our more popular and frequently referenced posts.  Today’s post is a topic where people can frequently make mistakes, causing production delays and costly rework.  Enjoy!

Most of the “press” associated with eDiscovery ranges from the “left side of the EDRM model” (i.e., Information Management, Identification, Preservation, Collection) through the stages to prepare materials for production (i.e., Processing, Review and Analysis).  All of those phases lead to one inevitable stage in eDiscovery: Production.  Yet, few people talk about the actual production step.  If Preservation, Collection and Review are the “John”, “Paul” and “George” of the eDiscovery process, Production is “Ringo”.

It’s the final crucial step in the process, and if it’s not handled correctly, all of the due diligence spent in the earlier phases could mean nothing.  So, it’s important to plan for production up front and to apply a number of quality control (QC) checks to the actual production set to ensure that the production process goes as smooth as possible.

Planning for Production Up Front

When discussing the production requirements with opposing counsel, it’s important to ensure that those requirements make sense, not only from a legal standpoint, but a technical standpoint as well.  Involve support and IT personnel in the process of deciding those parameters as they will be the people who have to meet them.  Issues to be addressed include, but not limited to:

  • Format of production (e.g., paper, images or native files);
  • Organization of files (e.g., organized by custodian, legal issue, etc.);
  • Numbering scheme (e.g., Bates labels for images, sequential file names for native files);
  • Handling of confidential and privileged documents, including log requirements and stamps to be applied;
  • Handling of redactions;
  • Format and content of production log;
  • Production media (e.g., CD, DVD, portable hard drive, FTP, etc.).

I was involved in a case a couple of years ago where opposing counsel was requesting an unusual production format where the names of the files would be the subject line of the emails being produced (for example, “Re: Completed Contract, dated 12/01/2011”).  Two issues with that approach: 1) The proposed format only addressed emails, and 2) Windows file names don’t support certain characters, such as colons (:) or slashes (/).  I provided that feedback to the attorneys so that they could address with opposing counsel and hopefully agree on a revised format that made more sense.  So, let the tech folks confirm the feasibility of the production parameters.

The workflow throughout the eDiscovery process should also keep in mind the end goal of meeting the agreed upon production requirements.  For example, if you’re producing native files with metadata, you may need to take appropriate steps to keep the metadata intact during the collection and review process so that the metadata is not inadvertently changed. For some file types, metadata is changed merely by opening the file, so it may be necessary to collect the files in a forensically sound manner and conduct review using copies of the files to keep the originals intact.

Tomorrow, we will talk about preparing the production set and performing QC checks to ensure that the ESI being produced to the requesting party is complete and accurate.

So, what do you think?  Have you had issues with production planning in your cases?  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.

Our 1,000th Post! – eDiscovery Milestones

When we launched nearly four years ago on September 20, 2010, our goal was to be a daily resource for eDiscovery news and analysis.  Now, after doing so each business day (except for one), I’m happy to announce that today is our 1,000th post on eDiscovery Daily!

We’ve covered the gamut in eDiscovery, from case law to industry trends to best practices.  Here are some of the categories that we’ve covered and the number of posts (to date) for each:

We’ve also covered every phase of the EDRM (177) life cycle, including:

Every post we have published is still available on the site for your reference, which has made eDiscovery Daily into quite a knowledgebase!  We’re quite proud of that.

Comparing our first three months of existence to now, we have seen traffic on our site grow an amazing 474%!  Our subscriber base has more than tripled in the last three years!  We want to take this time to thank you, our readers and subcribers, for making that happen.  Thanks for making the eDiscoveryDaily blog a regular resource for your eDiscovery news and analysis!  We really appreciate the support!

We also want to thank the blogs and publications that have linked to our posts and raised our public awareness, including Pinhawk, Ride the Lightning, Litigation Support Guru, Complex Discovery, Bryan University, The Electronic Discovery Reading Room, Litigation Support Today, Alltop, ABA Journal, Litigation Support Blog.com, InfoGovernance Engagement Area, EDD Blog Online, eDiscovery Journal, e-Discovery Team ® 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!

I also want to extend a special thanks to Jane Gennarelli, who has provided some serial topics, ranging from project management to coordinating review teams to what litigation support and discovery used to be like back in the 80’s (to which some of us “old timers” can relate).  Her contributions are always well received and appreciated by the readers – and also especially by me, since I get a day off!

We always end each post with a request: “Please share any comments you might have or if you’d like to know more about a particular topic.”  And, we mean it.  We want to cover the topics you want to hear about, so please let us know.

Tomorrow, we’ll be back with a new, original post.  In the meantime, feel free to click on any of the links above and peruse some of our 999 previous posts.  Now is your chance to catch up!  😉

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.

When Reviewing and Producing Documents, Don’t Forget the “Mother and Child Reunion” – eDiscovery Best Practices

I love Paul Simon’s music.  One of my favorite songs of his is Mother and Child Reunion.  Of course, I’m such an eDiscovery nerd that every time I think of that song, I think of keeping email and attachment families together.  If you don’t remember the Mother and Child Reunion, you might provide an incomplete production to opposing counsel.

BTW, here’s a little known fact: Paul Simon took the title of the song Mother and Child Reunion from the name of a chicken-and-egg dish he noticed on a Chinese restaurant’s menu.

Like the rest of us, attorneys don’t like to feel shortchanged, especially in discovery.  While there are exceptions, in most cases these days when an email or attachment is deemed to be responsive, the receiving party expects to also receive any “family” members of the responsive file.  Attorneys like to have the complete family when reviewing the production from the other side, even if some of the individual files aren’t responsive themselves.  Receiving an email without its corresponding attachments or receiving some, but not all, of the attachments to an email tends to raise suspicions.  Most attorneys don’t want to give opposing counsel a reason to be suspicious of their production, so parties typically agree to produce the entire email “family” in these cases.  Here’s a scenario:

The case involves a dispute over negotiated gas rate agreements between energy companies and Federal Energy Regulatory Commission (FERC) approval of those rate agreements.  A supervisor at the company verbally requests a copy of a key contract from one of his employees, along with the latest FERC filings and the employee emails a copy of the contract and FERC filing summary attached to an email with the subject “Requested files” and the body stating “Here you go…” (or something to that effect).  A search for “negotiated w/2 (gas or rate or agreement)” retrieves the contract attachment, but not the email, which doesn’t really have any pertinent information on it, or the FERC filing summary.  Only part of the email “family” is responsive to the search.

If it’s important to produce all communications between parties at the company regarding negotiated gas agreements, this communication could be missed – unless your review protocol includes capturing the family members of responsive files and your review software provides an option to view the family members of responsive files and include them in search results.  I underlined “option” because there are still a few cases where parties agree to limit production to actual responsive files and not produce the families (though, in my recent experience, those cases are exceptions).

If your case isn’t one of the exceptions, make sure you have a well thought out protocol and robust software for including family members in your search results and in your document reviews for responsiveness, as well as automated and manual Quality Assurance (QA) and Quality Control (QC) checks to ensure your production contains complete family groups.

So, what came first, the chicken or the egg?  It doesn’t matter, as long as the family group is intact.  🙂

So, what do you think?  How do you handle family groups in discovery?  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.

It’s Friday at 5 and I Need Data Processed to Review this Weekend – eDiscovery Humor

We’ve referenced Ralph Losey’s excellent e-Discovery Team® blog several times before on this blog – it’s a great read and you won’t find a blog that gets more in depth than his does (he has also been gracious enough to participate in our thought leader interview series for the last three years).  And, as Ralph has demonstrated before, he has a sense of humor when it comes to electronic discovery.

In his latest post, Are You The Lit Support Tech?, Ralph takes a humorous look at “what it is like on a Friday afternoon in the Litigation Support Departments of most law firms”.  Or so it seems sometime.  Like before, 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.

Anyway, the video involves a law firm partner coming to the lit support tech on a Friday afternoon and asking for help to process data for ten custodians so that he can review over the weekend as the production is due Monday.  “When did you receive the request?”, asks the tech.  “30 days ago”, says the partner, “Why?”.  “No reason”, says the tech.

The video continues with the partner telling the tech not to worry “it’s only 15 gigabytes…not such a big number”.  When the tech says that it’s over a million pages and he will have to process it and load it into their review platform, the partner says “I don’t have time for all the processing and stuff, just print it out and load it in my car.”

OK, so part of the humor is that it’s a bit farfetched (hopefully).  Ralph notes that because he no longer has to supervise a litigation support department (because Jackson Lewis outsources all of its nonlegal electronic data discovery work), his “Friday afternoons are much nicer”.

It’s the vendor that has to deal with these last minute requests.  At CloudNine Discovery, we can relate to the lit support tech who receives 15 gigabytes (or even more) on a Friday afternoon to process for weekend review – we get those types of requests more often than you think and our staff often works late Fridays to get the client’s data ready.  It goes with the territory.  So, we don’t make big plans on Friday night so that you can enjoy yours!

So, what do you think?  Have you had to deal with last minute eDiscovery requests?  If so, how do you handle them?  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.

Other Production Parameters from a Provider’s Point of View – eDiscovery Best Practices

Yesterday, we began to discuss some of the production parameters that CloudNine Discovery collects from our clients in order to ensure that the production includes the correct documents in the required format.  But, wait – there’s more!  Let’s take a look at some other examples of information we collect from our clients.

  • Naming Structure for Files: Files that are produced follow some sort of naming convention and structure, typically either the original file name or some sort of naming convention that involves a unique identifying prefix followed by a zero-filled number (e.g., ABC000001.{file extension}).
  • Image Endorsements: Of course, images that are produced typically include a Bates number on each page that involves a unique identifying prefix followed by a zero-filled number (see example above), but endorsements can also include special endorsements such as a confidential stamp, so we provide a place on our questionnaire for clients to provide additional endorsement instructions for text and placement.
  • Metadata Fields and/or Tags to Be Produced: If the client is producing metadata, it’s obviously important to know the fields to be produced and the desired order.  We also ask them to specify the delivery format – the typical formats are CSV (comma separated values, which can be loaded into Excel) or DAT (data) file.
  • Populate Production Numbers Back into Database: When clients produce documents, they typically want to track the production numbers, so we give them the option for us to create new fields in their (OnDemand®) database with those production numbers.
  • Branded Images Back into Database: We also offer the same option for putting images branded with the Bates numbers and other endorsements back into the database, so that the client can easily reference the production number when looking at the page.
  • Load File: Often parties agree to produce load files to make it easy for opposing counsel to load the documents and metadata into their own eDiscovery platform, so we will create load files in several industry standard formats to support that requirement.
  • Delivery Method for Production: There are several options for delivering documents and data including CD or DVD, portable hard drive or electronically via File Transfer Protocol (FTP).
  • Where to Send Production: If the client selects CD, DVD or Portable Hard Drive, we require the Name, Street Address and Phone Number where the media is being delivered, if they select FTP, we need an FTP address (and any credentials, if necessary, to access it).
  • Name of Production Set: We request that each production set be uniquely named for later reference purposes, which is especially useful when there are multiple productions to track.
  • Other Instructions: Believe it or not, all of the parameters that we’ve identified over the past two days don’t cover every scenario, so we provide a place on the questionnaire to provide any other instructions.  Those can range from special handling for other file types, extra copies requested, etc.

As you can see, we collect a lot of information from our clients at production time to ensure a proper production.  There are a lot of variables to consider, so it’s important to be consider those variables not just when producing, but WAY back at the beginning of the case, to ensure that you will be able to fulfill your discovery obligations to opposing counsel.  Hope this list of parameters was helpful.

So, what do you think?  How do you ensure proper productions?  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.

Production from a Provider’s Point of View – eDiscovery Best Practices
 

We sometimes forget that the end goal of the discovery process is production: to produce responsive electronically stored information (ESI) to opposing counsel.  But, do you realize how many parameters and potential permutations there can be to the production process?  Let’s take a look.

eDiscovery providers like (shameless plus warning!) CloudNine Discovery handle productions for our clients routinely, (in our case, often out of our eDiscovery review application, OnDemand®).  When a client asks for a production, there are a series of questions to ask to ensure that the production includes the correct documents in the required format.  To ensure that and avoid potential confusion, we provide a questionnaire to the client to complete to define the parameters of that production.  Examples of information we collect from our clients:

  • Documents to be produced: Typically, we expect the client to identify a tag that was applied to the documents (especially when the documents are in OnDemand) to be used to identify the documents to be produced (e.g., To Be Produced, Responsive-Produce, etc.) and confirm the count of documents that are included in that tag.  If the count doesn’t match the tag, we resolve with the client before proceeding.
  • Output Formats to Include: Productions can be native or image, may or may not include Optical Character Recognition (OCR) or extracted text and may or may not include metadata.  It’s important to confirm the formats to be produced, which can include all or just some of the available formats.
  • Format of Images: If images are to be produced, we confirm whether they single or multi-page TIFF, or in Adobe PDF.
  • Format of OCR/Extracted Text Files: OCR files can also be produced either in single or multi-page files, so we enable the client to specify the format.
  • Handling of Excel Files: Because they are often not formatted for printing, Excel files often don’t image well and generate a high number of image pages.  So, we provide options for producing a placeholder image along with the native Excel file (which is the default option), or TIFFing all or part of the Excel document.
  • Handing of AutoCad Files: Though less common, AutoCad DWG files can also be problematic to convert to TIFF, so we provide a placeholder and native option for this file type as well.
  • Handling of Redactions: If redactions are present, we confirm the production of documents with the redactions present.  We also recommend that (and assist clients with) removal of redacted text from OCR files of the redacted images to ensure that there are no inadvertent disclosures of privileged or confidential information via those text files.

This is just the beginning of what we ask clients.  Tomorrow, we will cover other information we collect to ensure a proper production.

So, what do you think?  How do you ensure proper productions?  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.

Privilege Not Waived on Defendant’s Seized Computer that was Purchased by Plaintiff at Auction – eDiscovery Case Law

In Kyko Global Inc. v. Prithvi Info. Solutions Ltd., No. C13-1034 MJP (W.D. Wash. June 13, 2014), Washington Chief District Judge Marsha J. Pechman ruled that the defendants’ did not waive their attorney-client privilege on the computer of one of the defendants purchased by plaintiffs at public auction, denied the defendants’ motion to disqualify the plaintiff’s counsel for purchasing the computer and ordered the plaintiffs to provide defendants with a copy of the hard drive within three days for the defendants to review it for privilege and provide defendants with a privilege log within seven days of the transfer.

In this fraud case, after several of the named defendants settled and confessed to judgment, the plaintiffs obtained a Writ of Execution in which the King County (Washington) Sheriff seized various items of personal property, including a computer owned by one of the defendants.  The computer was sold at a public auction, and an attorney for the plaintiffs outbid a representative sent by the defendants and purchased the computer.  The plaintiffs sent the computer to a third party for analysis and requested a ruling as to the admissibility of potentially attorney-client privileged documents contained on it, while the defendants contended the actions of the plaintiffs violated ethical rules, and requested that the plaintiffs return the computer to defendants, and also requested that the plaintiff’s attorneys should be disqualified from the case.

With regard to the plaintiff’s actions, Judge Pechman ruled that plaintiffs’ acquisition of the computer was not “inherently wrongful”, noting the plaintiffs’ claim that they had not reviewed the materials on the computer at the time of the motion.  She also determined that plaintiff’s “use of a third party vendor to make a copy of the hard drive is not equivalent to metadata mining of documents produced through the normal discovery process, because whereas the hard drive might plausibly contain many documents unprotected by any privilege, metadata mining is expressly aimed at the kind of information one would expect to be protected by attorney-client privilege and/or work-product protections”.  As a result, she denied the defendants’ motion to disqualify the plaintiff’s counsel.

As for the waiver of privilege, Judge Pechman used a balancing test to determine waiver “that is similar to Rule 502(b)”, which included these factors:

  1. the reasonableness of precautions taken to prevent disclosure,
  2. the amount of time taken to remedy the error,
  3. the scope of discovery,
  4. the extent of the disclosure, and
  5. the overriding issue of fairness.

Using the analogy of where “an opposing party discovers a privileged document in the other party’s trash”, Judge Pechman considered the potential waiver of privilege.  However, because the defendant stated in a declaration that she had “someone at her office” reformat the hard drive on the computer and install a new operating system and believed her documents had been erased and were not readily accessible, she related it “to the memo torn into 16 pieces than a document simply placed in a trash can without alteration”.

As a result, Judge Pechman determined that given “Defendants’ prompt efforts to remedy the error by filing a motion with the Court and the general sense that parties should not be able to force waiver of attorneyclient privilege through investigative activities outside the discovery process and a superior understanding of the relevant technology, the Washington balancing test weighs against waiver.”  She also and ordered the plaintiffs to provide defendants with a copy of the hard drive within three days for the defendants to review it for privilege and provide defendants with a privilege log within seven days of the transfer.

So, what do you think?  Were the plaintiff’s counsel actions ethical?  Should privilege have been waived?  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.

Texas Supreme Court Reverses Spoliation Ruling, Remands Case for New Trial – eDiscovery Case Law
 

In Brookshire Bros., Ltd. v. Aldridge (Tex. July 3, 2013), the Supreme Court of Texas determined “that imposition of the severe sanction of a spoliation instruction was an abuse of discretion” in the trial court, reversed the court of appeals' judgment and remanded the case for a new trial.

In this case, the plaintiff Aldridge (who is the respondent in the appeal) slipped and fell at the defendant’s (who is the petitioner in the appeal) store and sued for damages after the defendant stopped paying for medical expenses.  The plaintiff’s fall was captured on surveillance video and the defendant preserved the video footage from the time plaintiff entered the store until shortly after he fell, but did not preserve the remainder of the video, which was “presumably recorded over” by early the next month.

To recover in a slip-and-fall case, a plaintiff must prove, inter alia, that the defendant had actual or constructive knowledge of a dangerous condition on the premises such as a slippery substance on the floor and the plaintiff argued in the trial court that the defendant’s failure to preserve additional video footage amounted to spoliation of evidence that would have been helpful to the key issue of whether the spill was on the floor long enough to give the defendant a reasonable opportunity to discover it.

As a result, the plaintiff moved for a spoliation jury instruction and the trial court: 1) allowed the jury to hear evidence bearing on whether the defendant spoliated the video, 2) submitted a spoliation instruction to the jury, and 3) permitted the jury to decide whether spoliation occurred during its deliberations on the merits of the lawsuit.  The jury ruled in favor of the plaintiff and awarded him over $1 million in damages. The court of appeals affirmed the trial court's judgment on the verdict, holding that the trial court did not abuse its discretion in admitting evidence of spoliation or charging the jury with the spoliation instruction.

After analysis of the law associated with spoliation, the Supreme Court stated that “the harsh remedy of a spoliation instruction is warranted only when the trial court finds that the spoliating party acted with the specific intent of concealing discoverable evidence” and that a “failure to preserve evidence with a negligent mental state may only underlie a spoliation instruction in the rare situation in which a nonspoliating party has been irreparably deprived of any meaningful ability to present a claim or defense”.  As a result, the Court held “that a trial court's finding of intentional spoliation pursuant to the analysis set forth above is a necessary predicate to the proper submission of a spoliation instruction to the jury.”

While issuing the caveat that “[o]n rare occasions, a situation may arise in which a party's negligent breach of its duty to reasonably preserve evidence irreparably prevents the nonspoliating party from having any meaningful opportunity to present a claim or defense”, the court determined that there was no evidence of the requisite intent to conceal or destroy relevant evidence or that plaintiff was “irreparably deprived of any meaningful ability to present his claim” and held that the trial court therefore abused its discretion in submitting a spoliation instruction, reversed the court of appeals' judgment and remanded the case for a new trial.

So, what do you think?  Was the reversal of the ruling the right decision or should the sanction for spoliation of evidence have stood?  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.

Failure to Preserve Cloud-Based Data Results in Severe Sanction for Defendant – eDiscovery Case Law
 

In Brown v. Tellermate Holdings, 2:11-cv-1122 (S.D. Ohio Jul 1, 2014), Magistrate Judge Terence Kemp granted plaintiffs’ motion for judgment and motion to strike, ruling that the defendant could not “present or rely upon evidence that it terminated the Browns' employment for performance-related reasons” and enabling the plaintiffs to use documents produced by the defendant “designated as attorneys'-eyes-only” to be used by the plaintiffs “without restriction”, due to the defendant’s failure to preserve or produce data from their Salesforce.com database.

You have to love an opinion that begins like this:

“There may have been a time in the courts of this country when building stone walls in response to discovery requests, hiding both the information sought and even the facts about its existence, was the norm (although never the proper course of action). Those days have passed. Discovery is, under the Federal Rules of Civil Procedure, intended to be a transparent process.”

That’s how this lengthy opinion began in this case where the plaintiffs, former sales agents, sued the defendant for age discrimination after they were terminated.  The defendant responded by arguing that the terminations were performance related.  To address that argument, the plaintiffs sought records from the defendant’s through salesforce.com to demonstrate that they consistently met or exceeded their quotas. In response, the defendant “with the participation of its counsel, either intentionally or inadvertently failed to fulfill certain of its discovery obligations, leading to a cascade of unproductive discovery conferences, improperly-opposed discovery motions, and significant delay and obstruction of the discovery process.”  As Judge Kemp described, the defendant’s counsel:

  • “failed to uncover even the most basic information about an electronically-stored database of information (the ‘salesforce.com’ database);
  • as a direct result of that failure, took no steps to preserve the integrity of the information in that database;
  • failed to learn of the existence of certain documents about a prior age discrimination charge (the "Frank Mecka matter") until almost a year after they were requested;
  • and, as a result of these failures, made statements to opposing counsel and in oral and written submissions to the Court which were false and misleading, and which had the effect of hampering the Browns' ability to pursue discovery in a timely and cost-efficient manner (as well as the Court's ability to resolve this case in the same way).”

One of the defendant’s attorneys went so far as to provide these reasons to the plaintiffs as to why they could not produce the information from Salesforce.com:

  • "Tellermate does not maintain salesforce.com information in hard copy format."
  • "Tellermate cannot print out accurate historical records from salesforce.com. . . ."
  • "[D]iscovery of salesforce.com information should be directed to salesforce.com, not Tellermate."

The defendant later claimed that it was “contractually prohibited from providing salesforce.com information” and that it “cannot access historical salesforce.com data” – both of which were untrue.

Ultimately, it became clear that the defendant had not exported or preserved the data from salesforce.com and had re-used the plaintiffs’ accounts, spoliating the only information that could have addressed the defendant’s claim that the terminations were performance related (the defendant claimed did not conduct performance reviews of its sales representatives).  As a result, Judge Kemp stated that the “only realistic solution to this problem is to preclude Tellermate from using any evidence which would tend to show that the Browns were terminated for performance-related reasons” and issued the following severe sanctions:

“Tellermate shall not, in connection with either the pending summary judgment motion or at trial, be entitled to present or rely upon evidence that it terminated the Browns' employment for performance-related reasons. The documents produced by Tellermate in April, 2013 and designated as attorneys'-eyes-only may be used by the Browns without restriction, subject to Tellermate's ability to redesignate particular documents as confidential under the existing protective order, provided it does so within fourteen days and has a good faith basis for so designating each particular document. Tellermate shall produce the remaining Frank Mecka documents to the Browns within fourteen days. Finally, Tellermate and its counsel shall pay, jointly, the Browns' reasonable attorneys' fees and costs incurred in the filing and prosecution of those two motions as well as in the filing of any motions to compel discovery relating to the salesforce.com and Frank Mecka documents.”

So, what do you think?  Do the sanctions fit the activities by the defendant?  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.

Transparency Reports for Other Companies – Social Tech eDiscovery

Over the past couple of weeks, we’ve taken a fresh look at Twitter’s Law Enforcement Policies and their latest Transparency Report to show government requests for data, looked at (for the first time) LinkedIn’s Privacy and Law Enforcement Data Request Guidelines and Transparency Report and, yesterday, looked at Facebook’s policies and Government Request Reports.  Today, we will look at Transparency Reports for other companies.

Many other high profile companies also provide reports showing government requests for data, not just social media companies.  Some, like Google, provide a highly interactive report to navigate to various types of requests, ranging from government requests to remove data to requests for information about their users.  Others, like Apple, provide a simple one page letter with broad ranges of information requests and accounts affected (Apple’s latest letter is over a year old).  Some are current (through the end of 2013 at least), others have not been updated to reflect data since the end of 2012.  Evidently, some companies take transparency more seriously than others!  With that in mind, here are links to reports for various high profile technology companies where you might have data:

I tried to pull up the Transparency Report for Pinterest, but the link immediately redirects to their help page, so it’s only transparent if you can read really fast!

Obviously, in these modern times, our data (both personal and professional) is stored by a number of companies and law enforcement entities will request data from those companies for investigative purposes.  It’s a good idea to know how those companies respond to those requests and what rights you have as a customer.

So, what do you think?  Have you needed to request user information from any high profile technology companies for litigation purposes?  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.