These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Venue Booking System
- Features
- Venue packages
Venue packages
Hall, times and guest count reviewed for each booking.
OverviewPackages awaiting review×
Venue Booking System · Venue packages
New
Packages awaiting review
Approval waits for the package reviewer
| Id | Parent | Hall | Starts at | Ends at | Guest count | |
|---|---|---|---|---|---|---|
| IDD-456 | BKN-83660 | HLL-516 | 23 Oct | 29 Oct | 27 | |
| IDD-778 | BKN-18175 | HLL-697 | 18 Oct | 27 Oct | 2 | |
| IDD-118 | BKN-21934 | HLL-697 | 22 Oct | 31 Oct | 35 | |
| IDD-713 | BKN-31425 | HLL-614 | 13 Oct | 18 Oct | 19 | |
| IDD-280 | BKN-87229 | HLL-339 | 23 Oct | 30 Oct | 18 |
6 of 6 records
IDD-456Venue packages · VP-98261
ParentBKN-83660
HallHLL-516
Starts at23 Oct
Ends at29 Oct
Guest count27
What you can do
Agree the event before you confirm it
A venue package describes the event a booking will run: which hall, when it starts and ends, and how many guests are coming. A package moves from draft to submitted, and then an independent reviewer approves it, rejects it or returns it for changes. A completed package is the one the event ran on.
Review exists because the details in a package drive everything else: staffing, setup and what the customer has been told. The reviewer checks the hall, times and guest count against the supporting evidence attached to the booking. The submitted revision is frozen while it is reviewed. Nobody can approve a package they prepared themselves.
How the work is organized
Coordinators prepare packages; package reviewers decide them.
- One package per booking revision. The package belongs to its booking, and the decision applies to the revision reviewed.
- Evidence-backed. Supporting files such as the signed request or floor plan are attached to the booking for the reviewer.
- Independent decision. Self-approval is refused, and the decision records the reason.
What to agree during setup
Agree what a package must contain for each event type and what evidence the reviewer needs. Agree who reviews packages and how fast, and how a returned package is followed up. Prepare examples of a straightforward package, a package whose guest count exceeds the hall, a package returned for missing evidence and a package changed after approval.
Check the handoff on an actual case
A coordinator submits a package for a gala in the ballroom with 320 guests. The reviewer sees that the ballroom’s capacity on the reservation line is 300 and returns the package with that reason. The coordinator moves the overflow to the adjoining terrace, updates the package and submits it again. The reviewer approves the new revision, and the booking can be confirmed.
What your team sees
- Packages awaiting review — Submitted packages with hall, times and guest count.
- Venue package board — Packages by draft, submitted, approved, rejected and completed.
Follow the work through
- Venue package review: From a draft package to an approved one.
Check permissions for reviewers.
What it keeps track of
Data model- Venue packages
- Reviewed venue package revisions for a booking.
- Bookings
- Venue booking records with lifecycle, quoted amount and interval.
- Review decisions
- Independent review decisions recorded against a booking revision.
Who uses it
Permissions- Booking Coordinator
- , Package Reviewer.
- The coordinator prepares packages; the reviewer decides them.
Set up Venue Booking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.