Cywes v. Cywes

CourtDistrict Court, S.D. Ohio
DecidedApril 11, 2024
Docket2:22-cv-04189
StatusUnknown

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

Bluebook
Cywes v. Cywes, (S.D. Ohio 2024).

Opinion

UNITED STATES DISTRICT COURT SOUTHERN DISTRICT OF OHIO EASTERN DIVISION

COLETTE CYWES BENTLEY, Individually and as Co-Trustee of the Cywes Family Trust,

Plaintiff, Civil Action 2:22-cv-4189 Judge Edmund A. Sargus, Jr. v. Magistrate Judge Chelsey M. Vascura

ROBERT CYWES, Individually and as Co-Trustee of the Cywes Family Trust,

Defendant.

OPINION AND ORDER In this diversity action, Plaintiff Colette Cywes Bentley, individually and as co-trustee of the Cywes family trust, brings this action against Defendant Robert Cywes, Plaintiff’s brother and co-trustee, alleging that Defendant breached his fiduciary duties with regard to the trust. This matter is before the Court on Plaintiff’s Motion for Sanctions (ECF No. 43). For the reasons that follow, Plaintiff’s Motion is GRANTED IN PART and DENIED WITHOUT PREJUDICE IN PART. I. BACKGROUND On November 16, 2023, Plaintiff contacted the undersigned’s chambers via email in accordance with the Preliminary Pretrial Order (ECF No. 10) to request an informal conference to resolve a discovery dispute. In response to Plaintiff’s counsel’s email, chambers staff requested that Plaintiff’s counsel provide a brief summary of the discovery dispute and “copies of any discovery requests/responses in dispute.” Plaintiff’s counsel responded via email on November 28, 2023, asserting that Defendant had failed to provide complete production of his electronic communications, and that even electronic documents that had been produced had not included related metadata. Plaintiff’s counsel attached a deficiency letter sent to Defendant on

September 1, 2023, but did not attach copies of the underlying discovery requests. As it turned out, however, the Court did not need to engage with particular discovery requests, because during the informal conference on December 4, 2023, “[Defendant’s] counsel represented that [Plaintiff] had not requested any documents that [Defendant] was unwilling to produce.”1 (Order Memorializing Dec. 4, 2023 Disc. Conference, ECF No. 36.) Given Defendant’s agreement to produce the requested documents, the undersigned ordered Plaintiff to provide Defendant “with a list of particular documents for which [Plaintiff] has a good faith basis for requiring [Defendant] to produce metadata” and ordered Defendant “to produce any outstanding documents WITHIN 30 DAYS of the conference.” (Id.) The undersigned further extended the discovery period to January 29, 2024, for the limited purpose of completing

outstanding discovery. (Id.) As instructed, on December 12, 2023, Plaintiff emailed Defendant with a list of 36 documents for which Plaintiff was seeking production in native form. (ECF No. 43-1, PAGEID #1463.) That same email also laid out eleven categories of documents “to be supplemented in Defendant’s document production” “in follow up to the discovery conference with the court.” (Id.) Those categories are not tied to any particular discovery requests, and several categories seek communications in which Defendant does not appear to have been involved (e.g., “All of

1 The Court’s Order erroneously transposed the titles of Plaintiff and Defendant when memorializing the December 4, 2023 conference. The undersigned subsequently amended the Order nunc pro tunc to correct the error. (ECF No. 37.) [Defendant’s wife] Janae’s texts (entire threads) and emails with Sidney and/or Marlene”). (Id.) The email also noted that Defendant’s responses to Plaintiff’s Second Requests for Production of Documents were overdue (id.), which suggests that the eleven document categories did not encompass documents responsive to Plaintiff’s Second Requests for Production of Documents.

Defendant’s counsel emailed Plaintiff’s counsel on January 8, 2024, promising that production was forthcoming. (Id. at PAGEID #1463–64.) However, despite several follow up emails from Plaintiff’s counsel, Defendant had produced no additional documents by January 30, 2024. That day, Plaintiff’s counsel emailed the undersigned’s chambers to notify the Court of Defendant’s noncompliance. (ECF No. 46-1, PAGEID #1561–62.) Chambers staff responded to relay the undersigned’s guidance that, since Defendant had already been ordered to produce the documents and metadata at issue, another Court conference was unnecessary, and that “if Defendant had not completed his production by 5:00pm on Friday, February 2, Plaintiff may move for sanctions under Federal Rule of Civil Procedure 37.” (Id. at PAGEID #1561.) Over January 31 and February 1, 2024, Defendant made a supplemental production.

However, Plaintiff asserts the production remains deficient as it included only 21 of the requested 36 native files and did not include any documents responsive to the eleven categories outlined in Plaintiff’s December 12, 2023 email. (Pl.’s Mot. 3, ECF No. 43.) Plaintiff filed the present Motion for Sanctions on February 13, 2024. (ECF No. 43.) As sanctions, Plaintiff seeks entry of default judgment against Defendant and removal of Defendant as co-trustee of the Cywes family trust, or, alternatively, an order requiring Defendant to use a third-party vendor to collect discoverable documents. Plaintiff also seeks her reasonable expenses, including attorney’s fees, caused by Defendant’s failure to comply with the Court’s order to produce documents. (Id.) II. STANDARDS GOVERNING DISCOVERY SANCTIONS “The Federal Rules of Civil Procedure set forth the discovery obligations of parties and their attorneys, and authorize federal courts to impose sanctions on those who fail to meet these obligations.” United States v. Quebe, 321 F.R.D. 303, 310 (S.D. Ohio 2017) (quoting Laukus v. Rio Brands, Inc., 292 F.R.D. 485, 500–01 (N.D. Ohio 2013)). “Under Fed. R. Civ. P.

37(b)(2)(C), a district court may sanction parties who fail to comply with its orders in a variety of ways . . . .” Bass v. Jostens, Inc., 71 F.3d 237, 241 (6th Cir. 1995) (citing Bank One of Cleveland, N.A. v. Abbe, 916 F.2d 1067, 1073 (6th Cir. 1990)). Possible sanctions include directing adverse inferences, prohibiting the disobedient party from introducing particular matters in evidence, striking pleadings, staying or dismissing the action, entry of default judgment, or holding the disobedient party in contempt. See Fed. R. Civ. P. 37(b)(2)(A). Entry of default judgment as a discovery sanction “is a drastic step which should be resorted to only in the most extreme cases.” Prime Rate Premium Fin. Corp., Inc. v. Larson, 930 F.3d 759, 769 (6th Cir. 2019) (quoting United Coin Meter Co. v. Seaboard Coastline R.R., 705 F.2d 839, 845 (6th Cir. 1983)). When considering whether to enter default judgment, district

courts are required to consider four factors: “(1) Did the party act in bad faith? (2) Was the opposing party prejudiced? (3) Did the court give adequate warning? and (4) Could less drastic sanctions have ensured compliance?” Id. (citing Grange Mut. Cas. Co. v. Mack, 270 F. App’x 372, 376 (6th Cir. 2008) (per curiam)). III. ANALYSIS A. Violations of the Court’s Order Plaintiff seeks sanctions under Rule 37(b)(2), which provides for sanctions against a party who “fails to obey an order to provide or permit discovery.” Fed. R. Civ. P.

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
Cywes v. Cywes, Counsel Stack Legal Research, https://law.counselstack.com/opinion/cywes-v-cywes-ohsd-2024.