---

name: regulatory-comment-drafting

description: Use this skill when the user needs to draft, revise, or strengthen a public policy or regulatory comment letter for a proposed rule, interim final rule, ANPRM, RFI, agency consultation, Federal Register notice, or Regulations.gov docket submission. Trigger on requests to turn policy positions into section-by-section comments, answer agency questions, build a record-grounded submission, propose redlines or requested revisions, revise a trade association / NGO / company draft, or turn technical, operational, scientific, economic, or lived-experience evidence into a comment the agency can actually use.^[13]

---

Regulatory Comment Drafting

This skill helps you draft strong U.S. federal regulatory comments and similar consultation submissions that are specific, evidence-backed, easy for agency staff to process, and clear about what should change.^[1][11][12]

Use this process:

• Identify the commenter, the exact agency action, the requested outcomes, and the evidence the commenter can actually support.^[1][10][9]
• Read the notice like a drafting map: the agency's questions, rationale, legal authority, and proposed text usually determine the best comment structure.^[9][1][8]
• Organize the comment around the notice or the agency's question set, not around abstract talking points.^[7][6][8]
• Make each section do real work: identify the issue, state the position, support it with record material, and propose a usable fix.^[1][5][6]
• Keep the asks visible early, in headings, and again at the end.^[4][5][1]
• Match the voice to the commenter: counsel-grade if needed, plainspoken if the value is operational or lived experience.^[1][2][3]

Communicating with the user

Before drafting, decide what kind of comment this is. Do not force every submission into the same template.^[16][19]

• If the commenter is sophisticated counsel, a trade association, a company, or an expert organization, write an answer-first, record-heavy comment. Use docket identifiers, headings keyed to the proposal, citations next to the propositions they support, and explicit requested changes.^[7][18][6]
• If the commenter is a small business, practitioner, worker, patient, or individual with lived experience, keep the structure simpler, but still include four basics: who they are, what part of the proposal affects them, what they want changed, and why.^[19][2]
• If the notice asks commenters to answer numbered questions or organize by topic, mirror that structure unless there is a strong reason not to.^[8][1]
• If the user has deep evidence but a short filing channel, put a self-sufficient summary in the webform text and use attachments for the detail.^[16][8][20]
• If the user only has one narrow correction, do not inflate it into a faux merits brief.^[18][19]

Ask early:

• What is the exact docket ID, RIN, or Federal Register citation?^[10][1]
• What agency action is open: proposed rule, ANPRM, RFI, guidance, draft report, permit, waiver, or something else?^[10][16][13]
• Who is commenting, and why does that perspective matter?^[1][11]
• What are the top one to five requested changes?^[10][4][5]
• Which parts of the notice or question set matter most?^[1][17]
• What evidence is available: studies, internal data, operational facts, expert judgment, examples, or lived experience?^[10][16]
• Which claims are solid, and which are still just concerns?^[15][1]
• Is the goal to win textual changes, shape implementation, answer the agency's questions, preserve issues for later challenge, or simply add credible record evidence?^[9][1][14]

Creating a comment

Capture intent

Fix the objective in one sentence before you draft. Example: “Obtain three changes to proposed § 102.4, supported by operational data and a fallback compliance alternative.” Let that sentence control the whole comment.^[1][10][4]

Then decide the submission type:

• Section-by-section comment for a rule with discrete provisions or agency questions.^[1][7][6]
• Requested revision comment when the user knows the needed outcome but does not want to draft full rule text.^[5]
• Redline comment when the dispute is narrow enough for workable replacement text.^[6]
• Focused correction comment for a technical, scientific, or factual fix.^[18]
• Narrative impact comment for a lived-experience submission that still names a concrete requested action.^[2][23]

Gotcha: do not confuse forceful with sprawling. A comment can be useful without addressing every issue in the notice. The right scope is the scope the commenter can support.^[19][2][22]

Interview and research

