eDiscovery and Rule 30(b)(6): You Only Get What You Ask For (So Know Your Borders)

June 29, 2010

In Newman v. Borders, Inc., the United States District Court for the District of Columbia held that because plaintiff failed to notify defendant in a deposition notice that questions in a deposition would pertain to the defendant book’s email policies (or any electronically stored information (ESI) in general), plaintiff was not entitled to take further depositions despite the designated witness’s lack of knowledge regarding that subject matter. However, the Court further held that due to both parties’ failures to try hard enough to resolve the dispute and because discovery regarding document retention policies is a legitimate request, defendant was nonetheless ordered to answer specific questions posed by the Court regarding its email retention policies.

The lesson here is twofold: If you are going to depose witnesses regarding ESI, you must put the other party on notice of the scope of the deposition testimony being sought, or risk losing the opportunity to conduct further depositions. But regardless of whether you are the party who asks or the party who answers, you must be sure to make every reasonable effort to resolve discovery disputes. Continue reading »


“The Dog Ate It,” “We Didn’t Know About That Shared Directory,” and More Great eDiscovery Excuses

June 8, 2010

It happens all the time. To expedite the litigation process, parties reach agreements as to the scope and timing of electronic discovery. After all, who wants to delay litigation with the lengthy and expensive review of a universe of documents when you can significantly shrink that universe without compromising the quality of your production by agreeing on a set of specific custodians?

The parties in Wixon v. Wyndham Resort Development Corp. reached an agreement that by a specific date, Wyndham would produce electronically stored information (“ESI”) held by specific custodians that matched specific search terms. But what happened when, after the deadline, Wyndham revealed a stash of ESI found in a shared directory of a hard drive not allocated to a specific custodian? Does a document not directly linked to a specific custodian automatically become “nonresponsive”? Continue reading »