Lynch v. Experian Information Solutions, Inc.

CourtDistrict Court, D. Minnesota
DecidedJanuary 21, 2022
Docket0:20-cv-02535
StatusUnknown

This text of Lynch v. Experian Information Solutions, Inc. (Lynch v. Experian Information Solutions, Inc.) is published on Counsel Stack Legal Research, covering District Court, D. Minnesota primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Lynch v. Experian Information Solutions, Inc., (mnd 2022).

Opinion

UNITED STATES DISTRICT COURT DISTRICT OF MINNESOTA

Thomas Lynch et al., Case No. 0:20-cv-2535 (KMM/JFD) Plaintiffs, ORDER v.

Experian Information Solutions, Inc.,

Defendant.

This matter is before the Court on Defendant Experian Information Solutions, Inc.’s (“Experian”) Rule 72 Objection [ECF No. 58] to a nondispositive Order issued by Magistrate Judge John F. Docherty. In his Order, Judge Docherty granted in part and denied in part a motion to compel discovery filed by the plaintiffs. [Order, ECF No. 55; Pls.’ Mot., ECF No. 25]. The Court concludes that the Order is neither clearly erroneous nor contrary to law, and therefore overrules Experian’s Objections and affirms. I. Background In December 2020, Plaintiffs filed their Complaint pursuant to the Fair Credit Reporting Act (“FCRA”), alleging that Experian—a credit-reporting agency—negligently or willfully violated provisions of that Act by “failing to use reasonable procedures to assure maximum possible accuracy of information.” [ECF No. 1 at 11]. Specifically, Plaintiffs allege that Experian continued to report a particular account as owing for more than one year after it was in fact discharged in bankruptcy. They assert that this error was caused by Experian’s failure to follow reasonable procedures—procedures Experian refers to as “bankruptcy scrubs”—in contravention of 15 U.S.C. § 1681e(b). In August 2021, Plaintiffs filed a motion to compel discovery. By the time the Motion came before Judge Docherty, seven discovery requests remained at issue: 1 • RFP No. 15, which sought “[a]ll documents related to procedures followed and action taken to assure that pre-bankruptcy debts are reported as included in bankruptcy following the filing [sic] a bankruptcy;”

• RFP No. 16, which sought all documents related to the same but following the filing of a bankruptcy discharge;

• RFP No. 17, which sought “[a]ny documents or system manuals identifying how post-bankruptcy credit reports such as Plaintiffs’ are scrubbed through your automated process (if a person is involved please explain what involvement they have);”

• RFP No. 22, which sought “[a]ll agreements under which any public record vendor reported information or accessed information relating to Plaintiffs from one year preceding the filing of Plaintiff’s bankruptcy to the present;”

• RFP No. 26, which sought “all documents, memoranda emails, communication, manuals, guides, or other materials relating to your policy changes and implementation, including software and algorithms, as a result of the Settlement Order in Terri N. White v. Experian Information Solutions, Inc., CV 05-1070 DOC (MILGx) (C.D. Cal. Complaint filed Nov. 2, 2005);”

• RFP No. 32, which sought “[a]ll emails, communications, or memoranda sent or distributed to any and all Experian personnel that provided information related to any changes to Experian’s post-bankruptcy scrub procedures” as outlined in a prior stipulation; and

• Interrogatory No. 15, which asked Experian to “[i]dentify and describe all documents, data and information you provide to creditors, subscribers and/or third parties in response to a Soft Inquiry or Account Review Inquiry.”

[ECF Nos. 28-1, 28-2, 38-4]. Experian objected to these discovery requests, claiming that they were unduly burdensome, sought irrelevant information, or were duplicative of other requests. In his Order, Judge Docherty granted the motion in part and denied it in part. He found that RFP Nos. 15 and 16 were temporally overbroad and sought documents extending back to at

