Checklist · Administrative Law

Filing a Rulemaking Comment and Challenging a Final Rule: A Practical Checklist

5 U.S.C. § 605

Type
Checklist
Jurisdiction
National
Date
2026-03-26
Topic
Administrative Law

This checklist covers participating in a rulemaking and challenging the result. Part 1 covers monitoring so that a proposal is not missed. Parts 2 through 5 analyze a proposed rule, plan the comment, draft it, and file it. Part 6 covers coordination with other commenters and confidential material. Part 7 reads the final rule against the comment. Parts 8 through 11 assess whether a challenge is available, select the forum and deadline, plead the claims, and seek interim relief. Part 12 covers guidance documents. Part 13 covers petitions for rulemaking and agency delay. The final parts cover state and local practice and the mistakes that forfeit a challenge before it begins.

Filing a Rulemaking Comment and Challenging a Final Rule: A Practical Checklist

Administrative Law > Rulemaking and Judicial Review | Published 26 March 2026 - Updated 15 July 2026 | UpLaw - uplaw.us

How to Use This Checklist

If a proposal is open, start at Part 2. If a final rule has issued, start at Part 7. Doctrine is in the comprehensive guide; the orientation piece is the comment nobody read; the templates are in the toolkit.

⚠️ If it is not in a comment, it is usually not in the lawsuit. Every legal theory and every factual objection must be raised during the comment period or it is forfeited.

Part 1 — Monitoring

☐ Track the semiannual regulatory agenda for agencies that regulate you.

☐ Subscribe to Federal Register alerts for the agencies and subject areas that matter.

☐ Watch the docket for any advance notice, which is the earliest and most effective point of engagement.

☐ Identify the rule writer named in each notice and the office responsible.

☐ Watch for statutory deadlines requiring the agency to act; a missed deadline supports the most reliable claim in this field.

☐ Track state registers as well; for most regulated parties the state rule matters more.

Part 2 — Analyzing the Proposal

☐ Read the regulatory text first, at the end of the document. It is the only part that becomes law.

☐ Note the comment deadline and calendar a working deadline a week earlier.

☐ List the agency's specific requests for comment. These are where a comment can change the outcome.

☐ Identify the claimed statutory authority and evaluate it independently — after Loper Bright a court will.

☐ Read the cost and benefit analysis for the assumptions: compliance cost per entity, baseline, discount rate, and what is monetized.

☐ Read the alternatives section. An alternative the agency did not consider is a challengeable omission.

☐ Read the small entity analysis or certification under 5 U.S.C. § 605, reviewable under § 611.

☐ Read the paperwork burden estimate under 44 U.S.C. § 3507.

☐ Note the effective and compliance dates, which are the most negotiable elements.

☐ Review the docket for the studies and data relied upon. If something relied upon is not there, say so in the comment.

☐ Assess the impact on your operations concretely — what changes, for how many units, at what cost, over what period.

Part 3 — Planning the Comment

☐ Decide the objective: defeat the rule, change specific provisions, extend the compliance date, or preserve issues for review. These call for different documents.

☐ Identify every legal theory you may want later: authority, procedure, arbitrary and capricious, analytical failures, constitutional.

☐ Identify the factual submissions that support each.

☐ Draft the alternative regulatory text you want adopted.

☐ Determine what data you can gather in the time available, and start immediately — data collection is the long pole.

☐ Decide whether to seek an extension of the comment period, and do it early with a stated reason.

☐ Coordinate with others who share the interest, avoiding duplicative filings.

☐ Decide whether any submission requires confidential treatment, and follow the agency's procedure with a public redacted version.

Part 4 — Drafting

☐ Open with a one-page summary of the requested changes.

☐ State your interest: who you are, what you do, how the rule affects you. This supports standing later.

☐ Organize section by section, keyed to the proposed regulatory text.

☐ Propose alternative language in redline for every provision you object to.

☐ Submit data, not conclusions, with the methodology, the sample, and its limitations stated candidly.

☐ Answer each of the agency's specific questions, by number.

☐ Analyze at least one significant alternative and show it achieves the statutory objective.

☐ State legal objections plainly — that the agency lacks authority, not merely that the reading is unreasonable.

