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
- Review and evidence
Review and evidence
Independent decisions and supporting files.
OverviewReview decision log×
Venue Booking System · Review and evidence
New
Review decision log
Review decisions
| Id | Parent | Reviewer | Source revision | Decision | Decided at | |
|---|---|---|---|---|---|---|
| IDD-605 | BKN-99309 | 900 | Approve | 03 Oct | ||
| IDD-536 | BKN-69904 | 600 | Return | 21 Oct | ||
| IDD-835 | BKN-16669 | 490 | Approve | 24 Oct | ||
| IDD-366 | BKN-83543 | 600 | Return | 17 Oct | ||
| IDD-749 | BKN-59791 | 50 | Approve | 10 Oct |
6 of 6 records
IDD-605Review decisions · RD-82899
ApproveParentBKN-99309
Source revision900
Decided at03 Oct
ReasonApprove rd-175
What you can do
Keep the decision and the reason together
Review decisions record who decided, which revision of the booking they looked at, whether they approved, rejected or returned it, when, and why. They are kept as their own records on the booking, so the history shows each decision in order rather than only the latest state.
Evidence files sit beside the decisions: signed requests, floor plans, insurance certificates, supplier confirmations. Each file has a title, an evidence type, who uploaded it and when, and whether it is internal or can be shared with the client. Reviewers see the evidence on the booking they are deciding.
How the work is organized
Package reviewers decide; coordinators attach evidence.
- Independent decisions. The person who prepared a package cannot approve it.
- Revision on every decision. Each decision names the revision it applied to.
- Visibility per file. Internal notes stay internal; shared evidence can go to the client.
What to agree during setup
Agree which evidence each event type needs, such as insurance for external caterers or a floor plan for large events. Agree who can mark evidence as shared. Decide how long reviews should take. Prepare examples of an approval, a return for missing insurance and a rejection.
Check the handoff on an actual case
A client’s external caterer has not sent proof of insurance. The reviewer returns the package with that reason. The coordinator uploads the certificate as internal evidence and resubmits. The reviewer approves, and the booking shows the return, the uploaded certificate and the approval, each with its time.
A month later the client disputes a charge for the caterer’s late arrival. The coordinator opens the booking and finds the package the reviewer approved, the floor plan that was shared with the client and the reviewer’s notes on timing. The answer comes from the record, not from someone’s memory of the conversation. If the client had been sent an internal working note by mistake, its visibility would show it was never meant to be shared.
What your team sees
- Review decision log — Approvals, rejections and returns with reasons.
- Packages awaiting review — The reviewer’s queue.
Follow the work through
- Venue package review: How review decisions are made.
What it keeps track of
Data model- Review decisions
- Independent review decisions recorded against a booking revision.
- Record attachments
- Uploaded evidence files attached to a booking.
- Bookings
- Venue booking records with lifecycle, quoted amount and interval.
- Team members
- Staff members with an authenticated platform identity and role scope.
Who uses it
Permissions- Package Reviewer
- , Booking Coordinator.
- Reviewers decide; coordinators supply evidence.
Set up Venue Booking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.