CitizensCommunitiesAction
A public register for civic problems. Report it, get a reference number on the spot, and follow it through every stage until a department marks it resolved.
A report is a record, not a message into a form. It gets a number, a department, a status, and a history that anyone holding the number can read.
Every status change, assignment and priority change is written to the issue history with the time it happened, so the timeline shows who moved the report and when, not just where it ended up.
A fifth status, Rejected, closes a report that cannot be acted on. Nothing is deleted, and the entry stays in the history with the rest.
You are shown Issue #1024 the moment the report is filed. Anyone with that number can check the progress, with no account and no sign-in.
The check runs on what the form already holds: same category, within about a kilometre, and a trigram match on the title. Existing reports come back before a second one is created.
Category, priority, department and a short summary are stored beside the real fields, never instead of them. With no model key configured the report is filed exactly as you wrote it.
Issues are assigned to a department, and an officer acts within theirs. Public views carry a first name at most, never an email address or an account id.
Every table exports to one versioned file, checksummed, with the option to strip email addresses before it leaves trusted hands. The same file restores the register.
See the live issuesFiling a report, with the duplicate check running before it saves
An officer triaging it: category, priority, department, then a status move
The dashboard the office reads, counted straight off the register
A backup taken and restored inside a single transaction
A citizen reads one row of the register. An officer works the same row. Neither gets a private copy, which is why the history a citizen can read is the history the officer wrote.
What a citizen sees
#1024
AcknowledgedStreet light out on the river path
Riverside path, near the boat club
Roads
Read with the number alone. Tracking a report needs no account and no sign-in.
What an officer sees
#1024
Roads and transportThe model fills a second set of fields beside these, never over them. A report only counts as triaged once an officer has accepted or overridden each one.
Moves offered from here
Only the moves the workflow allows are offered, and closing a report needs a written reason before it will save.
Counted in the register itself, not quoted at you. Every one of them is open to read, with its status and the history behind it.
What the system does with a report, and what it does not do with your name.
Yes. Filing a report needs a signed-in account, so a report can be traced back to a person if a department needs to ask a question. Tracking is the part that needs no account.
You are shown a reference number, like Issue #1024, as soon as the report is filed. Enter it on the tracking page and you get the current status and the history behind it, signed in or not.
Submitted is filed and waiting. Acknowledged means a department has seen it. In progress means someone is working on it. Resolved means the department has closed it as done. Rejected means it cannot be acted on, and the report still stays on the record.
The system looks before you submit, not after. It compares the category, the location within about a kilometre, and the wording of the title, then shows you the existing reports so you can follow one instead of adding a second.
No. It suggests a category, a priority, a department and a short summary, and those suggestions are stored beside your report rather than replacing anything in it. An officer accepts or overrides them. If the model is unavailable the report is filed exactly as you wrote it.
The public view of an issue carries a first name at most. Email addresses, account ids and full names stay on the authority side, visible to the officers and administrators who act on the report.
Not through the product. A report that cannot be acted on is marked Rejected and stays in the register with its history, because a record that can quietly disappear is not a public record.
An administrator can export the whole register to a single versioned, checksummed file and restore from it. Email addresses can be replaced with stable placeholders when the file is going to leave trusted hands.