1 The parties had briefed other issues, but they were resolved or rendered moot prior to Judge Docherty’s Order. least 2008. He noted that the parties had subsequently agreed to limit RFP No. 32 to emails and documents since January 2020. He then held that all three requests, as written, were disproportionate to the needs of the case, but granted the motion to compel in part as to these requests as follows: Experian must produce all of the requested documents or emails, communications, or memoranda “that allow one experienced and knowledgeable about consumer

credit reporting—such as Plaintiffs’ counsel—to fully understand how Experian’s bankruptcy scrub worked” from May 1, 2019 through October 5, 2020. [ECF No. 55 at 8]. With respect to RFP No. 22, Judge Docherty held that most of the discovery sought was irrelevant, but granted the motion to compel as to communications and documents from third- party data providers “containing precatory language about the reliability of the information provided,” including “communications from Lexis Nexis to Experian, if any, warning Experian that the data was untrustworthy, unreliable, should be treated with caution, or similar words.” [ECF No. 55 at 16]. Finally, Judge Docherty denied the motion to compel entirely as to RFP Nos. 17 and 26 and Interrogatory No. 15.

Experian objects to the Order, arguing that the partial grant of the motion with respect to RFP No. 22 requires the production of irrelevant discovery, and that the partial grant with respect to RFP Nos. 15, 16, and 32 compels discovery that is disproportionate to the needs of this case. II. Analysis A. Standard of Review The Court’s review of a magistrate judge’s order on a nondispositive motion is “extremely deferential.” Scott v. United States, 552 F. Supp. 2d 917, 919 (D. Minn. 2008). Such an order should be overruled only where it is “clearly erroneous or contrary to law.” Fed. R. Civ. P. 72(a); L.R. 72.2(a)(3). “A finding is clearly erroneous when although there is evidence to support it, the reviewing court on the entire evidence is left with the definite and firm conviction that a mistake has been committed. A decision is contrary to law when it fails to apply or misapplies relevant statues, case law or rules of procedure.” Wells Fargo & Co. v. United States, 750 F. Supp. 2d 1049, 1050 (D. Minn. 2010) (cleaned up). Having thoroughly reviewed the record and the parties’ arguments, the Court concludes

that Judge Docherty’s Order was not clearly erroneous. Not only did Judge Docherty neither clearly err, nor misapply the law, the record reveals that he carefully and conscientiously assessed each issue, appropriately parsing each contested discovery request. B. Relevance Experian argues that Judge Docherty’s Order with respect to RFP No. 22 compels discovery that both he and the Plaintiffs have acknowledged is irrelevant. They argue that neither the nature nor accuracy of the data Experian received are at issue in this case, and that whether they received a warning regarding the reliability of that data is of no consequence in this litigation.

As an initial matter, the Court notes that Experian’s assertion that Judge Docherty “recognized” the irrelevancy of the discovery compelled is belied by even a cursory reading of his Order. The Order states that “most of the discovery Plaintiffs seek in RFP No. 22” is irrelevant, but that “[a] portion of the discovery sought by RFP No. 22 is relevant,” and then limits the compelled discovery to that which was deemed to be relevant. [ECF No. 55 at 15–16 (emphasis added)]. Likewise, the Court does not agree with Experian’s assertion that the compelled discovery—communications and documents from data providers “containing precatory language about the reliability of the information provided”—is irrelevant. A party is entitled “to obtain discovery regarding any non-privileged matter that is relevant to any party’s claim or defense.” Fed. R. Civ. P.

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

Related

Wells Fargo & Co. v. United States
750 F. Supp. 2d 1049 (D. Minnesota, 2010)
Scott Ex Rel. Scott v. United States
552 F. Supp. 2d 917 (D. Minnesota, 2008)
Coons v. BNSF Railway Co.
268 F. Supp. 3d 983 (D. Minnesota, 2017)
Heilman v. Waldron
287 F.R.D. 467 (D. Minnesota, 2012)
Shukh v. Seagate Technology, LLC
295 F.R.D. 228 (D. Minnesota, 2013)

Cite This Page — Counsel Stack

Bluebook (online)
Lynch v. Experian Information Solutions, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/lynch-v-experian-information-solutions-inc-mnd-2022.