Agenda night and records deadlines land on the same desk.
In most small cities the clerk is also the records officer, the meeting coordinator and the person residents call first. Packets are assembled in documents and email, requests arrive by mail, phone and web form, and the response clock runs whether or not anyone is watching it.
Records requests arrive by email, at the counter, by phone and through a web form, and the deadline lives in someone's calendar.
The agenda packet is built in a document, emailed to council, posted to the website and then re-typed as a notice for residents.
Minutes go up late because the person writing them is also answering the front counter.
Residents who don't read English never see the meeting notice, and translating it is one more job.
Meetings and requests, handled in one place.
Build an ordered agenda with attachments and publish it. The meeting lands on the calendar, the packet appears in the Documents listing and members get a translated notice. Publishing minutes sends a second one.
Requests come in through a no-login web form or are logged by staff at the counter. Each gets a business-day clock and a private status link for the requester. A request starts at the default department and staff assign it to the one that holds the records.
Announce a special meeting or a closure to the neighborhoods it affects, or to the whole city, in one send.
Collect applications and acknowledgements digitally, in the resident's language, instead of on paper.
"When is the next meeting?" and "How do I request a record?" get answered from your own pages and documents, with a citation.
A meeting week at the clerk's desk.
Items go in order with their attachments. Add the livestream link to the meeting.
One click puts the meeting on the calendar, the packet in Documents and a translated notice in members' hands.
A resident filed it online. The clock started, and staff assign it to the department that holds the records.
Anything past its deadline is flagged to staff, so the clerk hears about it before the requester does.
The agenda is already public and residents can find the stream from the meeting listing.
Minutes complete the meeting and send a second notice.
A deadline that watches itself.
Records requests are tracked the way a 311 ticket is: a response clock counted in business days, threaded responses, and a sweep that flags overdue items. You set the response window to match your state's law, so the clock your office keeps in a calendar is on the request itself.
What clerks ask first.
No. A resident can submit through a public form and check progress with a private status link. Staff can also log requests that arrive at the counter or by phone.
The response window is configurable in business days, so you set it to what your state requires. Bloomz doesn't give legal advice about what that number should be.
Yes. Publishing minutes completes the meeting and sends its own notice, separate from the agenda notice.
Also built for the people you work with.
City hall runs on handoffs. See how Bloomz works for the roles on the other side of yours.
One login. The whole platform.
Every department runs on one Bloomz platform. Explore it before you book a call.
See Bloomz built for your desk.
A short call focused on your department's work, your city's size and the systems you use today.