Bookings and the calendar

A room with more people than it sleeps

Moving a party of four into a room that sleeps three is allowed: the picker warns, asks once, does it, and records who said yes.

The room type says it sleeps three; the booking is four people — an infant, an extra bed, a guest who asked for exactly this. The software knows a number; the desk is standing in front of the guest. So the number is a warning, not a refusal.

The Move dialog: a Superior room offered with the warning "Sleeps 3 — this booking is 4 people", the reason box and the Move button.
The Move dialog: a Superior room offered with the warning "Sleeps 3 — this booking is 4 people", the reason box and the Move button.

Do this

  1. In Move room every room that can take the stay is offered. One that sleeps fewer than the party carries the warning beside it — *Sleeps 3 — this booking is 4 people*. Rooms that are taken, out of order or blocked are still greyed out; those are hard reasons.
  2. Pick the room. The summary repeats the warning and says **You will be asked once**.
  3. Type the reason — it is recorded.
  4. Press Move. The desk is asked *Move anyway?* once, and the move goes through for anyone who may move a room. No administrator is needed.

What is recorded

The booking's history carries the move with the room's capacity, the party size, and who accepted it — login, user, the address of the machine and the browser it came from. A report can find every room filled past its number and by whom. That record is the price of the door being open, and the owner's rule for it is the standing one: *refuse only for money; otherwise ask once, do it, and write down who said yes.*

More in Bookings and the calendar

Reading the calendarRooms down the side, dates across the top, and four things worth knowing about the colours. Blocking a room from the chartRight-click a room, say why, from which night to which, and who is blocking it. The channel is told; the chart draws it; a booking into it is refused. Making a bookingNew booking, or click an empty square on the chart. What each field is for. Bookings that have no room yetEvery live booking with no room number, from any source, is drawn on the chart and listed beside it — and dragged onto a room. Where the price comes fromThe rate plan sets the price. Who may change it is a separate question with a deliberate answer. Changing the rate on a bookingAnybody at the desk may name the rate until the guest checks out; after that only an administrator, and it is a tax note. An OTA rate is never changed here. Changing a bookingDates, room, guest and rate can all be amended. Some changes are refused, and some can be overridden. Cancelling, and no-showsBoth need a reason from the list, and both leave the record standing. Holding a room, and the guest pay linkA time-boxed hold with a link the guest can pay on. It releases itself if they do not. Putting a stay in another guest's nameOnly an administrator. Any status, before or after check-out. The booking and its bills carry the new guest; the invoice number, the charges and the tax do not move. Booking the same stay againBook again copies a stay for a returning guest, and tells you what the price would be now. Group bookingsMany rooms under one name, created together and cancellable together. Moving a guest to another roomDrag the bar on the chart, or use Move room. It asks for a reason and refuses for good ones. UpgradesMove a guest up a grade, priced or complimentary, with the reason recorded. Messaging a guestTemplates render the message; a person sends it. Nothing goes out on its own.