The Yale Law Journal

January 2016

Jurisdictional Rules and Final Agency Action

Administrative Law

When Congress creates a statutory cause of action, some required elements of that cause of action may be considered “jurisdictional,” while others may not. The difference between jurisdictional and nonjurisdictional requirements is subtle but important. A jurisdictional element limits the power and authority of the courts. If a litigant fails to satisfy a jurisdictional element of a cause of action, the court lacks the statutory authority to hear the case and issue a decision on the merits.1 By contrast, nonjurisdictional elements have no bearing on the authority of the courts. Even when a plaintiff fails to satisfy a nonjurisdictional requirement, the court can still decide the case on the merits. If the defendant decides not to address the plaintiff’s failure to satisfy a nonjurisdictional requirement, the court cannot dismiss the case sua sponteon those grounds, so the plaintiff can still win the case.

The distinction between jurisdictional and nonjurisdictional requirements has received significant attention in recent years, as the Supreme Court has issued a series of rulings narrowing the scope of what courts can properly consider jurisdictional.2 Nonetheless, despite the Court’s recent decisions narrowing the set of rules that qualify as jurisdictional, a number of lower federal courts continue to embrace the jurisdictional label, even absent clear statutory authorization. This Comment explores that phenomenon by evaluating recent doctrinal developments with respect to one salient legal rule in particular: the final agency action requirement in administrative law. Final agency action is the unusual statutory requirement that affects judicial review across a wide range of substantive issues and cases. That requirement, codified in the Administrative Procedure Act (APA), plays an important role in administrative-law litigation.3

Part I of this Comment explores the importance of jurisdictional treatment for courts and litigants. Erroneous jurisdictional treatment can jeopardize litigants’ access to the courts and tilt the playing field in the government’s favor. Part II then argues that the lower courts’ treatment of the final agency action requirement is out of sync with the Supreme Court’s decisions clarifying the proper scope of the jurisdictional label. In some cases, the lower courts engage with the underlying statute and simply come to the wrong result as a matter of statutory interpretation; in other cases, the courts ignore the statute altogether, using jurisdictional treatment as a mechanism for managing their rising caseloads and preventing premature judicial intervention. Part III explores how courts and Congress might recalibrate their treatment of final agency action to resolve the existing doctrinal discord. The Comment concludes by explaining that the tension between the lower courts’ application of the jurisdictional label and the Court’s doctrine on jurisdictional treatment appears to extend far beyond final agency action.

I. the importance of jurisdictional treatment

In recent years, the Supreme Court has paid significant attention to the boundary between jurisdictional and nonjurisdictional rules. Arguably the most important decision in this line of cases is Arbaugh v. Y & H Corp.,4 where the Court announced the doctrinal test that distinguishes jurisdictional from nonjurisdictional rules: Congress must “clearly state[] that a threshold limitation on a statute’s scope shall count as jurisdictional” in order for courts to treat the limitation as such.5 Since Arbaugh, the Court has applied this clear statement rule in a number of cases reversing lower-court decisions and narrowing the application of the jurisdictional label.6 To be sure, the Court has acknowledged that Congress need not “incant magic words in order to speak clearly”7 and that “context, including this Court’s interpretation of similar provisions in many years past, is relevant” to whether Congress has spoken with sufficient clarity to warrant jurisdictional treatment.8 As a result, the application of the clear statement rule sometimes can be more art than science.9 Nonetheless, these cases have a clear message: judges must train their focus, first and foremost, on the statutory text. Lower courts do not have discretion to apply the jurisdictional label without statutory authorization from Congress.

The distinction between jurisdictional and nonjurisdictional rules has captured the Court’s attention in recent years partly because of the significant consequences jurisdictional treatment carries for litigants. First, when a particular statutory requirement is considered jurisdictional, neither party can waive or forfeit arguments about whether that requirement has been met.10 Even when the defendant fails to argue in the trial court that a jurisdictional requirement was not satisfied, the courts can still consider that argument on appeal. By contrast, when the requirement is nonjurisdictional, litigants who fail to raise the issue in the court of first impression lose their opportunity to raise that challenge on appeal.11 Second, when a statutory element is treated as jurisdictional, courts have “an independent obligation” to determine whether that element has been satisfied.12 Even when the defendant concedes that the requirement has been met, the court is required to independently evaluate whether this is true. Courts are under no such obligation when the element is not considered jurisdictional.13

