Springbrook’s October 29, 2026 Cirrus roadmap brings available features and previews into one announcement. For a local-government team planning adoption, the useful unit of review is the individual capability. Keep its stated release stage beside the workflow you want to change.
Springbrook’s roadmap and feature descriptions
Read the labels feature by feature
The company labels AI Invoicing and AI Permitting available today. It describes the Reporting and Insights Module and Conversational ERP as previewed at Activate, and the Citizen Portal as in preview. Those are the announcement’s labels, rather than verification of availability in a particular agency’s account.
Springbrook describes AI as doing an initial pass, with staff reviewing and approving results. Its forward-looking statement also says development plans may change and do not commit to a particular delivery date or feature set.
Use a small readiness record
Create one row per capability. Record the source date, stated stage, intended users, account prerequisites, demonstration evidence and the person who can confirm access. Keep an unresolved field visibly unresolved rather than filling it from another feature’s status.
For example, an agency might want invoice intake assistance and a new way to ask for reports. Those requests can share a project meeting while having different readiness decisions. Ask the provider to show the specific feature in the intended configuration before setting a training date.
Try a fictional planning exercise
Imagine a fictional agency planning an invoice-intake trial next month. Its worksheet records the announcement’s availability label for AI Invoicing, then leaves licensing, account enablement and the trial date pending confirmation. This is an invented planning example; it does not establish a Springbrook customer’s entitlements.
The same fictional team adds a second row for Conversational ERP. That row retains the preview label. A demonstration can help the team understand the proposed workflow, but the team should ask separately what access is offered and which conditions apply before making it a dependency for a production deadline.
For each row, write a proposed acceptance task in ordinary work terms. An invoice trial could ask a reviewer to compare captured details with a disposable sample document. A reporting demonstration could ask for a familiar report and compare the result with an agreed reference. These are suggested evaluation tasks, not features or tests verified in this article.
Keep the date and decision owner
PR Newswire published a corrected version on October 30; its correction note says the headline was revised. That correction date should not replace October 29 as the roadmap’s announcement date.
Company-issued corrected release and correction note
Before changing a rollout plan, have the responsible owner confirm the current stage, applicable access and evidence needed to proceed. Save the dated source alongside that decision. Recheck any preview-dependent milestone when the provider supplies an update. No Cirrus account, invoice, application or report was tested for this guide.
Check the release-stage record
