Module

Revenue

Analytics, pace against the prior period, a per-night demand forecast, rate recommendations you accept or dismiss, and a portfolio view across properties.

What it is

Revenue reports what happened, what is on the books, and what the two together imply — and it shows the base for each. Occupancy is stated as a percentage and as the room-nights it came from; pace is this book against the prior period with pickup since a date; the forecast is per night against a house of known size. Recommendations are suggestions with their reasoning attached, which a person accepts or dismisses.

Figures that state their own base

Occupancy, ADR, RevPAR, room revenue, room-nights sold and capacity for a chosen date range, each card naming what it was computed from. A source and market breakdown splits the same period by channel, so channel mix and channel rate can be compared rather than conflated.

The Revenue analytics header in Nerve for a chosen date range: six cards giving occupancy of 70.7 per cent from 318 of 450 room-nights, ADR, RevPAR, room revenue, room-nights sold, and the capacity the figures were computed against. — Every headline figure states the base it was computed from.

A forecast per night, beside what is booked

One row per night: the occupancy already on the books, a forecast occupancy pill, and the forecast rooms against the size of the house. The weakest night in a window is a red pill rather than a number to hunt for.

The Demand forecast table in Nerve, one row per night, each showing the occupancy already on the books, a colour-coded forecast occupancy pill, and the forecast rooms out of a fifteen-room house. — A forecast per night, next to what is already booked for it.

Recommendations carry their reasoning; parity is checked

A recommendation states why it exists — a forecast occupancy over a date range — shows the current rate arrowed to the proposed one, and offers Accept or Dismiss. Parity is a separate, factual check: the intended rate against what the channel is actually showing, with the drift named.

The “Rate parity — intended vs. distributed” panel in Nerve, warning that a channel price has drifted from the intended rate and labelling the gap as 8.6 per cent drift. — Parity is checked against what the channel is actually showing.

Across properties, without hiding them

The portfolio view gives group occupancy, ADR, RevPAR, revenue and pace — and then the per-property table underneath, where two hotels can be pulling in opposite directions. The group figure is not allowed to be the whole answer.

The portfolio view of Nerve's Revenue app across two hotels, giving group occupancy, ADR, RevPAR, revenue and pace, above a per-property table where the two hotels are pulling in opposite directions. — A group figure that hides two properties moving apart is worth less than the table under it.

What it means for an agent

An agent can read the analytics, the pace summary and the per-night forecast, and it can read a rate recommendation along with the reasoning behind it. Applying one is an operation with its own permission — so an agent can be allowed to propose a rate change and not to make it, or allowed both, within the guardrails you set.

Go deeper

Every screen above is documented, operation by operation, against the shipped product.

Revenue documentation →

Wondering whether this is for a property your size?

← All features