How to Write a Public Comment in Your Own Words With AI Assistance

A public comment begins with the resident's own concern

A planning hearing can involve technical reports, drawings, staff recommendations and competing descriptions of the same proposal. Residents may have a clear concern but struggle to express it in a short, organized statement. An AI writing assistant can help arrange that information, but the starting point should be the resident's own observation or question. This might involve a driveway location, a pedestrian crossing, a building's relationship to nearby homes or the timing of construction.

Before opening a chatbot, write three rough sentences: what proposal is under consideration, what aspect concerns you and what information or action you want the public body to consider. These sentences do not need polished wording. They provide a personal starting point and help prevent an automated writing tool from introducing concerns that the resident does not actually hold.

• Identify the proposal or agenda item.
• Describe the specific concern.
• Explain who or what may be affected.
• State the question or request.

Collect the source material before drafting

Useful source material includes the official meeting agenda, hearing notice, planning staff report, site plan, relevant maps and any public documents that describe the issue. A resident concerned about pedestrian access, for example, may need a site plan showing driveway locations and a street drawing showing the existing sidewalk. A comment about building height may need the report's measurement table and the corresponding elevation.

Keep a short source list with the document title, date, page and relevant passage. If two documents describe different versions of a proposal, record the distinction. An AI assistant should not be asked to settle an unexplained conflict by selecting whichever passage sounds more convincing. The appropriate planning department can clarify which version belongs to the application currently before the public body.

• Official agenda and hearing notice.
• Current staff report.
• Relevant maps and site drawings.
• Specific tables or conditions.
• Supporting public records.

Use AI for an outline, not a substitute voice

Give the assistant a limited assignment. Ask it to organize your notes under four headings: project context, personal observation, supporting information and requested clarification or action. Instruct it to use only the supplied facts, identify statements that need sources and avoid inventing personal experiences. The result should be a working outline that the resident can accept, reject or rearrange.

For example, someone concerned about a proposed driveway near a school crossing might have notes about morning vehicle movements, the crossing's location and an unanswered question about sight lines. The assistant can group those points into a logical sequence. It should not invent a near-miss, claim that a crash occurred or add a statistic about school traffic without a source. A plausible sentence is still an unsupported sentence if the record does not establish it.

• Organize the resident's existing notes.
• Separate personal observations from document facts.
• Identify missing information.
• Suggest a clearer order for the points.
• Retain the resident's original request.

Fact-check every number and project description

Planning comments often refer to measurements, dates, property boundaries, traffic figures and proposed conditions. These details are easy to misstate when a chatbot compresses a report. Ask it to identify the exact source passage for every numerical claim and provide the original unit and page reference. Then compare the proposed wording with the public document.

Consider a hypothetical staff report describing a 24-foot-wide driveway and a proposed 30-foot-wide driveway. A comment might say the proposal increases the width by 6 feet. That arithmetic is straightforward, but the comment should also identify which driveway or entrance the measurements describe. If the source uses a different reference point or includes an adjacent apron, the comparison needs clarification. Preserve the distinction between a fact stated in the report and an inference drawn from it.

• Check measurements against the original table or drawing.
• Retain units and decimal places.
• Confirm the application and document dates.
• Distinguish proposed conditions from existing conditions.
• Remove claims without an identifiable source.

A useful comment connects evidence to a specific request

A clear comment usually contains a brief introduction, one or two focused concerns, supporting details and a specific request. The request might be for clarification of a measurement, additional information about a pedestrian route or an explanation of how a condition will be implemented. It should be possible for the person reading the comment to identify the issue without reconstructing an entire neighborhood debate.

A resident might write that the proposed driveway is close to an existing crossing and ask whether the site plan accounts for pedestrian visibility at that location. The comment can cite the drawing and explain the resident's observation of the street. It does not need to claim that a design violates a rule or predict an accident. Technical conclusions belong with the responsible professionals and public authorities.

• Opening: identify the agenda item.
• Concern: state one specific issue.
• Evidence: cite the relevant public record or observation.
• Request: ask for an explanation or consideration.
• Closing: identify any remaining question.

Edit the final wording until it sounds like you

Generated text can sound unusually formal, repetitive or certain. Replace phrases that do not match the resident's normal vocabulary. Remove adjectives that intensify a concern without adding information, and delete claims that the writer cannot explain. If the assistant turns a question into a declaration, restore the question. If it adds a personal experience that was never supplied, remove it completely.

A useful final review is to read the comment aloud and ask whether every sentence can be explained without the chatbot. A resident should be able to describe what a cited document says, why a particular location matters and what response is being requested. The comment should not imply that an AI assistant is the speaker or that an automated system represents a neighborhood.

Submission instructions determine how the comment reaches the hearing

Public participation procedures vary by city, public body and meeting type. An official hearing notice may specify a written submission deadline, an email address, a portal, an in-person speaking arrangement or a limit on speaking time. Some bodies accept written comments before a meeting and provide a separate opportunity for oral comments. A chatbot cannot establish the current instructions simply by recognizing the name of the city or hearing body.

Read the official notice and agenda, then prepare the comment in the requested format. Keep a copy of the submitted wording and any confirmation provided by the submission system. If a comment raises a technical question that cannot be answered from the public record, send that question to the planning department using its published contact method. The next step is to identify the hearing date, confirm the written comment deadline and submit the resident's own final statement through the official channel.

Questions readers ask