A tentative booking usually means the request is being held or reviewed and still needs one or more steps before confirmation. A confirmed booking means it has met the rules required for the organization to accept it.
The exact status names and confirmation rules can vary. Some organizations use words such as hold, option, pending, requested, approved, or confirmed instead.
Why Have a Tentative Stage?
Some bookings need a period between the first request and final confirmation.
That may happen because:
- Staff approval is required.
- A deposit or payment is still due.
- The customer must accept terms.
- Several spaces or resources must be checked.
- A quote, contract, or other information is still being reviewed.
Does a Tentative Booking Block Availability?
It can, but it does not have to in every setup.
One organization may hold the resource while a tentative booking is active. Another may keep the request visible without removing the space from sale. A third may hold it only until a deadline.
The status label alone is not enough. The booking rules must also say what that status does to availability.
What Usually Makes a Booking Confirmed?
Confirmation happens when the booking meets the rules chosen by the organization.
Depending on the workflow, that may include:
- Available capacity and resources.
- Required approval.
- Required customer information.
- Accepted terms.
- A deposit or other required payment.
See How Booking Rules Work and How Deposits Work.
What Happens When the Status Changes?
A status change can trigger other actions. Availability may update, confirmations may be sent, tasks may start, or billing may move to the next step.
The exact actions should follow the configured workflow rather than being assumed from the word “confirmed.”
How Does Booking Ninjas Support Confirmation Workflows?
Booking Ninjas' Booking Engine supports configurable booking rules, confirmations, approvals, availability controls, and automated notifications.
Its Reservation Management tools support controlled reservation creation, updates, approvals, changes, and policy enforcement.
The exact status names used in a specific setup should be defined during configuration. For what happens later, see What Happens When a Booking Changes?.
Sources and Further Reading
- Booking Ninjas: Booking Engine — covers configurable booking rules, approvals, confirmation workflows, availability, and notifications.
- Booking Ninjas: Reservation Management — covers reservation policies, controlled updates, approvals, and change tracking.