Gus Hurwitz on A Policy Statement Is Not Enough

Administrative law really is a strange beast. My last post explained this a bit, in the context of Chevron. In this post, I want to make this point in another context, explaining how utterly useless a policy statement can be. Our discussion today has focused on what should go into a policy statement – there seems to be general consensus that one is a good idea. But I’m not sure that we have a good understanding of how little certainty a policy statement offers.

Administrative Stare Decisis?

I alluded in my previous post to the absence of stare decisis in the administrative context. This is one of the greatest differences between judicial and administrative rulemaking: agencies are not bound by either prior judicial interpretations of their statutes, or even by their own prior interpretations. These conclusions follow from relatively recent opinions – Brand-X in 2005 and Fox I in 2007 – and have broad implications for the relationship between courts and agencies.

In Brand-X, the Court explained that a “court’s prior judicial construction of a statute trumps an agency construction otherwise entitled to Chevron deference only if the prior court decision holds that its construction follows from the unambiguous terms of the statute and thus leaves no room for agency discretion.” This conclusion follows from a direct application of Chevron: courts are responsible for determining whether a statute is ambiguous; agencies are responsible for determining the (reasonable) meaning of a statute that is ambiguous.

Not only are agencies not bound by a court’s prior interpretations of an ambiguous statute – they’re not even bound by their own prior interpretations!

In Fox I, the Court held that an agency’s own interpretation of an ambiguous statute impose no special obligations should the agency subsequently change its interpretation.[1] It may be necessary to acknowledge the prior policy; and factual findings upon which the new policy is based that contradict findings upon which the prior policy was based may need to be explained.[2] But where a statute may be interpreted in multiple ways – that is, in any case where the statute is ambiguous – Congress, and by extension its agencies, is free to choose between those alternative interpretations. The fact that an agency previously adopted one interpretation does not necessarily render other possible interpretations any less reasonable; the mere fact that one was previously adopted therefore, on its own, cannot act as a bar to subsequent adoption of a competing interpretation.

What Does This Mean for Policy Statements?

In a contentious policy environment – that is, one where the prevailing understanding of an ambiguous law changes with the consensus of a three-Commissioner majority – policy statements are worth next to nothing. Generally, the value of a policy statement is explaining to a court the agency’s rationale for its preferred construction of an ambiguous statute. Absent such an explanation, a court is likely to find that the construction was not sufficiently reasoned to merit deference. That is: a policy statement makes it easier for an agency to assert a given construction of a statute in litigation.

But a policy statement isn’t necessary to make that assertion, or for an agency to receive deference. Absent a policy statement, the agency needs to demonstrate to the court that its interpretation of the statute is sufficiently reasoned (and not merely a strategic interpretation adopted for the purposes of the present litigation).

And, more important, a policy statement in no way prevents an agency from changing its interpretation. Fox I makes clear that an agency is free to change its interpretations of a given statute. Prior interpretations – including prior policy statements – are not a bar to such changes. Prior interpretations also, therefore, offer little assurance to parties subject to any given interpretation.

Are Policy Statements entirely Useless?

Policy statements may not be entirely useless. The likely front on which to challenge an unexpected change agency interpretation of its statute is on Due Process or Notice grounds. The existence of a policy statement may make it easier for a party to argue that a changed interpretation runs afoul of Due Process or Notice requirements. See, e.g., Fox II.

So there is some hope that a policy statement would be useful. But, in the context of Section 5 UMC claims, I’m not sure how much comfort this really affords. Regulatory takings jurisprudence gives agencies broad power to seemingly-contravene Due Process and Notice expectations. This is largely because of the nature of relief available to the FTC: injunctive relief, such as barring certain business practices, even if it results in real economic losses, is likely to survive a regulatory takings challenge, and therefore also a Due Process challenge.  Generally, the Due Process and Notice lines of argument are best suited against fines and similar retrospective remedies; they offer little comfort against prospective remedies like injunctions.

Conclusion

I’ll conclude the same way that I did my previous post, with what I believe is the most important takeaway from this post: however we proceed, we must do so with an understanding of both antitrust and administrative law. Administrative law is the unique, beautiful, and scary beast that governs the FTC – those who fail to respect its nuances do so at their own peril.