Year-end peak season: how small hotels avoid double-booking a room

There is a paradox every operator of a small accommodation property knows well: the days that earn the most money are also the days when guests are most easily lost. Through the year-end peak the phone rings without a pause, messages arrive on three or four apps at once, every online sales channel is open for business — and there is usually only one person on duty. That is exactly when something very specific tends to happen: two different guests are given the same room for the same night.

This article is written for owners of mini hotels, guesthouses, homestays and serviced apartments — places where the owner answers the phone personally, and one person takes the booking, takes the deposit and assigns the room. One thing to state plainly at the outset, because it runs through everything that follows: a double booking is almost never the fault of the person on duty. It is the consequence of hold information sitting in several places at once — part of it in the head of whoever answered the phone, part in a message thread, part on the sales channels, part in a notebook — with none of those places aware of the others. The more careful the person on duty, the more exhausting it becomes; the structure does not change.

Part 1: The four routes to a double booking

To deal with something you first have to name it accurately. In practice at small properties almost every double booking arrives by one of the four routes below, and each route has its own way of being closed.

Route 1 — Availability updates slowly between sales channels

• Selling in several places, deducting availability by hand. The property is open for sale on several online channels at once, plus guests who call directly. Every time a booking arrives in one place, the person on duty has to remember to close rooms in all the others. The interval between those two actions is precisely the gap through which a room gets sold a second time.
• The gap widens exactly when things are busiest. On an ordinary day with a handful of bookings it is easy to keep up. At the year-end peak the bookings crowd into the evening — which is also when the person on duty is checking in a guest standing at the counter.
• Rooms closed by hand are easy to forget to reopen. The less discussed side of this: many properties, afraid of overselling, close rooms on the channels and then forget to reopen them when a guest cancels — losing sellable nights without anyone noticing.

Route 2 — A room held on a promise, never written into the system

• The most familiar sentence of the peak season. "Could you hold a double for me for the night of the 30th? I'll transfer this afternoon." The person on duty agrees, writes it on a scrap of paper or simply remembers it, and in the system that room is still shown as free.
• A hold with no expiry. The guest says "this afternoon", does not transfer, and does not call back. The room hangs indefinitely, the person on duty has no idea when it may be sold again, and usually holds it longer than necessary rather than risk offending a guest.
• A shift change loses the trail. Whoever accepted the promise in the afternoon is not the person on duty that evening. The scrap of paper may survive; what was held in someone's head does not.

Route 3 — Two people taking bookings at the same moment

• Owner and duty staff working simultaneously. The owner is on the phone with a regular guest while the person on duty is answering a different guest by message — and both are thinking about the last free room.
• Nowhere to stake a claim instantly. If the system only records a booking once the paperwork is complete, then the whole conversation with the guest is a period during which that room is invisible to the other person.

Route 4 — Rooms that are not ready but are still listed for sale

• Rooms under repair, with faulty equipment, or not yet cleaned. Technically they cannot be sold for tonight, but if that status only travels by word of mouth between housekeeping and the front desk, the system still counts them as available.
• Rooms set aside with nobody marking them. Small properties often keep a room in reserve for emergencies or for a regular guest who may turn up unannounced. If that reservation is not visible on screen, it exists only in one person's memory.

Part 2: Bringing every hold into a single book

The remedy for all four routes has one thing in common, and it is not complicated: every commitment to hold a room, wherever it comes from, must become a line in the same book at the moment the commitment is made. "Book" here means the system the property already runs on, not a second notebook.

Four rules for the single book

• Record it when you promise it, not when the money arrives. This is the most important change and also the one most often skipped. A promise to hold a room with no deposit behind it must still occupy the space in the system, in a "tentative hold" state, so that nobody sells over the top of it.
• Every tentative hold carries a specific expiry. Held until 6pm today, held until noon tomorrow — one clear moment in time, told to the guest as the hold is taken, and written on that line. When the expiry passes with no deposit, the room returns to sellable on its own.
• A tentative hold must be visible, not merely present. On the room assignment screen, a room on tentative hold should be a different colour from a room with a deposit and from a free room. The person coming on the next shift understands at a glance, without having to ask anyone.
• One single source of availability for every channel. When a property sells in several places, availability has to be deducted automatically everywhere the instant a booking arrives anywhere. This is work a person can do by hand at a small scale, and cannot keep up with at the peak. How to organise the connection between sales channels was set out in detail in the article on integrating online sales channels and direct booking.

