
Programs fill in minutes, payments come in as cash, checks and a separate portal, and the facility calendar lives in one person's head.
Rosters get rebuilt from paper forms and email at the start of every season.
Program fees are collected one way and facility rentals another, so reconciling takes a second pass.
Two groups ask for the same pavilion on the same Saturday and nobody sees the overlap until the day.
A rained-out program means calling every registrant by hand.
Publish programs with a price, a capacity and a registration window. When a program fills, the next registrants join a waitlist and move up as spots open. The roster is live, not an export.
Residents request a facility and staff approve or decline. Overlapping approved bookings for the same facility are blocked.
A paid registration creates a charge on the resident's own account in the same app, and the money lands on the same ledger as permits and other fees.
Rain-outs and closures go out on every channel, in each resident's language.
Staff can award civic points for participation. Residents redeem them at local businesses.
Residents sign up in the app. Paid programs charge through the same billing engine as every other fee.
Capacity is enforced when the registration is counted. Everyone after that joins the waitlist.
Staff see the request and any approved booking that overlaps it before they approve.
It is the live list of who is registered. There is nothing to export.
One send tells every affected resident, in their language.
A resident who registers for a paid program is charged through the same billing engine that handles permits and facility fees, on their own account. Recreation revenue reaches the same ledger as everything else, and free programs skip billing entirely.
Residents who register after capacity is reached join a waitlist instead of being turned away, and are promoted as spots open.
Yes, in the app, by card or ACH, with the invoice and receipt kept there. Card and ACH processing fees are passed through.
Not yet. Today a booking is a single request that staff approve or decline.
City hall runs on handoffs. See how Bloomz works for the roles on the other side of yours.
Every department runs on one Bloomz platform. Explore it before you book a call.
A short call focused on your department's work, your city's size and the systems you use today.