versus

National Labor Relations Board, A Federal Administrative Agency; Jennifer Abruzzo, In her official capacity as the General Counsel of the National Labor Relations Board ; Marvin Kaplan, Chairman, National Labor Relations Board, In his official capacity as the Chairman of the National Labor Relations Board ; Marvin E. Kaplan, In their official capacities as Board Members of the National Labor Relations Board ; Gwynne A. Wilcox, In their official capacities as Board Members of the National Labor Relations Board ; David M. Prouty, In their official capacities as Board Members of the National Labor Relations Board ,

Defendants—Appellees ,

Teamsters Amazon National Negotiating Committee,

Intervenor .

Appeal from the United States District Court for the Western District of Texas USDC No. 5:24-CV-1000Page 2 Before Richman, Graves, and Ramirez, Circuit Judges .

Irma Carrillo Ramirez, Circuit Judge :

Our prior panel opinion, Amazon.com Servs. LLC v. Nat’l Lab. Rels. Bd. , 136 F.4th 577 (5th Cir. 2025), is WITHDRAWN , and the following opinion is SUBSTITUTED:

Amazon appeals the “constructive denial” of its motion for injunctive relief from 'being subjected to [two] unconstitutional administrative proceedings” before the National Labor Relations Board (“ NLRB” ). We DISMISS this appeal for lack of subject-matter jurisdiction.

