1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA
9 Navajo Health Foundation-Sage Memorial No. CV-23-08072-PCT-DJH Hospital Incorporated, 10 ORDER Plaintiff, 11 v. 12 Razaghi Development Company LLC, et 13 al.,
14 Defendants. 15 16 Before the Court is a Motion for Reconsideration filed by Defendants Razaghi 17 Development Co, LLC (“RDC”), Ahmad R. Razaghi (“Razaghi”) and Tausif Hasan 18 (“Hasan”) (collectively, “Defendants”) (Doc. 468). Defendants ask the Court to 19 reconsider its finding that RDC breached the Second Amended CEO Services Contract 20 (“SAC”) when it took an unauthorized $10.8 million Termination Payment from Sage on 21 August 27, 2018. (Doc. 464). Plaintiff Navajo Health Foundation—Sage Memorial 22 Hospital, Inc. (“Sage”) has filed a Response (470) and Defendants have filed a Reply 23 (Doc. 471). 24 I. Legal Standards 25 District courts have discretion to reconsider prior orders. Navajo Nation v. Norris, 26 331 F.3d 1041, 1046 (9th Cir. 2003); Barber v. Hawaii, 42 F.3d 1185, 1198 (9th Cir. 27 1994). However, reconsideration is an “extraordinary remedy” that is available only in 28 “highly unusual circumstances.” Kona Enters., Inc. v. Est. of Bishop, 229 F.3d 877, 890 1 (9th Cir. 2000) (internal quotation marks omitted); Carroll v. Nakatani, 342 F.3d 934, 2 945 (9th Cir. 2003) (circumstances justifying reconsideration are rare). Motions for 3 reconsideration are ordinarily denied “absent a showing of manifest error or a showing of 4 new facts or legal authority that could not have been brought to its attention earlier with 5 reasonable diligence.” LRCiv 7.2(g)(1). They are generally “disfavored . . . and are not 6 the place for parties to make new arguments not raised in their original briefs.” 7 Motorola, Inc. v. J.B. Rodgers Mechanical Contractors, 215 F.R.D. 581, 582 (D. Ariz. 8 2003); LRCiv 7.2(g)(1). 9 II. Discussion 10 On September 19, 2025, the Court granted partial summary judgment in favor of 11 Sage on its breach of contract claim relating to RDC’s unauthorized taking of a $10.8 12 million Termination Payment. (Doc. 464). In their Motion for Reconsideration, 13 Defendants argue that the Court’s ruling was in error because it rested “entirely on its 14 factual determination that RDC committed an ‘unauthorized taking’ of the Termination 15 Payment.” (Doc. 468 at 2). Defendants say that there was no unauthorized taking 16 because the invoice seeking the Termination Payment was processed and paid by Sage. 17 (Id.) Defendants say “no less than four agents and employees of Sage reviewed, 18 approved, processed and/or issued the Termination Payment.” (Doc. 468 at 3). 19 Defendants argue that these agents owed fiduciary duties to Sage and acted at its behest 20 in processing the Termination Payment. (Id. at 4). They say that because a reasonable 21 juror could have reached the conclusion that RDC’s actions in sending an invoice and 22 receiving payment for that invoice did not constitute a breach of contract, the Court’s 23 contrary finding was manifest error. (Id.)1
24 1 Defendants also argue that the Court erred in “its reliance on Altimayer-Pizzorno v. L-Soft Int’l, Inc., 302 Fed Appx. 148, 153 (4th Cir. 2008) . . . to support its conclusion 25 that the Court may determine as a matter of law whether RDC’s conduct terminated the SAC.” (Doc. 468 at 10). The Court summarily rejects this argument because, as Sage 26 points out, it plainly mischaracterizes the Court’s Order. Sage, not the Court, relied on Altimayer-Pizzorno in its Partial Motion for Summary Judgment (“PMSJ”). The Court 27 even noted that “Sage’s citation to an unpublished Fourth Circuit opinion applying Maryland law [was] peculiar.” (Doc. 464 n.17). The Court instead relied on Miller v. 28 Crouse, 506 P.2d 659, 644 (Ariz. Ct. App. 1973) to support its conclusion that RDC terminated the SAC when it issued and took the $10.8 million Termination Payment. (Id. 1 A. Defendants’ Arguments are New 2 Defendants do not cite any new evidence or legal authorities in their Motion for 3 Reconsideration. Instead, they offer new arguments for why RDC’s receipt of the $10.8 4 million Termination Payment on August 27, 2018, was not a breach of the SAC. When 5 Sage sought summary judgment on this breach of contract claim, Defendants never 6 asserted that RDC’s taking of the Termination Payment was authorized because it was 7 processed by Sage employees. Instead, Defendants argued RDC did not breach the SAC 8 because RDC was entitled to the Termination Payment on August 27, 2018—either 9 because Sage terminated the SAC without cause, or because RDC terminated the SAC for 10 cause. (See Doc. 430 at 10–14 (arguing that it was entitled to the Termination Payment 11 under the SAC because Sage terminated the SAC without cause) and id. at 14–18 12 (arguing that even if RDC terminated the SAC, it did so for cause and it was therefore 13 entitled to the Termination Payment)). The Court found that the undisputed facts showed 14 that neither circumstance existed on August 27, 2018, and RDC was not entitled to the 15 $10.8 million Termination Payment it invoiced and caused Sage employees to process. 16 Defendants do not explain why they did not make their check processing argument 17 earlier. Instead, in a footnote, Defendants say their Response “repeatedly made clear that 18 RDC requested and ‘received’ the Termination Payment which was approved and issued 19 by Sage.” (Doc. 468 n. 4). But Defendants’ use of the verb “receive” did not alert the 20 Court to factual disputes over Sage’s proper (or improper) processing of the Termination 21 Payment.2 The deposition testimony cited in Defendants’ Motion shows that they 22 at 24–25 (noting that “[i]n Arizona, a notice to rescind ‘is not required to be formal and 23 may be evidenced by conduct, but manifestation of an intent to rescind must be unequivocal.”). 24 2 To the contrary, RDC leaned into the characterization of its receipt of the payment 25 as a breach in defending its entitlement to the Termination Payment in its Response. (See Doc. 430 at 10 (arguing that Sage terminated the SAC without cause when it 26 discovered RDC took the Termination Payment because “for Sage to validly terminate the SAC for cause based on a material breach, it was required to first provide notice and 27 an opportunity to cure to RDC” and Sage did not do so); id. at 12 (arguing “RDC’s receipt of the Termination Payment was not a ‘vital’ breach relieving Sage of its 28 contractual obligation to provide RDC written notice of and an opportunity to cure a material breach of the SAC.”). id. n.4 citing Doc. 422-8 at 90, Ex. 43, Defs’ Third Supp. 1 undeniably possessed this information at the time of the summary judgment briefing. 2 Defendants offer no excuse for why it was not presented to the Court in their Response to 3 Plaintiff’s PMSJ. 4 Litigation is not a game of hopscotch. It is generally accepted that a party may not, on a motion for reconsideration, advance a new argument that 5 could (and should) have been presented prior to the district court’s original 6 ruling. . . Litigants normally must frame the issues in a case before the trial court rules. After that point, a litigant should not be allowed to switch from 7 theory to theory like a bee in search of honey. 8 Cochran v. Quest Software, Inc., 328 F.3d 1, 11 (1st Cir. 2003) (affirming district court’s 9 refusal to reconsider its decision based on movant’s newly raised argument).
Free access — add to your briefcase to read the full text and ask questions with AI
1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA
9 Navajo Health Foundation-Sage Memorial No. CV-23-08072-PCT-DJH Hospital Incorporated, 10 ORDER Plaintiff, 11 v. 12 Razaghi Development Company LLC, et 13 al.,
14 Defendants. 15 16 Before the Court is a Motion for Reconsideration filed by Defendants Razaghi 17 Development Co, LLC (“RDC”), Ahmad R. Razaghi (“Razaghi”) and Tausif Hasan 18 (“Hasan”) (collectively, “Defendants”) (Doc. 468). Defendants ask the Court to 19 reconsider its finding that RDC breached the Second Amended CEO Services Contract 20 (“SAC”) when it took an unauthorized $10.8 million Termination Payment from Sage on 21 August 27, 2018. (Doc. 464). Plaintiff Navajo Health Foundation—Sage Memorial 22 Hospital, Inc. (“Sage”) has filed a Response (470) and Defendants have filed a Reply 23 (Doc. 471). 24 I. Legal Standards 25 District courts have discretion to reconsider prior orders. Navajo Nation v. Norris, 26 331 F.3d 1041, 1046 (9th Cir. 2003); Barber v. Hawaii, 42 F.3d 1185, 1198 (9th Cir. 27 1994). However, reconsideration is an “extraordinary remedy” that is available only in 28 “highly unusual circumstances.” Kona Enters., Inc. v. Est. of Bishop, 229 F.3d 877, 890 1 (9th Cir. 2000) (internal quotation marks omitted); Carroll v. Nakatani, 342 F.3d 934, 2 945 (9th Cir. 2003) (circumstances justifying reconsideration are rare). Motions for 3 reconsideration are ordinarily denied “absent a showing of manifest error or a showing of 4 new facts or legal authority that could not have been brought to its attention earlier with 5 reasonable diligence.” LRCiv 7.2(g)(1). They are generally “disfavored . . . and are not 6 the place for parties to make new arguments not raised in their original briefs.” 7 Motorola, Inc. v. J.B. Rodgers Mechanical Contractors, 215 F.R.D. 581, 582 (D. Ariz. 8 2003); LRCiv 7.2(g)(1). 9 II. Discussion 10 On September 19, 2025, the Court granted partial summary judgment in favor of 11 Sage on its breach of contract claim relating to RDC’s unauthorized taking of a $10.8 12 million Termination Payment. (Doc. 464). In their Motion for Reconsideration, 13 Defendants argue that the Court’s ruling was in error because it rested “entirely on its 14 factual determination that RDC committed an ‘unauthorized taking’ of the Termination 15 Payment.” (Doc. 468 at 2). Defendants say that there was no unauthorized taking 16 because the invoice seeking the Termination Payment was processed and paid by Sage. 17 (Id.) Defendants say “no less than four agents and employees of Sage reviewed, 18 approved, processed and/or issued the Termination Payment.” (Doc. 468 at 3). 19 Defendants argue that these agents owed fiduciary duties to Sage and acted at its behest 20 in processing the Termination Payment. (Id. at 4). They say that because a reasonable 21 juror could have reached the conclusion that RDC’s actions in sending an invoice and 22 receiving payment for that invoice did not constitute a breach of contract, the Court’s 23 contrary finding was manifest error. (Id.)1
24 1 Defendants also argue that the Court erred in “its reliance on Altimayer-Pizzorno v. L-Soft Int’l, Inc., 302 Fed Appx. 148, 153 (4th Cir. 2008) . . . to support its conclusion 25 that the Court may determine as a matter of law whether RDC’s conduct terminated the SAC.” (Doc. 468 at 10). The Court summarily rejects this argument because, as Sage 26 points out, it plainly mischaracterizes the Court’s Order. Sage, not the Court, relied on Altimayer-Pizzorno in its Partial Motion for Summary Judgment (“PMSJ”). The Court 27 even noted that “Sage’s citation to an unpublished Fourth Circuit opinion applying Maryland law [was] peculiar.” (Doc. 464 n.17). The Court instead relied on Miller v. 28 Crouse, 506 P.2d 659, 644 (Ariz. Ct. App. 1973) to support its conclusion that RDC terminated the SAC when it issued and took the $10.8 million Termination Payment. (Id. 1 A. Defendants’ Arguments are New 2 Defendants do not cite any new evidence or legal authorities in their Motion for 3 Reconsideration. Instead, they offer new arguments for why RDC’s receipt of the $10.8 4 million Termination Payment on August 27, 2018, was not a breach of the SAC. When 5 Sage sought summary judgment on this breach of contract claim, Defendants never 6 asserted that RDC’s taking of the Termination Payment was authorized because it was 7 processed by Sage employees. Instead, Defendants argued RDC did not breach the SAC 8 because RDC was entitled to the Termination Payment on August 27, 2018—either 9 because Sage terminated the SAC without cause, or because RDC terminated the SAC for 10 cause. (See Doc. 430 at 10–14 (arguing that it was entitled to the Termination Payment 11 under the SAC because Sage terminated the SAC without cause) and id. at 14–18 12 (arguing that even if RDC terminated the SAC, it did so for cause and it was therefore 13 entitled to the Termination Payment)). The Court found that the undisputed facts showed 14 that neither circumstance existed on August 27, 2018, and RDC was not entitled to the 15 $10.8 million Termination Payment it invoiced and caused Sage employees to process. 16 Defendants do not explain why they did not make their check processing argument 17 earlier. Instead, in a footnote, Defendants say their Response “repeatedly made clear that 18 RDC requested and ‘received’ the Termination Payment which was approved and issued 19 by Sage.” (Doc. 468 n. 4). But Defendants’ use of the verb “receive” did not alert the 20 Court to factual disputes over Sage’s proper (or improper) processing of the Termination 21 Payment.2 The deposition testimony cited in Defendants’ Motion shows that they 22 at 24–25 (noting that “[i]n Arizona, a notice to rescind ‘is not required to be formal and 23 may be evidenced by conduct, but manifestation of an intent to rescind must be unequivocal.”). 24 2 To the contrary, RDC leaned into the characterization of its receipt of the payment 25 as a breach in defending its entitlement to the Termination Payment in its Response. (See Doc. 430 at 10 (arguing that Sage terminated the SAC without cause when it 26 discovered RDC took the Termination Payment because “for Sage to validly terminate the SAC for cause based on a material breach, it was required to first provide notice and 27 an opportunity to cure to RDC” and Sage did not do so); id. at 12 (arguing “RDC’s receipt of the Termination Payment was not a ‘vital’ breach relieving Sage of its 28 contractual obligation to provide RDC written notice of and an opportunity to cure a material breach of the SAC.”). id. n.4 citing Doc. 422-8 at 90, Ex. 43, Defs’ Third Supp. 1 undeniably possessed this information at the time of the summary judgment briefing. 2 Defendants offer no excuse for why it was not presented to the Court in their Response to 3 Plaintiff’s PMSJ. 4 Litigation is not a game of hopscotch. It is generally accepted that a party may not, on a motion for reconsideration, advance a new argument that 5 could (and should) have been presented prior to the district court’s original 6 ruling. . . Litigants normally must frame the issues in a case before the trial court rules. After that point, a litigant should not be allowed to switch from 7 theory to theory like a bee in search of honey. 8 Cochran v. Quest Software, Inc., 328 F.3d 1, 11 (1st Cir. 2003) (affirming district court’s 9 refusal to reconsider its decision based on movant’s newly raised argument). 10 The Court was thus entitled to rely on the undisputed evidence for its summary 11 judgment analysis, see FRCP 56(e)(2), and Defendants cannot obtain reconsideration of 12 the summary judgment order by belatedly pointing to evidence that was always available 13 to them to create factual disputes. Motorola, 215 F.R.D. at 582 (“Motions for 14 reconsideration are . . . not the place for parties to make new arguments not raised in their 15 original briefs.”). See also, e.g., Preston v. City of Pleasant Hill, 642 F.3d 646, 652 (8th 16 Cir. 2011) (affirming denial of motion to reconsider in part because movant “belatedly 17 [brought] the DHS applications to the district court’s attention, even though the DHS 18 applications were available to [movant] at the time he resisted defendants’ summary 19 judgment motion”); Moro v. Shell Oil Co., 91 F.3d 872, 876 (7th Cir. 1996) (denying 20 Rule 59(e) motion where movant “submitted a second affidavit of [declarant] that 21 contained statements not found in [declarant’s] initial affidavit filed in opposition to 22 [defendant’s] summary judgment motion,” because “[t]he rule does not provide a vehicle 23 for a party to undo its own procedural failures, and it certainly does not allow a party to 24 introduce new evidence or advance arguments that could and should have been presented 25 Resps. to Pl’s First Set of Rogs (“receipt of the Termination Payment on August 27, 26 2018, rather than on September 1, 2018, 30 days after RDC’s August 2, 2018, notice of Plaintiff’s breaches of the Contract, may have constituted a non-criminal material breach 27 of the Contract. However, Plaintiff terminated the SAC without providing RDC with written notice of this breach and without giving RDC 30 days to cure any such breach.”); 28 Doc. 430 at 17 (“RDC’s receipt of the Termination Payment on August 27, 2018, was at best premature and at worst a material breach of the SAC.”). 1 to the district court prior to the judgment”). 2 B. Defendants’ New Arguments Lack Merit 3 Defendants’ arguments, even if considered, also lack merit. Defendants say that 4 the Court’s “determination that RDC ‘took’ the payment, instead of Sage voluntarily 5 issuing payment of a legitimate invoice, required factual findings in favor of the 6 nonmovant that the Court was not entitled to make.” (Doc. 468 at 6). Defendants say 7 after RDC issued Invoice 1369 for $10,855,134.15 “it passed through the hands of at 8 least four of Sage’s employees and agents: Nicole Hardy (Sage accounting employee), 9 Thomas Matenaer (Sage Comptroller), Tausif Hasan (Sage CFO), and Tad Greenfield 10 (Sage Co–CEO).” (Id.) Defendants say “the full knowledge, involvement, and approval 11 of the Termination Payment by multiple agents and employees of Sage creates a fact 12 issue which the jury must resolve regarding whether Sage approved the Termination 13 Payment versus whether RDC engaged in an ‘unauthorized taking’ of that payment.” 14 (Id.) Defendants argue for the first time that Sage can only act through and be held 15 responsible for the actions of its agents and employees and at all relevant times, Hardy, 16 Matenaer, Hasan, and Greenfield were Sage’s acting agents. (Id. at 6–9). Defendants say 17 Matenaer and Hardy’s “actions in processing and ultimately paying that invoice are, as a 18 legal matter, the actions of Sage itself,” and that factual disputes surround Hasan and 19 Greenfield’s knowledge and actions related to the Termination Payment. (Id. at 8). 20 The Court disagrees. The SAC provides that RDC, with Razaghi as both CEO of 21 RDC and Sage, had the “the right and commensurate authority and responsibility, express 22 or implied, to oversee the supervision and effective management of the day-to-day 23 business operations of [Sage],” and that RDC “shall oversee. . . the collection of accounts 24 and monies owed to [Sage].” (Doc. 422-5, Ex. 18). Razaghi, the undisputed CEO of 25 RDC and Sage at the time of the Termination Payment, testified that he directed the 26 $10.8 million Termination Payment to be paid to RDC. When he was asked, “Who made 27 the decision to take the $10.8 million?” Mr. Razaghi testified, “I did.” (Doc. 422-3 at 28 131, Ex. 13, Razaghi Depo. 140:21–22 (emphases added)). When asked, “And who did 1 you discuss taking the $10.8 million with in your organization?” he answered, “Mr. 2 Greenfield and Mr. Hasan.” (Id. at 140:23–24). When he was asked whether he was “the 3 one that directed that this $10.8 million be taken out of the Sage account,” he 4 unequivocally responded, “I directed it be invoiced and paid.” (Id. at 132 (emphasis 5 added)). He also testified he did not believe he needed to use the Escrow Account to 6 process the payment or to seek approval for the Termination Payment from the Sage 7 Board. (Id. at 144:23–145:3). Razaghi further stated that all the authorized signors of 8 Sage’s checking account were under his authority, including Hardy, Matenaer, Hasan, 9 and Greenfield. (Id. at 144:13–21). 10 Considering this testimony, the fact that Hasan testified that Greenfield approved 11 the Termination Payment invoice does not, as Defendants contend in their Reply, create 12 “a genuine issue of material fact as to the extent to which Razaghi participated in the 13 payment itself.” (Doc. 471 at 5). Razaghi, by his own admission, directed the processing 14 and payment of the unauthorized Termination Payment invoiced on August 27, 2018. 15 Razaghi was the CEO of both Sage and RDC. He admitted that Hardy, Matenaer, Hasan, 16 and Greenfield were under his control and authority. The fact that any of these 17 individuals may have breached a fiduciary duty to Sage when, at Razaghi’s direction, 18 they “approved” or “processed” the invoice does not raise factual issues as to whether 19 Razaghi, as CEO of Sage and RDC, properly directed the $10.8 million Termination 20 Payment to RDC.3 As the Court’s Order found, no circumstances existed under the SAC
21 3 In their Reply, Defendants argue the Court erred in finding that RDC improperly took the Termination Payment because “the Court rejected Sage’s summary judgment 22 argument that Defendants had violated their fiduciary duties — including with respect to the Termination Payment.” (Doc. 471 at 5). Again, this is a mischaracterization of the 23 Court’s Order. The Court denied Sage’s request to enter summary judgment against Defendants on Sage’s breach of fiduciary duty claims because Sage had only summarily 24 made the arguments and failed to “cite to the specific evidence supporting its [breach of fiduciary duty] claims.” (Doc. 464 at 39–40 (stating, “ít is Sage’s burden, not the 25 Court’s, to identify the undisputed evidence supporting its claims”). If properly made, these claims against Defendants certainly present an uphill battle for them at trial, but on 26 summary judgment, Sage had not sufficiently met that burden because that specific evidence was not identified in the briefing. There is no conflict in the Court’s finding 27 that Sage had met its burden of establishing a breach of contract but not on its breach of fiduciary duty claims. 28 Notably, in their Response to the PMSJ, Defendants exclusively defended by saying that Defendants did not owe fiduciary duties to Sage and ignored Sage’s breach 1] that would have entitled RDC to a Termination Payment on August 27, 2018. Given 2|| multiple uncontested facts in the record, including Razaghi’s own actions, the Court 3|| “afforded no weight” to Razaghi’s belief that RDC was contractually entitled to the 4|| Termination Payment because Sage had terminated the SAC on or before August 27. || (Doc. 464 at 21). Razaghi’s unsupported averment likewise does not provide evidence 6|| of a factual issue as to whether he properly directed the payment of the Termination 7|| Payment to RDC. RDC’s receipt of the $10.8 million Termination Payment, processed 8 || and paid at Razaghi’s direction, breached the SAC because RDC was not entitled to that payment. 10 For the foregoing reasons, 11 IT IS ORDERED denying Defendants’ Motion for Reconsideration (Doc. 468). 12 Dated this 3rd day of November, 2025. 13 14 Ap a 15 norable'Diang4. Humfetewa 16 United States District Judge 17 18 19 20 21 22 23
arguments. (Doc. 430 at 26-28 (arguing that no duty was owed to Sage because neither 25 | Hasan nor Razaghi served as a member of Sage’s board of directors; because RDC served only as an independent contractor to Sage; and because Sage did not entrust Hasan with 26 any particular knowledge when RDC made him CFO of Sage). The Court rejected Defendants’ arguments and found that RDC, Razaghi, and Hasan owed fiduciary duties 271) to Sage. (Doc. 464 at 39). To the extent Defendants now aim to present facts relevant to those alleged breaches in seeking reconsideration, they again are precluded from doing so under LRCiv 7.2(g)(1).
-7-