Guides
Short-term rental scheduling failures: double bookings, colliding turns, first hour
What short-term rental scheduling failures look like: channel latency, silent connection failures, the first hour after a double booking, and colliding turns.
What to take away
- Selling one property on several channels means one calendar published in several places. The risk is not complexity, it is latency: the minutes between a booking landing and every other channel knowing.
- A double booking is a scheduling failure that has already happened. Everything useful is either upstream of it or in the first hour after it.
- Decide in advance who gets moved and who pays for it. Making that call under pressure produces a different answer every time and a worse one.
- The other scheduling failure is quieterturns that collide because bookings were accepted without checking the window.
Where the latency actually is
Two bookings for the same nights get accepted because, for a short period, two channels each believed the property was free.
How a Double Booking Happens
- Two channels each believe the property is free
- Channel update intervals create a latency window
- Your system pushes a change, sometimes slowly
- A failed update retries silently
- Nobody notices a connection dead for days
- Two bookings accepted for the same nights
That period has several contributors. How often each channel checks for updates. How quickly your own system pushes a change. Whether an update failed and retried silently. And whether anybody would notice if a connection had stopped working three days ago.
You cannot remove the window. You can shorten it, and more importantly you can make its failures visible.
Three practices do most of the work. Hold one calendar as the authority, and let every channel take from it instead of holding its own truth. On a schedule, check that each connection is actually alive rather than assuming silence means health.
Set a rule for how far in advance you accept a booking on the highest-latency channel, because risk concentrates in short-notice bookings.
Making a failed connection loud
The dangerous state is not an error. It is a connection that stopped updating and said nothing.
Daily Connection Health Check
- Compare each channel to the authoritative calendar
- Check availability for the next fortnight
- Confirm every connection is actually updating
- Record when the check was done
- Record who performed the check
- Flag any channel that has gone silent
Give someone a daily task of confirming that each channel shows the same availability as your authoritative calendar for the next fortnight. It takes minutes and it catches the silent failure, which is the one that produces the double booking three weeks later on the busiest weekend of the year.
Record when the check was done and by whom. This is the same discipline that produces every other operating record, and the case for holding those is in the Internal Revenue Service's guide to what records a business should keep.
The first hour after a double booking
Write this down before you need it, because the version you invent under pressure is worse and slower.
First Hour After a Double Booking
- Block the dates everywhere immediately
- Establish which booking was confirmed first
- Apply the standing rule for who moves
- Contact the moving guest with an alternative
- Cover the relocation difference
- Tell the property owner the same day
- Record the cause, not just the incident
- Stop the bleeding. Block the dates everywhere immediately, so a third booking does not arrive while you are solving the first two.
- Establish the facts. Which booking was confirmed first, on which channel, and what each guest has been told and has paid.
- Decide who moves, using a rule you set in advance rather than by who complains loudest.
- Contact the guest who is moving, personally, with a specific alternative already in hand rather than an apology and a question.
- Cover the difference. Decide beforehand what you will pay to relocate someone, and treat it as the cost of the failure rather than as a negotiation.
- Tell the property owner the same day, before they hear it another way.
- Record the cause, not just the incident. Which connection, what latency, what check would have caught it.
Step three is the one to settle in advance. A defensible rule is that the later booking moves, applied consistently, with the exception written down if you have one. Deciding it case by case produces a different answer each time and no way to explain any of them.
Step five is where operators lose money badly by improvising. Set a figure you are willing to spend to relocate a guest well, before the day you need it.
The quieter failure: colliding turns
Most scheduling pain in this business is not double bookings. It is three check-outs and three check-ins on one Saturday morning with one cleaner.
Can This Booking Be Serviced?
Does the booking exceed the turn capacity rule?
Refuse or reprice the booking
Accept against the calendar
That failure is accepted at booking time. A booking that fits the calendar can still be impossible to service, and a calendar that only knows about nights cannot see it.
The fix is a capacity rule rather than a calendar rule. Decide how many turns one person can complete in a morning at your distances, and refuse or reprice the booking that exceeds it. The time budget behind that number is set out in the operations and workflow guide, which measures a turn by stage rather than as a total.
Same-day bookings deserve their own rule tied to a time of day. After a certain hour, the window no longer survives an arrival, and that hour should be a setting rather than a judgment.
Who decides what, and when
| Decision | Who makes it | Made when |
|---|---|---|
| Accept a booking that creates a fourth turn | Whoever holds the calendar | Before confirming, against a written capacity rule |
| Accept a same-day booking | Automatic, by a cutoff time | Set once, reviewed each season |
| Which guest moves in a clash | By the standing rule | Written before the first clash |
| What to spend relocating a guest | Named person, up to a stated limit | Limit set in advance |
| Whether to close dates after a fault | Whoever coordinates maintenance | Immediately, without approval |
The right-hand column is the point. Every one of these gets decided badly if it is decided during the incident.
Consistency in who you accept
Scheduling includes refusals, and refusals have to follow written criteria applied the same way to everyone, with the reason recorded.
Written Refusal Criteria
- Establish which anti-discrimination rules apply to you
- Write the refusal criteria down
- Apply the same criteria to every request
- Record the reason for each refusal
- Apply them on a quiet Tuesday and a full Saturday
Anti-discrimination protections cover housing-related transactions. They vary by state and locality above the federal position, which the Department of Housing and Urban Development summarizes in its statement of fair housing rights and obligations.
Whether and how they apply depends on the facts. Establish yours, write the criteria, and apply them the same way whether a request arrives on a quiet Tuesday or a full Saturday.
What the calendar promises the guest
Availability shown is a claim. So is a check-in time, an arrival method and an amenity listed against a date.
The Federal Trade Commission's advertising guidance for small businesses sets the ordinary standard for what you publish. In scheduling terms it means two things. Do not show availability you cannot service. And where a booking has to be moved, say what happened rather than describing it as a maintenance issue that did not occur.
Guests forgive a genuine failure explained honestly far more often than they forgive a tidy explanation that turns out to be untrue, which is also the difference between a recoverable review and a permanent one. How that plays out in public is covered in the marketing and growth guide.
When scheduling problems are really something else
Persistent collisions usually mean one of three things, and none of them is fixed by a better calendar.
Too few people for the peak, which is a staffing question handled in the hiring and training guide. Properties too far apart, which is a route problem. Or too many properties for the operation you have, which is the growth question argued in the expansion and market guide.
Compliance also touches the calendar in places: where a local requirement limits nights or occupancy, the calendar has to enforce it rather than the person. Establishing what applies is the licensing and compliance guide.
Common questions
Do I need channel management software?
You need it the first time two calendars disagree. Before that a single authoritative calendar and a daily check will do, and will teach you what the software has to solve.
How often should the availability check happen?
Daily in season. The check is cheap and the failure it catches is not.
Whose booking should I cancel?
Whichever your written rule says, applied every time. The rule matters more than which rule you chose.
Should I keep a buffer night between stays?
It is the most reliable protection against a failed turn and the most expensive. Price it honestly rather than treating it as free insurance.
What if a guest refuses to be moved?
Then you are choosing between two unhappy guests, which is why step five exists. Decide in advance what a good relocation costs and offer it immediately rather than after an argument.
