NA 2 · Neighbor Advocate~10 min

The Comment That Counts: What Only You Can Put in the Record

A public comment period is not a vote, and identical comments count for no more than one. What moves a formal record is substance: a specific fact, tied to a specific part of the document, with a specific ask. NA2 teaches what the law requires an agency to do with a substantive comment, the five-part shape of a comment that gets answered, the difference between a docket comment and an environmental-review comment, why a comment can matter even if you lose, and why it has to be written in your own words.

The Comment That Counts: What Only You Can Put in the Record

Picture the inbox of the team writing an environmental report on a large project. Two thousand comments arrive in a week. Nineteen hundred share the same three paragraphs, word for word, with different names at the bottom. One comes from a woman who has lived at the end of a dirt road for thirty years. She writes that the road the draft report names as an evacuation route floods most Februaries, that it was impassable for nine days in 2023, and that the report's traffic section does not mention it. She attaches two photographs and a county road-closure notice.

The nineteen hundred tell the team that many people object. Her comment tells them something they did not know, in a form they are required to answer. Which one changes the document?

Not a vote

The most common misunderstanding about public comment is that it is a referendum. It is not. Federal guidance written for exactly this question puts it plainly: "the public comment process is not a vote," and "multiple identical comments are not likely to be more persuasive than if the comment had been sent only once" (regulations.gov). The same guidance names what does move agencies: comments "that simply provide good reasoning and evidence or a perspective that the agency had not previously considered."

That guidance is about federal rulemaking, but state law in California points the same way, and with teeth.

What the agency must do with substance

Under CEQA, the lead agency "shall evaluate comments on environmental issues received from persons who reviewed the draft EIR and shall prepare a written response" (CEQA Guidelines §15088). It must respond to comments "raising significant environmental issues" received during the comment period, and the response must show "good faith, reasoned analysis." "Conclusory statements unsupported by factual information will not suffice."

Read the next sentence of that section carefully, because it is the whole lesson in one line: "The level of detail contained in the response, however, may correspond to the level of detail provided in the comment (i.e., responses to general comments may be general)." A general comment ("this project will destroy our community") lawfully earns a general answer. A specific comment earns a specific one.

The Guidelines also say what a useful comment looks like. Reviewers "should focus on the sufficiency of the document in identifying and analyzing the possible impacts on the environment and ways in which the significant effects of the project might be avoided or mitigated," and comments "are most helpful when they suggest additional specific alternatives or mitigation measures" (§15204). Reviewers "should explain the basis for their comments" and submit "facts, reasonable assumptions based on facts, or expert opinion supported by facts." Elsewhere: "Argument, speculation, unsubstantiated opinion or narrative" do not constitute substantial evidence, while "facts, reasonable assumptions predicated upon facts, and expert opinion supported by facts" do (§15384).

You are not expected to be an expert. You are expected to bring facts. The facts you hold about the place you live are exactly the ones a consultant working from maps and site visits is most likely to miss.

The local-knowledge inventory

Before writing anything, list what you know firsthand that the document might not. The categories that recur in infrastructure and land-use fights:

  • Access and evacuation. Which roads flood, ice, jam, or are the only way out. When, and for how long.
  • Water. Wells, their depth and history; springs; drainage after a storm.
  • Living things. What you have seen, where and when: nests, dens, migrations, a spring used at dusk.
  • Fire. What burned, how it moved, where the crews staged, what the wind does in that canyon.
  • Work. The farm, the ranch, the business, the trail economy, and what each depends on.
  • Culture and history. Places that matter to a community, stated with care and never on another community's behalf.

For each item, write it as precisely as you can and say how you know it. "The creek floods" is a feeling. "Since 2016 I have photographed the [creek] crossing on [road] under water on at least eleven days, most in February; dated photos attached" is a fact the record can use. (The figures are invented; the precision is the point.)

The shape of a comment that gets answered

Most effective written comments, at any agency, share five parts.

  1. Locate. One or two sentences: who you are, where you live or work in relation to the project, and which proceeding or document you are commenting on.
  2. Point. The specific section, page, figure or table you are responding to. "Section 4.14, Transportation, Table 4.14-3" lets the response team find your issue in seconds and makes it hard to answer generically.
  3. Fact. The thing you know, stated precisely, with how you know it. One strong fact beats five weak ones.
  4. Ask. What you want done: study an impact the document missed, analyze an alternative, add a mitigation measure, correct an error. The incremental-ask discipline from F8 applies: the ask should be something the agency can actually do in this document.
  5. Source. Attach or cite what supports the fact: photographs with dates, records, a public document. Use the number the source actually gives.

Then repeat parts two through five for a second point if you have one, and stop. Length is not weight.

