George Mandala v. NTT Data, Inc.

CourtDistrict Court, W.D. New York
DecidedJanuary 15, 2026
Docket6:18-cv-06591
StatusUnknown

This text of George Mandala v. NTT Data, Inc. (George Mandala v. NTT Data, Inc.) is published on Counsel Stack Legal Research, covering District Court, W.D. New York primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
George Mandala v. NTT Data, Inc., (W.D.N.Y. 2026).

Opinion

UNITED STATES DISTRICT COURT WESTERN DISTRICT OF NEW YORK _______________________________________

GEORGE MANDALA, DECISION AND ORDER Plaintiff, 6:18-CV-6591 MAV CDH v.

NTT DATA, INC.,

Defendant _______________________________________

INTRODUCTION Plaintiff George Mandala (“Plaintiff”) asserts claims of (1) disparate impact discrimination in violation of Title VII of the Civil Rights Act of 1964, (2) disparate impact discrimination in violation of the New York Human Rights Law (“NYHRL”), and (3) discriminatory denial of employment in violation of the NYHRL and Article 23-A of the New York Correction Law against defendant NTT Data, Inc. (“Defendant”). (Dkt. 49, see Dkt. 71 at 9-10, 19). Plaintiff has filed a motion to compel a conference pursuant to Federal Rule of Civil Procedure 26(f) and Local Rule of Civil Procedure 16(b). (Dkt. 76). Defendant opposes Plaintiff’s motion and asks the Court to award it attorney’s fees pursuant to Federal Rule of Civil Procedure 37(a)(5)(B). (Dkt. 81 at 22). For the reasons that follow, both Plaintiff’s motion and Defendant’s request for fees are denied. BACKGROUND This matter has been referred to the undersigned for all non-dispositive pretrial proceedings. (See Dkt. 48; Dkt. 68). The Court assumes the parties’ familiarity with the factual and procedural background of this matter for purposes of this Decision and Order. The facts and procedure salient to the instant motion are summarized below.

Plaintiff commenced this action on August 15, 2018. (Dkt. 1). The matter was originally dismissed in 2019 (Dkt. 28), and the dismissal was affirmed on appeal (Dkt. 34). However, Plaintiff subsequently filed a motion to vacate the judgment and file a first amended complaint. (Dkt. 35). The Court denied that motion (Dkt. 40), but on appeal, the Second Circuit reversed and remanded (Dkt. 46). On remand, Plaintiff filed the first amended putative class action complaint on March 18, 2024. (Dkt. 49). Defendant moved for dismissal (Dkt. 57), and on July 28,

2025, the Court issued a Decision and Order (the “July 2025 Order”) granting in part and denying in part Defendant’s motion (Dkt. 71). On August 11, 2025, Plaintiff sent Defendant a letter “requesting to schedule an initial conference to begin the Rule 26(f) conferral process[.]” (Dkt. 76-1 at 6; Dkt. 76-2 at ¶ 3). The meeting was set for August 27, 2025. (Dkt. 76-1 at 6; Dkt. 76-2 at ¶ 3). However, on August 25, 2025, Defendant filed a motion for reconsideration of

the July 2025 Order or, in the alternative, for certification of the July 2025 Order for interlocutory appeal. (Dkt. 72). That motion is currently pending before the presiding District Judge. On August 26, 2025, Defendant emailed Plaintiff saying that a “meet and confer [was] woefully premature because [Defendant] ha[d] a pending motion with the Court and ha[d] not even filed an Answer.” (Dkt. 76-1 at 6 (quotations and original alteration omitted); see also Dkt. 76-2 at ¶ 4; Dkt. 81 at 9). The parties held their scheduled meeting on August 27, 2025, during which Defendant reiterated its position that a Rule 26(f) conference was premature and that the parties need not