Given the consequences of jurisdictional treatment for litigants and courts, it is unsurprising that jurisdictional treatment sometimes can affect case outcomes. Consider, for example, the D.C. Circuit’s recent decision in Marcum v. Salazar.14 The plaintiffs challenged the government’s decision to deny their applications for permits to import “elephant trophies” from a hunting trip. The government did not contest the existence of final agency action in district court, but it decided to do so on appeal.15 The D.C. Circuit explained that the government was right: the plaintiffs’ claim ordinarily would not have been actionable “for want of final agency action.”16 But as the court acknowledged, and as explained in Part II, final agency action is not a jurisdictional requirement in federal-question cases brought under 28 U.S.C. § 1331.17 For that reason, the government had “forfeited the objection” by not raising it in district court.18 Though the court recognized that the government’s position had merit, treating finality as nonjurisdictional meant that the court could not decide the case in the government’s favor on finality grounds. If the requirement had instead been jurisdictional, the court would have been required to dispose of the case based on the lack of finality.19

Of course, jurisdictional treatment is not always outcome determinative. As long as the government contests the existence of final agency action in the court of first impression, the jurisdictional label likely will not affect case outcomes; the court can dismiss the case for failure to state a claim.20 It is only where the government fails to raise the issue that the jurisdictional label matters. In these cases, erroneously treating final agency action as jurisdictional means that, even where the government technically has waived or forfeited the finality argument, the court can address finality sua sponteand dismiss the case on finality grounds without ever reaching the merits. This gives the government a free pass, and it deprives plaintiffs of the protection of traditional waiver and forfeiture rules, making a successful lawsuit against the government less likely. For that reason, erroneous jurisdictional treatment tilts the playing field in the government’s favor, threatening to skew the relationship between the executive branch and citizens adversely affected by government policy.

II. final agency action and jurisdiction

Despite the Court’s efforts to fashion a “readily administrable bright line” narrowing the scope of the jurisdictional label,21 lower federal courts continue to treat the final agency action requirement as jurisdictional, even absent clear statutory authorization. As with any clear statement rule, reasonable jurists often disagree about whether a statute speaks clearly. For that reason, faulty jurisdictional treatment is sometimes simply the result of lower courts relying on a plausible but ultimately incorrect interpretation of a jurisdictional statute. But on other occasions, the lower courts diverge much more dramatically from the Court’s clear statement rule. In this latter class of cases, lower courts ignore the text of the jurisdictional statute altogether, applying the jurisdictional label as a common-law mechanism for managing rising caseloads and shielding the executive branch from judicial review early on in the agency’s process.

A. Jurisdictional Treatment Through Faulty Statutory Interpretation

The courts of appeals are divided over whether to treat final agency action as jurisdictional when an administrative law case is first brought in district court pursuant to 28 U.S.C. § 1331, the federal-question statute. Some federal circuits treat the requirement as jurisdictional in these circumstances,22 while others do not.23 The Fifth Circuit’s 2014 decision in Belle Co. v. United States Army Corps of Engineers illustrates the intuitive appeal of jurisdictional treatment.24In Belle,the Fifth Circuit relied on the language of the APA, noting that section 704 of the statute “authorizes judicial review only of ‘final agency action for which there is no other adequate remedy in a court.’”25 From that seemingly obvious statutory language, the court concluded that “[i]f there is no final agency action, a court lacks subject-matter jurisdiction.”26