Amazon is a major online retailer that receives, sorts, and ships products from warehouses called “fulfillment centers.” In December 2021, the Amazon Labor Union (' ALU ') filed a petition with the NLRB to represent more than 8,000 Amazon employees at the fulfillment center in Staten Island, New York. The election was held on April 1, 2022, and a majority of the employees voted in favor of ALU . The election resulted in two separate NLRB proceedings concerning the NLRB ’s alleged interference with the union election, Case 29-RC-288020 (the 'Election Case”), and Amazon’s alleged refusal to bargain with the union, Case 29CA-318069 (the “Bargaining Case”).

On April 8, 2022, Amazon initiated the Election Case by filing 25 objections, alleging that ALU and the Regional Office had interfered with the conditions for a free and fair election. On March 31, 2022, the day before the election, the NLRB ’s Regional Director—with approval from the General Counsel—sought an injunction ordering the immediate reinstatement of an Page 3employee that Amazon had terminated almost two years earlier. That employee had filed a charge against Amazon in June 2020, and the NLRB ’s Regional Office had issued a complaint against Amazon in December 2020. Amazon claimed that the General Counsel should have sought an injunction as soon as the Regional Office issued its complaint in December 2020, rather than waiting until the eve of the union election. This 'undermined the integrity of the April 2022 election that the [ NLRB ] was obliged to supervise neutrally.” Amazon sought to have the NLRB invalidate the election results and order a second election.

Amazon sought to transfer the case to a different, non-conflicted region, and the General Counsel transferred the matter to Region 28, which serves parts of Texas. On September 1, 2022, after a 24-day hearing, the Region 28 Hearing Officer recommended that all of Amazon’s objections be overruled. On January 11, 2023, the Region 28 Regional Director affirmed the Hearing Officer's recommendation and certified ALU as the bargaining representative for Amazon’s Staten Island fulfillment center. On February 9, 2023, Amazon requested review of the decision, which the NLRB denied on August 29, 2024.

Meanwhile, because of the election, ALU demanded that Amazon recognize and bargain with it. It filed a charge with the Regional Office, alleging that Amazon refused to recognize it or bargain with it as the exclusive representative for the Staten Island employees. On July 12, 2023, the Regional Director issued a complaint, which initiated the Bargaining Case.

On August 23, 2023, the General Counsel moved for summary judgment on the complaint, alleging that Amazon violated the National Labor Relations Act by refusing to bargain with ALU until its objections were adjudicated. The General Counsel also sought an order directing Amazon to Page 4recognize and bargain with ALU, pay consequential damages as a 'makewhole” remedy for certain Amazon employees, and transfer the Bargaining Case from the Regional Office to the NLRB itself.

Later that day, the NLRB granted the motion to transfer and issued a notice to show cause as to why the summary judgment motion should not be granted. On August 25, 2024, the day after the NLRB denied Amazon's request for review in the Election Case, the NLRB issued an updated notice to show cause in the Bargaining Case. The updated notice instructed Amazon to file any supplemental opposition to the summary judgment motion on or before September 13, 2024.

On September 5, 2024, Amazon sued the NLRB in the Western District of Texas, requesting temporary, preliminary, and permanent declaratory and injunctive relief. It sought:

[T]o avoid serious and irreparable harm that it will otherwise suffer from being subjected to unconstitutional administrative proceedings. Because the structure of the proceedings in NLRB Cases 29-CA-310869 and 29-RC-288020 violate the United States Constitution under Supreme Court and Fifth Circuit precedent, Amazon respectfully brings this action for declaratory and injunctive relief . . . .

Amazon also requested an 'immediate' temporary restraining order and that the district court “set a hearing for a preliminary injunction [and] issue a preliminary injunction' because the NLRB could theoretically issue an order any time after it filed its supplemental opposition on September 13, 2024. It did not otherwise request that the hearing—or the requested relief— occur before a specific date.

On September 9, 2024, the district court informed Amazon that a local rule required that its application for a preliminary injunction must be Page 5made in a separate motion. Accordingly, on September 10, 2024, Amazon moved for a temporary restraining order and preliminary injunction, again seeking “immediate relief” because its brief was due by September 13, 2024, and the NLRB was 'poised' to rule 'in the imminent future.' Amazon argued that it faced imminent and irreparable harm because, if the administrative proceedings went forward, “Amazon will lose its right not to undergo an unconstitutional proceeding.” That same day, the NLRB moved to transfer the case to the Eastern District of New York. The next day, on September 11, 2024, the NLRB agreed to extend Amazon's deadline to file a supplemental opposition until September 27, 2024.

The district court held a hearing on the motions to transfer and for temporary restraining order on September 24, 2024. Amazon argued that it needed immediate injunctive relief, because 'if the [Bargaining Case proceeding] goes forward after this Friday and [the NLRB ] issues an order granting the summary judgment, then the constitutional issues . . . are mooted.” But it did not specifically request a ruling by a specific date.¹ The court specifically asked Amazon how fast it thought the NLRB would issue a decision. Amazon acknowledged that the NLRB 'normally [takes] weeks' to issue a decision, but it “believe[d]” that “a ruling could issue as soon as we file a brief' on September 27 because of the 'relationship between [Amazon] and the NLRB .'² When asked why relief was needed immediately Page 6instead of after “a more orderly briefing process, considering the magnitude of the issues,” Amazon responded that the NLRB could 'theoretically . . . issue an order Monday,” September 30. The NLRB , in turn, represented that “a period of months, generally, is about as quick as the board can act given its caseload.”

The district court afforded the parties leave to raise any additional points that had not been addressed via letter briefs filed by Friday, September 27. The court stated that it was “going to try to get this out as soon as” it could. Amazon then asked if the court wanted the briefs by a particular time, and the court set a deadline of noon. It then adjourned the hearing.

Two days later, on September 26, 2024, Amazon filed a letter brief with the district court, “a day ahead of the 12:00 p.m. Central, September 27, 2024, deadline” to give the court “as much time as possible” to consider its request for an immediate temporary restraining order. It stated its concern that the NLRB ' could ” issue its decision as early as Monday, September 30, and for the first time advised that its “effective deadline” to seek emergency appellate review was “Friday morning, after which time it would be “forced to consider its motion for injunctive relief effectively denied because of the imminence of potential Board action.” The next day, Amazon noticed the appeal of the district court's 'constructive denial' of its motion for temporary restraining order and preliminary injunction.

On Sunday, September 29, 2024, and while the current appeal was pending before this court, the district court granted-but stayed-the NLRB 's motion to transfer.³ It also denied Amazon's request for a temporary restraining order. The district court explained that “Amazon has Page 7failed to establish a substantial threat of irreparable harm if an injunction is not granted.' Instead, 'it predicates its claim based on a claim that the NLRB may depart from precedent and require it to provide some form of compensation to employees for their lost opportunity to engage in collective bargaining.” “This is both speculative and unripe,” the district court found.

On September 30, 2024, a motions panel of this court administratively stayed the proceedings before the district court and the NLRB and expedited the matter to the next available merits panel.

At issue is whether the district court constructively denied Amazon’s motion for a temporary restraining order and preliminary injunction.

Under § 1292(a)(1), this court has jurisdiction to review interlocutory orders, including orders that refuse or dissolve injunctions.²⁸ U.S.C. § 1292(a)(1). This also includes orders that do not expressly refuse an injunction but have the “practical effect of doing so.” Carson v. Am. Brands, Inc. , 450 U.S. 79, 83 (1981) (citing Gen. Elec. Co. v. Marvel Rare Metals Co. , 287 U.S. 430, 433 (1932)).

Amazon argues that the district court constructively denied its motion for a preliminary injunction by failing to rule on or before September 27, 2024; as a result, it faced an injury that could not be undone—the NLRB 'consummating a final order in its unconstitutional proceeding.' We disagree.

Because “a motion for preliminary injunctive relief ‘must be granted promptly to be effective,’” a district court’s failure to timely rule on motion can amount to an ''effective' denial.' In re Fort Worth Chamber of Commerce , 100 F.4th 528, 533 (5th Cir. 2024). “[W]hat counts as an effective denial is Page 8contextual—different cases require rulings on different timetables.” Id. at 535. “District courts have wide discretion in managing their docket, and they do not necessarily deny a motion by failing to rule on a parties’ requested timeline.” Id. “Appeal cannot be achieved simply by asserting that the trial court has failed to act promptly as wished by a party seeking an injunction.” Id. 'There must be a legitimate basis for [any] urgency.' Id. (citing 16 Charles Allen Wright & Arthur Miller, Federal Practice & Procedure § 3924.1 (3d ed.)). Another consideration is the litigant’s “diligence in seeking to expedite briefing and consideration,” such as whether it has made 'repeated requests for a ruling by a specific date.' Id.

In Fort Worth Chamber of Commerce , a group of business associations sued the Consumer Financial Protection Bureau, challenging a new rule that required them to print and distribute materials about credit card late fees to customers and provide notice of mitigating changes by March 29, 2024. 100 F.4th at 531. On March 7, the associations moved to enjoin the rule and specifically requested an expedited ruling 'within 10 days, or as soon as possible thereafter, to prevent irrecoverable harm.' Id. at 531-32. The district court did not rule within 10 days and instead sua sponte requested briefing on venue on March 18. Id. The next day, the associations again specifically requested an expedited ruling and informed the court that they would understand the preliminary injunction to have effectively been denied if it had not ruled by March 22. Id. The district court denied the motion for expedited review, and without having ruled on the motion, transferred the case to the District of Columbia on March 28. Id. We held that the district court had effectively denied the motion for preliminary injunction because the associations demonstrated a legitimate basis for the urgency, i.e., “the unusually short timeline for complying with the rule.” Id. at 535. They had also “repeatedly requested swift review,” including “repeated requests for a ruling by specific dates.” Id. at 534.

We first consider Amazon’s diligence in seeking expedited briefing and consideration. Id. at 535.

Here, unlike the business associations in Fort Worth Chamber of Commerce , Amazon did not '[make it] clear from its first filing [on September 5, 2024] that the [final order] was going into effect on an unusually short timeline.” 100 F.4th at 534. It “made clear” that its deadline to respond to the NLRB ’s summary judgment motion was September 13, and it requested “immediate” relief because the NLRB could issue an order any time after that deadline. When it separately moved for a temporary restraining order and a preliminary injunction, it again sought immediate relief on grounds that the NLRB was 'poised' to rule 'in the imminent future,' without explanation. Unlike Fort Worth Chamber of Commerce , Amazon did not 'repeatedly request[] swift review.' 100 F.4th at 534. It never made a specific request for an expedited briefing schedule, an expedited hearing, or an expedited ruling in its filings.

At the hearing on September 24, Amazon expressed its belief that the NLRB could issue an order as soon as Monday, September 30, but it acknowledged that the NLRB usually took weeks to issue a decision. And despite an extended discussion with the district court regarding its need for immediate injunctive relief, Amazon did not specifically request a ruling by a specific date. When the district court set a deadline for filing letter briefs on the same day as Amazon’s extended submission deadline, Friday, September 27, Amazon did not object. When the court stated that it would issue a ruling as soon as it could, Amazon did not ask if a ruling would be forthcoming by September 27 or request a ruling by that date. Nor did it advise the district court that it would construe a failure to issue a ruling by September 27 as an effective denial of its motion for injunctive relief. Amazon instead only asked Page 10if the court wanted the briefs by a particular time. On this record, we cannot find that Amazon made clear its need, as opposed to its wish, for an expedited ruling by September 27 to the district court at the hearing. Amazon did not request relief by a specific date-or even expedited relief-until its letter brief dated September 26, in which it requested for the first time that the district court rule by the morning of September 27. During oral argument, Amazon was also unable to identify any other specific request for a ruling by this date. Amazon has not shown that it acted diligently.

Amazon also failed to establish a legitimate basis for the alleged urgency. See Fort Worth Chamber of Commerce , 100 F.4th at 535. The associations in Fort Worth Chamber of Commerce “made clear from [their] first filing that the Final Rule was going into effect on an unusually short timeline, which meant the credit card issuers had an unusually short window of time to comply.' Id. at 534. Here, Amazon's deadline to file its supplemental opposition to the summary judgment motion was Friday, September 27. Nothing before the district court indicated that the NLRB would—or even could—issue a decision as soon as Monday, September 30. Amazon acknowledged at the preliminary injunction hearing that it normally takes weeks for decisions to issue; the NLRB stated that 'a period of months, generally, is about as quick as [it] can act given its caseload.' Although a certain date such as the one in Fort Worth Chamber of Commerce is not required to show a legitimate basis for urgency, Amazon’s belief or the theoretical possibility that the NLRB could issue a decision by September 30 does not suffice.

Finally, this court has also considered the district court’s timeliness in assessing urgency. Fort Worth Chamber of Commerce , 100 F.4th at 535 (“[G]iven the issuers’ unusually short timeline for complying with the Final Page 11Rule or obtaining injunctive relief, the district court effectively denied the Chambers' motion for a preliminary injunction by not promptly ruling on it and instead opting to hear an unrelated motion sua sponte .' (emphasis added)). See, e.g., United States v. Lynd , 301 F.2d 818, 823 (5th Cir. 1962) (finding effective denial where the district court conducted a merits hearing on the injunction motion and the movant “proved without question” its entitlement to relief, but the district court unduly delayed ruling on that motion). In contrast to Fort Worth Chamber of Commerce , the district court here conducted a hearing concerning Amazon's motion for injunctive relief. During that timely hearing, it specifically explored Amazon's basis for urgency. Although Amazon’s request for immediate relief was based only on its belief that the NLRB could issue a decision as soon as September 30, the district court stated its intent to issue a decision as soon as it could. And it followed through by filing its decision on September 29, one day before the date Amazon claimed on which NLRB “ could ” issue its decision. But by that point, Amazon had already petitioned this court for relief.

A litigant cannot “simply say they need an expedited ruling and then appeal by claiming effective denial when they do not get it on their preferred timeline.” Fort Worth Chamber of Commerce , 100 F.4th at 535. Amazon neither diligently requested consideration by September 27 nor demonstrated a legitimate basis for the urgency. The district court did not effectively deny the motion for injunctive relief in failing to rule on or before September 27. Because there is no effective denial, there is no interlocutory decision before this court under 28 U.S.C. § 1291(a)(1). This appeal must be dismissed for lack of subject-matter jurisdiction.

Amazon's appeal is DISMISSED for lack of subject-matter jurisdiction under 28 U.S.C. § 1291(a)(1).

Page 12Priscilla Richman , Circuit Judge , dissenting:

I would hold that the district court effectively denied Amazon's motion for a preliminary injunction, giving rise to our interlocutory appellate jurisdiction. I respectfully dissent. Our court’s decision today says that our jurisdiction depends on a combination of two ephemeral factors: 1) when will it be more than “theoretically possible” an agency might act, even though the agency was free to act when the appeal was taken; how much longer must a party must wait to appeal-a day, a week, a month-the bar is left to wonder, at its and its clients’ peril; and 2) how vociferously a litigant must tell a district court the date by which it needs a ruling. In the present case, the NLRB could have ruled at any time after noon on Friday, September 27. The district court was advised early and often of that deadline. Amazon filed an appeal on Friday, September 27. Yet, the court says no appeal could be taken until an indeterminate date and time beyond September 27.

Under 28 U.S.C. § 1292(a)(1), we have jurisdiction over appeals from interlocutory orders denying injunctive relief.¹ Litigants may also, in certain circumstances, appeal an otherwise unappealable interlocutory order that does “not in terms ‘refus[e]’ an ‘injunctio[n],’” but nonetheless has “the practical effect of doing so.” 2 We have also 'recognized that simply sitting Page 13on a preliminary-injunction motion for too long can effectively deny it.” 3 In constructive-denial cases, we require a showing that the practical or effective denial “threatens ‘serious, perhaps irreparable[,] consequences’ and can be effectively challenged only by immediate appeal.” 4 This showing serves as “a safeguard against undue widening of the floodgates which currently keep in proper bounds” our § 1292(a)(1) jurisdiction.⁵ Amazon asserts that the district court’s inaction effectively denied its motion.

We recently discussed how to “determine whether the district court’s inaction . . . amounts to an ‘effective’ denial” in In re Fort Worth Chamber of Commerce . 6 There, the plaintiff filed suit challenging a new administrative rule two days after the agency finalized the rule. 7 The new rule required the plaintiff to take steps toward compliance twenty-two days later.⁸ The plaintiff immediately moved for a preliminary injunction, expressly requesting a ruling within ten days.⁹ The district court did not rule within Page 14ten days; instead, on the eleventh day, the court 'sua sponte requested briefing on venue.” 10 On the twelfth day, the plaintiff moved for expedited review of its preliminary injunction motion and informed the court that if “it did not receive a ruling by [the fifteenth day], it would understand its preliminary injunction to be effectively denied and would accordingly seek appellate review.” 11 The district court did not rule by the fifteenth day.¹² On the eighteenth day—four days before the date for compliance—the plaintiff appealed.¹³

We concluded that the district court had effectively denied the plaintiff’s motion for a preliminary injunction such that we had interlocutory appellate jurisdiction.¹⁴ We reasoned that 'a motion for preliminary injunctive relief ‘must be granted promptly to be effective.’” 15 Accordingly, “[a]mong the considerations when determining whether a district court has waited too long to rule on a motion is ‘the urgency of preliminary relief as a means of preserving the opportunity for effective permanent relief.''¹⁶ In this vein, “[t]here must be a legitimate basis for the urgency.” 17 'Thus, whether Page 15a district court fails to act promptly depends entirely on context.” 18 We also emphasized that “[f]or its part,” the moving party “acted diligently.” 19

In Fort Worth , the plaintiff had a legitimate basis for urgency because 'the Final Rule's fast-closing window for compliance demanded faster review of the motion for a preliminary injunction.'²⁰ The plaintiff acted diligently by filing suit within two days after the agency finalized the rule; by 'ma[king] clear from its first filing that . . . [it] had an unusually short window of time to comply” with the new rule; by specifically requesting a ruling on its preliminary injunction motion within ten days; by making 'repeated requests for a ruling by specific dates'; and by requesting expedited briefing.²¹ Yet the district court failed to rule on the preliminary injunction motion, but instead “g[a]ve its attention to” the venue issue.²² This amounted to an effective denial of the motion for a preliminary injunction.

These principles support appellate jurisdiction here. While some of the operative facts differ in degree, “what counts as an effective denial is contextual.” 23

Amazon had a legitimate basis for urgency in seeking preliminary injunctive relief against the Bargaining Case. Impending summary judgment in the Bargaining Case could moot Amazon's district court claims, precluding the district court’s ability to grant any relief. I am persuaded that this would be “a ‘serious, perhaps irreparable, consequence’” that “can be ‘effectually challenged’ only by immediate appeal” from the district court’s effective denial of Amazon’s motion.²⁴

Amazon’s constitutional objections to the Bargaining Case all allege ongoing subjection to an illegitimate decisionmaker. While “[t]hat harm may sound a bit abstract,” the Supreme Court “has made clear that it is ‘a hereand-now injury'' district courts have jurisdiction to redress prior to the termination of an agency proceeding.²⁵ This injury is conceptually distinct from an injury arising from an adverse agency order, which a party might challenge—also on constitutional grounds—after the proceeding.²⁶ Importantly, the here-and-now injury 'is impossible to remedy once the proceeding is over' because '[a] proceeding that has already happened cannot be undone.'²⁷

Amazon and the NLRB agree that the Board could grant summary judgment against Amazon after the September 27 show-cause deadline, including on that same day, and the NLRB acknowledged in oral arguments Page 17that 'the administrative proceeding would likely have concluded at that point had the Board addressed all issues in the case.' In that event, the 'proceeding is over,' and it 'cannot be undone.'²⁸ Post hoc '[j]udicial review of [Amazon’s] structural constitutional claims”—framed as ongoing subjection to an illegitimate decisionmaker-'would come too late to be meaningful,'²⁹ and the district court would be unable to provide the relief Amazon requested in its complaint. That is exactly why “preliminary relief [functions] as a means of preserving the opportunity for effective permanent relief.” 30 Just as in Fort Worth a 'fast-closing window for compliance demanded faster review of the motion for a preliminary injunction,” a fastclosing window before potential summary judgment in the Bargaining Case demanded faster review here.³¹

The majority opinion concludes that there was no legitimate basis for Amazon’s urgency because there was no indication that the Board would issue a decision on the same day as the show-cause deadline.³² To be sure, the parties dispute how quickly the Board would likely act after the showcause deadline, and there is admittedly no guarantee that the Board would grant summary judgment against Amazon, thus ending the proceedings. But the prospect that the Board could issue an adverse decision any time after the show-cause deadline, as the parties agree was possible, presented a legitimate basis for urgency. In reaching the opposite conclusion, the majority opinion states that “Amazon acknowledged at the preliminary injunction hearing that Page 18it normally takes weeks for decisions to issue.'³³ In context, however, Amazon’s “acknowledgement” is far from any concession that the Board issuing a decision soon after the show-cause deadline was a mere “theoretical possibility.” 34 The district court asked, '[H]ow fast do you think the Board is going to issue a decision?” Amazon responded:

This would certainly be a guess, although an educated one; but, typically, in test of certification proceedings the rulings come out fairly quickly, much quicker than in the normal course. [The court then stated: 'Give me timeframes.'] Normally weeks, but given the posture of this case and sort of the nature of the—what I’ll call the relationship between our client and the NLRB , we believe that a ruling could issue as soon as we file a brief.

Even if Amazon acknowledged that it “normally” takes weeks for decisions to issue, Amazon argued that the NLRB would likely act faster than usual in its case. Further, we cannot consider the fact that the Board has yet to render a decision because a motions panel of this court administratively stayed the Bargaining Case on September 30, preventing the Board from acting.

Similarly, although the district judge stated during the September 24 motions hearing that he intended “to try to get this [ruling on the motions] out as soon as I can,” Amazon could not know how long the court would take, or if the Board would grant summary judgment before the court could act. Even though we now know that the district court issued a ruling on Amazon’s request for a temporary restraining order ( TRO ) two days after Amazon noticed its appeal, we must consider the context as it existed on September 27—the date on which Amazon had to file its response at the NLRB , thus Page 19making ripe the General Counsel's motion for summary judgment-not September 29. On September 27, neither the district court nor Amazon could know how long the Board would wait to issue a decision in the Bargaining Case—two days, two weeks, two months, or longer. Accordingly, I give little weight to the fact that the district court ruled on the motion two days later.³⁵

Importantly, I do not see—and the majority opinion has not offered— any principled way for us to determine whether the district court failed to “timely rule on [Amazon’s] preliminary-injunction motion” 36 other than by tethering that inquiry to the show-cause deadline. Assume Amazon had not noticed its appeal on September 27 and assume the district court did not eventually act on September 29. How long after the show-cause deadline would have been too long of a delay by the district court? At what point could Amazon have invoked our interlocutory appellate jurisdiction on an effectivedenial theory? After the show-cause deadline arrived, no one could know, other than the NLRB , when the Board intended to issue a decision that could moot Amazon’s district court claims. What was certain was that the Board could issue a ruling after the show-cause deadline, at its convenience.

Amazon’s basis for urgency was all the more legitimate given that the Board had the power to moot Amazon's claims against the NLRB . To moot those claims, the Board only had to render an adverse order quickly against Amazon disposing of all the issues in the Bargaining Case. It is notable that the Board apparently declined requests to defer its proceedings. According to Amazon, '[i]mmediately after filing suit, [it] asked the Board to administratively stay the [Bargaining Case],' but '[t]he Board refused.'Page 20 Only after the district court on September 10 scheduled the motions hearing for September 24 did the Board on September 11 extend the initial showcause deadline to September 27—thus setting the deadline after the district court's hearing on both Amazon's motion and the NLRB 's motion to transfer . Amazon represented to the district court after the motions hearing that it “again requested” that the Board stay the Bargaining Case, but the “Board [was] unwilling to do so.” Even the district court at the motions hearing asked the NLRB why it was not “just agreeing to stay a decision until all this is handled.” The NLRB responded: “Because the agency obviously has an interest in continuing its orderly processes.” But that is exactly the point: the Board’s continuing its orderly processes, which no doubt is a legitimate interest, could moot Amazon’s district court claims. That potential outcome provided Amazon’s legitimate basis for urgency in seeking preliminary relief.

The moving party also must act diligently. While Amazon was arguably less diligent here than the moving party in Fort Worth , Amazon's efforts in this context were sufficient.

Amazon filed suit on September 5-just six days after the Board issued its second notice to show cause in the Bargaining Case-seeking declaratory and permanent injunctive relief. Although the Bargaining Case had begun a little more than a year prior, there was minimal action in the Bargaining Case while the related Election Case proceeded; in fact, Amazon had argued in response to the Board’s first notice to show cause that the Board could not resolve issues in the Bargaining Case until it completed the Election Case. The Board denied review of the Election Case on August 29, 2024, and issued its second notice to show cause in the Bargaining Case on August 30. Amazon had little reason to challenge the effectively paused Page 21Bargaining Case until the Election Case ended, and Amazon promptly sued once it did.

Amazon's complaint also requested a TRO and a preliminary injunction against the Bargaining Case. The complaint made clear Amazon’s deadline to respond to the NLRB 's summary judgment motion was September 13.³⁷ Amazon also emphasized that its 'need for a temporary restraining order is imminent and dire because the NLRB may issue an order in [the Bargaining Case] any time on or after September 13, 2024.” Amazon also requested that the court “set a hearing for a preliminary injunction, and, after a properly noticed hearing, issue a preliminary injunction.”

On September 9, the court advised Amazon that a local rule required submitting an application for temporary or preliminary relief in a separate motion. Amazon filed its motion for a TRO and preliminary injunction on September 10. Amazon’s motion reiterated the urgency it had raised in its complaint, emphasizing that “Amazon must file any supplemental opposition to the original Notice to Show Cause on or before Friday, September 13, 2024 ' (bold, italics, and underline in original).

Both the September 5 complaint and September 10 motion made clear that Amazon’s show-cause deadline was (initially) September 13, after which the Board would be poised to issue a ruling on the General Counsel's summary judgment motion, potentially mooting Amazon's district court claims. Amazon repeatedly emphasized the (postponed) September 27 show-cause deadline at the September 24 motions hearing, even stating at one point that it “want[ed] the TRO today.' At the end of the hearing, Amazon represented that “a TRO or preliminary injunction does need to be granted to, again, stop the NLRB from issuing an order in the' Bargaining Page 22Case '[b]ecause if it goes forward after this Friday and issues an order granting the summary judgment [motion], then the constitutional issues again are mooted.” Finally, Amazon’s September 26 letter brief told the district court that Amazon would consider its motion effectively denied on September 27.

In my view, these facts show that Amazon “made clear from its first filing that . . . [it] had an unusually short window of time” before it needed injunctive relief, which it “repeated” multiple times.³⁸ I accept that Amazon failed until September 26 to state expressly that it would consider its motion “effectively denied” when the show-cause deadline arrived on September 27. But it was indisputably clear from the earlier filings that Amazon, if it were entitled to preliminary injunctive relief, needed a ruling before the show-cause deadline, after which the Board’s action could leave Amazon’s alleged injury “impossible to remedy.” 39 The NLRB argues that Amazon tried “to impose a decisional deadline with barely one day’s notice.” Yet even the district court commented at the motions hearing that Amazon was “asking [it] to make a major decision on two weeks’ notice.” Given this statement by the district court, I cannot agree with the majority opinion’s conclusion that, by the end of the hearing, Amazon had failed to “ma[k]e clear its need” for an expedited ruling by the show-cause deadline.⁴⁰

Ironically, whatever doubt there might have been from Amazon's failure to repeat some apparently talismanic phrase earlier, the NLRB 's September 10 transfer motion made clear that “Amazon can claim that its motion for injunctive relief has been 'effectively denied,' . . . [on] Friday, Page 23September 13,” which was the then-operative show-cause deadline. While the NLRB ’s brief in this court characterizes this concession as a suspicion “that Amazon might seek to manufacture an effective-denial argument,” the concession at the very least makes clear that the parties and district court understood by September 10 that Amazon was seeking relief before the Board-imposed show-cause deadline.

The majority opinion faults Amazon for failing to object at the motions hearing when the district court set the supplemental briefing deadline at noon on September 27.⁴¹ I do not believe this means Amazon failed to act diligently. Amazon had repeatedly made clear—including, by my count, five times earlier during that very hearing-that it needed relief by the showcause deadline.⁴² Our decision in Fort Worth does not require that Amazon have repeated its need for relief yet again .

I do not mean to criticize the district court. “District courts have wide discretion in managing their docket,” and “plaintiffs cannot simply say they need an expedited ruling and then appeal by claiming effective denial when they don’t get it on their preferred timeline.” 43 Amazon asked the court to consider complex constitutional issues on an accelerated timeline, which no doubt placed great pressure on the court. Notably, unlike in Fort Worth —Page 24 where the district judge sua sponte directed his attention to another matter entirely-the judge here took some action on Amazon's motion by scheduling a hearing and eventually denying the TRO after Amazon appealed. We have declined jurisdiction where the district court has done far less because “mere inaction is not an order refusing injunctive relief, and is not appealable.'⁴⁴ But at bottom, there was limited time in which preliminary relief could preserve the district court’s ability to grant meaningful permanent relief, assuming Amazon was entitled to either. Given that legitimate basis for urgency, as well as Amazon's relative diligence pursuing its precise claims and the uncertainty as to what would transpire (and when) after the show-cause deadline, I believe the principles in Fort Worth support interlocutory appellate jurisdiction here.

* * *

For these reasons, I would exercise interlocutory appellate jurisdiction to reach the merits of Amazon's appeal. Because the court instead dismisses the appeal for lack of jurisdiction, I respectfully dissent.