JITESH SHAH, et al. v. COUNTY OF KERN, et al.

District Court, E.D. California·Decided August 12, 2026·No. 1:25-cv-01130·Unknown

Opinion

JITESH SHAH, et al., Case No. 1:25-cv-01130-JLT-CDB

Plaintiffs, ORDER GRANTING DEFENDANTS’ v. MOTION TO COMPEL AND FOR SANCTIONS COUNTY OF KERN, et al., (Doc. 53) Defendants. ORDER FOR PLAINTIFFS TO SHOW CAUSE WHY UNSERVED DEFENDANTS SHOULD NOT BE DISMISSED Deadline – Aug. 26, 2026

Background Plaintiffs Jitesh, Nipa, and Manraj Shah, together with Manraj Hospitality, Inc. (“Plaintiffs”) commenced this action with the filing of a complaint in the Central District of California on July 2, 2025. In the operative complaint, Plaintiffs assert causes of action against Defendants County of Kern and its Kern County Public Health (“KCPH”) division, various officers/employees of KCPH, and the City of Bakersfield and a named code enforcement officer.1 Plaintiffs are the owners and operators of a 50-unit hotel in Bakersfield and their claims against

1 There is no record evidence that Plaintiffs served the Bakersfield defendants with summons and complaint and neither defendant has appeared in the action. Accordingly, the Court will order Plaintiffs to show cause why these defendants should not be dismissed for Plaintiffs’ failure to timely effect service of Defendants derive from Defendants’ alleged code enforcement-related activities at the hotel beginning in or around July 2024 through at least February 2025. On September 3, 2025, the Central District court granted County of Kern’s motion in the alternative to transfer the case to this Court. (Doc. 16). Thereafter, at the Court’s direction, the parties filed a joint scheduling report and the Court convened with the parties for scheduling conference on December 11, 2025. (Docs. 31, 37, 38). That same day, the Court entered the operative scheduling order and therein adopted all of the case management dates as proposed by the parties. Cf. (Doc. 31) with (Doc. 39). Relevant here, the Court ordered that Rule 26 initial disclosures be exchanged no later than January 4, 2026, and that nonexpert discovery be completed by May 25, 2026. (Doc. 39). To date, no party has requested any extensions or continuances of the case management dates. On June 1, 2026 (after nonexpert discovery had closed), counsel for Defendants contacted the Courtroom Deputy to report that the parties' good faith efforts to resolve a discovery dispute have been unsuccessful. (Doc. 45). Thereafter, the parties filed a joint discovery dispute brief and convened in Court for an informal discovery dispute conference on June 15, 2026. (Docs. 45-48). In short, the discovery dispute involved Defendants’ contention that Plaintiffs failed to respond to any of the interrogatories and requests for production of documents Defendants propounded pursuant to Rules 33 and 34, Federal Rules of Civil Procedure. Consistent with the parties’ letter brief (Docs. 46, 47), counsel for Plaintiffs maintained during the discovery dispute conference that he did not dispute Defendants’ entitlement to relief but explained that he had been unable to timely respond to Defendants’ discovery requests due to a medical issue and his absence for approximately one week in observance of a religious holiday. See (Doc. 47 at 3). In the parties’ letter brief, Plaintiffs requested that the Court permit them to respond to Defendants’ discovery demands by no later than July 9, 2026. After entertaining arguments and discussion at the discovery dispute conference, the Court ordered Plaintiffs to serve upon Defendants responses (verified as required) and produce documents responsive to Defendants' written discovery demands (see Docs. 47-1 through 47-8). (Doc. 48). The Court initially indicated its intention to set Plaintiffs’ response deadline for June 25, 2026, but counsel for Plaintiffs requested five additional days, stating “If I could just have another five days I will get [discovery] out” and that he was “going to be very diligent now.” The Court relented and set the deadline for Plaintiffs to respond to Defendants’ discovery demands on June 30, 2025. Plaintiffs did not produce any discovery responses by the June 30 deadline. Accordingly, Defendants requested permission and the Court authorized their filing of a motion to compel. (Docs. 49-51). Defendants filed their motion on July 16, 2026; Plaintiffs filed an opposition on July 27, 2026; and Defendants file a reply on July 28, 2026. (Docs. 53, 56-57). The Court convened with the parties for motion hearing on August 6, 2026. (Doc. 58). As of that date, Plaintiffs still had not served responses to Defendants’ discovery requests. Governing Legal Standard Court orders and rules governing discovery “make a trial less a game of blindman's bluff and more a fair contest with the basic issues and facts disclosed to the fullest practicable extent. Only strong public policies weigh against disclosure.” United States v. Procter & Gamble Co., 356 U.S. 677, 682 (1958) (internal citation omitted). As a foundational component of civil discovery, Federal Rule of Civil Procedure 26 provides in relevant part that “a party must, without awaiting a discovery request, provide to the other parties: ... (ii) a copy – or a description by category and location – of all documents, electronically stored information, and tangible things that the disclosing party has in its possession, custody, or control and may use to support its claims or defenses, unless the use would be solely for impeachment.” Fed. R. Civ. P. 26(a)(1)(ii). Separately, Rules 33 and 34 permit parties to seek discoverable information from each other through interrogatories and requests for production of documents. Those rules set forth the responding party’s obligations in relation to timely responding to such discovery demands. Rule 37 permits a party to seek to compel another party to comply with its discovery obligations imposed pursuant to Rule 26(a), Rule 33, Rule 34, or other order of the court governing discovery. Under Rule 37(c), a party that “fails to provide information or identify a witness as required by Rule 26(a) or (e)” may not “use that information or witness to supply evidence ... at a trial, unless the failure was substantially justified or is harmless.” Fed. R. Civ. P. 37(c)(1). See Yeti by Molly, Ltd. v. Deckers Outdoor Corp., 259 F.3d 1101, 1106 (9th Cir. 2001) (“Rule 37(c)(1) gives teeth to these requirements by forbidding the use at trial of any information required to be disclosed by Rule 26(a) that is not properly disclosed.”). “The Advisory Committee Notes describe it as a ‘self-executing,’ ‘automatic’ sanction to ‘provide[ ] a strong inducement for disclosure of material....’” Id. (quoting Fed. R. Civ. P. 37 advisory committee's note (1993)). Similarly, under Rule 37(d), the Court may impose sanctions where a party’s failure to respond to interrogatories or requests for production of documents is neither substantially justified nor harmless. Rule 37(b)(2)(A) sets forth the sanctions available, including evidentiary and financial sanctions. “Among the factors that may properly guide a district court in determining whether a violation of a discovery deadline is justified or harmless are: (1) prejudice or surprise to the party against whom the evidence is offered; (2) the ability of that party to cure the prejudice; (3) the likelihood of disruption of the trial; and (4) bad faith or willfulness involved in not timely disclosing the evidence.” Lanard Toys Ltd. v. Novelty, Inc., 375 Fed. Appx. 705, 713 (9th Cir. 2010) (citing David v. Caterpillar, Inc.,

JITESH SHAH, et al. v. COUNTY OF KERN, et al., (E.D. Cal. 2026).

JITESH SHAH, et al. v. COUNTY OF KERN, et al. (JITESH SHAH, et al. v. COUNTY OF KERN, et al.) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Lanard Toys Limited v. Novelty, Inc.
375 F. App'x 705 (Ninth Circuit, 2010)
R & R Sails, Inc. v. Insurance Co. of Pennsylvania
673 F.3d 1240 (Ninth Circuit, 2012)
Lori David v. Caterpillar, Incorporated
324 F.3d 851 (Seventh Circuit, 2003)
Gregory Martino v. Pika International, Inc.
600 F. App'x 908 (Fifth Circuit, 2015)
Jarritos, Inc. v. Reyes
345 F. App'x 215 (Ninth Circuit, 2009)