Resources for hospitality teams
Explore practical Daily operations guides for vacation rental hosts and property managers.
A stay that has finished is not yet money you hold. This guide walks through the four stages between a guest checking out and cleared funds, what can pause the payout at each one, how a disputed amount sits apart from the rest, and a two-lines-a-month habit that makes the gap visible before it starts costing you.
A 2am call is a bad time to decide who you are going to phone. This guide sets out why an escalation list has to be written in daylight, the three fault types that behave nothing alike — pest, water and power — and for each one the first action, the person allowed to say yes to money, and the message the guest gets. It ends with the short information pack every call needs.
A turnover clean is whatever fits between one guest leaving and the next one arriving, so the clock sets its scope. A season-end deep clean is whatever only comes apart once a year, so disassembly sets its scope. This guide separates the two by scope, crew and booking lead time, shows how to tell whether a complaint was a missed item or a missed standard, and turns both jobs into one written list a new cleaner can be held to.
Two units and one group reads like a calendar problem and behaves like an accounting one: one payment arrives, two lots of inventory are consumed, and nobody can later say which door earned what. Three decisions settle it — which unit owns the booking, where the charge sits, and what the guest is told. This guide walks each one, including why splitting the charge across two reservations usually costs more than keeping it on one.
A cleaning or damage charge can be reversed months after the guest agreed to it, because the decision is made by somebody who was not there and can only read what survived. Four pieces of documentation decide it, and each has a moment when it can be made and after which it cannot. This guide covers that order, the gap where most hosts lose their evidence, and a one-page file that answers any later enquiry without starting from zero.
A neighbour complaint is cheap while it is between you and the neighbour, and expensive the moment it reaches a platform or a dispatcher. Several cities now write a response clock into the licence itself, some as short as 15 minutes. This guide covers the four-step first response, the arithmetic behind your actual budget, and the record that makes the second complaint survivable.
Response rate is a share, not a speed: every new inquiry must be answered inside 24 hours or it counts against you, and the window looks backwards so a bad month lingers. The published eligibility line is 90%, but the operators who rank well work to a much tighter number. This guide covers how to protect the figure with three kinds of reply, and how to read your own numbers before they drop.
A unified inbox carries guest conversations and nothing else. A booking generates three streams — messages, availability and money — and only the first ever reaches an inbox. This guide maps which channel actually feeds guest messages, why the other three were never in scope, and the two short reviews that keep the other two streams from leaking.
A remote co-host handover does not fail on the first question, it fails on the eleventh, three weeks in, when you are asleep. This guide sets out what a co-host needs on day one, in week one and in month one, the five documents that absorb most of the back-and-forth, which access to grant and which to withhold, and how to test the pack before you actually need it.
A quarterly walk-through catches what a reported-fault culture never sees, because most of what fails in a short-term rental is not reported by anybody. This guide gives twelve checks grouped by what each one protects, who is qualified to run them, what disqualifies a runner, and how to turn forty minutes on site into a record worth keeping.