The foundations of modern administrative law were laid in 1980, with the disparate opinions of a sharply divided Court in Industrial Union Department, AFL-CIO v. American Petroleum Institute (commonly referred to as the “Benzene Case”). Consider four points.
- The Benzene Case is now understood to be the first contemporary appearance of the Major Questions Doctrine.
- The Benzene Case marked the return of the nondelegation doctrine, signaled most plainly by then-Justice William Rehnquist’s elaborate concurring opinion but also by a favorable reference in the plurality opinion by Justice John Paul Stevens and an open-minded sentence from Justice Lewis Powell.
- The Benzene Case is the origin of contemporary cost-benefit default principles, permitting or requiring agencies to exempt de minimis risks, to consider costs, and to engage in some form of cost-benefit balancing, unless Congress has squarely said otherwise.
- The Benzene Case essentially defined “significant risk,” with a precise numerical definition (one in one thousand) that persists at the Department of Labor to this day. At the same time, a close analysis of the plurality opinion in the Benzene Case shows that it is best understood as a specification, above all, of the Absurdity Canon—a Church of the Holy Trinity v. United States for the modern administrative state—with the specific purpose of ensuring against the imposition of high costs for small benefits, and thus of requiring a kind of proportionality between costs and benefits. So understood, the Benzene Case had, and continues to have, an important and salutary effect on regulatory programs. Its significant and much broader current role, more than four decades after the opinions were issued, is an intriguing case study in doctrinal development, and in particular, how Supreme Court decisions can plant small seeds that become big trees.
I. Introduction: Seeds Into Trees
Was modern administrative law born in 1980? Did it spring from the disparate opinions of a sharply divided Court in Industrial Union Department, AFL-CIO v. American Petroleum Institute (often referred to as the “Benzene Case”)? Did Chief Justice Warren Burger and Justices William Brennan, Potter Stewart, Byron White, Thurgood Marshall, Harry Blackmun, Lewis Powell, William Rehnquist, and John Paul Stevens—all now deceased—establish the foundations of administrative law as it stands today?
One could make the argument. Consider four points.
- The Benzene Case uses and adapts a specification of the Absurdity Canon to the particular setting of the administrative state. In brief, the specification requires the benefits of regulation to justify the costs of regulation. The Benzene Case can even be seen as a Church of the Holy Trinity v. United States for the modern era, particularly designed for a period of pervasive national regulation involving safety, health, and the environment. So understood, the Benzene Case launched a thousand ships.
- The Benzene Case marks the return of the nondelegation doctrine, signaled most plainly by Justice William Rehnquist’s elaborate and somewhat shocking concurring opinion, but also by a favorable and also somewhat shocking reference in the plurality opinion by Justice John Paul Stevens.
- The Benzene Case is now understood to be the first appearance of the Major Questions Doctrine, requiring explicit congressional authorization for certain kinds of agency action best described as “transformative” or “staggering.”
- The Benzene Case is the origin of contemporary cost-benefit default principles, permitting and even requiring agencies to exempt de minimis risks, to consider costs, and to engage in some form of cost-benefit balancing unless Congress has explicitly said otherwise.
- The Benzene Case essentially defined “significant risk,” with a definition that persists at the agency level to this day.
My goal in this Essay is to develop each of these points, with close reference to the plurality opinion. My major emphasis is on (1), (4), and (5) above: by calling for a demonstration that risks are “significant,” and by strongly signaling the need to balance benefits against costs, the Benzene Case was a defining moment in the rise of the Cost-Benefit State. But it must be emphasized that the decision has done much more; contemporary administrative law owes a great deal to it. The Benzene Case planted numerous seeds. They are now trees.
II. “Reasonably Necessary or Appropriate”
Two statutory provisions were at issue in the Benzene Case. The first is the definition of an “occupational safety and health standard.” That provision states: “The term ‘occupational safety and health standard’ means a standard which requires conditions, or the adoption or use of one or more practices, means, methods, operations, or processes, reasonably necessary or appropriate to provide safe or healthful employment and places of employment.”
Suppose that this provision was the only substantive one in the Act. What does it mean? An obvious puzzle is that a definitional clause need not be taken to include substantive criteria. It defines what a term means, but it is not the usual place to find restrictions on agency authority. In the case of the Occupational Safety and Health Administration (OSHA), however, it is the only port in a storm outside the context of toxic substances. No other provision of the statute offers relevant criteria for the agency to follow.
One possibility, and perhaps the most natural, is that the definitional provision contemplates some form of cost-benefit balancing. The words “reasonably necessary” are plausibly taken to do that: “[N]ecessary” signals that there has to be some problem of safety to which the agency must respond, while “reasonably” connotes some form of balancing. If the only language were “reasonably necessary to provide safe or healthful employment,” it might be understood to favor cost-benefit balancing. The words “or appropriate” can be seen to make that interpretation easier rather than harder. The term “appropriate” might well be taken to suggest some form of balancing. Whether a regulation is “appropriate” depends on its costs and benefits.
At the same time, the cost-benefit interpretation of the clause is hardly unavoidable. Some statutes explicitly refer to consideration of costs and benefits, but the term “reasonably necessary or appropriate” is abstract and does not explicitly do that. Because it does not, some interpreters might insist that it is important to pause before accepting the view that it does so implicitly.
A second possibility is that the relevant words signal a simple requirement: a standard must address a significant risk to safety and health in the workplace. If a standard would reduce a nonexistent risk, it would not be “reasonably necessary or appropriate,” and so too if it would address a trivial or de minimis risk. In this view, there is no need to engage in cost-benefit balancing. What is required is identification of a significant risk so that the Secretary is acting in a way that responds to the reason that the Act was enacted in the first instance: to protect occupational safety and health. This is the view that the plurality embraced in the Benzene Case.
A third view is that the phrase “reasonably necessary or appropriate,” especially in a definitional clause, is essentially an open-ended grant of discretion. It could mean anything at all. Its meaning lies in the eye of the beholder. Therefore, it is a blank check to the Secretary of Labor. If there is a nondelegation doctrine, the definitional clause violates it. That is Justice Rehnquist’s view in the case. What is remarkable, and not much noticed, is that Justice Rehnquist raised the nondelegation objection entirely on his own. The issue was not briefed or argued. Not used to invalidate a statute since 1935, and never used to invalidate a statute before that year, the nondelegation doctrine was widely regarded as a kind of dinosaur, which is undoubtedly one reason that no one in the case raised it.
Which view is best? The Avoidance Canon suggests that the third view should be rejected if it is possible to do so. The Court ought not to lightly strike down an act of Congress. Cost-benefit balancing would not violate the nondelegation doctrine; the same is true of a requirement that the Secretary identify a significant risk. But it cannot be said that the phrase “reasonably necessary or appropriate” clearly makes a choice between the two options. Perhaps the best approach would be to invoke Chevron U.S.A., Inc. v. Natural Defense Council, Inc., and thus to allow the Secretary to choose between the two interpretations. Or perhaps the best approach would be to invoke Michigan v. Environmental Protection Agency; that agencies should be required to consider costs unless Congress has squarely forbidden them from doing so. On reflection, that is indeed the best approach. A cost-blind approach would not be reasonable, and Congress should not be taken to have forbidden reasonableness or even to have permitted unreasonableness. Thus far, the appropriate interpretation of “reasonably necessary or appropriate” is that the agency must show that the benefits of occupational safety and health standards justify the costs. To be sure, that idea leaves many questions open. But it provides a legally acceptable framework within which the agency must operate.
Let us notice, however, that there is a problem with using the Avoidance Canon to avoid a nondelegation problem. If a court chooses the interpretation that avoids that problem, how, exactly, is that problem avoided? It is one thing to say that a court should choose an interpretation that avoids a free speech problem. By hypothesis, the relevant choice simply avoids that problem. But a nondelegation problem exists when and because Congress has failed to make relevant policy choices. If it is a court that is making such choices, the nondelegation problem would not be avoided at all.
The best response must be that the court is not really making such choices. Instead, it fairly interprets congressional instructions. If Congress uses the phrase “reasonably necessary or appropriate,” the choice of cost-benefit balancing, as the preferred interpretation, is not one of judge-made policy; it is the best understanding of that phrase, taken in context. Here, then, is where we are. Standing by itself, the “reasonably necessary or appropriate” clause requires a form of cost-benefit balancing, though it could also be understood to require the agency to show a “significant risk.” In the Benzene Case, Justice Powell was the only one to press this point. Let us now see why.
III. “No Employee Will Suffer”
Where toxic materials or harmful physical agents are concerned, a standard must also comply with § 6(b)(5), which provides:
The Secretary, in promulgating standards dealing with toxic materials or harmful physical agents under this subsection, shall set the standard which most adequately assures, to the extent feasible, on the basis of the best available evidence, that no employee will suffer material impairment of health or functional capacity even if such employee has regular exposure to the hazard dealt with by such standard for the period of his working life. Development of standards under this subsection shall be based upon research, demonstrations, experiments, and such other information as may be appropriate. In addition to the attainment of the highest degree of health and safety protection for the employee, other considerations shall be the latest available scientific data in the field, the feasibility of the standards, and experience gained under this and other health and safety laws.
That is a mouthful. What does it mean? We know that insofar as we are dealing with toxic materials or harmful physical agents, the standard must be imposed “to the extent feasible.” That means that it cannot be beyond the point that is feasible and also that it cannot fall short of what is feasible. But what counts as feasible? In one view, feasibility is only a matter of technology. If employers lack the technology that would do what the standard requires, they cannot comply with it and cannot be directed to comply with it. But that proposition raises questions of its own. Insofar as we are dealing with technological feasibility, is there a kind of off-on switch? Some technologies do not exist, but they can be made to exist for the right price. Some technologies exist, but they are exceedingly expensive. Are they feasible or not? A judgment about technological feasibility is not simply one of fact. It requires a major judgment, or a series of major judgments, of policy.
We might also think that “to the extent feasible” refers not only to technological feasibility but also to economic feasibility. Suppose that employers have access to the relevant technology to reduce risk (it is readily available) but that the technology costs too much for them to bear. They can no longer stay in business. It stands to reason that the standard is not “feasible.” Even if so, the underlying idea is both abstract and vague: What is meant by the claim that for “employers,” the cost is “too much to bear”? To make sense of that idea, it would have to be specified. What if the cost can be borne by most employers but not all? What if the cost can be borne by eighty percent of employers? Seventy percent? Sixty percent? What if the cost can be borne in the technical sense that employers can stay in business but with a significant reduction in profits (and perhaps a need to scale back operations and thus reduce employment)? Let us bracket these questions for now and simply note that, as with technological feasibility, the idea of economic feasibility requires major judgments of policy, not simply of fact.
Thus far, the words “to the extent feasible” are naturally read to refer to technological and economic feasibility. On an alternative interpretation, “feasible” can be taken to mean something altogether different: justified by reference to an analysis of costs and benefits. In that view, “to the extent feasible” means to the extent desirable after assessing its likely effects, both good and bad. Justice Powell favored that interpretation, and Justice Rehnquist thought it was a reasonable candidate. But there are two problems with that interpretation of “to the extent feasible.”
The first is that it strains ordinary meaning. If someone is asked to do something “to the extent feasible,” they are usually being directed to do it if they possibly can, not if they think they should, all things considered. “Feasible” is more naturally taken to mean “possible” or “practicable,” rather than justified on the basis of cost-benefit balancing. The second problem, and an even more formidable one, is the rest of the statutory phrase: “The standard which most adequately assures, to the extent feasible, on the basis of the best available evidence, that no employee will suffer material impairment of health or functional capacity.”
Pause over the italicized words. Suppose that a regulation would cost $900 million and prevent twenty deaths. Because statistical lives are valued at about $12 million, the regulation would not survive cost-benefit balancing. But if an agency declines to issue that regulation on that ground, it would not “most adequately assure[] . . . that no employee will suffer material impairment of health.” The “no employee will suffer” language seems flatly to preclude an interpretation of “feasible” that would entail cost-benefit balancing.
A textualist might, therefore, settle on the following view: standards must be technologically and economically feasible—no more and also no less. Within that constraint, they must be maximally protective; they must ensure that no employee is killed or (seriously or materially) hurt. That was Justice Thurgood Marshall’s view in the Benzene Case. But is that interpretation mandatory?
Within the bounds of the provision we are now discussing, the simplest answer is yes. A textualist would greatly struggle to avoid that answer. One option would be to invoke the Absurdity Canon. Suppose that a standard would cost $900 million annually and prevent one death annually. Does the Act require the agency to issue that standard? A court might think that Congress could not possibly have meant to mandate that outcome. At the very least, Congress would have to express itself unambiguously if that is the outcome it sought to require. To be sure, the words “no employee will suffer” might be taken to be unambiguous. But perhaps they are best taken as expressive or precatory—a suggestion of the importance of prioritizing health and safety, rather than as a serious directive that the Secretary must ensure against a “material impairment” on the part of even a single employee. A textualist should be nervous here; “no employee will suffer” is not exactly ambiguous.
IV. Canons
What if we take the two provisions together? Consider two alternatives.
The first is to insist that the specific provision involving toxic substances trumps the more general, which is also, after all, a (mere) definitional one. In that view, the “reasonably necessary or appropriate” language may or may not call for cost-benefit balancing, but it cannot possibly overcome or trump the “no employee will suffer” language. Whatever the meaning of the definitional provision, it is essentially irrelevant. Everything depends on the more specific one. This, too, was Justice Marshall’s view, and a majority of the Court accepted it in 1981.
The second is to insist that the “reasonably necessary or appropriate” language establishes a threshold requirement that all standards must meet. Whether it requires cost-benefit balancing or a significant risk, what it requires must be met first before the “no employee will suffer” language becomes relevant. Whether we are dealing with ladders, elevators, or toxic substances, an occupational safety and health standard must always be “reasonably necessary or appropriate.” The additional level of stringency for toxic substances follows a demonstration to that effect. This was the plurality’s view in the Benzene Case.
Under ordinary principles of interpretation, the first alternative is clearly better. A definitional clause is not properly taken to contain a substantive standard that trumps a more specific provision geared to a particular set of problems. For this reason, the committed textualist would be strongly drawn to the first alternative. Here again, the most plausible response would invoke the Absurdity Canon, or perhaps a broader Reasonableness Canon, seeing legislators as reasonable people acting reasonably. The idea would be that if it is fairly possible, courts should interpret statutes to make sense, and an interpretation that gives priority to the “reasonably necessary or appropriate” language makes sense.
In the Benzene Case itself, the plurality offered two different arguments in favor of the “significant risk” requirement, notwithstanding its evident tension with the “no employee will suffer” language, which the plurality entirely ignored. The first argument is worth quoting at length:
In the absence of a clear mandate in the Act, it is unreasonable to assume that Congress intended to give the Secretary the unprecedented power over American industry that would result from the Government’s view of §§ 3(8) and 6(b)(5), coupled with OSHA’s cancer policy. Expert testimony that a substance is probably a human carcinogen—either because it has caused cancer in animals or because individuals have contracted cancer following extremely high exposures—would justify the conclusion that the substance poses some risk of serious harm no matter how minute the exposure and no matter how many experts testified that they regarded the risk as insignificant. That conclusion would in turn justify pervasive regulation limited only by the constraint of feasibility. In light of the fact that there are literally thousands of substances used in the workplace that have been identified as carcinogens or suspect carcinogens, the Government’s theory would give OSHA power to impose enormous costs that might produce little, if any, discernible benefit.
What kind of argument is this? It seems to be something like the Absurdity Canon or, again, a broader Reasonableness Canon. The plurality does not want to attribute to the national legislature an intention that it would be “unreasonable to assume.” That unreasonable intention (and this may well be the key sentence in the entire opinion) would be “to impose enormous costs that might produce little, if any, discernible benefit.” Notwithstanding that iconic phrase, it is important to be careful here; the plurality did not rule that the agency had to show some kind of cost-benefit justification. Its narrower conclusion is that the agency must show a significant risk. But with that requirement in place, at least it can be said that if enormous costs are being imposed, it is not for “little, if any, discernible benefit.”
It should be emphasized that the plurality’s argument, as stated, has nothing at all to do with the actual statutory language. It seems to be a clear statement principle meant to avoid absurdity: if Congress wants to authorize agencies to impose enormous costs for little or no benefit, it must do so expressly.
Here is an alternative way of supporting what the Court is saying here. Consider this footnote from twentieth-century Austrian philosopher Ludwig Wittgenstein: “Someone says to me: ‘Shew the children a game.’ I teach them gaming with dice, and the other says ‘I didn’t mean that sort of game.’ Must the exclusion of the game with dice have come before his mind when he gave me the order?”
The answer to Wittgenstein’s question is “no.” If someone asks me to show a “game” to children, gambling is ordinarily not included in the category of “game,” even though it is technically a game. The same is true of Russian roulette, spin-the-bottle, and boxing. If someone asks me to make a dinner reservation or to find a place for a vacation over the holiday, a wild, absurd, or palpably unreasonable understanding requires strong contextual justification. “I didn’t mean that sort of restaurant!” or “I didn’t mean that sort of vacation place!”—in ordinary conversation, people anticipate that response, and they do not make choices that would elicit it.
Applied to the Benzene Case, the basic idea would be that if Congress has used an ambiguous term, akin to “game,” it should not be taken to have done something unlikely, extraordinary, bizarre, or evidently unreasonable. To be sure, and importantly, the “no employee will suffer” language is not an ambiguous term, akin to “game.” But an understanding of that language to require massive expenditures for small gains might well be thought likely to evoke this kind of reaction from Congress: “We did not mean that sort of game.” Textualists might well be Wittgensteinians; in fact, they ought to be. To be sure, the Benzene Case was not simple on this count, again, because the phrase “no employee will suffer” does not seem ambiguous. Whether textualists should understand that phrase as expressive or precatory, or instead as fixed and firm, is a legitimate question. But the plurality’s answer is simple: The phrase cannot possibly be taken to mean what it appears to say.
The plurality also offered a second and quite different argument:
If the Government was correct in arguing that neither § 3(8) nor § 6(b)(5) requires that the risk from a toxic substance be quantified sufficiently to enable the Secretary to characterize it as significant in an understandable way, the statute would make such a “sweeping delegation of legislative power” that it might be unconstitutional under the Court’s reasoning in A.L.A. Schechter Poultry Corp. v. United States, 295 U.S. 495, 539, and Panama Refining Co. v. Ryan, 295 U.S. 388. A construction of the statute that avoids this kind of open-ended grant should certainly be favored.
What is remarkable here is that since 1935, the Court had not invoked the nondelegation doctrine with this degree of enthusiasm—a span of forty-five years. What is also remarkable is that no party in the case had raised the specter of Schechter Poultry. Invocation of the nondelegation doctrine to cabin agency discretion was, in 1980, a major step.
If there is a nondelegation doctrine, we should be able to agree on the general principle. Suppose a statute could be interpreted in two ways: The first would be an open-ended grant of authority. The second would contain an intelligible principle. In light of the Avoidance Canon, the second interpretation should be preferred. But does that general principle support the paragraph quoted above? That is not at all clear. If a statute required an agency to eliminate all workplace risks, to the extent feasible, it would hardly be an unconstitutional grant of discretion. It would instead be a severe, even draconian requirement, of the kind that is unusual but not unheard of in federal regulatory law. The plurality seems to have confused (1) a statute that grants unbounded discretion with (2) a statute that imposes an absolute requirement of safety. A law that requires the U.S. Environmental Protection Agency (EPA) to ensure that no one dies from mercury is very different from a law that authorizes EPA to do whatever it likes with respect to mercury. The former statute is not a grant of open-ended discretion.
Can we imagine a response to this objection? The best attempt might be to concede that if a statute requires an agency to regulate very aggressively, it does not confer much discretion on the agency once it has decided what toxic material or harmful agent to regulate—but to emphasize that it does confer on the agency a great deal of discretion in deciding which toxic material or harmful agent to regulate. The fact that the agency can pick or choose what to regulate (very severely) is effectively a nondelegation problem. Perhaps that is the problem that the plurality had in mind in the Benzene Case.
The difficulty with this argument is that broad prosecutorial discretion has never been thought to produce a nondelegation problem, and for good reasons. It is central to executive authority to decide against whom or what to initiate proceedings. To be sure, Congress can constrain that discretion, but nothing in Article I requires it to do so.