California State Capitol. (Photo: Katy Grimes for California Globe)
The Anatomy of a Rulemaking File
Requires checking whether the agency met its statutory duties under administrative law
By Chris Micheli, November 17, 2026 2:00 pm
Reviewing a rulemaking file requires checking whether the agency met its statutory duties under administrative law (i.e., met the requirements of the California Administrative Procedure Act – APA). Advocates can spot procedural vulnerabilities by auditing the Initial Statement of Reasons (ISOR), the Final Statement of Reasons (FSOR), and the agency’s responses to public comments for gaps including missing evidence and unaddressed objections.
Initial Statement of Reasons (ISOR) Checklist
The ISOR establishes the baseline justification for a proposed rule. Look for flaws in how the agency defines the problem and supports its solution.
Check that the cited statutes actually grant the agency power to regulate the specific subject matter. Ensure the agency is not exceeding its legislative mandate or inventing new authority.
Verify that the agency identifies a concrete problem and explains why each specific provision of the regulation is reasonably necessary to solve it. Vague assertions or circular reasoning (“this rule is needed to implement the program”) can signal a vulnerability.
Confirm that every factual claim, scientific study, or economic model relied upon is explicitly listed in the ISOR and placed in the public rulemaking file. Hidden or unreferenced data violate public notice requirements.
Check whether the agency evaluated reasonable alternatives that would be less burdensome or more effective, especially for small businesses. Dismissing viable alternatives without explanation is a common procedural defect.
Look for unsupported assumptions in cost estimates, job impacts, or compliance burdens. If the agency claims “no significant statewide adverse economic impact,” check whether the underlying data actually supports that conclusion.
Agency Responses to Public Comments Checklist
Agencies are legally required to meaningfully respond to every relevant objection or recommendation submitted during the public comment period.
Cross-reference your own submitted comments (and those of other interested persons) against the agency’s summary list. Omitted comments or mischaracterized arguments are clear procedural errors.
Flag responses that rely on generic responses like “comment noted” or “the agency disagrees” without explaining why. The agency must state the specific reasons for rejecting an objection or proposed alternative.
Check if commenters submitted contradictory data, studies, or legal arguments that the agency completely ignored. Failing to address significant counter-evidence renders the final decision arbitrary and capricious.
Verify that the agency did not rely on new studies, internal memos, or data to rebut public comments without reopening the record for a 15-day (or equivalent) public review period.
Final Statement of Reasons (FSOR) Checklist
The FSOR updates the ISOR and finalizes the administrative record for judicial or executive review (such as review by California’s Office of Administrative Law).
Compare the final text against the originally proposed text. If the agency made substantial changes that were not reasonably foreseeable from the initial notice, check whether it issued a supplemental notice and comment period.
Check if the agency’s rationale shifted dramatically between the initial proposal and the final rule without supporting evidence in the record. If the agency modified sections of the rule in response to comments, verify that the FSOR includes updated necessity statements explaining why the revised language is required.
Confirm that the FSOR contains all required final findings, such as determinations regarding local mandates, housing costs, or consistency with existing state and federal regulations.
Summary of High-Value Vulnerabilities
| Document / Phase | Primary Red Flag | Legal / Procedural Consequence |
| ISOR | Missing technical studies or reliance on unstated assumptions | Violates notice-and-comment transparency; undermines substantial evidence standard. |
| Public Comments | Boilerplate dismissals or ignored counter-studies | Demonstrates arbitrary and capricious decision-making; violates statutory duty to respond. |
| FSOR | Major text changes without a supplemental comment period | Invalidates the modified provisions due to inadequate public notice. |
| Overall Record | Rule exceeds the scope of the authorizing statute | Renders the regulation void for lack of authority (ultra vires). |
- The Anatomy of a Rulemaking File - November 17, 2026
- Challenging ‘Underground Regulations’ at OAL - November 17, 2026
- How to Draft a Legally Sound Special Statute Clause - November 17, 2026




