Money Mailer, LLC v. Wade Brewer

District Court, W.D. Washington·Decided March 30, 2020·No. 2:15-cv-01215·Unknown

Opinion

UNITED STATES DISTRICT COURT AT SEATTLE MONEY MAILER, LLC, NO. C15-1215RSL Plaintiff, v. ORDER REGARDING DEFENDANT’S MOTION TO WADE G. BREWER, COMPEL Defendant. This matter comes before the Court on “Counterclaim Plaintiff Wade Brewer’s Motion to Compel Discovery Responses.” Dkt. # 163. Brewer asserts that Money Mailer has improperly produced thousands of pages of documents without identifying to which discovery request they are responsive, has refused to state whether all responsive documents have been produced, and has improperly withheld documents on which its in-house counsel was copied. Having reviewed the memoranda, declarations, and exhibits submitted by the parties, the Court finds as follows: A. Production of Electronically Stored Information (“ESI”) A party producing documents must either produce them as they are kept in the ordinary course of business or organize and label them to correspond to the categories in the discovery requests. Fed. R. Civ. P. 34(b)(2)(E)(i). Essentially, the Federal Rules of Civil Procedure require that the producing party give some structure to its production: a party may not dump voluminous, poorly organized documents on its adversary and force him or her “to rummage ORDER REGARDING DEFENDANT’S through piles of paper in search of what is relevant. To comply with the rule, a party must rationally organize[ ] its productions, so that the requesting party may readily identify documents, including ESI, that are responsive to [the] production requests.” Teledyne Instruments, Inc. v. Cairns, 2013 WL 5781274, at * 8 (M.D. Fla. Oct. 25, 2013) (alterations in original). The underlying assumption of Fed. R. Civ. P. 34(b)(2)(E)(i) is that businesses have an incentive to maintain their documents in a manner that allows the “systemized retrieval of relevant documents” when needed, so a production of documents as kept in the ordinary course of business will allow the opposing party to utilize that system and locate responsive documents. Andritz Sprout–Bauer, Inc. v. Beazer East, Inc., 174 F.R.D. 609, 630 (M.D. Pa. 1997). When producing ESI “as kept in the ordinary course of business,” the most straight-forward method is to produce the device(s) (or forensic copies of the device(s)) on which the files are stored. In the alternative, the responding party may choose to produce electronic files or documents rather than the devices. If it does so, however, it must ensure that the ESI is produced in a format that preserves the functional utility of the electronic information and provides sufficient information about the context in which the information was kept and organized by the producing party so that the requesting party can substantially replicate the system and find relevant documents. McKinney/Pearl Rest. Partners, L.P. v. Metro. Life Ins. Co., 322 F.R.D. 235, 249-50 (N.D. Tex. 2016). A file that is converted to another format solely for production, or for which the application metadata has been scrubbed or altered, is not produced as kept in the ordinary course of business. . . If a document is maintained on a hard drive or in a storage device in the form in which it is created and edited (its “native” format, in the technical sense of the term), it must be produced in native format to be produced as it is kept in the ordinary course of business. Preservation of format is ORDER REGARDING DEFENDANT’S important because conversion from native format may eliminate or degrade search and other information processing features (e.g., copy, paste, and sort). Such features may allow a user to identify relevant information in a document much more quickly, which would significantly enhance the value of a document to a business. Allowing a party to defeat this functionality would undermine the purpose of producing information as it is kept in the usual course of business. [In addition], the producing party must provide information about where the documents are kept and how they are organized. For documents stored on a computer or external storage device, this means providing system metadata indicating at least the file name and path for produced files. The files and system metadata[] must be organized in a manner that “permits systemized retrieval” of files based on the metadata. In other words, the requesting party must be able to search for and readily access files with particular characteristics (e.g. all .doc files in X folder). For emails, the relevant context is somewhat different. A user typically views emails not in a file browser, but in an email client. While the relevant organizational information for files viewed in a file browser is file name and path, the relevant information in an email client is the date the email was transmitted, perhaps along with the parties to the email (sender and recipients), and the subject line. McKinney/Pearl Rest. Partners, 322 F.R.D. at 250 (quoting Teledyne Instruments, 2013 WL 5781274, at * 9-10) (internal citations and footnotes omitted). Brewer complains that Money Mailer’s production was not labeled to correspond with his discovery requests, but Money Mailer was entitled to produce ESI as kept in the usual course of business instead. Brewer all but ignores this option, simply asserting that the ESI was not produced “with sufficient meta data to meaningfully identify the author, title, subject matter, or unique file information” for each record. Dkt. # 159 at ¶ 4. No specific documents were discussed and no examples were provided. In addition, Brewer failed to raise the alleged insufficiency of Money Mailer’s metadata during the parties’ meet and confer. Dkt. # 170 at ¶ 4. When Money Mailer pushed back against Brewer’s general claims of insufficiency with competent evidence that it produced its ESI as it is kept in the usual course of business and with ORDER REGARDING DEFENDANT’S extensive metadata, Brewer withdrew its objections to the vast majority of Money Mailer’s production (approximately 95%), instead focusing on 1,600 pages that were produced as part of plaintiff’s initial disclosures, 4,045 spreadsheets or worksheets “that were not produced in categorized folders,” and Money Mailer’s use of the word “almost” in its response memorandum. Dkt. # 172 at 3-4; Dkt. # 173 at ¶¶ 3-4. None of these arguments is availing. Initial disclosures are made pursuant to Fed. R. Civ. P. 26(a), which does not require either functionality or location/context when copies of documents are produced. With regards to the 4,045 documents specifically mentioned by Brewer in reply, he does not explain what a “categorized folder” is or how its absence impacted the functionality of the ESI produced or his ability to locate responsive documents contained therein. The folderol regarding Money Mailer’s use of the word “almost” is difficult to comprehend. Money Mailer noted that its “productions were almost exclusively email and attachments collected from Money Mailer’s custodians . . . .” Dkt. # 162 at ¶ 2. See also Dkt. # 169 at 6. As discussed above, the metadata that must be produced regarding emails varies from that which applies to other types of ESI. If there were a discovery violation associated with the production of emails - if, for example, Money Mailer has hidden key spreadsheets or Google Drive documents in dysfunctional .pdfs attached to the emails it produced - Brewer makes no effort to identify or substantiate such a violation. Rather, Brewer misinterprets Money Mailer’s statement regarding the content of its production as a statement that it produced its documents “almost” - but not entirely - in accordance

Free access — add to your briefcase to read the full text and ask questions with AI

Money Mailer, LLC v. Wade Brewer, (W.D. Wash. 2020).

Money Mailer, LLC v. Wade Brewer (Money Mailer, LLC v. Wade Brewer) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related