Use public, authorized source text only. Do not paste private community messages, residents’ identifying information or confidential consultation material into a general chatbot.
A local proposal may be spread across a planning report, an agenda and linked attachments, alongside competing stakeholder summaries. Start with the actual documents: a circulated summary may omit conditions that matter to your decision.
A model can meaningfully help with the reading and organizing part: turning a dense planning document into a plain-language summary, and laying out competing stakeholder claims side by side so you can see where they actually disagree. What it should never do is form your opinion for you, tell you how to vote, or become a tool for manufacturing the appearance of community sentiment that does not exist; civic participation is valuable specifically because it is a real person’s considered judgement, and that value disappears the moment the judgement, or the comment, is not genuinely yours.
Do not use a model to generate deceptive advocacy, impersonate other residents or organizations, mass-produce near-identical public comments to make an issue look more or less supported than it is, or write persuasion content targeted at swaying specific individuals or groups. A model also cannot verify a disputed factual claim about a local issue with certainty; treat any claim it surfaces as a lead to check against a primary source, not a settled fact. Your vote, your public comment, and your position on a community issue need to be genuinely yours, formed after reading the real material, not generated for you.
Step 1: Gather the primary documents, not the summaries about them
Pull the actual proposal text, meeting agenda, staff report, or ballot measure language from the official source, such as a municipal website, the organization’s published minutes or the measure itself, rather than working from a social media post, a neighborhood group’s characterization, or a news article that may itself have compressed or slanted the material.
Primary source: [official URL or document name]
Document date / meeting date: [date]
Retrieved: [today's date]
Step 2: Ask for a plain-language summary, working only from the text
Paste the actual document text and ask for a summary that stays anchored to what it says, not to background knowledge about “how these proposals usually go.”
Here is the text of [proposal / agenda item / measure], copied
directly from [official source]: [paste text]. Summarize in plain
language: what is being proposed, who it would affect, what would
change if it passes, and what the stated timeline or next step is.
Work only from this text; if something is unclear or not addressed
in it, say so rather than filling in a plausible-sounding answer.
Step 3: Lay out stakeholder claims side by side, and flag disputes
Civic issues almost always have competing framings: a developer’s economic-benefit claim, a residents’ group’s traffic-impact concern, a city staff report’s technical assessment. Ask the model to organize these claims rather than adjudicate which one is correct.
Here are statements from different stakeholders on this issue:
[paste, e.g. developer statement, resident petition excerpt, staff
report finding]. Organize these side by side by claim, noting where
they directly contradict each other on a factual point (not a values
disagreement) and where they agree. Do not decide which claim is
correct; flag disputed factual claims as needing verification
against a primary source, and clearly separate factual disagreements
from differences in values or priorities.
Illustrative shape:
Claim: "The development will add 200 parking spaces" (developer) vs.
"The traffic study only counted 140 spaces" (resident petition);
factual dispute, needs verification against the actual traffic
study document, not either party's summary of it.
Values disagreement (not a factual dispute): whether the economic
benefit of the development outweighs the change in neighborhood
character; this is a judgement call, not something to verify.
Step 4: Verify the disputed facts against a primary source
For any claim flagged as a factual dispute, go find the actual underlying document (the traffic study itself, the budget line item, the referenced ordinance) rather than trusting either stakeholder’s characterization of it, and rather than trusting the model’s own recollection of similar cases elsewhere.
Step 5: Draft your questions, and write your own position
Use the organized summary to prepare specific questions for a public meeting or comment period; but write your actual position statement yourself, in your own words, informed by what you have read.
From this summary and claims comparison [paste], draft 3-4 specific,
answerable questions I could raise at a public meeting or in a
written comment about this proposal. Do not draft a position
statement or comment on my behalf; questions only.
If you choose to submit a public comment, write it yourself. A model can help you edit for clarity once you have drafted your own actual view, the same way it might help with any piece of writing; but the view itself, and the choice to speak, need to originate with you.
Why language and document barriers are where AI genuinely helps
Translation, plain-language summaries and read-aloud tools may help someone access a document. They still need checking: translation can change a condition, a summary selects emphasis, and a read-aloud tool may misread a number. Compare the parts that matter with the original, and ask the issuing body when the source is unclear. Access support does not make an interpretation neutral or settle what a resident should think.
Primary-source starting points
For Estonia, use the Riigikogu for bills and proceedings, Riigi Teataja for published law, and the eesti.ee state portal for official services. EU-level participation and primary text are available through the Commission’s Have Your Say, EUR-Lex, and the European Parliament’s Petitions Portal. For local issues, add the municipality’s agenda, minutes, consultation notice, and contact record. Do not let a generated summary substitute for the actual proposal being discussed.
Validation and fallback
Cross-check any factual claim that materially affects your view against at least one source outside the document that first made the claim: a staff report, an independent study, or the raw data the claim is based on. If the primary documents are genuinely unclear or contradictory even after this, that is worth raising directly as a question at the meeting rather than resolving privately with a model’s best guess.
Compare a claim with the actual proposal
Invented source passage: “The pilot would remove ten parking spaces on Saturdays for six months. Funding has not been approved.” Stakeholder claim: “The council has permanently removed all parking.” A useful table marks three mismatches: proposed versus completed, ten versus all, and temporary Saturdays versus permanent. It also preserves the unresolved funding.
A separate statement, “I value vehicle access more than this pilot,” is a preference, not disproved by the passage. Ask where the full proposal defines the review and funding decision. Even an accurate summary selects emphasis, so compare the original before forming your position. Use public, authorized documents; exclude private group chats and residents’ identifying details.