engage in discovery planning until after a Rule 16 conference. (Dkt. 76-1 at 6; Dkt. 76-3 at 3; Dkt. 81 at 9). On the same day, the Court issued a Text Order holding that “Defendant is not required to file an answer in this matter until after the Court issues its decision on the pending motions.” (Dkt. 74). On September 16, 2025, Defendant emailed Plaintiff, again stating that a meet and confer was premature given that Defendant had not served its answer, no Rule 16 conference was scheduled, and no discovery demands had been served. (Dkt. 76-1

at 6-7; Dkt. 76-2 at ¶ 7). On September 17, 2025, Plaintiff responded, again requesting that the parties conduct a Rule 26(f) conference. (Dkt. 76-1 at 7; Dkt. 76-2 at ¶ 8). Defendant did not respond to this request. (See Dkt. 76-1 at 7). On September 25, 2025, Plaintiff filed the instant motion to compel Defendant “to participate in a discovery planning conference” pursuant to Rule 26(f) and Local Rule 16(b). (Dkt. 76 at 1). Specifically, Plaintiff argues that the Court should compel

a Rule 26(f) conference because: (1) “[Defendant]’s second motion to dismiss has been denied” (Dkt. 76-1 at 5) and the motion for reconsideration “does not automatically stay . . . the parties’ obligations under Rule 26(f)” (Dkt. 76-1 at 7; see also Dkt. 82 at 5); (2) now is a practicable time to hold a Rule 26(f) conference (see Dkt. 76-1 at 5); and (3) a stay of discovery is inappropriate here because the motion for reconsideration is unlikely to succeed, the burden of holding a Rule 26(f) conference upon Defendant is minimal, “it is in the public interest to avoid further delay in the adjudication of [Plaintiff’s] important civil rights claims[,] . . . [and a stay] would disproportionately burden Plaintiff[] . . . [who has] the burden [of proof][.]” (Dkt. 76-

1 at 9). On October 10, 2025, Defendant filed its opposition, asking the Court to deny Plaintiff’s motion and “award [Defendant] its reasonable expenses, including attorney’s fees incurred in opposing” Plaintiff’s motion, pursuant to Rule 37(a)(5)(B). (Dkt. 81 at 22). Defendant argues that Plaintiff’s motion should be denied because: “(1) [Defendant]’s motion for reconsideration . . . is currently pending; (2) this Court has already ordered [Defendant]’s deadline to file an answer . . . stayed pending

resolution of [it]’s Motion; (3) [Defendant]’s Motion sought a stay pending its resolution; and (4) . . . it would be inefficient to address discovery before the threshold legal questions [in this litigation] are reached.” (Dkt. 81 at 7 (citations omitted)). Plaintiff filed a reply on October 17, 2025. (Dkt. 82). DISCUSSION I. Legal Standard

Rule 26(f) provides that “[e]xcept in a proceeding exempted from initial disclosure under Rule 26(a)(1)(B) or when the court orders otherwise, the parties must confer as soon as practicable—and in any event at least 21 days before a scheduling conference is to be held or a scheduling order is due under Rule 16(b).” Fed. R. Civ. P. 26(f) (emphasis added). While “Rule 16 typically requires the issuance of a scheduling order ‘within the earlier of 90 days after any defendant has been served with the complaint or 60 days after any defendant has appeared,’ a court need not do so if ‘finds good cause for delay.’” Israel v. O'Malley, No. 24-CV-86-LJV, 2024 WL 5040722, at *1 (W.D.N.Y. Dec. 9, 2024), (citing Fed. R. Civ. P. 16(b)(2)), appeal

dismissed, No. 24-3284, 2025 WL 882886 (2d Cir. Mar. 12, 2025). Further, “[a] party may not seek discovery from any source before the parties have conferred as required by Rule 26(f), except . . . when authorized by these rules, by stipulation, or by court order.” Fed. R. Civ. P. 26(d)(1); see also Strike 3 Holdings, LLC v. Doe, 329 F.R.D. 518, 520 (S.D.N.Y. 2019). Courts in this Circuit have held that a pending dispositive motion is good cause to delay issuance of a scheduling order. See, e.g., Adams v. Credit Acceptance Corp.,

No. 25-CV-410JLS(SR), 2025 WL 1953268, at *3 (W.D.N.Y.

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

Related

Gomez-Beleno v. Holder
644 F.3d 139 (Second Circuit, 2011)

Cite This Page — Counsel Stack

Bluebook (online)
George Mandala v. NTT Data, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/george-mandala-v-ntt-data-inc-nywd-2026.