☐ Address the small entity impact with specifics if the certification appears unsupported.

☐ Request that identified materials be placed in the docket, creating a record of the request.

☐ Keep it readable. Short, precise, and documented beats long and rhetorical.

Part 5 — Filing

☐ File to the correct docket, citing the docket number and the rule identifier.

☐ File before the deadline, and keep the confirmation with the timestamp.

☐ File attachments separately and reference them in the text.

☐ Confirm the comment appears in the public docket within a few days, and follow up if it does not.

☐ Send a courtesy copy to the rule writer named in the notice.

☐ Log what you filed, because it is the map of your later challenge.

Part 6 — Coordination and Confidentiality

☐ One comprehensive submission plus tailored member comments is more effective than duplicates.

☐ Avoid form campaigns. Volume does not persuade; agencies are not counting votes.

☐ Where several parties file, divide the issues so each is developed thoroughly.

☐ Confidential business information goes in under the agency's procedure, with a public redacted version. It remains part of the record and must be considered.

☐ Consider whether any submission creates admissions usable in enforcement or litigation, and draft accordingly.

Part 7 — Reading the Final Rule

☐ Compare the final regulatory text to the proposal. Is it a logical outgrowth, or does it address something no one had notice of?

☐ Read the response to comments against your comment, line by line.

☐ Flag any significant comment not addressed at all.

☐ Flag any comment mischaracterized in the summary.

☐ Flag any response that asserts a conclusion without reasoning.

☐ Flag any alternative dismissed in a sentence.

☐ Check whether new data appeared in the final rule that was never available for comment.

☐ Check the effective and compliance dates and whether they changed.

☐ Check whether the agency changed position from a prior rule without acknowledging or explaining the change.

☐ Check the final small entity analysis and the paperwork clearance.

☐ Diary the petition deadline immediately.

Part 8 — Is a Challenge Available?

☐ Is this final agency action? 5 U.S.C. § 704; Bennett v. Spear.

☐ Is review precluded by statute or committed to agency discretion? 5 U.S.C. § 701(a); Heckler v. Chaney.

☐ Do we have standing? Injury in fact, traceability, redressability. Lujan.

☐ Is the claim ripe? Abbott Laboratories.

☐ Is exhaustion required by statute or by a rule making the action inoperative pending appeal?

☐ Did we comment, and does the comment contain every theory we now want to raise?

☐ What is the realistic remedy — vacatur, remand, or a stay — and is it worth the cost?

Part 9 — Forum and Deadline

☐ Find the review provision in the organic statute first. A petition for review in a court of appeals within a stated period is frequently jurisdictional and displaces everything else.

☐ If no special provision applies, the action proceeds in district court under 5 U.S.C. § 703 with the six-year default of 28 U.S.C. § 2401(a).

☐ Consider Corner Post where the plaintiff was injured only recently by an older rule.

☐ File protectively if the deadline is near and the analysis is incomplete.

☐ Choose the venue deliberately, and see the forum checklist.

☐ Identify co-petitioners and whether an association can sue on members' behalf.

☐ Consider intervention in an existing challenge rather than a separate action.

Part 10 — Pleading the Claims

☐ Statutory authority — the rule exceeds the agency's power, decided independently after Loper Bright; invoke West Virginia v. EPA where the assertion of power is extraordinary.

☐ Procedure — inadequate notice; not a logical outgrowth; undisclosed data; inadequate response to significant comments; invalid good cause; legislative rule issued as interpretive. 5 U.S.C. § 553.

☐ Arbitrary and capricious — failure to consider an important aspect; explanation counter to the evidence; unexplained change of position; failure to consider reliance interests; pretext. State Farm; Department of Commerce; Ohio v. EPA.

☐ Analytical failures — unsupported certification under 5 U.S.C. § 605, reviewable under § 611; uncleared information collection under 44 U.S.C. § 3507.

☐ Constitutional — delegation, appointments, removal, adjudicatory structure; Axon for forum; Jarkesy for jury rights.

☐ Request the certified administrative record early and compare it to the preamble.

☐ Plead the remedy precisely — vacatur, remand, or declaratory relief.

Part 11 — Interim Relief

☐ Assess whether compliance costs will be sunk before a decision.

