Booking Operations
System
One event.
Lots of moving parts.
For Grand Hire Herts, I built an operating space around enquiries, service combinations, quotations and the paperwork behind every booking.
The occasion
is the starting point.
The detail follows.
A customer’s plans become a record the owner can work with. Different services bring different pricing and timing requirements.
The actual Booking Desk.
A clearer working view.
I grouped the operational decisions into overview, bookings, actions and money views. These owner-supplied screens show the actual empty workspace, keeping the interface and its hierarchy visible.
Overview
Next booking, attention items and the operational overview.
One occasion.
Every window matters.
Allocate the work around one occasion.
Fictional same-day timings. The internal workspace and document work were tested; live confirmations, invoice issuing and reminder chains are not implied.
The right detail.
The right revision.
As a plan changes, its quotation needs to keep up. I connected service selections, pricing and document revisions within the Booking Desk.
Deposit and waiting states belong with that record. Tested internal document generation is separate from sending live invoices or collecting payments.
A clear record
of the occasion.
Illustrative document anatomy. No private prices, client record or invented invoice is reproduced.
Public enquiry.
Controlled handoff.
The public website has an enquiry route. The internal Booking Desk gives the owner a place to review what comes next.
The internal workspace has been built and tested. This does not imply that every reminder, calendar operation or live invoice action is active.
The guest sees an occasion.
The owner sees the whole plan.