Find your fit
Who it is for
It can serve an organization whose people need to book finite resources: a meeting room, tennis court, rental car, piece of equipment or person. The workflow is especially relevant when many users share a resource and need a common view of open time.
Administrators can set up schedules and reservation controls, while bookers use the availability view and reservation form. A small pilot with one real resource and a few users will show whether the chosen layout and rules match the organization’s booking pattern.
The work it supports
Core capabilities
Start by creating each resource and assigning it to a schedule. The schedule controls when that resource is available, so a room with business hours can be configured differently from a court or item that is available on weekends.
Bookers can browse a schedule grid, search for open time, look at a calendar or use a visual map. After choosing a slot, the reservation page captures time, invitees and other details; Quick Add can keep a simple booking inside the schedule view.
Configure limits where an open slot still needs control. The vendor lists quotas, reservation approvals, no-show release and automatic setup or cleanup buffers. Test those rules with a realistic reservation so they do not block legitimate use.
Group access controls and tiered roles can limit who administers and books resources. The feature page also describes registered-user and guest access, so decide whether a public or internal booking path is appropriate before publishing a schedule.
Booked lists email and SMS reminders and a wait list for unavailable resources. Custom fields can collect information relevant to a reservation, while check-in/check-out records whether the reserved item was actually used.
For connected workflows, the vendor lists Outlook and Google Calendar integration, iCal, Zoom meeting creation, SSO and an API. Payment and credit features are also listed, including Stripe and PayPal. Confirm the exact configuration and any gateway terms if those are central to the use case.
The reporting system can deliver scheduled reports by email. A team can use those reports to inspect reservations and usage, but should confirm the exact fields and access roles in a trial.
Understand the offer
Pricing and getting started
The current pricing page presents Booked Cloud as a fully managed subscription with unlimited usage and support. It shows USD $15 per month under an annual $180 subscription, or $20 with monthly billing. The homepage emphasizes hosted service.
The same current pricing page also lists Booked On-Prem for the buyer’s infrastructure. The licensing page describes Community, Professional and Enterprise licenses with all features included but differing support and installation help. Confirm the chosen deployment, number of instances and ongoing responsibilities before purchasing.
There is a material price-term discrepancy for the on-premises Community license: pricing calls it annual, while the licensing page calls it one-time. The vendor should confirm the charge, renewal, update and support terms in writing. The licensing page also advertises a no-cost, unsupported option for qualifying tax-exempt nonprofits.
Look a little closer
Before you choose
Map the resources, opening hours, booking roles and exception rules before configuration. Try one busy resource with a guest or group role, an approval rule and a setup buffer to catch conflicts early.
If the buyer needs payments, calendar connections or SSO, run a small end-to-end test with the selected gateway and identity system. The feature list establishes availability, but does not prove compatibility with a particular account or policy.
Choose Cloud or On-Prem only after confirming the current offer and operating scope. The home, pricing and licensing pages use different deployment and Community payment wording, so a written quote is more reliable than any one page alone.
6 distinct sources behind this profile. Research observed Oct 19, 2026. Features and offers can change.
View sources and research →