Read the notice and docket before you outline

Read the actual notice before drafting. At minimum, extract the rule title, docket ID, RIN, deadline, submission method, agency problem statement, legal authority, specific questions, and the exact sections, pages, tables, or proposed text the commenter wants to address.^[9][1][21]

• If the agency asks numbered questions, answer those question numbers directly when they match the user's point.^[1][21]
• If the proposal contains amendatory text, cite the proposed section number and page.^[12][21]
• If the dispute is with an assumption in the preamble or impact analysis, quote or paraphrase that assumption accurately and respond to it.^[9]
• If relevant docket materials already sharpen the issue, use them.^[22][9]

Gotcha: do not rely on external links as the place where the real argument lives. Keep the substance in the primary submission or the attachment itself.^[8]

Build the comment strategy

Map the notice into a working outline before writing prose. A good internal table has five columns: notice section or question, agency rationale or assumption, commenter position, support available, and requested fix. If a row does not yet have both support and a fix, it is not ready to become a major section.^[1][9][10]

Choose the argument mix deliberately. Use legal arguments for authority or procedure problems, technical arguments for expert-subject disputes, economic or operational arguments for burden and implementation problems, and policy-design arguments when the agency has lawful discretion among several workable options.^{[9][14][7][18]}

Do not spend pages attacking a statutory mandate the agency cannot change. Move the argument to interpretation, implementation, assumptions, exemptions, safe harbors, compliance dates, or other areas of discretion.^[21][9]

Write the comment

Comment anatomy

Use the lightest structure that still makes the submission easy to process. For most serious comments, use: caption or opening line with agency, rule title, and docket; opening paragraph identifying the commenter and interest; short summary of the main requested changes; issue-by-issue sections keyed to the notice; and a short conclusion restating the asks.^[1][7][6]

For short webform comments, compress that structure rather than deleting it.^[20][19]

Opening and standing

Use the opening to establish why this commenter is worth listening to. The best standing paragraphs identify who is commenting, show the experience or expertise that gives the submission value, and connect that experience to the agency's implementation problem.^[6][5][1]

Weak opening: long organizational biography, slogans about caring deeply, or ideological attacks before naming the actual issue.^[6][4]

[Commenter] appreciates the opportunity to comment on [rule title, docket, and citation]. [Commenter] represents / operates / studies / experiences [relevant facts]. Because [specific operational fact, expertise, or lived experience], [commenter] is well positioned to comment on how the proposal will work in practice and what changes would better advance the agency's stated objectives.

Gotcha: standing is not throat-clearing. Move to the asks quickly.^[1][4][6]

Summarize the requested changes early

Surface the asks before the deep analysis. Use an executive summary, short bullets, or answer-first headings.^[24][4][5]

A good summary identifies the parts of the proposal being addressed, states the requested changes in concrete terms, and signals any fallback alternative if the agency rejects the primary ask.^[1][11][5]

Executive Summary
1. The agency should retain the current definition of [term] rather than adopt proposed § [x].
2. If the agency finalizes proposed § [y], it should add a safe harbor for [defined category].
3. The compliance date for [requirement] should be delayed by 12 months to reflect implementation realities documented below.

Gotcha: do not make the reader wait to discover what the commenter wants.^[4][5][1]

Write section-by-section comments

Use headings that help the agency route the point internally. The strongest headings usually track the notice and state the answer.^[1][4][6]

II. Proposed § 102.4 Should Exempt De Minimis Transactions
Question 12: The Proposed Reporting Threshold Is Too Low To Produce Reliable Data
Requested Revision: Clarify That Contract Pharmacists Remain Eligible
Geographic Distribution in the Western Gulf of Mexico

Inside each section, identify the exact issue, state the commenter's position in one sentence, support it with evidence or concrete experience, explain why that support matters for the agency's reasoning, and state the requested revision, redline, or implementation alternative.^[6][5][11]

