Quick answer
An online booking system is more than a calendar on a website. The difficult part is expressing the rules of your business: who can book, which resources are available, how long an appointment takes, and what happens when plans change.
Practical scope
Write down opening hours, staff availability, buffer time, locations, capacity and the earliest and latest booking times. Decide whether customers pay in full, leave a deposit or pay later. Define cancellation and rescheduling rules, reminders, no-shows and refunds. If staff already use calendars or a CRM, identify how bookings should sync and who resolves conflicts.
For a simple process, an existing booking tool may be enough. Custom development becomes more relevant when pricing, availability or approval rules are unusual. Ask vendors to demonstrate the customer and staff journeys, including a failed payment and a fully booked slot.
What to define before requesting proposals
- Bookable services, staff, rooms and capacity
- Availability, buffers and booking cut-off rules
- Deposits, cancellation, refunds and no-shows
- Reminders, calendar sync and staff administration
Questions to ask service providers
- Can standard booking software cover these rules?
- How are clashes, failed payments and full slots handled?
- What can staff change without developer support?
How to assess the answers
Ask vendors to demonstrate one normal booking and at least two exceptions. The rules and staff workload are more important than the calendar screen alone.
Define the booking state, not only the screen
Distinguish available, temporarily held, confirmed, cancelled and expired bookings where relevant. Decide when a place becomes confirmed and when it becomes available again. For event registration, define participant capacity separately from appointment duration; the same calendar layout may hide different rules.
Ask vendors to demonstrate exceptions
- Two customers attempt to reserve the last place.
- Payment succeeds after a temporary hold has expired.
- Staff cancel a session and must contact affected customers.
- A customer reschedules and the old place becomes available.
Should booking always include online payment?
No. Define whether confirmation requires payment, staff approval or neither. Quote payment collection and refund handling explicitly if they are required.
Booking exception acceptance sheet
Copy these items into your brief, adapt the requirements and assign an owner and status. Examples illustrate planning decisions, not customer case studies. Fill cost fields with HKD quotations you obtain and state the billing period.
| Decision / item | Information to provide | Acceptance / comparison check |
|---|---|---|
| Last available place | Capacity, temporary hold and expiry rules | Two customers cannot confirm the same final place |
| Late payment | Payment result arrives after the hold expires | Define refund, review or rebooking responsibility |
| Cancellation | Customer/staff permissions and notification owner | The place is released and affected people are identified |
Download the editable worksheet (CSV)