Despite its surface-level appeal, however, the Fifth Circuit’s position is likely incorrect as a matter of statutory interpretation. The D.C. Circuit’s 2006 decision in Trudeau v. FTC illustrates why final agency action is actually nonjurisdictional in federal-question cases.27 The Trudeau court emphasized the Supreme Court’s decision in Califano v. Sanders, which held that the APA is not itself a grant of subject-matter jurisdiction.28 As the Supreme Court has explained, this means that the “judicial review provisions of the APA”—where the final agency action requirement appears—“are not jurisdictional.”29 With Califano in mind, the D.C. Circuit then applied Arbaugh’s clear statement rule.30 “Because Congress did not clearly state that the final agency action requirement of APA § 704 is jurisdictional,”31 the final agency action requirement could not deprive the court of jurisdiction.32 This conclusion was underscored by the fact that nothing in the federal-question statute—the actual jurisdictional statute in the case—can be construed to require finality.33

The D.C. Circuit’s reasoning suggests that a number of circuits have ignored Califano when evaluating the jurisdictional status of the APA’s finality requirement in federal-question cases. In fact, upon recognizing this omission, at least three circuits that had previously treated final agency action as jurisdictional in at least some federal-question cases—the Second, Fourth, and Federal Circuits—have recently questioned the appropriateness of treating finality as jurisdictional under such circumstances.34 But even as some courts begin to recognize the error in their interpretation of the APA’s final agency action requirement, jurisdictional treatment in federal-question cases remains the prevailing view in several of the federal courts of appeals.35 In light of the Supreme Court’s decision in Califano, this is a view undergirded by a faulty interpretation of the APA.

B. Jurisdictional Treatment Through Judge-Made Common Law

Even when lower courts adopt a second-best interpretation of a jurisdictional statute, they are at least following the Court’s statute-focused approach to distinguishing jurisdictional from nonjurisdictional rules. But the lower courts do not always follow that approach. Sometimes, they ignore the statutory text altogether.

Consider how courts treat final agency action in direct-review cases. In these cases, litigants bring suit directly in the court of appeals under one of roughly one thousand direct-review statutes that allow litigants to bypass district courts.36 In many direct-review statutes, jurisdictional treatment of final agency action makes sense, as Congress clearly indicates that finality should be jurisdictional. For example, Congress has given the courts of appeals direct-review jurisdiction to hear cases challenging “all final orders of the Federal Communications Commission” and “all final orders of the Secretary of Agriculture.”37 These statutes specifically indicate that the courts of appeals only have direct-review jurisdiction over “final orders.” In other words, finality is a prerequisite to jurisdiction.

While many direct-review statutes clearly indicate that finality is jurisdictional, not all do. For example, the direct-review provision of the Resource Conservation and Recovery Act (RCRA) specifies that “a petition for review of action of the [EPA] Administrator in promulgating any regulation[] or requirement . . . may be filed only” in the D.C. Circuit.38 The judicial review provision never mentions finality, nor does it provide any kind of clear signal—at least not the type of clear signal found in other direct-review statutes—that finality is a prerequisite to exercising jurisdiction. Other jurisdiction-conferring statutes, such as those relating to Federal Energy Regulatory Commission and Federal Aviation Administration decisions, also do not mention finality in their judicial review provisions.39

Even though these direct-review statutes do not mention finality, several courts of appeals have indicated that the final agency action requirement should be considered jurisdictional under these statutes.40 These decisions do not explain why the statutory text compels jurisdictional treatment of the finality requirement.41 In fact, some of these decisions have explicitly acknowledged the disconnect between their holdings and the statutory text.42

Why do courts impose a jurisdictional finality requirement without statutory authorization? In turning away from the statutory text, courts have offered two prudential justifications. First, some courts contend that jurisdictional finality prevents judges from prematurely intruding into the agency decision-making process. As one court explained, by denying courts the ability to hear cases until the agency has made a final decision, a jurisdictional finality requirement “ensure[s] there will be no interference with the administrative process.”43 Second, some courts argue that making finality jurisdictional prevents courts from “squander[ing] judicial resources” while litigants still have the “opportunity to convince the agency to change its mind.”44 Applying the jurisdictional label makes it less likely that courts will have to engage in piecemeal review prior to the completion of the agency’s process. On this view, jurisdictional treatment allows courts to avoid addressing the merits in litigation that would otherwise unnecessarily burden their dockets.45

