A resident describes what they want and submits, with no account. Bloomz starts a business-day due clock. The request lands with your default department, and staff assign it to the department that holds that kind of record. An hourly check flags overdue requests to the department, or to administrators when there is no department list.
Every request gets a private link the requester uses to check status without an account. Staff can reply publicly or keep internal notes, change status, reassign the department and log requests that arrived by phone, email or in person.
With automatic acknowledgement on, the requester is emailed your own message straight away, with the due date and a link to the status page, and the request moves to Acknowledged. Staff are alerted to every new request. Where your city charges for records, staff estimate the cost from staff hours, take a deposit before work starts and collect the balance before release, and each request shows its projected amount, deposit, final amount and dates. A Public Records Officer can run the queue without full admin rights.
Bloomz tracks a due clock you set. It does not give legal advice, and its clock counts business days without a holiday calendar. Your city remains responsible for its deadlines.
No. It counts Monday to Friday. Adjust the due-day count if your rules require.
Not automatically. A request starts at your default department and staff assign it to the right one.
No. They see status, the due date and public replies.
Yes. Upload a .csv or .xlsx of your request log, match the columns, check the preview and import. Duplicates are skipped and no emails or alerts go out for imported requests.
Yes, when automatic acknowledgement is on. They get your message by email with the due date and the status link, whether they used the online form or staff logged the request for them.
A short call focused on your city's size, your priorities and the systems you use today, not a generic pitch.