USI Insurance Services LLC v. Alliant Insurance Services Incorporated

• Court: District Court, D. Arizona
• Decided: June 24, 2025
• Docket: 2:23-cv-00192
• Status: Unknown

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA

9 USI Insurance Services LLC, No. CV-23-00192-PHX-SMB

10 Plaintiff, ORDER

11 v.

12 Alliant Insurance Services Incorporated, et al., 13 Defendants. 14 15 Pending before the Court is Plaintiff USI Insurance Services, LLC’s (“USI”) Motion 16 for Leave to Amend First Amended Complaint (Doc. 336). The parties have fully briefed 17 the pending Motion. (See Doc. 338 (Defendants’ Response); Doc. 342 (USI’s Reply); see 18 also Doc. 337 (USI’s Notice of Errata); Doc. 339 (Defendants’ Declaration of Seth Gerber 19 in Support of Response).) For the following reasons, the Court will grant USI leave to 20 amend. 21 I. BACKGROUND 22 This case concerns Defendants William Havard, Robert Engles, Jenise Purser, and 23 Justin Walsh (the “Individual Defendants”), and other non-parties, leaving their 24 employment with USI to join Defendant Alliant Insurance Services Inc (“Alliant”) 25 (collectively, the “Defendants”). On January 23, 2023, USI filed its original Complaint 26 (the “Original Complaint”) against Defendants Alliant, Havard, and Engles, asserting 27 claims for breach of contract, breach of the duty of good faith and fair dealing, breach of 28 the duty of loyalty, tortious interference with contract, and aiding abetting breach of the 1 duty of loyalty. (See generally Doc. 1.) That same day, USI sought a temporary restraining 2 order and preliminary injunction to enjoin and restrain Defendants Havard and Engles from 3 breaching the restrictive covenants in their employment agreements, including preventing 4 use and disclosure of USI’s confidential information. (Doc. 2 at 2.) Defendants Alliant, 5 Havard, and Engles faulted USI for seeking an injunction based on an alleged further 6 breach of confidentiality provisions and argued “USI [did] not actually allege that Havard 7 of Engles breached their obligations under the confidentiality provisions in their 8 employment agreements.” (Doc. 18 at 6.) 9 Defendants Alliant, Havard, and Engles thereafter moved to dismiss the Original 10 Complaint under Federal Rule of Civil Procedure 12(b)(6). (See generally Doc. 36.) They 11 again faulted USI for not alleging a breach of contract claim premised on the confidentiality 12 restrictive covenants in Havard and Engles employment agreements. (Id. at 4 (“Nothing is 13 alleged in the breach of contract claim about violating the confidentiality covenant . . . .”).) 14 USI proceeded to file its operative First Amended Complaint (“FAC”), mooting the 15 then-pending Rule 12(b)(6) motion. (Doc. 52 (USI’s FAC); see also Doc. 78 (dismissing 16 the motion as moot).) There, USI reasserted many of the same claims but added 17 Defendants Purser and Walsh. (Compare Doc. 52 ¶¶ 33, 44, 55, 64, 91–92, with Doc. 1 18 ¶¶ 26, 37, 59.) 19 The Defendants moved to dismiss the FAC under Rule 12(b)(6), claiming, in 20 relevant part, USI failed to allege facts to support the breach of contract claim based on 21 alleged violations of the confidentiality provisions. (Doc. 76 at 2, 7–8.) The Defendants 22 argued the only relevant factual allegation to support that Havard breached the 23 confidentiality provision related to an email containing a copy of a list of clients that Lori 24 Hartman, a non-party and former USI employee, had sent to him and others the day before 25 he resigned, but there were no allegations that Havard actually accessed that document or 26 that the information contained in it was confidential or transmitted outside of USI. (Id.; 27 see also Doc. 52 ¶ 75.) In turn, USI argued this allegation was sufficient to infer that 28 Havard breached the confidentiality covenant. (Doc. 90 at 7.) The Defendants did not 1 address the issue in their reply. (See generally Doc. 91.) The Court denied the Defendants’ 2 motion to dismiss in the FAC but did not discuss whether USI adequately pleaded that 3 Havard breached the confidentiality restrictive covenant. (Doc. 154 at 10–12.) Rather, the 4 Court found USI adequately pleaded a breach of contract claim based on breaches of the 5 restrictive covenants generally. (But see id. at 10 (“These claims are based on the 60-day 6 notice requirement, the non-solicitation, and the non-acceptance/non-service 7 agreements . . . .”).) 8 While the Rule 12(b)(6) motion remained pending, the parties engaged in discovery 9 in preparation for the preliminary injunction hearing. The Defendants “repeatedly sought 10 testimony and information regarding USI’s contention that the individual defendants 11 improperly acquired, used, or disclosed any USI confidential information.” (Doc. 94 at 2.) 12 During a discovery dispute, the Defendants’ counsel represented one of the primary issues 13 was USI’s “allegations that the defendants stole confidential information. (Doc. 337-1 14 at 88.) The Defendants’ deposition notices and interrogatories frequently referenced 15 evidence related to the alleged misuse of confidential information or breach of 16 confidentiality obligations. (See Doc. 94-1 at 6, 9–10, 50–52, 55–63; Doc. 337-1 17 at 107–08.) The Defendants’ counsel also questioned USI’s corporate representative about 18 the allegations of improper use or disclosure of USI’s confidential information. (See Doc. 19 337-1 at 94–105.) At the preliminary injunction hearing, the Defendants’ counsel 20 specifically addressed the “alleged breach of confidentiality.” (See id. at 130.) The Court 21 ultimately denied issuance of a preliminary injunction but did not address the alleged 22 breach of the confidentiality provision. (See Doc. 111 at 10–14.) 23 The parties continued to conduct discovery throughout the merits phase of the 24 litigation. Once again, the Defendants sought discovery related to breach or misuse of 25 confidential information, including requests for production, interrogatories, and deposition 26 testimony. (Doc. 337-1 at 135–42, 144–50, 153–57, 159–66.) After the close of discovery, 27 both parties moved for summary judgment on all claims. (See Doc. 238 (The Defendants’ 28 Motion for Summary Judgment); Doc. 245 (USI’s Motion for Summary Judgment).) The 1 Defendants renewed its arguments that USI failed to plead a breach of contract claim 2 premised on a breach of the confidentiality provision. (See Doc. 238 at 3; Doc. 315 3 at 23–24.) The Court heard oral argument on the motions on April 2, 2025, in which the 4 Defendants’ counsel reiterated the FAC failed to allege the breach of contract claim based 5 on the confidentiality provisions. (See Doc. 329; Doc. 333 at 32:22–33:14.) The Court 6 granted and denied summary judgment in part for both parties based on their respective 7 motions. (See generally Doc. 332.) Relevant here, the Court denied summary judgment 8 for USI that the Individual Defendants breached the confidentiality restrictive covenants 9 because it was not pleaded in the FAC and not properly before the Court. (See Doc. 332 10 at 27 (noting that the Defendants did not separately move on the merits a breach of the 11 confidentiality provision).) 12 USI now moves to amend its FAC, adding an allegation that “Havard, Engles, 13 Purser, and Walsh also breached their obligations by, among other things, improperly using 14 USI’s confidential information for the benefit of Alliant, in violation of their agreements.” 15 (See Doc. 337-1 at 42 ¶ 93.) The Defendants oppose the amendment. (See Doc. 338.) 16 II. DISCUSSION 17 A. Legal Standard 18 The parties first dispute what legal standard applies. Typically, Federal Rule of 19 Civil Procedure 15(a) requires that leave to amend be “freely give[n] when justice so 20 requires.” To that end, “a district court should grant leave to amend even if no request to 21 amend the pleading was made, unless it determines that the pleading could not possibly be 22 cured by the allegation of other facts.” Lopez v. Smith, 203 F.3d 1122, 1127 (9th Cir. 2000) 23 (cleaned up). 24 USI initially argues under the Rule 15 standard. (See Doc. 336 at 7–8.) But the 25 Defendants disagree that standard is applicable. (See Doc. 338 at 3, 12.) The Defendants 26 advance that where the district court has entered a scheduling order Federal Rule of Civil 27 Procedure 16 standard controls a plaintiff’s ability to amend its complaint. (Id. at 12 (citing 28 Johnson v. Mammoth Recreations, Inc., 975 F.2d 604, 607–08 (9th Cir. 1992)).) USI 1 replies that the Rule 16 standard should not apply because the Defendants waited to attack 2 the sufficiency of the pleadings until summary judgment and had it been raised earlier, USI 3 would have had the opportunity to amend the FAC. (Doc. 342 at 2–3 (citing Jones v. L.A. 4 Cent. Plaza LLC, 74 F.4th 1053 (9th Cir. 2023)).) 5 USI’s reliance on Jones is misplaced. There, the Ninth Circuit found that the district 6 court committed procedural errors after it, in deciding the plaintiff’s motion for summary 7 judgment on whether he had Article III standing, decided to sua sponte dismiss the 8 plaintiff’s claim for failing to adequately plead Article III standing, rather than addressing 9 the parties’ factual disputes. 74 F.4th at 1058–61. Here, the Defendants raised the issue, 10 the Court did not do so sua sponte. Further, the Court did not dismiss the claim but rather 11 found there was no claim for it to reach. Finally, and most importantly, Jones says nothing 12 about the applicable standard. 13 USI cites Desertrain v. City of Los Angeles, 754 F.3d 1147 (9th Cir. 2014) in which 14 the Ninth Circuit reasoned that where plaintiffs failed to raise a claim properly in their 15 pleading but raised it in their motion for summary judgment and in their opposition to the 16 defendant’s motion for summary judgment, the district court should have allowed 17 incorporation of the claim by amendment under Rule 15(b) or construed the matter as 18 raising a request to amend. 754 F.3d at 1154. More recent, however, the Ninth Circuit has 19 made clear that once a district court issues a scheduling order and the amendment deadline 20 has passed—which has occurred here1—Rule 16 governs the ability to amend a complaint. 21 DRK Photo v. McGraw-Hill Glob. Educ. Holdings, LLC, 870 F.3d 978, 989 (9th Cir. 2017); 22 see also Johnson, 975 F.2d at 608 (noting courts may construe a motion for leave to amend 23 a complaint as a motion to amend the scheduling order). This Court has also consistently 24 rejected applying Desertrain and the more liberal Rule 15(b) standard under similar 25 circumstances. Chaffin v. Centurion of Ariz., LLC, No. CV-22-02034-PHX-DWL (MTM), 26 2025 WL 522518, at *5 (D. Ariz. Feb. 18, 2025); Williams v. Circle K Stores Inc., No. CV- 27 19-01952-PHX-SMB, 2020 WL 5748132, at *3 (D. Ariz. Sept. 25, 2020), aff’d, No. 20-

