Module 2: Rulemaking: Notice-and-Comment & Beyond
This is how most binding federal regulations actually come into existence — not by a single official’s decree, but through a structured, publicly visible process Congress built to keep agency lawmaking genuinely accountable. Every section below is pre-written and deterministic; nothing is generated live.
Free preview
The first two lectures of Administrative Law are free, so you can see exactly what the course is like. Like it? Unlock the whole course.
Look first, then buy. Free previews on every product page. Secure payment by Stripe. Pay once, keep it forever. Details
Part 1 — Learn the Material
Read this first. Everything below assumes you know these things — come back here any time you need a refresher.
The APA §553 Framework
Recalling Module 1’s introduction to the APA, its §553 rulemaking provision sets the basic sequence: propose, take comments, finalize. This structure applies across virtually all federal agencies adopting a legislative rule.
That basic sequence is deliberately close to the floor of what an agency must do, not the floor of what a court can demand. In Vermont Yankee Nuclear Power Corp. v. NRDC, 435 U.S. 519 (1978), the Supreme Court unanimously reversed a court of appeals that had required a federal agency to use additional procedures beyond what §553 itself specifies, reasoning that Congress struck a deliberate balance when it wrote the APA’s procedural requirements, and that courts generally may not impose extra procedural hurdles on top of that balance simply because a judge thinks more process would produce a better rule. Vermont Yankee remains the reason §553’s propose-comment-finalize sequence is treated as essentially the complete recipe for informal rulemaking, rather than a floor courts are free to build additional requirements onto case by case.
Example. An agency proposing a new workplace-safety standard follows the same basic §553 sequence a different agency would follow proposing an entirely unrelated environmental standard.
The Notice of Proposed Rulemaking
A Notice of Proposed Rulemaking (NPRM) must include the terms or substance of the proposed rule, or a description of the subjects and issues involved, published in the Federal Register.
The Federal Register itself exists because of a genuine embarrassment the government suffered in court. In Panama Refining Co. v. Ryan, 293 U.S. 388 (1935) — the famous “hot oil” case — government lawyers arguing to defend a New Deal oil-production regulation discovered, mid-litigation, that the specific regulatory provision at issue had actually been revoked months earlier, but no reliable, centralized publication existed anywhere confirming what federal regulations were currently in force. Congress responded the very same year with the Federal Register Act of 1935, creating the Federal Register as the single, authoritative, publicly available record of federal regulatory action — the same publication an NPRM appears in today. That origin is worth remembering: the notice requirement isn’t merely a procedural nicety, it exists because the alternative — regulated parties and even the government itself unable to reliably determine what the law actually required — proved genuinely unworkable in practice.
Example. An NPRM proposing a specific numeric emissions threshold, along with the agency’s reasoning and the data it relied on, gives the public real, meaningful notice — a vague announcement that “emissions rules may change” would not.
The Comment Period
During the comment period, the public submits data, objections, and alternatives — and the agency must genuinely consider and respond to significant comments, not merely collect them as a formality.
That genuineness requirement extends to more than just the written comments themselves — it also constrains private, off-the-record contact with the agency while the record is still open. In Home Box Office, Inc. v. FCC, 567 F.2d 9 (D.C. Cir. 1977), the D.C. Circuit held that once an NPRM issues, undisclosed ex parte contacts between agency officials and interested parties threaten the integrity of the public comment process itself — if the agency is quietly persuaded by arguments or data outside the record, the public record everyone else relied on to comment no longer reflects the real basis for the agency’s eventual decision. The case pushed agencies toward requiring disclosure of significant ex parte contacts during informal rulemaking, precisely so that whatever actually influences the agency’s decision remains part of the same public record everyone had a genuine chance to respond to.
Example. A trade association submits detailed cost data during the comment period; the agency’s final rule preamble must genuinely grapple with that data, not simply ignore it.
The Final Rule & Logical Outgrowth
The final rule must be a logical outgrowth of the original proposal — if interested parties couldn’t reasonably have anticipated the final rule’s content from the proposal and comments, the agency generally must issue new notice and reopen comments.
Chocolate Manufacturers Association v. Block, 755 F.2d 1098 (4th Cir. 1985), is the case most commonly used to teach where that line actually falls. The USDA proposed limiting sugar content in a federal nutrition program’s food packages, but its final rule went further and eliminated flavored milk from the program entirely — flavored milk having relatively high sugar content, but never itself specifically mentioned anywhere in the original proposal. The Fourth Circuit struck the flavored-milk provision down, holding that affected parties (dairy producers, program participants) couldn’t reasonably have anticipated that a proposal about sugar limits would actually eliminate an entire food category, even though the connection between “high sugar content” and “flavored milk” seems logical in hindsight. The case is a useful corrective against reading “logical outgrowth” too loosely — the test asks what interested parties would reasonably anticipate from the proposal’s actual text, not what an agency could later justify as a logical extension of its own general goals.
Example. Tightening a proposed threshold within the range already debated by commenters is likely a logical outgrowth; adding an entirely new category of regulated machinery never mentioned in the proposal likely is not.
Legislative vs. Interpretive Rules
A legislative rule has the force of law and generally requires notice-and-comment. An interpretive rule (explaining existing law) or a policy statement (announcing non-binding future enforcement plans) is generally exempt — though a narrow good cause exception can also excuse notice-and-comment in genuine emergencies.
A once-influential line of D.C. Circuit case law — the so-called Paralyzed Veterans doctrine — had required an agency to use notice-and-comment before significantly changing its own prior, settled interpretive rule, reasoning that abruptly reversing a long-relied-upon interpretation deserved the same public input as adopting the interpretation in the first place. The Supreme Court unanimously rejected that doctrine in Perez v. Mortgage Bankers Association, 575 U.S. 92 (2015), holding that the APA’s text draws a clean, categorical line: interpretive rules never require notice-and-comment, whether the agency is issuing one for the first time or substantially revising an existing one. The Court reasoned that courts may not add procedural requirements the APA’s own text doesn’t impose — the same basic Vermont Yankee principle from earlier in this module, applied here to strike down a judge-made gloss on the interpretive-rule exemption itself. The practical effect is real: agencies can revise their own interpretive guidance relatively quickly and flexibly, without triggering the same public process a genuine legislative rule requires.
Example. A binding new safety standard is a legislative rule requiring notice-and-comment; a guidance document merely explaining how the agency already interprets an existing standard is an interpretive rule that generally doesn’t.
Arbitrary-and-Capricious Review
Under State Farm, an agency must examine the relevant data and articulate a rational connection between the facts found and the choices made — failing to consider an important aspect of the problem can render a rule arbitrary and capricious.
Motor Vehicle Manufacturers Association v. State Farm Mutual Automobile Insurance Co., 463 U.S. 29 (1983), arose when the National Highway Traffic Safety Administration rescinded a rule requiring automatic seatbelts or airbags in new cars, reasoning that the passive-restraint requirement would likely just prompt manufacturers to install easily-detachable automatic seatbelts drivers would simply unbuckle, undermining the rule’s safety purpose anyway. The Supreme Court held the rescission arbitrary and capricious, because the agency never seriously considered the airbag alternative even though its own reasoning applied only to detachable seatbelts, not to airbags — a genuine, obvious alternative sitting directly in the agency’s own record that its explanation simply failed to engage with. State Farm’s real significance is that it confirmed arbitrary-and-capricious review has actual teeth: it is not simply a rubber-stamp check for whether an agency wrote something down, but a genuine requirement that the agency’s stated reasoning actually holds together against its own record, including reasonable alternatives it chose not to pursue.
Example. An agency that silently ignores significant contrary cost data in its own record, with no explanation, risks having its rule vacated under this standard.
U.K. Delegated Legislation
The U.K.’s statutory instruments (SIs) are the functional analog to U.S. legislative rules, made under authority granted by a parent Act. Under the affirmative resolution procedure, an SI needs active parliamentary approval; under the negative resolution procedure, it becomes law automatically unless Parliament actively objects.
The U.K.’s own foundational statute for this system, the Statutory Instruments Act 1946, was passed the same year as the U.S. APA — both countries responding, on their own separate tracks, to the same underlying postwar pressure of rapidly expanding delegated regulatory power needing some uniform procedural framework. One genuinely distinctive U.K. controversy this system has produced is the “Henry VIII clause” — a provision in a parent Act that authorizes a statutory instrument to actually amend or repeal primary legislation itself (the Act of Parliament that created the SI-making power in the first place), named for the Statute of Proclamations 1539, which let King Henry VIII’s proclamations carry the force of an Act of Parliament. Modern Henry VIII clauses remain genuinely contested in U.K. constitutional practice precisely because they let executive-made delegated legislation override the primary legislation Parliament itself enacted — a concentration of lawmaking power in the executive that has no close U.S. analog, since a U.S. legislative rule can never override or amend its own enabling statute the way a Henry VIII clause permits.
Example. A minor technical SI might proceed under the negative procedure with little parliamentary attention, while a more significant SI might be made subject to the affirmative procedure, requiring an actual vote before it takes effect.
Part 2 — See How It Fits Together
Click any box to jump back to that part of the lecture.
The APA §553 Framework
Propose, comment, finalize.
2The Notice of Proposed Rulemaking
Real content, published in the Federal Register.
3The Comment Period
Genuine public input the agency must actually consider.
4The Final Rule & Logical Outgrowth
How much can change before new notice is required.
5Legislative vs. Interpretive Rules
Only binding, force-of-law rules trigger notice-and-comment.
6Arbitrary-and-Capricious Review
State Farm's real, meaningful 'hard look' standard.
7U.K. Delegated Legislation
Statutory instruments, and the affirmative/negative split.
Click any step to jump straight to that section of the lecture.
Part 3 — Drill the Terms
Flip each card, then rate yourself honestly.
Card 1 of 14
Click the card to flip it.
At a Glance
The notice-and-comment sequence in five steps.
Notice of Proposed Rulemaking
Published in the Federal Register, describing the rule's terms or the subjects and issues involved.
The Comment Period
The public — companies, advocacy groups, individuals — submits data, objections, and alternatives, typically over 30 to 60 days.
The Agency Considers & Responds
Significant comments must be genuinely considered, with the agency's reasoning explained in the final rule's preamble.
The Final Rule
Published in the Federal Register — must be a logical outgrowth of the original proposal, or new notice is required.
The Effective Date
Generally at least 30 days after publication, giving regulated parties time to come into compliance.
Part 4 — Apply What You’ve Learned
Now that the material is in place, put it to work.
4.1 — Is This a Legislative Rule Requiring Notice-and-Comment?
Toggle each element and watch the conclusion update.
The Legislative Rule Checker
The scenario. An agency publishes a guidance document explaining how it interprets an existing statutory emissions requirement Congress already enacted, stating that the document merely clarifies the agency's understanding of the existing law and creates no new legal obligations beyond what the statute itself already requires.
Read each element below against the scenario above, then toggle Yes or No for what you think is actually true here.
1. Force of Law
Is the rule intended to have the force of law, creating new binding legal obligations?
2. Intended to Bind Regulated Parties and Courts
Does the agency intend this rule to bind regulated parties and be treated as binding by reviewing courts?
3. No Recognized Exemption Applies
Does the rule fall outside the recognized exemptions (interpretive rule, policy statement, procedural rule, good cause)?
4.2 — Is This Final Rule a Logical Outgrowth?
Toggle each element and watch the conclusion update.
The Logical Outgrowth Checker
The scenario. An agency's proposed rule addresses emissions limits for coal-fired power plants only. Without any prior indication in the proposal or public comments, the agency's final rule instead imposes those same limits on natural-gas power plants as well — a category of facility never mentioned anywhere in the original proposal.
Read each element below against the scenario above, then toggle Yes or No for what you think is actually true here.
1. Same Basic Subject Matter
Does the final rule address the same basic subject matter as the original proposal?
2. Reasonably Anticipated by Interested Parties
Should interested parties reasonably have anticipated the final rule's content from the proposal and the comments already on record?
3. Fair Opportunity to Comment Preserved
Was the public's fair opportunity to comment on the rule's actual final content preserved, rather than defeated by the change?
4.3 — What Would Change?
An arbitrary-and-capricious sandbox — watch how evidence and explanation change the outcome.
What Would Change? — Arbitrary-and-Capricious Review
Move the slider to change how much of the relevant record evidence the agency genuinely considered, and toggle whether it articulated a rational connection between that evidence and its final choice.
Likely arbitrary and capricious — no articulated rational connection.
Under State Farm, an agency must articulate a rational connection between the facts found and the choices made. Without that explanation, a rule is vulnerable to being vacated as arbitrary and capricious, regardless of how much evidence the agency actually gathered.
4.4 — You’re the Analyst: The Emissions Rule
A branching case scenario — pick your path through the analysis.
The Emissions Rule
An environmental agency proposes a binding new emissions standard for industrial boilers, intending it to have the force of law and bind regulated companies going forward.
4.5 — Argue It, Then Argue Against It
You don’t really understand an institutional design choice until you can question it too.
Should Agencies Get Deference on Technical Fact-Finding, Even Post-Loper Bright?
Loper Bright eliminated Chevron deference on legal questions — but arbitrary-and-capricious review still asks how much weight a court should give an agency's own factual and scientific judgments within its record.
Step 1 — pick the strongest argument for genuine deference on agency fact-finding.
4.6 — Case File Review
A plain-English account — which concepts from this module are actually in play?
Case File Review
Which of these concepts from this module are plausibly in play here? Select all that apply, then check your answer.
4.7 — Write It Out
Put the whole module together in one answer, then self-audit against a model answer.
Write It Out
An agency proposes a rule requiring new safety equipment on industrial machinery, takes public comments, and then issues a final rule that (a) covers an entirely new category of machinery never mentioned in the original proposal, and (b) sets a compliance cost estimate that directly contradicts detailed cost data several commenters submitted, with no explanation in the preamble addressing that contradiction. Analyze both potential defects in this rulemaking.

Where It Counts
The Graded Assessment
Everything above was practice. This is the one part of the module that produces a real score — pass it, and you’re a step closer to this course’s Certificate of Completion.
10 questions drawn from a larger pool. You need 75/100 to pass, and you can retake this as many times as you want.
This course teaches general legal and structural principles about administrative agencies using original hypothetical scenarios. It does not provide legal advice about any specific situation and does not create an attorney-client relationship. For advice about your own circumstances, consult a licensed attorney.
Teaching? Share this with your class
Free to use in class. The free parts open for everyone, no account needed.