While much of the most forceful prudential reasoning predates Arbaugh, these prudential arguments still continue to influence the courts even after the Court’s recent efforts to narrow the use of the jurisdictional label.46 Some courts have even explicitly acknowledged that they issue jurisdictional dismissals for want of final agency action “for the sake of judicial economy.”47 These justifications are untethered from the statutory text and are in tension with the Court’s approach to identifying jurisdictional rules. They are a product of exactly the kind of judge-made common law the Court has sought to eliminate in this area.

III. recalibrating the doctrine in the lower courts

The foregoing discussion suggests that the doctrine in the lower courts is in need of recalibration. Many courts incorrectly treat finality as jurisdictional in federal-question cases because they have misinterpreted the underlying jurisdictional statute.48 In these cases, the lower courts must acknowledge that the APA is not a jurisdictional statute.49 Where a court takes jurisdiction pursuant to the federal-question statute, final agency action should not be considered jurisdictional. Instead, it is a nonjurisdictional element of an APA cause of action.

In other cases, the lower courts base their jurisdictional determinations on prudential considerations entirely external to the jurisdictional statutes adopted by Congress. This kind of judge-made common law is out of step with the Arbaugh clear statement rule, which requires courts to train their focus primarily on the text of the jurisdictional statute.50 To bring their doctrine into line with the Court’s precedent, the lower courts should pay attention first and foremost to the text of the jurisdictional statute. In many direct-review cases, this will still mean that finality should be jurisdictional. But in some cases, such as those brought under RCRA’s direct-review provision, the courts should treat finality as nonjurisdictional because the direct-review statute does not speak with the requisite level of clarity to warrant jurisdictional treatment.51

Nonetheless, any attempt to bring long-term stability to the jurisdictional doctrine on final agency action—particularly in direct-review cases—may not ultimately succeed without Congress’s help. The lower courts’ prudential justifications for viewing finality as jurisdictional hint at some of the institutional incentives that might push the lower courts toward jurisdictional treatment. As some scholars have explained, lower federal courts face a “crisis of volume.”52 Rising caseloads have stretched judicial resources thin.53 By treating statutory requirements as jurisdictional, the lower federal courts may be able to constrict the scope of their own jurisdiction and thereby reduce the number of cases they must address on the merits. Indeed, this logic seems to undergird the prudential arguments that courts sometimes use to justify jurisdictional treatment.54

Without congressional action to address the institutional incentives that drive jurisdictional treatment, some lower courts might continue to ignore the Arbaugh clear statement rule and treat finality as jurisdictional, even without clear statutory authorization. Scholars have offered a laundry list of possible solutions to reduce the burdens facing the federal courts, and I do not intend to recapitulate that list here.55 The point is simply that Congress might be able to bring more stability to the doctrine by alleviating some of the existing pressures on the federal courts.


While this Comment has focused specifically on the final agency action requirement, the tension between the Supreme Court’s doctrine on jurisdictional rules and the lower courts’ implementation of that doctrine is one that extends beyond final agency action. This tension is perhaps best captured by the fact that the Court recently has granted certiorari in a surprisingly high number of cases in which the lower courts have treated statutory requirements as jurisdictional.56 In many of these cases, the Court has unanimously reversed the lower courts.57

This Comment sheds light on why this tension has emerged. It is hardly surprising that matters of statutory interpretation sometimes divide the courts. More surprising, however, is that lower courts sometimes ignore the Court’s clear statement rule altogether, choosing instead to impose jurisdictional treatment as a common-law mechanism for managing their caseloads and narrowing the scope of judicial review. Indeed, this kind of prudential reasoning also appears in other lower-court cases outside the final agency action context.58 Resolving the tension between the lower courts and the Supreme Court thus may require more than just a concerted effort by the lower courts to adhere to the Court’s doctrine. It may also require congressional action to address the underlying institutional incentives that push the lower courts toward jurisdictional treatment.