The booking chart
Rooms down the side, nights across the top, every stay drawn as a bar — the one screen a front desk lives on, with the price and the rules on it.
The chart is the whole hotel on one screen. Every room is a row, every night a column, and every booking is a bar you can read from across the desk: the guest's name, the nights, and a colour that says where the business came from — an OTA, the hotel's own page, a company, a walk-in.
What is on it, and why
Above the rooms sit the rate for each night, the minimum stay and any stop-sell. The price and the rule are on the same screen as the booking, so the desk never quotes a rate the chart will refuse a minute later.
Below the chart, a shaded row says how many rooms of each type are still free on each night — the number a reservations manager wants without opening a report.
- Drag a bar to another room or another night; the system asks once if the move needs asking about, and refuses only when money would be wrong.
- Right-click a room to book it or block it; a block asks why, from which night to which, and writes the person's name on it.
- A booking that has no room yet — a channel booking arriving when its type is full — sits in a lane of its own for its room type, still draggable, so it is never invisible.
- The chart keeps itself current: a booking pushed by a channel is drawn in the same request that accepted it.
What it will not do
It will not let a stay be moved behind the business date, and it will not let a closed night be dragged into a different day. Those are the ways a chart quietly corrupts a hotel's books, and each is a refusal with a sentence attached.
Every picture on this site is this screen, on a demo hotel, taken by a script that fails if the screen has moved.