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
- Operations control
Operations control
Operation receipts, exceptions and reconciliation.
OverviewOperation exceptions×
Venue Booking System · Operations control
New
Operation exceptions
Operation receipts
| Id | Operation key | Action | Parent | Result state | Occurred at | |
|---|---|---|---|---|---|---|
| IDD-910 | OK-179 | ACT-448 | BKN-46568 | Pending | 23 Oct | |
| IDD-140 | OK-257 | ACT-838 | BKN-21696 | Failed | 09 Oct | |
| IDD-310 | OK-106 | ACT-882 | BKN-93745 | Needs review | 13 Oct | |
| IDD-140 | OK-905 | ACT-288 | BKN-10132 | Pending | 09 Oct | |
| IDD-829 | OK-400 | ACT-319 | BKN-84715 | Failed | 18 Oct |
6 of 6 records
IDD-910Operation receipts · OR-82666
PendingOperation keyOK-179
ActionACT-448
ParentBKN-46568
Occurred at23 Oct
Failure reasonCut to length
What you can do
Be sure every hold and cancellation took effect
Each guarded action (hold, confirm, cancel, record a no-show, correct scope) writes an operation receipt with a stable operation key, the action, the revision expected, the time and a result: pending, completed, failed or needs review. It also lists the effects the action was meant to produce and, if something went wrong, the reason.
Receipts are what stop a double click from booking a hall twice or releasing capacity twice, and what make failures visible. Reconciliation reads what was actually saved before it marks a receipt completed: the reservation lines, the status change, the review decision. It checks with the payment provider only when the action involved money.
How the work is organized
The operations analyst works the exception queue; the venue manager watches it.
- One key, one effect. A repeated action returns the earlier result.
- Read first. Completion is confirmed from saved records, not assumed.
- Exceptions together. Pending, failed and needs-review receipts appear in one list with their reason.
What to agree during setup
Agree who works the queue, how often reconciliation runs and when an exception is escalated to the venue manager. Prepare examples of a completed hold, a timed-out confirmation that did complete, one that did not, and a cancellation refused because capacity was already released.
Check the handoff on an actual case
A coordinator’s confirmation times out during a busy afternoon. Its receipt is left pending. Reconciliation finds the booking confirmed and the deposit verified, and marks the receipt completed. Another pending receipt for a hold finds no reservation lines saved, so it stays in the queue with its reason. The analyst runs the hold again under the same key, it reserves the hall once, and the queue is clear.
At the end of each week the venue manager looks at the exception list before the weekend’s events. Anything still pending or failed for a booking in the next few days is cleared first, so the team does not discover on the day that a hold never reached the hall or that a cancellation never released the room.
What your team sees
- Operation exceptions — Pending, failed and needs-review receipts with their reason.
Follow the work through
- Operation reconciliation: From pending receipts to verified results.
What it keeps track of
Data model- Operation receipts
- Durable receipts for guarded operations with stable operation keys.
- Bookings
- Venue booking records with lifecycle, quoted amount and interval.
- Booking resources
- Reserved resource lines belonging to a booking.
Who uses it
Permissions- Operations Analyst
- , Venue Manager.
- The analyst reconciles; the venue manager follows exceptions.
Set up Venue Booking System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.