civic · local-first tool
Prepare a Community Meeting Comment with a Clear Ask
A short point, the evidence behind it, and a question for the decision-maker are easier to deliver than a page of notes.
Organize a meeting date, agenda item, user-selected question, source, brief comment outline, current time limit, and follow-up owner.
What changes the result: your local agenda, rules, evidence, and the point you want decision-makers to hear.
Privacy: Calculations run in this browser tab. This tool has no input-upload, account, or AI endpoint. The site may send a page-view signal to Cloudflare; this tool does not add form entries to that signal. A draft is stored only if you choose “Save draft on this device”; that browser storage is not encrypted. Avoid identifiers or sensitive details, and delete saved drafts when finished.
Your entries
The starting rows below are fictional examples. Edit them, replace them with non-sensitive labels and values, or load the sample again. The result is not advice or a source verification.
Amount fields use the same units you enter; the app does not choose a currency. Dates are the ones you provide. Up to 100 rows per run.
Calculated output
What the calculation does
Count open and received entries separately from verified entries. Missing source labels remain visible. The app cannot decide whether an agency, school, provider, or contract has received enough documentation.
Question to keep open: Should a comment lead with personal experience, public data, or a specific request for action?
Boundary: San Diego's guide is for that city's Council process, not a universal meeting rule. Confirm the relevant body's current agenda, time limit, deadline, and channel; this app does not submit a comment.
Copy includes the headline, aggregate metrics, and boundary—not the row-by-row input. The CSV contains entries you choose to download. Review it before sharing.