Property management analytics for hosts

Measure booking pace, not just occupancy

Occupancy describes what already sold. Pace shows how quickly future dates are filling against a useful reference, which is what lets you act while there is still time. Pick checkpoints at 90, 60, 30, 14, 7 and 2 days before arrival and compare nights booked, average rate and remaining availability with the same season last year or a comparable prior period.

Decide the actions before you look at the numbers, or you will rationalise whatever you see. If high-demand weekends are filling earlier than usual above target, hold or raise within your ceiling. If midweek pace is weak, check minimum stay, closed arrival days, photos and the final guest total before discounting.

• Pace against a reference period
• Rate achieved versus floor
• Net after all costs
• Questions and incidents

Track net, not headline revenue

Revenue before costs flatters every decision. Track what remains after channel commission, payment fees, cleaning, consumables and the tax you absorb. Booking.com and Airbnb host-only pricing commonly sit around 15-20%, so the channel a booking arrives through changes the net materially even at the same nightly rate.

Do this per stay rather than per month at first. A two-night booking carrying a full turnover cost can look fine in a monthly total while losing money on its own. Once you can see net per stay, minimum-stay rules and orphan-night decisions stop being guesswork.

Attribute carefully or not at all

It is tempting to credit a rate change for a good month. Evaluate by stay date rather than booking date, change one variable at a time, and note the date of each change. On small volumes several weeks are needed before an effect is distinguishable from noise.

Remember that price explains less than it seems. Season, weather, local events, recent reviews, photo quality and stay restrictions all move demand. A simple change log preserves the reasoning behind each decision and is worth more than any dashboard, because it lets you learn instead of react.

Measure the guest experience with two honest numbers

Repeated questions per stay tells you whether your information is working. If the same question keeps arriving, the answer is unclear, badly timed, or living where the guest cannot find it. Fixing it once in the guide removes it from every future stay, which is why [connected guest communication](/guest-communication-software) matters more than message volume.

Problems found by the guest rather than by you is the second. Every one of those is a check that did not happen: a cleaning not confirmed, an appliance not tested, a code not rotated. Counting them turns vague unease into a specific operational fix.

Keep owner reporting readable

If you report to owners, clarity beats completeness. Occupancy, revenue, main costs, incidents and what you did about them, on one page. A comprehensible summary reduces calls and disputes far more effectively than twenty metrics that each person interprets differently.

State assumptions plainly: what period, what is included in costs, what is estimated. An owner who understands the basis of a number argues with it far less than one presented with a confident figure and no method.

Run a weekly review that ends in decisions

Twenty to thirty minutes on a fixed day. First the next fourteen days: unsellable gaps, operational risks, wrong totals. Then fifteen to sixty days: pace and minimum stays. Finally the important distant dates: events, ceilings, protected periods.

Record only what changes: a rate, a rule, an experiment. Looking at a calendar without deciding anything is not a review. Close the loop after the stay date with rate achieved, net, length, cancellations and operating cost, because that is the only point at which you know whether the decision was right.

Know when the data is lying to you

Owner stays, maintenance blocks, manually closed dates and test bookings all distort occupancy and demand analysis. Exclude them deliberately or your baseline drifts. A tool that cannot separate them will quietly mislead you about how your calendar is performing.

Be equally sceptical of comparable-listing data. An unbooked competitor rate is an asking price, not a market price, and a booked one does not reveal the conditions attached. Use it as context alongside your own costs and pace, never as a valuation.

Keep the toolkit proportionate

With a handful of properties, a spreadsheet plus your channel reports is often enough to run this well. Add software when a specific measure is too slow to assemble by hand, not because a dashboard looks professional. The [templates and tools hub](/templates-tools) has the starting formats.

The test is whether the reporting survives a busy month. Analytics you stop updating in high season are worse than none, because you will make decisions on stale numbers while believing they are current.