These four rules are what a cloud AI hotel management software enforces in place of human memory: tentative holds that expire by themselves, availability deducted once for every channel, and each room's status displayed the same way on every device belonging to everyone on duty. It is worth saying that the first three rules can be adopted this week even without changing any tool — they are internal conventions, not features. These four rules are only one slice of the operating cycle; the whole chain from booking through check-in, housekeeping and cashiering to reporting is set out in the article on the total hotel management solution.

Part 3: Deposits — the five places they go missing

If double bookings are the visible risk of the peak season, deposits are the quieter one and usually the more expensive. The year-end peak is when the largest amount of money received in advance arrives in the year, from many guests, along many routes, while the method of keeping track of it is still the method used in the quiet months.

Five places deposits go missing

• 1. A payment reference that cannot be matched to any booking. The guest transfers and writes only their own name, or "room deposit", or leaves it blank. Whoever reads the bank statement has no idea whose money it is, for which dates, for which room. If the guest used somebody else's account, it is harder still.
• 2. Deposits arriving through several different channels. Some by transfer to the property's account, some to the owner's personal account once a guest is a regular, some by e-wallet, some as cash handed to an acquaintance to bring over. Four flows of money, four places they are recorded, and usually nowhere that adds them up.
• 3. No clarity about who confirmed receipt. The guest says they have transferred, the person on duty cannot check immediately because they are busy, and then forgets to check. On the day of arrival nobody knows for certain whether the money came in, and nobody is accountable for the answer.
• 4. The deposit is in but the room is still free in the system. The money has arrived while the booking has never been confirmed on screen — the worst case of all, because the property is simultaneously holding a guest's money and offering that very room for sale.
• 5. The deposit is added straight into the revenue of the day it arrives. By nature a deposit is money that has entered the account but does not yet belong to the property — it becomes revenue only when the guest actually stays. Recognising it early inflates revenue in the month the money arrives and deflates it in the month of the stay, which robs every month-to-month comparison of meaning.

Part 4: A seven-step routine for a deposit

Below is the routine we recommend for small properties. It is deliberately short, because a long procedure gets skipped at exactly the moment things get busy. These seven steps are an approach to hotel booking deposit management that one person on duty can still follow in the middle of the peak.

The seven steps

• Step 1 — Create the booking first, ask for the money afterwards. The moment a hold is accepted, create the booking line in a tentative hold state with an expiry. The booking reference generated at this step is what every remaining step relies on.
• Step 2 — Send the guest a payment reference already written out. Include the booking reference and the arrival date, for instance in the form "booking reference + arrival date". Write it out so the guest only has to paste it in; ten guests writing their own version produce ten different versions.
• Step 3 — State the payment deadline and what happens if it passes. One sentence, said at the moment the hold is taken. This is the sentence that prevents most of the later arguments, and saying it in advance is always easier than explaining it afterwards.
• Step 4 — When the money arrives, attach it to the right booking reference immediately. Do not leave a batch to be reconciled at the end of the day; end of day is when misallocation is most likely, because several amounts look identical.
• Step 5 — Change the booking status and confirm back to the guest. A short confirmation message carrying the booking reference, arrival and departure dates, room type, amount received and amount outstanding. That message is the evidence both sides rely on if anything needs checking.
• Step 6 — Record the deposit as money received in advance, not as revenue. It converts into revenue night by night as the guest actually stays. How this connects through to the books was set out in the article on accounting for small hotels under Circular 99.
• Step 7 — At the end of every shift, review exactly two lists. Tentative holds past their expiry with no deposit, and money received that has not been attached to any booking. When both lists are empty, that shift is clean.

Part 5: Cancellations, date changes and no-shows — handling them cleanly

The peak is when cancellations and changes are most frequent, partly because guests book in several places at once and then choose, partly because year-end travel plans shift. What decides the outcome is not whether the policy is strict or generous, but whether the policy was stated in advance and written down.

Four things to settle before the season, not while it is happening

• The cut-off for a refundable cancellation. Pick a single cut-off for the whole peak season, for example a set number of days before arrival. One cut-off that is easy to remember and applied to every guest is far fairer than several flexible ones that each member of staff interprets differently.
• How date changes are handled. Keep them separate from cancellations: whether the deposit moves to the new dates, how many times it may move, and whether there is a time limit on using it. In the system, a date change must keep the same booking reference so the history does not break.
• Guests who neither arrive nor call. This is where the real loss happens, because the room stayed locked through the peak. The policy should be clear from the outset, and more importantly the room must be returned to sellable the following morning, not left hanging another day.
• Where refunds go and who approves them. Refund to the same account the money came from, have one person approve, and record the refund against the original booking reference. Every refund without a trace is a small hole in the book.