Proposed § [section] assumes [agency assumption]. That assumption does not fit [commenter data / cited study / operational reality]. [Evidence]. Because the proposal would [practical or legal consequence], the agency should [requested change]. If the agency does not adopt that change, it should at minimum [fallback].

Use evidence and citations the way agencies can use them

Every serious assertion needs a support type. Treat it as a sourced fact, a commenter fact, an expert judgment, or a concern that still needs support.^[15][1]

• If you cite the notice, identify the page, section, question, or proposed regulatory text.^[12][21]
• If you use internal or member data, say whose data it is and how representative it is.^[15][8]
• If you estimate burden or cost, show the assumptions.^[8]
• If you have only anecdotal evidence, call it anecdotal and avoid claiming universal prevalence.^[11][1]
• If the user cannot support a factual claim, rewrite it as a concern, a hypothesis, or a request for analysis.^[11][1]

Gotcha: unsupported certainty hurts more than modestly framed truth.^[11][8]

Choose between redlines, requested revisions, and alternatives

Use a redline when the problem is narrow and textual, the commenter can draft workable replacement language, and the agency would benefit from implementation-ready wording.^[6]

Use a requested revision when the outcome is clear but exact regulatory text is premature, or when the comment is responding to a long proposing release rather than compact amendatory text.^[5]

Use an implementation alternative when the commenter cannot responsibly draft replacement text or when the strongest point is about timing, sequencing, exemptions, thresholds, safe harbors, or phased compliance.^[1][11][6]

Requested Revision: Revise proposed § [x] to exclude [defined category] from [requirement]. The current proposal assumes [assumption], but [support] shows [contrary or missing fact]. If the agency declines this revision, it should at minimum adopt [fallback].

Redline to proposed § [x]:
"[insert workable replacement text]"

Gotcha: a redline without explanation is just markup. Pair text with rationale.^[6]

Write in a way that preserves credibility

Write for an agency reader who must evaluate substance, not volume. Use specifics over slogans, criticize the proposal rather than speculating about motives, distinguish what the agency can change from what only Congress can change, avoid sarcasm and inflated estimates, and say what you support as well as what you oppose when that improves credibility.^[11][25][24]

For lived-experience comments, use the story to show a real-world consequence, then translate it into a concrete ask.^[2][23]

Final review

• Does the opening identify the commenter and why their perspective matters?^[1][11]
• Are the top requested changes visible in the first page or first screen?^[24][4]
• Does each section identify the exact issue being addressed?^[1][6]
• Does each serious claim have support or careful framing?^[11][1]
• Do the headings help an agency team route the issue?^[4][6]
• Did you answer the agency's questions where relevant?^[1][21]
• Did you offer a usable fix, fallback, or implementation alternative?^[1][11][5]
• Did you remove rhetoric that adds heat but no record value?^[11][25][3]
• If using an attachment, does the webform text still summarize the asks?^[20][16]
• Does the conclusion restate the requested actions briefly?^[1][4]

Writing patterns

Example 1

Input:

The user represents a trade association of regional manufacturers commenting on an EPA proposed rule. They want three changes: keep the current emissions-testing method, exempt pilot facilities below a defined annual throughput, and delay the compliance date by one year. They have member operational data, a consultant memo, and page citations to the proposal. They want a formal section-by-section comment and one modeled requested revision.

Output:

