The real cost of a double-booking — and how to stop it

What it actually costs

The room-night is the visible loss. If your rate is ₱2,500, that is ₱2,500 — and it is the least of it.

You will usually walk the guest to another property, which means paying the difference, and often paying more than your own rate because you are buying at the last minute. You lose the rest of their stay, and whatever they would have spent in your restaurant or on a tour. You lose the staff time — typically your most senior person, for an hour, at the busiest moment of the day.

Then there is the review. A one-star review describing a guest turned away at check-in is read by every prospective guest for the next year, and no reply you write underneath it undoes the first sentence.

Why it happens to careful people

Double-bookings are almost never carelessness. They are a timing problem.

A booking arrives on Messenger while the front desk is checking someone in. It gets written down later, or it gets written down by someone else who does not know about the one taken by phone ten minutes earlier. An agent holds two rooms and releases one, verbally. Someone updates the sheet on their laptop, and the printed copy at the desk is now wrong.

In every case the information existed. It just was not in one place at the moment the second yes was given.

The two ways software handles this — and they are not equal

Some systems check availability when the booking is entered. The conflict is refused at the moment someone tries to create it, and the person entering it finds out immediately, while the guest is still on the phone.

Others sync availability between channels on a schedule. That closes the window but does not eliminate it: between two syncs, two channels can both believe the room is free. For a property whose bookings mostly arrive through OTAs, sync is essential. For one whose bookings arrive by Messenger, phone and walk-in, it solves a problem you do not have while leaving the one you do.

The practical answer for most Philippine properties under fifty rooms is that every booking, from every source, has to be entered into one place — and that place has to refuse the collision rather than report it afterwards.

Room types are where it quietly goes wrong

There is a subtler version of this that survives even after you have a system.

If your software tracks availability by room type rather than by room, then two Sea View doubles means a count of two, and the count is right up until the moment someone needs to know which two. A room taken out of service for a repair, a guest moved because of a noisy aircon, a long-stay guest who wants the same room throughout — each of those breaks a count that was technically accurate.

Tracking the actual rooms underneath the type costs nothing at entry time and removes a whole class of argument at the desk.

When it happens anyway: the recovery

It will happen at least once, and how it is handled decides whether it becomes a review.

Tell the guest immediately and plainly, before they ask a second question. People forgive an error handled openly far more readily than one they catch you managing. Do not explain the internal reason — they do not care whose fault it was.

Have the alternative ready before you start the conversation, not during it. That means knowing, in advance, which two or three nearby properties of a similar standard you would send someone to, and having the number of someone who answers.

Pay the difference, and pay the transport. If the alternative is more expensive, that is your cost, and arguing about it in a lobby costs more than the gap.

Then do something for the rest of the stay if they are coming back to you — a room upgrade, a meal, an activity. Not as compensation for the night, but so the last thing they remember is not the first thing that happened.

Deliberate overbooking is a different thing

Large hotels overbook on purpose, because a predictable percentage of bookings never arrive and an empty room earns nothing. That is a calculated position, taken with data on your own no-show rate and a plan for the overflow.

For a property under fifty rooms it is almost always a bad trade. Your sample is too small for the percentage to behave, your guest is more likely to be a repeat or a referral, and you do not have thirty other rooms to shuffle. The upside is one room-night; the downside is the scene described at the top of this article.

If your no-show rate is genuinely costing you, the fix is a deposit policy, not an overbooking policy.

A deposit policy does more than a rule ever will

Most of the pressure to double-book comes from uncertainty: you are holding a room for someone who may not turn up, and a second enquiry arrives for the same nights.

A downpayment removes the ambiguity. A booking with money against it is real, and one without it is an enquiry — which means your calendar stops holding rooms for people who were never coming. That alone recovers more nights in a year than most operators expect, and it does it without anybody having to make a judgement call at the desk.

It only works if the rule is written down and applied to everyone, including the guest who messaged the owner directly. A policy with exceptions is a policy that lives in one person's head, which is where this problem started.

What to do this week

You do not need to buy anything to make this better. Three things help immediately:

• One place. Whatever it is — a system, a shared sheet, a notebook — there is exactly one, and a booking is not a booking until it is in there.
• One rule for the moment of yes. Nobody confirms a room without looking at that one place first, including the owner, including on Messenger at eleven at night.
• A visible calendar. Not a list of bookings — a grid of rooms against nights, where a gap looks like a gap and an overlap is impossible to miss.