28 1 The Court entered its Case Management Order (the “CMO”), setting the deadline to amend pleadings for September 11, 2023. (Doc. 113 ¶ 3.) 1 16949, 2022 WL 229293 (9th Cir. Jan. 25, 2022); CWT Canada II Ltd. P’ship v. Danzik, 2 No. CV16-0607 PHX DGC, 2019 WL 79001, at *5–6 (D. Ariz. Jan. 2, 2019). Absent 3 contrary authority—which USI has not offered—the Court is bound to follow precedent 4 and apply Rule 16. 5 Therefore, the Court will apply the Rule 16 standard but ultimately the issue is not 6 dispositive. Under the Rule 16 standard, the party seeking to amend a pleading must first 7 show “good cause.” Id. at 608 (quoting Fed. R. Civ. P. 16(b)(4)). “Rule 16(b)’s ‘good 8 cause’ standard primarily considers the diligence of the party seeking the amendment.” Id. 9 at 609 (“The district court may modify the pretrial schedule ‘if it cannot reasonably be met 10 despite the diligence of the party seeking the extension.’” (citation omitted)). The district 11 court’s focus remains on the movant’s reasons for seeking a modification to the scheduling 12 order, and thereby leave to amend a complaint, but the existence and degree of prejudice 13 to the opposing party “might supply additional reasons to deny a motion.” Id. 14 B. Good Cause 15 The Defendants argue that USI is unable to show good cause to warrant leave to 16 amend because USI was not diligent in seeking an amendment after it became aware of the 17 issue. (Doc. 338 at 12–16.) USI argues good cause exists because the Defendants’ moved 18 to dismiss the FAC for failing to allege sufficient facts to support a breach of the 19 confidentiality restrictive covenants, not like the Original Complaint where the argument 20 was that no breach claims was asserted all together. (Doc. 342 at 4–5.) According to USI, 21 it operated under the belief that the FAC asserted breach of the confidentiality provisions 22 and argues the Court should have provided it the opportunity to object or to seek leave to 23 amend before the filing deadline passed. (Id. at 6–7.) Further, USI contends that the parties 24 understood that misuse of confidential information remained a central issue in the FAC. 25 (Id. at 2.) 26 Whether USI asserted a breach of contract claim premised on violating the 27 confidentiality provisions has lingered in the ether of this litigation, with neither party 28 tackling the issue head-on nor seeking further clarification from the Court. The Defendants 1 challenged the factual support for the purported breach in their Rule 12(b)(6) motion, rather 2 than challenge existence of the claim premised on that breach in the first place. By the 3 time the Court ruled on the motion to dismiss, the deadline for amendments had already 4 passed. The Court did not raise the issue sua sponte at summary judgment. The Defendants 5 reraised the pleading issue in their briefings, this time in relation to whether the claim exists 6 under the FAC but did not separately move on the merits because they operated under the 7 assumption there was no claim. (See, e.g., Doc. 338 at 10 (explaining that they “did not 8 seek summary judgment on any claim for breach of confidentiality covenant because USI 9 failed to plead any such claim”).) 10 Throughout this litigation, the Defendants have continued to conduct discovery to 11 target evidence relevant to confidentiality violations, so to assume they were not aware that 12 this issue lingered in the background contradict their conduct. Similarly, while USI could 13 have sought leave to amend if it doubted the adequacy of the FAC, the Defendants did not 14 squarely present the issue until summary judgment. The assumption that USI was aware 15 of the inadequacy before summary judgment is contradicted by its efforts to amend the 16 Original Complaint to address the deficiencies, its responses to the Defendants’ discovery 17 targeting evidence under the umbrella of USI’s confidential information, the Defendants’ 18 framing of the issue as a matter of factual support for the breach in its Rule 12(b)(6) motion 19 for the FAC, and its efforts in moving for summary judgment on the matter, albeit 20 mistakenly. 21 As USI conveys, it “did not deploy a ‘wait-and-see’ approach or disregard ‘red-flag 22 warnings,’ but fully expected to litigate the merits of its breach of confidentiality claim at 23 summary judgement or trial.” (Doc. 42 at 9; see also Doc. 333 at 53:22–54:12 (advancing 24 arguments at oral argument on the summary judgment motions that are consistent with 25 USI’s understanding that it had adequately pleaded the issue). While USI primarily 26 addresses the Rule 15 standard, the arguments cover its diligence in not seeking an 27 amendment sooner. The Court never dismissed the claim to warrant USI seeking leave to 28 amend prior to summary judgment. The deadline had already passed by the time USI had 1 reason to believe its pleading was deficient, rendering compliance with the deadline a 2 matter of impossibility. In response to the Defendants raising the issue in their summary 3 judgment briefings, USI appeared to have construed the issue narrowly to address Alliant’s 4 liability under the tortious interference with contract claim, not the Individual Defendants’ 5 liability under the breach of contract claim. (See Doc. 238 at 3, 28–29 (relating to the 6 Defendants arguments about Alliant’s measures to avoid improper use of confidential 7 information and a tortious interference claim); Doc. 278 at 26–27 (responding to the 8 Defendants argument pertaining to the tortious interference claim); Doc. 319 at 15 9 (replying without addressing the pleading of the direct breach of contract claim).) At the 10 earliest, the Defendants’ response to USI’s motion for summary judgment presented the 11 issue directly. 12 The Court may have been mistaken in not reaching the merits of the claim based on 13 the parties’ confusion about the existence of confidentiality-based breach in the first place, 14 see, e.g., Jones, 74 F.4th at 1059–61 (explaining judicial efficiency is best served by 15 addressing the facts support summary judgment as opposed to deciding an issue on 16 pleading technicalities), or in not inferring that USI intended to request an amendment to 17 the FAC and incorporate the relevant amendment to reach the merits, see, e.g., Desertrain, 18 754 F.3d at 1154. The pending Motion is not now the appropriate vehicle to reach the 19 merits or reconsider what it has already decided. But the Court finds that USI has 20 demonstrated good cause for leave to amend the FAC given the unique circumstances of 21 this case. Given that USI established good cause, it also true that USI meets the more 22 liberal Rule 15 standard. 23 The Defendants assert that it would be prejudiced by the amendment, arguing it 24 would have engaged in more fulsome discovery and it will likely require reopening 25 discovery and rescheduling trial. (Doc. 338 at 17.) No such request is before the Court 26 and USI has presented the evidence as deduced through discovery it believes supports the 27 merits of the claim in its summary judgment briefing. Additionally, because both parties 28 appear to have operated from assumption that the claim existed prior to summary judgment || and the Court never dismissed such a claim, the Court finds leave to amend is warranted. TT. CONCLUSION 3 Accordingly, 4 IT IS ORDERED granting Plaintiff’s Motion for Leave to Amend First Amended 5 || Complaint (Doc. 336). 6 IT IS FURTHER ORDERED that Plaintiff shall file the Second Amended || Complaint within seven days (7) of the date of this Order. 8 Dated this 24th day of June, 2025. 9 = . 10 SO ts ll A lonorable Susan M. Brnovich United States District Judge 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28

-9-