[Opening]
The Regional Manufacturers Association appreciates the opportunity to comment on EPA's proposed rule, [title], [docket/citation]. RMA's members operate 74 facilities in 19 states, including pilot-scale and specialty production sites that would be directly affected by the proposed testing and compliance provisions. Because our members have multi-year experience implementing the current testing method across facilities with different production volumes, RMA is well positioned to comment on how the proposal will function in practice.
[Executive Summary]
RMA respectfully requests three changes. First, EPA should retain the current testing method rather than finalize proposed § 60.18(c). Second, EPA should exempt pilot facilities with annual throughput below [threshold] or adopt an equivalent safe harbor. Third, EPA should delay the compliance date by 12 months to account for vendor lead times and state permitting dependencies.
[I. EPA Should Retain the Current Testing Method in Proposed § 60.18(c)]
At 89 Fed. Reg. [page], EPA proposes to replace the current testing method with a method designed for continuous high-volume operations. That assumption does not fit pilot and specialty facilities. Based on data from 23 member facilities, the proposed method would require repeated shutdowns and retesting without improving measurement reliability. The consultant memorandum attached as Exhibit A explains why intermittent operations produce distorted readings under the proposed method. EPA should retain the current method for these facilities, or at minimum allow either method where intermittent operations make the proposed protocol unreliable.
[Requested Revision]
Requested Revision: Revise proposed § 60.18(c) to provide that facilities with annual throughput below [threshold] may continue using the current testing method or an EPA-approved equivalent protocol.
[Conclusion]
EPA should adopt the three changes described above. If EPA does not exempt pilot facilities entirely, it should at minimum adopt the requested safe harbor and extended compliance date.

This example uses the strongest organizational pattern from the record: standing grounded in operational scope, an early summary of requested changes, section headings keyed to the proposal, and a labeled requested revision the agency can route.^[6][5][4]

Example 2

Input:

The user is an advocacy organization commenting on a draft NOAA assessment. They are not trying to rewrite the whole document. They want to correct two statements about habitat range and ask NOAA to update one table using a recent study. They have publication citations and page references.

Output:

Thank you for the opportunity to comment on the draft assessment. Coastal Habitat Watch and its members care about the accuracy of this assessment because it is used in federal management decisions affecting habitat protection and vessel-routing measures.
I. Habitat range in the western corridor
The draft states at page 14 that recent confirmed observations are limited to the central corridor. [Study citation] documents confirmed observations in the western corridor during the 2023 and 2024 survey seasons. Revise page 14 to reflect that the current record includes confirmed western-corridor observations and update Figure 3 accordingly.
II. Table 5 should incorporate the 2024 abundance estimate
Table 5 appears to rely on a pre-2024 estimate. NOAA should update Table 5 to incorporate [study], which reports a revised abundance estimate using the most recent survey data. If NOAA concludes that the new estimate cannot be fully incorporated in this cycle, the final assessment should at minimum acknowledge the study and explain why it was not used.

This example follows the narrow-correction pattern from expert NGO comments: one short interest statement, issue headings keyed to the draft itself, precise corrections with citations, and a limited requested edit rather than a faux merits brief.^[18][20]

Gotchas

• Do not write a generic civics essay about why public participation matters.^[13][1]
• Do not treat the comment process like a vote count.^[1][9]
• Do not lead with anger when the user has facts, experience, or technical corrections the agency could actually use.^[11][25]
• Do not copy the notice's background section into the letter unless it advances an argument.^[1][4]
• Do not answer every agency question just because it exists. Answer the ones that matter to the user's objective.^[21][19][2]
• Do not present unsupported numbers as facts.^[11][1]
• Do not use legal jargon to fake sophistication when plain language would carry the point better.^[2][3][1]
• Do not hide the primary ask inside an attachment.^[20][8]
• Do not forget fallback options.^[11][1][5]

Reference files

• Go deeper only when the user's objective requires it.^[13]
• If the user wants a litigation-aware record, sharpen legal authority, notice citations, and preservation of alternatives.^[9][1]
• If the user has technical evidence, spend more time on the support chain and on reproducing burden or cost calculations.^[8][18]
• If the user is filing a short lived-experience comment, strip the format down but keep the concrete ask.^[2][23]
• If the agency has special submission instructions, follow those over any generic template.^[8][26]
• If you need more material than fits comfortably in the main draft, prefer appendices, exhibits, or attachments over bloating the core comment.^[13][20][16]