The weekly report for short-term rental hosts

The Monday review, before checking email

Most independent short-term rental hosts open the week by reconciling last week's bookings across channels, sorting cleaning fees by listing, and chasing a payout that posted late because of a timezone mismatch. None of that is revenue work. It is bookkeeping that masquerades as revenue work, and it eats Monday before the host has looked at a single number.

A weekly report for short-term rental hosts is what replaces the Monday scrub. Four numbers, on one page, in five minutes: revenue for the week just closed, occupancy for the week ahead, average daily rate for the same forward window, and review velocity for the trailing fourteen days. Read them in sequence and the week tells its own story. Most hosts never realize the order matters until they start with revenue.

Revenue, the number that doesn't lie on its own

Revenue is the headline number on any weekly report for short-term rental hosts, and it is also the easiest to misread. A $4,200 week can be a great week or a disappointing one depending on how many listings produced it, what the market was doing, and whether the bookings came in at the rate the host actually wanted. Two listings running flat-out at a low ADR can produce the same revenue number as one listing that caught a conference window at the right rate — and only one of those weeks is repeatable, because only one was driven by the market rather than by defensive discounting.

That is why revenue has to be read against the context that produced it. The table below is a four-week discipline check — three columns, one number at a time — that a host can run on Monday morning in under sixty seconds, and that translates revenue into a decision instead of a screenshot.

Each row reads one number from the weekly report, names what the number alone is hiding, and forces a decision rule that does not depend on what the host remembers from last month. Running it on the same Monday each week turns a static set of figures into a habit. The table is intentionally short — three to four rows is enough to catch the patterns that compound, and short enough that the host never skips a week because the loop felt expensive. The pairing of metric and decision is what makes the discipline work: a number without a decision is a screenshot, and a decision without a number is a guess.

Occupancy and ADR, read together

Occupancy and ADR are the two numbers that explain revenue, so they have to be read together. High occupancy with a falling ADR is a host discounting into more bookings — volume up, dollars up less. Low occupancy with a stable ADR is a host holding rate while the market drifts. High occupancy and a rising ADR is pricing power in the moment, often a weekend or event. Low occupancy and a falling ADR is the worst combination — neither lever is helping, and the host needs to ask which of them they have left.

The discipline is to name the combination before reacting. A host who reads occupancy alone tends to lower the rate when occupancy dips, even when a small rate lift would have caught a better guest. A host who reads ADR alone tends to raise the rate when revenue dips, even when a fuller calendar would have closed the gap at the existing rate. Read together, the two numbers force a one-sentence diagnosis before any rate change goes out.

Reviews, the leading indicator

Reviews move before revenue does. A single one-star review doesn't change the next week; it changes the week after, because the listing's positioning inside the channel drops, click-through softens, and the conversion curve slips. Two weeks of declining review velocity — especially on cleanliness or check-in — is the earliest signal that next month's revenue will underperform, long before the P&L makes it obvious.

This is why review velocity belongs on the weekly report, not in a separate quarterly review. A host who only checks reviews when something goes wrong treats the score as a snapshot. The hosts who compound revenue notice when review velocity drifts down a half-star at a time, and adjust listing copy or ops before the channel's algorithm finishes adjusting for them.

From numbers to actions in five minutes

The Monday workflow collapses to four numbers, one table, one sentence of diagnosis, and one change. Print revenue this week versus last week. Print occupancy and ADR for the next fourteen days, together, not separately. Print review velocity for the trailing fourteen days. Run the discipline check from the table above. Write one sentence naming the combination the week produced. Make one change in the calendar before closing the tab.

Most weeks the change is small: a price-floor nudge, a three-night minimum lifted on a slow Tuesday, a guest comms template tightened after a review pattern. The compounding happens because the change is always named, not because it is always large. A host who runs this loop weekly closes more calendar at higher ADRs with fewer surprises, and that is what a good weekly report for short-term rental hosts is built to enable. See how Halgrove's /pricing tiers package the report and the agents behind it.