RevPAR and your maintenance backlog: a number every operator should know
RevPAR is the standard measure of hotel room revenue. Maintenance backlogs eat into it in ways that rarely get quantified. Here's how to connect the two.
RevPAR — Revenue Per Available Room — is the metric that revenue managers live by. It combines occupancy and average daily rate into a single number that represents how efficiently the property is converting its available capacity into revenue. A RevPAR of £120 means the property is generating £120 of room revenue per night for every room in the building, whether or not it's occupied.
Most hotels track RevPAR carefully. Very few formally connect it to the maintenance backlog.
That disconnection is expensive.
What RevPAR actually measures
The formula is simple: RevPAR = Average Daily Rate × Occupancy Rate. Or equivalently: RevPAR = Total Room Revenue ÷ Total Available Room Nights.
A hotel with 100 rooms, an average rate of £160 and 75% occupancy generates a RevPAR of £120. The same hotel with the same rate but two rooms permanently blocked for maintenance has 98 effective available rooms — and every night those rooms are blocked, they contribute nothing to revenue while still counting as available capacity in the denominator.
England's average hotel RevPAR was £117 in April 2026. For urban properties in major cities, it runs considerably higher. For a premium London hotel at £300 RevPAR, a room blocked for a month is £9,000 in foregone revenue. That's one room. One month. One blocked repair.
How maintenance backlogs suppress RevPAR
The most visible connection between maintenance and RevPAR is the formally blocked room. A room taken out of service because of a broken piece of FF&E doesn't generate room revenue. That's straightforward to quantify.
The less visible connection is the sub-standard room that stays in service. A room with a broken lamp reported by a guest, a chair with visible wear, a headboard that's been waiting on a replacement for three months — these rooms generate revenue, but at lower ratings scores. And lower ratings scores suppress future occupancy and rate.
Cornell research found that a one-point improvement in a hotel's reputation score is associated with a 1.42% increase in RevPAR. The inverse applies: a room operating consistently below the standard that guests expect pulls review scores down, which pulls RevPAR down, often long after the specific issue has been fixed.
This means the maintenance backlog has both a direct RevPAR cost (rooms offline) and an indirect RevPAR cost (rooms online but underperforming). The indirect cost is harder to measure but likely larger in aggregate.
The backlog as a number
Most hotels have some version of a maintenance job list. What most don't have is a view of that list with revenue impact attached.
A simple calculation changes that. For each open item on the maintenance backlog:
- Identify the room number.
- Estimate the number of nights the item has been, or will be, affecting room performance (either formally blocked or operating below standard).
- Multiply by the room's RevPAR contribution (a blended figure using the room type's average rate and the property's average occupancy).
That gives you a rough floor for the revenue cost of each outstanding item. It's not a precise number — there are too many variables for precision — but it's directionally accurate enough to be useful for prioritisation.
A room blocked for a total of 30 nights at £117 RevPAR costs roughly £3,500. A room that's been sub-standard for 60 nights doesn't directly block revenue, but if it's contributed to three negative reviews at an average of 200 future impressions each, the rate suppression compounds over months rather than weeks. Neither of these costs appear in any maintenance cost ledger — they're invisible revenue that was never earned.
Why this number doesn't exist in most hotels
Revenue management and facilities management operate as separate functions with separate systems, separate KPIs and separate reporting lines. Revenue managers track occupancy and rate; facilities managers track work orders and completion times. Nobody is running the joined-up number that shows each outstanding maintenance item with its revenue cost attached.
This isn't a structural problem that requires a major technology investment to fix. The data exists — room numbers, job descriptions, completion dates — it's just not combined with revenue data in a useful form. The minimum viable version is a shared spreadsheet that links open jobs to rooms and estimates the revenue cost of each. The more sophisticated version links the maintenance ticket directly to the room's revenue performance, so the cost of delay is visible at the moment the decision to delay is made.
The second version is what changes behaviour. When a facilities manager sees that a postponed repair costs £400 a week in RevPAR terms, the prioritisation calculus changes. When that number is invisible, the repair competes with all other outstanding jobs on equal terms, regardless of its revenue impact.
What changes when the number is visible
Hotels where maintenance impact is expressed in revenue terms tend to make different decisions about prioritisation and speed. The repair that "isn't urgent" looks different when it has a weekly cost attached. The supplier who quotes a 12-week lead time on a replacement is a different conversation when 12 weeks at £117 RevPAR represents a £11,000+ conversation.
This is part of why we built the revenue impact view directly into Controlbook's replacement workflow. When a fault is reported and a spec is identified, the platform shows the current revenue cost of the room being offline — not as an afterthought, but as part of the decision context. See the platform page for how the full workflow functions, or book a demo to see it on your own data.
Frequently asked questions
Should I use RevPAR or average daily rate for the maintenance cost calculation?
RevPAR is the more accurate figure because it accounts for actual occupancy — the revenue you'd realistically earn on that room type at your current occupancy rate — rather than the theoretical maximum. Using RevPAR gives you a conservative floor; using ADR at 100% occupancy gives you the theoretical ceiling. The realistic cost sits somewhere between the two, but RevPAR is the more defensible number for budgeting purposes.
How does room category affect the calculation?
Significantly. A suite at £400+ per night has a higher revenue cost per night offline than a standard room at £120. When prioritising a maintenance backlog, the revenue cost per room type should be one input alongside the urgency of the repair and the complexity of the replacement. A minor item in a premium suite may warrant faster action than a more significant item in a lower-rate room, purely on revenue impact grounds.
Can we use this approach to justify capital investment in better FF&E records?
Yes, and this is often the most compelling way to present the business case. If improving your FF&E records reduces the average replacement lead time by three weeks — a conservative assumption once spec data is immediately accessible — and you have a property that manages 30 replacements a year across 200 rooms, the revenue recovery from faster replacements can be quantified against the platform cost. The numbers are usually favourable at RevPAR levels above £80.