Mahboob v. Educational Credit Management Corporation

CourtDistrict Court, S.D. California
DecidedMarch 1, 2021
Docket3:15-cv-00628
StatusUnknown

This text of Mahboob v. Educational Credit Management Corporation (Mahboob v. Educational Credit Management Corporation) is published on Counsel Stack Legal Research, covering District Court, S.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Mahboob v. Educational Credit Management Corporation, (S.D. Cal. 2021).

Opinion

1 UNITED STATES DISTRICT COURT 2 SOUTHERN DISTRICT OF CALIFORNIA 3 4 Beheshta MAHBOOB, on behalf of Case No.: 15-cv-0628-TWR-AGS herself and all others similarly situated, 5 REPORT AND RECOMMENDATION

ON PLAINTIFF’S SANCTIONS 6 Plaintiffs, MOTION FOR EVIDENCE v. 7 SPOLIATION (ECF 183)

8 EDUCATIONAL CREDIT MANAGEMENT CORPORATION, 9

10 Defendant.

11 12 Plaintiff moves for sanctions, claiming that defendant destroyed relevant call data 13 and recordings. The question is whether defendant’s actions constitute spoliation and, if 14 so, what sanctions are appropriate. 15 BACKGROUND 16 Defendant Educational Credit Management Company purportedly recorded 17 incoming phone calls without consent. (ECF 153, at 2.) Plaintiff Beheshta Mahboob 18 maintains that during the class period, a caller put on hold for less than four seconds would 19 miss the automated warning that ECMC was recording the call, violating the California 20 Invasion of Privacy Act. (ECF 183-1, at 6 n.3.) 21 When receiving calls, ECMC uses a “dialer” that captures and stores information, 22 such as “the caller’s telephone number,” the “hold time,” and other data. (ECF 201-1, 23 at 11.) ECMC also creates an audio recording and retains the call data and call recording 24 for two years. (ECF 76-4, at 35-36.) 25 Mahboob alleges that after this case began, ECMC failed to suspend this two-year 26 data-retention policy, so months of relevant call data and recordings were improperly 27 deleted. (ECF 183-1, at 9-10.) Plaintiff’s initial complaint defined a yearlong putative class 28 period beginning March 20, 2014, “one year prior to the filing of this Complaint.” (ECF 1, 1 at 12.) But in February 2017, plaintiff discovered that call data—including hold-time 2 information—had been deleted for calls between March 20 and August 1, 2014. (See 3 ECF 76-4, at 36-37.) Without the call data, plaintiff could not identify callers and their hold 4 times. (ECF 183-1, at 6.) Plaintiff was forced to move the class-period start date to 5 August 2, 2014, shortening the period by over four months. (ECF 76-1, at 13 n.6.) 6 More recently, during a meet and confer, ECMC informed plaintiff that the call 7 recordings had also been deleted for calls between March 20 and September 29, 2014. 8 (ECF 183-2, at 3-4.) A timeline of relevant events follows: 9 10 Elapsed Time Date Event 11 Event Total Complaint filed. (ECF 1.) Plaintiff alleges a class 12 March 20, 2015 N/A N/A beginning March 20, 2014 . (ECF 1, at 12.) 13 ECMC discovers there was no litigation hold in 2016 N/A N/A 14 place. ECMC issues a hold. (ECF 76-4, at 37-38.) ELAPSED TIME BEFORE MOVING FOR SANCTIONS 15 Deposition of Darrell Mott reveals that ECMC lost 16 February 1, 2017 call data through August 1, 2014. (ECF 76-4, at 37.) 1 yr., 17 Motion for Class Certification filed. (ECF 76-1.) 1 mo., February 24, 2017 Plaintiff “narrows” the class period due to deleted 12 days 18 call data. (Id., at 13 n.6.) 19 March 13, 2018 Motion for Stay granted. (ECF 143.) 20 3 yrs., March 13, 2018 Stay begins to permit appeal of class certification 1 yr., 5 mo., 21 January 22, 2020 Amended Complaint filed. (ECF 153.) 11 mo., 30 days 22 15 days February 28, 2020 Stay lifted (ECF 155.) 23 February 28, 2020 Case continues. 24 At a meet and confer, plaintiff discovers that call 5 mo., 25 July 10, 2020 recordings from March 20 to September 29, 2014, 3 days have also been deleted. (ECF 183-2, at 3-4.) 26 July 31, 2020 Plaintiff’s Motion for Sanctions filed. (ECF 183.) 27 28 1 DISCUSSION 2 A. Timeliness 3 As a threshold issue, defendant complains that this motion is late. (See ECF 188, 4 at 8-9.) An “unreasonable delay can render a spoliation motion untimely.” Cottle-Banks v. 5 Cox Commc’ns, Inc., No. 10CV2133-GPC WVG, 2013 WL 2244333, at *16 (S.D. Cal. 6 May 21, 2013). Though there is no set deadline, spoliation motions “should be filed as soon 7 as reasonably possible after discovery of the facts that underlie the motion.” Id. (citation 8 omitted). Federal courts have denied such motions when the moving party knew about the 9 evidence destruction and failed to move for sanctions within a reasonable time. See, e.g., 10 id. (denying as untimely a spoliation motion filed “almost nine months” after plaintiff 11 knew); Scalia v. Cnty. of Kern, No. 117CV1097NONEJLT, 2020 WL 5959905, at *7 (E.D. 12 Cal. Oct. 8, 2020) (finding a sanctions motion untimely because “Plaintiff fails to offer any 13 reason for the [nine-month] delay in raising the issue of spoliation to the Court”). In 14 addition, spoliation motions are subject to chambers discovery rules. See Cottle-Banks, 15 2013 WL 2244333, at *16 (rejecting a spoliation motion for, among other things, violating 16 a chambers-rule 30-day deadline to bring discovery disputes (citation omitted)). 17 1. Deleted Call Data 18 Plaintiff first discovered that call data was missing during a February 1, 2017 19 deposition. (See ECF 76-4, at 36-38.) But instead of immediately seeking sanctions, 20 plaintiff declared that “[a]t the appropriate time, Plaintiff will ask the Court to impose 21 evidentiary [penalties] and/or issue sanctions against ECMC.” (ECF 76-1, at 13 n.6.) 22 Plaintiff then waited almost three and a half years to move for sanctions. (See ECF 183.) 23 Plaintiff Mahboob’s explanation is that the case was stayed from March 2018 until 24 February 2020, pending an appeal. (ECF 191, at 4; see ECF 155.) But that stay only lasted 25 two years. There was ample opportunity to seek sanctions in the remaining year and a half, 26 a far longer period than the nine-month delays deemed too long in Cottle-Banks and Scalia. 27 In fact, plaintiff sought court intervention for two unrelated discovery disputes in April and 28 July 2017, months after learning about the lost call data. (See ECF 86; ECF 107.) Finally, 1 plaintiff’s delay contravenes this Court’s chambers rules, which require that any discovery 2 motion be filed “within 30 days of the date the dispute first arose.” Chambers Civ. R. 2. 3 Because waiting a year and a half to bring a spoliation motion is unreasonable and violates 4 chambers rules, the portion of the motion concerning call data should be denied as 5 untimely. 6 2. Deleted Call Recordings 7 By contrast, the portion of the motion regarding deleted call recordings is timely. 8 During a July 10, 2020 meet and confer, plaintiff learned that six months of “actual 9 recordings for call data . . . had been deleted.” (ECF 183-2, at 3-4.) Plaintiff moved for 10 sanctions three weeks later, on July 31, 2020. (ECF 183.) A three-week delay is reasonable 11 and falls within the timeframe allowed by chambers rules. 12 B. Spoliation of Call Recordings 13 The Court will thus focus solely on plaintiff’s charge of call-recording spoliation. 14 Spoliation is “the destruction or significant alteration of evidence, or the failure to preserve 15 property for another’s use as evidence, in pending or future litigation.” Kearney v. Foley 16 & Lardner, LLP, 590 F.3d 638, 649 (9th Cir. 2009) (citation omitted). To prove spoliation 17 of electronically stored information, including “sound recordings,” Fed. R. Civ. 18 P. 34(a)(1)(A), there are three requirements: (1) the ESI “should have been preserved in 19 the anticipation or conduct of litigation”; (2) that ESI “is lost because a party failed to take 20 reasonable steps to preserve it”; and (3) “it cannot be restored or replaced through 21 additional discovery.” Fed. R. Civ. P. 37(e). 22 1. Duty to Preserve 23 “As soon as a potential claim is identified, a litigant is under a duty to preserve 24 evidence which it knows or reasonably should know is relevant to the action.” Cottle- 25 Banks, 2013 WL 2244333, at *13 (citation omitted).

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

Related

Michael Lacey v. Joseph Arpaio
693 F.3d 896 (Ninth Circuit, 2012)
Kearney v. Foley & Lardner, LLP
590 F.3d 638 (Ninth Circuit, 2009)
Zubulake v. UBS Warburg LLC
229 F.R.D. 422 (S.D. New York, 2004)
Lewis v. Ryan
261 F.R.D. 513 (S.D. California, 2009)

Cite This Page — Counsel Stack

Bluebook (online)
Mahboob v. Educational Credit Management Corporation, Counsel Stack Legal Research, https://law.counselstack.com/opinion/mahboob-v-educational-credit-management-corporation-casd-2021.