Field notes for people who run properties
Guides, reports and working practice from the team building Vestibel — written about behaviour that ships, not roadmap.
The answer your AI should refuse to give
A guest asks about the pet policy at midnight. The confident wrong answer is worse than no answer at all.
The restaurant charge that never reached the room
The single most common piece of lost revenue in a hotel with a restaurant, and the two-system seam that causes it.
The Tuesday that quietly costs you a thousand pounds
A single ordinary day at a twenty-room property, and the six places money leaks when the systems do not talk.
Routing a charge to the right payer, automatically
Standing rules that decide which sub-account a future charge lands on, evaluated at the moment it posts.
Out of order, out of service, and the revenue difference
One of these takes a room off sale. The other does not. Getting the distinction wrong quietly costs you nights.
Why a booking status trail matters more than a status
Confirmed, seated, checked in, no-show, cancelled. Each transition is a decision somebody made, and the record of who made it is the useful part.
Closing the day without closing the property
Why the night audit runs while guests are still asleep upstairs owing money — and why that is the healthy state, not an exception.
Scheduling a team that works ten-hour days
Split shifts, mandatory off-days and attendance that reconciles to payroll without a spreadsheet in the middle.
One guest record across rooms and outlets
How the Party model gives a hotel a single billing anchor for a stay, a dinner table and a spa treatment — without three disconnected systems.