RevPAU (Revenue per Available Unit)
RevPAU (Revenue per Available Unit) is total accommodation revenue divided by the number of available units over a period, whether or not each unit was let, typically expressed per unit per month. It is BTR's revenue-efficiency metric, the multifamily equivalent of PBSA's RevPAB and hotels' RevPAR, blending occupancy and rent into one figure.
What is RevPAU?
RevPAU adapts a long-established hotel metric, RevPAR (Revenue per Available Room), to build-to-rent residential. RevPAR is calculated by dividing total room revenue by total available rooms, or equivalently by multiplying the average daily rate by occupancy; the calculation counts every available room, occupied or not. RevPAU applies exactly the same logic at unit level: total rental revenue (typically rent plus other income such as parking or amenity fees, depending on the operator's reporting convention) divided by total available units, or achieved rent per unit multiplied by occupancy rate. Because the denominator is available units rather than let units, an empty unit still counts, and the revenue it fails to generate shows up in the result rather than being hidden by looking at achieved rent alone.
Why RevPAU matters for BTR operators
A scheme can raise its headline rent and still earn less overall if occupancy falls faster than the rent increase compensates for, and RevPAU is the one number that surfaces this trade-off immediately. It is the figure investors and asset managers benchmark BTR schemes against, because it cannot be inflated by quoting rent in isolation from fill rate, or fill rate in isolation from rent. Optimising RevPAU means deliberately trading occupancy against rent rather than maximising either blindly, and that decision is only made well when leasing data (who is signed, at what rent, on what incentive) and finance data (what is actually collected, once concessions are applied) sit in one system.
How is RevPAU calculated?
| Input | Value |
|---|---|
| Occupancy | 94% |
| Achieved rent per unit per month | £1,500.00 |
| RevPAU (occupancy × rent) | £1,410.00 per available unit per month |
The calculation multiplies achieved rent, ideally net effective rent rather than headline rent, so concessions are already reflected, by the occupancy rate. A scheme fully let at £1,500 per unit per month would show a RevPAU of £1,500. At 94% occupancy, the unfilled 6% pulls RevPAU down to £1,410, a gap of £90 per available unit per month that a rent-only report would never reveal.
How does RevPAU differ from RevPAB, net effective rent, and occupancy rate?
RevPAU and RevPAB are the same underlying calculation applied to different asset types: RevPAB is used in bed-based accommodation such as PBSA and is typically expressed per bed per week; RevPAU is used in unit-based residential such as BTR and is typically expressed per unit per month. Both are the residential-sector descendants of hotels' RevPAR.
Net effective rent is a per-let rate: it tells you what a signed tenant is actually paying once concessions are spread across the term. Occupancy rate is a fill rate: it tells you what proportion of units are let, independent of price. Neither figure alone tells you how a scheme is performing, because a high net effective rent on a half-empty building is not success, and full occupancy at a heavily discounted rent is not success either. RevPAU combines both into one number, which is why it, rather than either component, is the figure that gets reported up to investors.
A void period is what actually creates the gap between headline rent and RevPAU. Every void day is revenue RevPAU counts as zero for that unit, which is why the two metrics move together.
Key takeaways
- RevPAU is total revenue divided by total available units (occupied or not), calculated the same way hotels calculate RevPAR and PBSA calculates RevPAB.
- Because it uses available units rather than let units, RevPAU captures the revenue cost of voids automatically.
- RevPAB is the PBSA equivalent, applied per bed and typically expressed weekly rather than monthly.
- RevPAU combines net effective rent (a per-let rate) and occupancy rate (a fill rate) into one figure, which is why investors benchmark BTR schemes against it.
- Improving RevPAU means deliberately trading occupancy against rent, a decision that needs leasing and finance data in one system.
How Cloudfox Helps With RevPAU
RevPAU only works as a management tool if its two inputs, occupancy and achieved rent, are visible in one place and update automatically. Cloudfox connects the leasing side (HubSpot deal and tenancy data) to the finance stack (Xero, Syft) so occupancy and net effective rent per unit roll up into RevPAU automatically, at scheme and portfolio level, rather than being reconciled manually at month end. That gives BTR operators and their investors a live view of revenue efficiency, not a snapshot built from two disconnected spreadsheets. Find out more at cloudfox.it/what-we-do.
Frequently Asked Questions About RevPAU
Is RevPAU the same as average rent per unit?
No. Average rent per unit (or net effective rent per unit) only reflects units that are actually let. RevPAU divides revenue by all available units, so an unfilled unit pulls the figure down even though it contributes no rent. A scheme with a high average rent but low occupancy can show a lower RevPAU than a scheme with slightly lower rent but higher occupancy.
What is a good RevPAU for a BTR scheme?
There is no universal benchmark. RevPAU depends heavily on local market rent levels, so it is most useful compared against a scheme's own prior periods or against comparable schemes in the same location, not as an absolute figure across markets.
Why is RevPAU calculated on available units rather than let units?
Calculating on let units only measures rent, not performance, because it ignores the impact of voids entirely. Using available units means the metric automatically reflects both how full a scheme is and how much it charges, which is the whole point of tracking it.
Is RevPAU the same thing as RevPAB?
They are the same underlying calculation, applied to different asset types. RevPAB is used in bed-based accommodation such as PBSA; RevPAU is used in unit-based residential such as BTR, typically expressed per unit per month rather than per bed per week.
Does RevPAU include ancillary income like parking or amenity fees?
That depends on the operator's reporting convention. Some schemes calculate RevPAU on rent revenue only, in line with the hotel RevPAR convention; others build a fully loaded figure that includes ancillary income such as parking, storage, or amenity fees. As with any revenue metric, the important thing is applying the same treatment consistently period to period so comparisons remain meaningful.