☐ Seek a stay under 5 U.S.C. § 705 or the applicable appellate rule.

☐ Document irreparable harm concretely — capital commitments, contracts, workforce changes, and expenditures that cannot be recovered.

☐ Ask the agency first for a delay of the effective date; agencies sometimes grant one and the request builds the record.

☐ Address the public interest and the balance of equities with evidence rather than assertion.

☐ Move promptly. Delay in seeking a stay undercuts the irreparable harm showing.

Part 12 — Guidance Documents

☐ Determine what it is — legislative rule, interpretive rule, policy statement, or informal guidance.

☐ Look for indicators of a legislative rule: mandatory language; no case-by-case exception; enforcement staff instructed to apply it; third parties treating compliance as a condition; publication in the Code of Federal Regulations.

☐ Assess finality under Bennett v. Spear: consummation of decisionmaking, plus legal consequences.

☐ Comply in the meantime and document the burden.

☐ Ask the agency in writing whether it considers the document binding, and keep the answer.

☐ Petition for rulemaking under 5 U.S.C. § 553(e) if the guidance is doing the work of a rule; the denial is reviewable.

☐ Note that guidance can change without process under Perez v. Mortgage Bankers, so a compliance program built on it carries that risk.

☐ Check whether an organic statute imposes broader process than the APA, as in Azar v. Allina.

Part 13 — Petitions and Delay

☐ Draft the petition as a proposed rule, with regulatory text, authority, factual basis, and a requested timeline.

☐ File under 5 U.S.C. § 553(e) and expect a response under § 555(e).

☐ Treat the denial as valuable — it is a written statement of the agency's position and is reviewable.

☐ Identify any missed statutory deadline. A deadline suit under 5 U.S.C. § 706(1) is the most reliable claim available.

☐ For unreasonable delay without a deadline, build a record: requests made, time elapsed, interests at stake, and the agency's competing priorities.

☐ Use 5 U.S.C. § 552 to obtain the agency's internal analyses and communications; see the public records checklist.

☐ Request an interpretation, advisory opinion, waiver, or exemption where the agency offers one, and exhaust it before challenging an application.

Part 14 — State and Local

☐ Find the state administrative procedure act and its comment, hearing, and impact analysis requirements.

☐ Check whether a legislative review committee can object to or suspend the rule, and file with it as well.

☐ Determine the state's deference rule, which varies sharply and is the first question in any state matter.

☐ Note the deadline to petition for review, frequently thirty days and unforgiving.

☐ Confirm exhaustion requirements, which are stricter and often jurisdictional.

☐ For local action, participate at the hearing before the board — that hearing is the record, and what is not said there generally cannot be said later. See the zoning guide.

Part 15 — Mistakes That Forfeit a Challenge

☐ Not commenting at all, and losing every argument. ☐ Commenting with opinions instead of data. ☐ Failing to raise a legal theory in the comment and trying to raise it in court. ☐ Failing to propose an alternative, so the agency had nothing to consider. ☐ Missing a jurisdictional petition deadline in the organic statute. ☐ Filing in district court where the statute channels review to a court of appeals. ☐ Waiting to seek a stay until after compliance costs are sunk. ☐ Ignoring the small entity certification and the paperwork clearance. ☐ Assuming guidance is unreviewable and therefore not worth addressing. ☐ Failing to request the certified record and compare it to the preamble. ☐ Assuming a win means the rule disappears rather than a remand. ☐ Overlooking the state rule, which frequently matters more than the federal one.

Part 16 — Decision Trees

Should we comment on this proposal?

  1. Does the rule affect your operations, costs, or obligations in any way? → Yes, comment.
  2. Do you have facts the agency does not have — cost data, feasibility evidence, timelines? → Comment, and lead with them.
  3. Might you ever challenge this rule? → Comment, because unraised objections are forfeited.
  4. Is the only available point "we oppose this"? → A comment is still worth filing for preservation, but invest the effort in finding a fact or an alternative.
  5. Is the deadline too near to gather data? → Request an extension in writing, immediately, with a stated reason, and file what you have on time.

