Solutions · Counties
Dispersed sites, several departments, and one calendar that covers all of it.
A county's problem is distance and duplication. Facilities sit across a wide geography, several departments book them, and the same room is often managed by two teams who have never seen each other's diary.
Counties, regional authorities and county park systems.
Typical county portfolio
- Parks and open space
- Regional parks, shelters, trails, boat launches, campgrounds
- Buildings
- Community buildings, senior centers, fairgrounds, extension offices
- Administration
- Board rooms, hearing rooms, department meeting space
- Libraries
- County library branches, each with their own rules
- Sites
- Many locations on one diary
- Departments
- Unlimited staff accounts across all of them
- Reporting
- By site, by department, county-wide
- Compliance
- April 26, 2027 date applies to most counties
What changes for a county
Distance stops being an excuse for duplication.
When every site is on one diary, a resident finds the nearest available shelter rather than the one they happen to know about, and the county stops running the same booking process four different ways.
- 01
One intake across every site
A resident searches by location, capacity, amenity or date across the whole county, instead of calling the district office nearest to them.
- 02
Departmental boundaries, without departmental systems
Each department manages its own facilities, rules and rates, with permissions down to facility and function level, on shared infrastructure.
- 03
Reporting that rolls up
Utilization and revenue by site, by department and county-wide, which is what a board asks for and what four systems cannot produce.
- 04
Field teams included
Function sheets, task lists and crew assignments generated from bookings, which matters more when the crew is forty minutes from the office.
The reviews a county has to pass
More departments means more reviewers, not a different product.
Counties tend to have a more formal procurement route and a more structured IT review than a small city, and both are easier when the vendor publishes rather than presents.
- Security review. ISO 27001, SOC 2 Type II, PCI DSS, US or Canadian Azure regions, single sign-on, and a security pack released under NDA on request.
- Accessibility. WCAG 2.1 AA resident portal with a conformance report, ahead of the April 26, 2027 date that applies to entities of 50,000 or more.
- Procurement. We hold no cooperative purchasing contract. Where your policy requires one, tell us during the RFP and we will say honestly whether we can meet your timeline. Procurement routes.
- Finance. Named integrations, and an open REST API plus middleware for the North American stacks that are scoped per deployment.
Questions
Asked on most calls.
If your panel needs an answer that is not here, send the question and we will publish it.
Can each department keep its own rules and rates?
Yes. Rules, rates, approval routing, hours and conditions are set per facility and per space, not per organization, so two departments can run entirely different policies on one platform.
Do we pay per site?
No. Pricing is based on the population you serve, not the number of sites or spaces. A county with 400 bookable spaces across 60 sites pays the same as one with 40 spaces in the same population band.
What about our library branches?
Library rooms are a business area on the same platform, with library card verification and per-branch rules. Library rooms.
See it against your own facilities.
Bring the list of every space you rent out and your adopted fee schedule. Forty-five minutes, no slides.