Back to playbooks

Public Comment + Rulemaking

Use when: agencies ask for comments on proposed rules, permits, plans, or enforcement changes.
Goal: get a clear request into the official record, in a form agencies can use.

Why this matters

Rules and enforcement shape reality more than speeches do.

The comment structure (short)

1. Stake: who you are + how it affects you
2. Position: support/oppose specific provision
3. Evidence: 2–3 bullets (observed impact, data, implementation reality)
4. Fix: change A → B (one ask)
5. Metric: what to track + how often to publish
6. Close: confirm it’s in the record

Tips

• Be concrete: timelines, staffing, reporting
• Avoid speculation
• One credible source beats five angry links

Agency-friendly formatting

• Put a 150-250 word executive summary at the top
• Use numbered asks
• Default to one page unless the record clearly needs an appendix
• Attach evidence only if it adds something staff can actually use

Agencies are more likely to use comments that can be pasted into a staff memo.

Comment scoreboard

• Docket or comment channel confirmed? (Y/N)
• Executive summary included? (Y/N)
• Numbered asks included? (Y/N)
• Metric and reporting cadence requested? (Y/N)
• Confirmation or docket receipt saved? (Y/N)

What success looks like

Your comment is received and referenced. A rule changes, or a reporting requirement gets added.

Definition of done

Leave with:

1. one submitted comment
2. one docket receipt or confirmation
3. one follow-up date
4. one log entry

Back to playbooks