1. Venue Booking System
  2. Features
  3. Bookings and holds
Feature · Bookings and holds

Bookings and holds

Requests, held intervals, confirmation and completion.

OverviewBooking requests
Venue Booking System · Bookings and holds

Booking requests

Held waits for the booking coordinator

New
Record numberSubjectCustomer nameStarts atEnds atQuoted amount USD
BKN-93085Requested bkn-960Customer 54624 Oct27 Oct510
BKN-88078Requested bkn-255Customer 90308 Oct15 Oct40
BKN-95201Requested bkn-716Customer 10123 Oct29 Oct420
BKN-80488Requested bkn-786Customer 11910 Oct12 Oct830
BKN-25622Requested bkn-232Customer 64318 Oct26 Oct540
6 of 6 records
Requested bkn-960Bookings · BKN-93085
Customer nameCustomer 546
Starts at24 Oct
Ends at27 Oct
Quoted amount USD510
Example screen with sample data

What you can do

Never promise the same hall twice

A booking records who it is for, what the event is, when it starts and ends, and the quoted amount. It starts as a request. Holding the booking checks the resources it needs: the capacity available, the setup and cleanup time around the event, and whether the resource can be used for this kind of booking. If another booking already claims the same space for an overlapping time, the hold is refused. If the checks pass, the reservation lines are written together and the booking becomes held.

From held, the booking is confirmed once the deposit evidence is in place, moves to in progress when the event starts and to completed with the actual completion time. It can also end as cancelled or as a no-show. The revision number rises with every change, so an action taken on an out-of-date view of the booking is refused.

How the work is organized

The booking coordinator owns each booking from request to completion; the venue manager follows the calendar.

  • Hold before you sell. A booking is held, with its resources reserved, before the package is finalised or the deposit is taken.
  • Buffers count. Setup and cleanup minutes are part of the reservation, so back-to-back events still leave time to turn the room.
  • One effect per action. Each hold, confirmation and cancellation carries an operation key, so a double click never books twice.

What to agree during setup

Agree your resources, their capacities and default setup and cleanup times. Agree how long a booking may stay held without confirmation, what deposit is needed to confirm and who may confirm. Prepare examples of two enquiries for the same hall and time, a back-to-back booking, a confirmation without a deposit and a late cancellation.

Check the handoff on an actual case

Two couples ask for the main hall on the same Saturday evening. The coordinator holds the first request; the hall is reserved with two hours of setup and an hour of cleanup. When the second request is held for the same evening, the overlap is found and the hold is refused. The coordinator offers the garden room instead, which has capacity for the smaller party.

The first booking is confirmed when the deposit is verified, runs on the day, and is completed with the time the last guests left.

What your team sees

  • Open bookings — Requested, held, confirmed and in-progress bookings with their times.
  • Booking lifecycle board — Bookings grouped by status.
  • My bookings — Each coordinator’s own bookings.

Follow the work through

Review the implementation plan before importing bookings.

What it keeps track of

Data model
Bookings
Venue booking records with lifecycle, quoted amount and interval.
Booking resources
Reserved resource lines belonging to a booking.
Resources
Bookable halls, rooms and service resources with eligibility notes.

Who uses it

Permissions
Booking Coordinator
, Venue Manager.
The coordinator runs bookings; the venue manager follows the calendar.

Set up Venue Booking System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started