Is this document a rule we have to follow?

  1. Is it published in the Code of Federal Regulations, or does it invoke legislative rulemaking authority? → Legislative rule.
  2. Does it use mandatory language and admit no case-by-case exception? → Functionally legislative, whatever it is called.
  3. Does it merely state the agency's reading of an existing statute or rule? → Interpretive, exempt from notice and comment.
  4. Does it describe how the agency will exercise discretion, leaving room for a different result in a particular case? → Policy statement.
  5. If it is functionally legislative but was issued without notice and comment, it is vulnerable — but comply while preserving the objection.

Can we challenge this rule now?

  1. Is there final agency action under Bennett?
  2. Is review precluded, or committed to agency discretion under 5 U.S.C. § 701(a)?
  3. Do we have standing and is the claim ripe under Abbott Laboratories?
  4. What does the organic statute say about the forum and the deadline? That controls.
  5. Did we comment, and does the comment contain the theory?
  6. What is the realistic remedy, and is it worth the cost of obtaining a remand?

What is our strongest claim?

  1. Procedure is usually strongest: a legislative rule issued as interpretive, an unsupported good cause finding, undisclosed data, a final rule that is not a logical outgrowth, or a significant comment never addressed.
  2. Arbitrary and capricious next: an important aspect not considered, an unexplained change of position, or reliance interests ignored.
  3. Statutory authority where the text genuinely does not support the rule — a stronger argument after Loper Bright than before.
  4. Analytical failures as supporting claims: the small entity certification and the paperwork clearance.
  5. Constitutional claims last, and only where the structure is genuinely at issue.

Should we seek a stay?

  1. Will compliance require expenditures that cannot be recovered if we win? Quantify them.
  2. Will the compliance date arrive before a decision on the merits?
  3. Can we show a likelihood of success on at least one claim?
  4. Have we asked the agency to delay the effective date first, and preserved the refusal?
  5. Are we moving promptly? Delay defeats the irreparable harm showing more often than anything else.

Part 17 — The Comment Docket Log

Maintain one row per rulemaking you are tracking. It is the map of your later challenge and the file an outside counsel will ask for first.

Field Entry
Agency and docket number
Regulation identifier number
Rule writer named in the notice
Date proposed; comment deadline; extension requested / granted
Claimed statutory authority
Provisions we object to, by section
Alternative text proposed
Data submitted, with the underlying files
Agency questions answered, by number
Requests made to place materials in the docket
Date filed; confirmation number; date it appeared publicly
Meetings held with agency staff, and whether summarized in the docket
Date of final rule; effective date; compliance date
Comments not addressed in the response
Comments mischaracterized
New data appearing only in the final rule
Position changes not acknowledged
Petition deadline under the organic statute
Decision on challenge, and rationale

☐ Keep the filed comment and all attachments exactly as submitted.

☐ Keep the docket confirmation with its timestamp.

☐ Save the final rule as published, not a summary of it.

☐ Note the sections of the response to comments that address your submission, by page.

☐ Diary the petition deadline the day the final rule publishes.

⭐ Why the log matters. By the time anyone decides whether to challenge a rule, the comment period has closed and the record is fixed. The organization that can answer "what did we say, when, and what did they do with it" in five minutes is the one that can make the decision on the merits rather than on guesswork.

Part 18 — Timing Reference

Event When to act Source
Regulatory agenda published Engage before a proposal issues Executive practice
Advance notice issued Comment; this is the highest-leverage moment 5 U.S.C. § 553
Proposed rule published Calendar the deadline and a working date a week earlier Federal Register
Comment period closing soon, data incomplete Request an extension immediately, in writing Agency discretion
Comment filed Confirm it appears in the public docket within days Docket
Final rule published Diary the petition deadline that day Organic statute
Effective date Not less than 30 days after publication, with exceptions 5 U.S.C. § 553(d)
Rule submitted to Congress Before taking effect 5 U.S.C. § 801
Petition for review Frequently 60 days and jurisdictional Organic statute
No special review provision Six years from accrual 28 U.S.C. § 2401(a); Corner Post
Compliance date approaching before decision Seek a stay 5 U.S.C. § 705
Statutory deadline for agency action missed File a deadline suit 5 U.S.C. § 706(1)
Petition for rulemaking filed Expect prompt notice of any denial 5 U.S.C. § 555(e)

Related Documents