Booking software is a solved problem right up to the point where the booking has rules — multiple sites with different availability, capacity that is not simply a headcount, attendance that has to be evidenced, and an inspector who wants a report the off-the-shelf product does not produce.
Create a regulated booking and reporting platform.
Generic booking tools optimise for the simple case: one location, uniform slots, a confirmation e-mail, done. Regulated and multi-site services break every one of those assumptions, so the tool gets used for the easy half and the difficult half moves into a spreadsheet — which is where the two versions of the truth come from.
Attendance is where it usually falls apart completely, because most booking products treat it as an afterthought. For anyone funded or inspected on the basis of attendance, it is not an afterthought; it is the reason the system exists. A booking that nobody attended and a booking that was attended look identical in most tools.
The third gap is reporting. The data is there, but locked in a product whose export is a flat list, so producing what an inspector or a commissioner actually wants means someone with a pivot table and an afternoon.
Unlimited calendars, each with its own bookings, event types, permissions and availability. Availability is expressed the way real operations work: a recurring weekly schedule with overrides for bank holidays and one-off closures, and a choice between bookable-only-during-specified-periods or always-bookable-except.
Booking length is either fixed slots or a range the user enters, which is what makes the same system handle a thirty-minute appointment and a fortnight of annual leave. Event types each carry their own length, their own data-collection fields and their own colour on the itinerary, and multiple locations mean users browse slots per site.
Attendance is recorded against the booking with your own attendance options rather than a fixed attended/did-not-attend. Confirmations go out automatically using your own template or an auto-generated one, by e-mail or SMS. And because it is all ordinary datastore data, the report builder produces the evidence pack rather than someone assembling it.
One calendar per service, team or resource, each with its own permissions. Locations are added so users browse and book per site, which is the assumption most generic tools get wrong first.
Recurring weekly availability with overrides for closures, plus a choice of availability mode depending on whether your default is open or closed. Advance-booking notice controls how far ahead users can see and book.
Event types with their own lengths, colours and custom fields, so booking an assessment collects different information from booking a room. Fixed slots or user-entered ranges, depending on the event type.
Automated confirmations by e-mail or SMS from your own templates, reminders on a schedule, and attendance recorded against the booking using your own options — because "attended", "attended late" and "cancelled within 24 hours" are different facts with different consequences.
Attendance, capacity and no-show reporting from the report builder, scheduled to whoever needs them. For inspected services this is the deliverable the whole system exists to produce.
Nothing here is written specially for this use case — it is the same platform every ActiveManage application is built from. The full feature list is on the platform page.
| Feature | What it does | Why it matters here |
|---|---|---|
| Booking calendars | Unlimited calendars, each with its own bookings, events and permissions. | Services rarely share one calendar in practice, and forcing them to is where generic tools start being worked around. |
| Recurring availability & overrides | A repeating weekly schedule, with overrides to remove specific dates such as bank holidays. | Availability that is maintained by a rule rather than by someone remembering to block out December. |
| Variable booking lengths | Fixed time slots, or a user-entered date and time range. | The same platform handles a twenty-minute appointment and a two-week leave request without a second system. |
| Attendance recording | Attendance tracked against bookings using your own custom attendance options. | For funded or inspected services this is the entire point, and it is exactly what generic booking tools treat as optional. |
| Automated confirmations & SMS | Confirmation e-mails from your own template or auto-generated, plus SMS. | SMS reminders are the single most effective intervention against no-shows, and no-shows are usually the largest quantifiable cost here. |
| Phone / manual bookings | Administrators book on behalf of users who are not online. | Any service with a genuinely public user base has people who will never self-serve, and a system that cannot represent them produces a shadow spreadsheet. |
One calendar, one site, real bookings. Availability rules are much easier to get right against a live week than in a specification.
The remaining sites and event types, attendance recording, reminders, and the reporting the funder or inspector needs.
Adding a calendar, a site, an event type or a report is configuration, which matters here because services reorganise more often than software normally allows for.
Yes. Availability is per calendar with its own recurring schedule and overrides, and locations are a first-class concept, so users browse and book slots per site rather than against one shared assumption.
Yes, and with your own attendance options rather than a fixed set — "attended", "attended late", "did not attend", "cancelled within notice" and so on are different facts and usually have different consequences.
Yes. Administrators can make manual bookings for users who are not online, which is what keeps phone bookings inside the system instead of in a parallel spreadsheet.
Yes, by e-mail using your own template or an auto-generated one containing the booking details, and by SMS. Reminders run as scheduled tasks.
Bookings and attendance are ordinary datastore records, so the report builder can join and filter them like anything else, and reports can be scheduled. That is the difference from a booking product whose export is a flat list.
Tell us what you are trying to fix and we will tell you whether this is the right shape for it — including when it is not.