Two records, two boxes

NA1 described the two records. They take comments differently.

The docket. At the CPUC, "any member of the public may submit written comment in any Commission proceeding using the 'Public Comment' tab of the online Docket Card," and relevant written comment "will be summarized in the final decision" (Rule 1.18). The statute is precise about the status of those comments: they are included in the record "but the comments shall not be treated as evidence" (Pub. Util. Code §1701.1). The Commission's own guidance sets a limit on each comment of "4,000 word/2-page" and reminds parties that they "must still formally file comments" (CPUC). The docket is where you speak to the decision: need, cost, route, the public interest.

The environmental review. Comments on a draft EIR go where its notice of availability says, by the date it sets. This is where the obligation to respond in writing lives. If your point is about an environmental effect or an alternative, this is its box.

When a point belongs in both, send it to both, adapted to each.

Why it can matter even if you lose

A comment has a second life. In California, a lawsuit challenging a decision under CEQA can raise only grounds that "were presented to the public agency orally or in writing by any person during the public comment period provided by this division or before the close of the public hearing on the project" (Pub. Resources Code §21177). Note "by any person": a point you put in the record can preserve that issue for everyone. Local land-use decisions carry a parallel rule when the notice includes the required warning: a court challenge is limited to issues "raised in the public hearing or in written correspondence delivered to the public agency prior to, or at, the public hearing" (Gov. Code §65009).

This is method, not legal advice, and NA5 covers when to bring in a lawyer. The lesson for now is simple: the record is permanent, and what is not in it may as well not exist.

Write it yourself

A form letter fails for the reason the guidance gives: identical comments count once. A machine-written comment tends to fail for the reason §15088 gives: generic text invites a generic answer. Neither one contains the thing that makes a comment worth answering, which is a fact from your life.

So the Academy's tools will help you plan a comment and will not write it for you. Find your fact here, organize it with the worksheet, and then write the comment in your own words, as plainly as you would explain it to a neighbor across a fence.

Coordinate, don't copy. If your group wants many comments, divide the ground: one person takes the evacuation road, another the well records, another the business, another the nesting site. Twenty comments that each add a different fact are twenty pieces of substance. Twenty copies are one.

Skill, not side

Everything in this module works the same for a comment in support of a project. A neighbor who wants the housing built, or the line routed through an existing corridor, gets answered on the same terms: a specific fact, a specific section, a specific ask.

Bringing the Foundations toolkit here

The public comment (Field 2.4) is the general version of this module. The story map (F5) helps you find the one fact that carries your experience. ALARA (F6) lets you acknowledge the applicant's strongest point before answering it, which reads as credibility to the people writing the response. The incremental ask (F8) keeps your ask inside what the document can do.

What comes next

A written comment can run two pages and be read at a desk. NA3 takes the other public door, the public participation hearing, where you have three minutes, a microphone and a court reporter, and where the person who matters most may be the judge at the front of the room.

Exercise

Make the inventory before you write a word of the comment. List five things you know about the place this project would touch that a consultant who has never lived there would probably not know: a road and when it floods or jams, a well and its depth, a nest or a spring and when you have seen it used, a fire and what it did, a business and what it depends on. For each, write the fact as precisely as you can (where, when, how far, how many) and how you know it (you saw it, you measured it, you keep records). Then pick the one that matters most, find the section of the application or the draft environmental report that should have addressed it, and write the one-sentence ask that goes with it. Do not draft the comment here. That part is yours, in your own words, once the window opens.

Sign in to write and save your response here — the Library stays free either way.

Downloadables

  • The Comment That Counts Worksheet

    A one-page worksheet for building a written comment on a formal proceeding or an environmental review: the local-knowledge inventory, the five-part shape (locate, point, fact, ask, source), which record it belongs in, and a pre-send checklist.

Frequently asked questions

Should I just sign the petition or send the form letter my group is circulating?
Sign the petition if you like; it shows breadth. But federal guidance on public comment says the process is not a vote, and that multiple identical comments are not likely to be more persuasive than if the comment had been sent only once. A short comment in your own words, with one fact only you can supply, does work a form letter cannot.
My comment is not technical. Will an agency take it seriously?
A comment does not need to be technical; it needs to be specific. California's CEQA Guidelines say substantial evidence includes facts, and that argument, speculation and unsubstantiated opinion do not count. A precise firsthand fact (where, when, how far) is the raw material. An adjective is not.
Can I comment if I am not a formal party?
Yes. At the CPUC, any member of the public may submit a written comment on a proceeding through the Public Comment tab on its docket card. Comments on a draft environmental impact report go wherever its notice of availability says to send them, and that notice also sets the deadline.