One note on tone when dealing with guests through the peak: a firm policy does not require a hard manner. Most guests accept clear conditions stated in advance; what irritates them is a condition that only appears at the moment they want to cancel.

Part 6: Money taken this month for a stay next month

This is particular to the year end, and it is also where the state of the business is most easily misread. In the month before the peak, the property's account can look very healthy — but most of that balance is money for nights that have not yet happened.

Three things to keep separate

• The account balance is not the trading result. A month that takes in a lot of deposits for next month's stays will look like a boom, and the following month — when the guests actually stay — will look like a slump, when in reality the opposite is true.
• The total of money received in advance and still held must be viewable at any time. This is the figure to know before committing to any large spending during the season — repairs, stock purchases, year-end advances on wages and bonuses. It is an obligation, not a source of funds.
• Revenue is recorded by the night the guest stays, not by the day the money arrives. This convention is what makes a year-on-year comparison meaningful, and what makes the figures in the owner's app reflect the real rhythm of the business. How to read these metrics at a small property was covered in the first article in the DiOwner series, and once you have more than one property, how to add them up correctly is covered in the article on running 3–5 hotels at once.

Part 7: Summary — where things go wrong in the peak, and what to do

Part 8: What to do in the ten days before the peak

The order below is deliberate: the first five items are internal conventions that cost nothing and can be done this week; the last three involve tools and should be started early enough to become familiar before the guests arrive.

Five internal steps

• Step 1 — Fix a default hold expiry applying to every promise to hold a room with no deposit behind it, for example the end of the following day. Write it as one line and post it where the person on duty can see it.
• Step 2 — Write out three message templates in advance: requesting a deposit with the payment reference, confirming a deposit received, and a reminder before arrival. Prepared in advance, they only have to be sent when things are busy, and the wording stays consistent across shifts.
• Step 3 — Settle the cancellation and date-change policy for the whole season, a single cut-off, told to the guest at the moment the hold is taken.
• Step 4 — Redefine how deposit money reaches you. Best is a single property account; if several routes must remain, every one of them has to be recorded against the same booking, with a note of how it was received.
• Step 5 — Make a habit of reviewing two lists at the end of every shift: tentative holds past their expiry with no deposit, and money received that has not been attached to a booking.

Three steps about tools

• Step 6 — Bring availability across every channel onto a single source. This is what closes route 1, and it is also the work no person can take over when bookings arrive in a rush.
• Step 7 — Set up multiple seasonal rate plans and event rate plans before the peak begins, so the person on duty picks a rate plan that already exists instead of working each case out in their head. Call it by its proper name: this is preparing several rate plans and applying them by date range, not a feature that adjusts prices automatically to the market — that one is on the roadmap with a Coming soon label.
• Step 8 — Turn on alerts for dates approaching full occupancy. Knowing in advance that a night has only two rooms left leaves time to decide whether to keep them for regular guests or push them out for sale; knowing after the night has sold out leaves nothing to decide.

Conclusion

The peak season does not create new faults; it simply exposes the existing gaps all at once. Three things decide the outcome, in this order: every hold becomes a line with an expiry in the same book at the moment it is promised; availability has one single source for every sales channel; and every deposit can be attached to exactly one booking and is tracked as money received in advance rather than as revenue. The first two close off double bookings; the third keeps both the books and the guest relationships out of trouble during the busiest month of the year.

On that footing, DiCloud — an online AI hotel management software — takes on the part human memory cannot carry through a peak: tentative holds that expire by themselves, availability deducted once for every channel, deposits attached directly to bookings, and identical room status on the screen of everyone on duty. All of it sits within the total hotel management solution from DiHotel Solutions Corps — an ecosystem that has served more than 300 accommodation properties in Vietnam and Japan over more than 20 years.

If you run a 4–5 star hotel, a resort, or several properties entering the peak at the same time, the companion piece on the DiHotel Blog addresses exactly that tier: conference and year-end event season — controlling deposits and availability across several properties — event deposits split across several payment instalments, groups holding many rooms, and shared availability when several properties fill up at once. At that tier the operational work is handled by DiHotel, the AI hotel management software — the original platform for 4–5 star hotels and resorts — while an owner holding both large and small properties brings them together in one place through multi-property hotel management software.