A typical public comment email to proposed government rule changes is usually short, formal, and specific: it identifies the rule, says who you are, explains what you support or oppose, and gives reasons with facts or examples. Effective comments also point to particular sections of the proposal and, when possible, suggest exact changes.

Typical structure

A common format looks like this:

  1. Subject line with the rule name or docket ID.
  2. Greeting to the agency contact.
  3. Brief introduction of yourself or your organization.
  4. Clear statement of support, concern, or suggested change.
  5. Specific evidence, examples, or data.
  6. A direct request or recommendation.
  7. Polite closing and contact information.

Simple template

Dear [Agency Name],
I am writing to comment on [rule name/docket number]. I am [name/role/organization], and I have experience with [topic].
I support/opose [specific part] because [reason]. In particular, [section or requirement] may [impact].
I recommend [specific change]. Thank you for the opportunity to comment.
Sincerely,
[Name]

What makes it strong

The strongest comments are original, fact-based, and tied to the actual proposal rather than being generic form letters. They are more persuasive when they explain real-world impact, cite specific provisions, and propose a workable alternative.

Quick example

I support the goal of the proposed rule, but I am concerned that Section 3’s timeline is too short for small businesses to comply. A 180-day phase-in would reduce disruption while still meeting the agency’s objective.

TL;DR

A typical public comment email is a polite, focused message that says who you are, what part of the rule you’re commenting on, why it matters, and what change you want.