Last Room Value (LRV)
In hotel revenue management, last room value (LRV) is the minimum you should accept for your final available room on a date, set by what that room could earn from the best alternative booking rather than by any published rate.
It is the idea underneath length-of-stay pricing at large hotels, it is the cleanest way to think about a multi-night request that crosses your best night, and at 46 rooms the formal version is more precision than your forecast can support.
See how ampliphi prices for independent hotels
Get a free revenue audit · Book a demo
What is last room value?
An opportunity cost expressed as a threshold.
The question it answers is not what the room is worth in the abstract. It is what you give up by selling it to this booking rather than holding it for the next one. On a date forecast to finish half empty, the next booking is nobody, so the threshold is barely above the cost of servicing the room. On a date forecast to sell out at $290, the threshold is $290, because that is what you are turning away.
The same idea appears under other names. A hurdle rate is the threshold a booking must clear. A bid price is the same concept borrowed from airline revenue management. They differ in derivation and not in what they are for.
The reason it matters is multi-night stays. A single-night request on a date either clears the threshold for that date or it does not, which is a simple comparison. A three-night request spans three dates with three different thresholds, and the correct evaluation is the total the stay produces against the total of what those three rooms would otherwise earn.
That total framing is important and frequently got wrong. A booking that fails the threshold on one night can still be worth taking if it clears comfortably on the other two, because the nights it fills were going to be empty.
Resources: Displacement analysis · Length of stay · Demand forecasting
How last room value works in practice
You compare the stay against the sum of what those rooms would earn without it.
Worked example. A 46-room inn receives a three-night Friday to Sunday request at $165 a night, worth $495. Its forecasts say Friday finishes around 30 of 46, Saturday sells out at $235, and Sunday finishes around 22. Declining the booking means keeping the Saturday room for a one-night guest at $235 and leaving the Friday and Sunday rooms empty, so the alternative is worth $235. Accepting is worth $495, which is $260 better. Now change one input: if Friday were also forecast to sell out, at $210, and Saturday at $290, the alternative becomes $500 against the same $495, and the answer flips by five dollars.
Five dollars is the point of that example rather than an accident of it.
At a property where a single booking is over two percent of the house and a 30-day forecast can easily be four or five rooms out, a decision resolved by $5 is not a decision the arithmetic actually made. It was made by the forecast error. That is the honest limit of the technique at this scale.
What survives the scaling down is the habit. Before accepting any multi-night booking that crosses a date you know is strong, ask what that night alone would have earned, and whether the whole stay beats it. That question takes thirty seconds and catches the cases that are genuinely lopsided, which are the majority.
The cases it catches are worth catching. A four-night stay at a modest rate running through your single best Saturday of the year is the classic expensive acceptance, and it is usually accepted because four nights feels better than one.
Resources: Compression night · Dynamic pricing
Why last room value matters for independent hotels
Because the mistake it prevents is one small properties make repeatedly, and it is invisible afterwards.
A long stay booked at an ordinary rate across a peak date produces a full house, a decent total and no sign of a problem anywhere. The room nights you could not sell at $290 do not appear on any report, because they never existed. Only a forecast made in advance would have shown them.
The second reason is the direction of the instinct. Four nights confirmed feels safer than one night forecast, in the same way a confirmed group feels safer than transient demand. That instinct is right on soft dates and expensive on strong ones, and the threshold question is what separates them.
The honest framing is that this is enterprise machinery scaled down. Large hotels compute last room values continuously across every date and length of stay, as part of a system. A 46-room inn cannot do that and does not need to. What it needs is a list of its ten or fifteen strongest dates and the discipline to check any multi-night booking that touches one.
Resources: Revenue management for independent hotels
How to use last room value at your property
- Name your ten to fifteen strongest dates a year. Those are the only ones where the threshold matters.
- Estimate what the last room earns on each, from your own history of what those dates achieved.
- Evaluate multi-night requests as a total, not night by night. A booking failing one night can still be worth taking.
- Compare against the sum of the alternatives, counting empty nights as zero rather than as your published rate.
- Treat close calls as ties. If the arithmetic resolves within a few percent, your forecast error decided it, not the method.
- Record what you accepted and what the date finished at. It is the only way your thresholds get better.
What last room value will not tell you
It is entirely dependent on the forecast, and it inherits every weakness of one. A threshold built on an expectation that is four rooms out is a threshold that is wrong by whatever those four rooms were worth.
It offers false precision at small room counts. A method producing an answer to the dollar, applied to a business where one booking moves occupancy by two points, invites more confidence than the inputs justify.
And it counts only rooms. A long stay bringing meaningful food and beverage, or a guest who returns annually, is worth more than the room arithmetic shows, and there is no term in the calculation for either.
How ampliphi approaches last room value
Ampliphi does not compute last room values and does not price by length of stay. The everyday rate suggestion is demand-based, built on booking pace and occupancy, and it covers your base rate and the differential between room types.
That means the suggestion is per date rather than per stay pattern. A three-night booking crossing a strong Saturday pays the suggested rate for each of those nights, and the threshold question above remains a judgment you make rather than a rule the system enforces. Length-of-stay pricing and hurdle rates are a separate discipline with their own maintenance burden, and they are not what this does.
Where the two connect is the input to your judgment. Knowing whether a Saturday is tracking toward a sellout is exactly what the demand-based assessment is watching continuously, and that is the fact the threshold question depends on. You approve every rate before it publishes, and ampliphi runs on top of the PMS you already use.
Key takeaways: last room value
- The minimum worth accepting for your final available room, set by what the next best booking would pay.
- An opportunity cost threshold, not a price. Also called a hurdle rate or a bid price.
- It exists mainly to evaluate multi-night stays that cross a strong date.
- Evaluate the whole stay against the sum of the alternatives, counting empty nights as zero.
- Close calls are ties. At 46 rooms the forecast error is larger than a narrow margin.
- The mistake it prevents is a long modest stay running through your single best night of the year.
Frequently asked questions about last room value
What is the difference between last room value and displacement analysis?
Scale and subject. Displacement analysis usually means a group block. Last room value is the same logic applied to an individual booking, typically a multi-night one.
Both ask the same question: does this business earn more than what it pushes out. Both depend entirely on a forecast for the dates concerned. Both count empty nights as worth nothing rather than as worth your published rate.
The practical difference is that a group enquiry arrives with someone waiting for an answer and a displacement calculation is expected, while a three-night transient booking arrives silently through your booking engine and nobody evaluates it at all.
Is last room value the same as a hurdle rate?
In everyday use, yes. The terms are close enough that the distinction rarely matters outside a textbook.
A hurdle rate is the threshold a booking must clear to be accepted. Last room value is the opportunity cost that sets where that threshold sits. Bid price is the same idea again, borrowed from airline revenue management, where it refers to the value of the marginal seat.
All three describe the same decision: whether this booking is worth more than holding the inventory for something better.
Can a small hotel use last room value?
The concept yes, the formal implementation no.
Computing thresholds continuously across every date and stay length requires a system, a forecast with tight error bars and volumes that make the statistics meaningful. A 46-room property has none of those, and a method whose answer flips on a five-dollar margin is not giving you a decision at that scale.
The usable version is a named list of your strongest dates, a rough sense of what the last room earns on each, and a thirty-second check before accepting any multi-night booking that crosses one. That catches the lopsided cases, which are where the money is.
Should I refuse a long stay that covers my best night?
Only if the whole stay earns less than the alternative, which is less often than it feels.
Run the total. Three nights at $165 is $495. If the Friday and Sunday were going to be empty and only the Saturday would have sold at $235, accepting is clearly right, and refusing costs you $260 to protect a night you would have sold anyway.
The refusal case is when several of the nights were going to sell well. Two strong nights at $210 and $290 against a $495 three-night booking is genuinely marginal, and that is exactly the situation where the relationship, the guest and the operational picture should decide it rather than a number that close.
How do I estimate last room value without a system?
From your own history of what those dates achieved, not from a formula.
Take your ten or fifteen strongest dates. For each, look at what the final rooms actually sold for in previous years and how early the date sold out. A date that consistently sells out a week ahead at $280 has a last room value near $280. A date that limps to 80 percent has one near zero.
That is coarse, and coarse is adequate here. You are trying to separate the clearly-accept from the clearly-refuse, and the cases in between should not be decided by a number you estimated anyway.
Related terms
Displacement analysis
Whether accepting business earns more than what it pushes out. The same logic applied to group blocks rather than individual stays.
Demand forecasting
Predicting how a date will finish. Last room value is derived from it entirely, and is only as good as it is.
Length of stay
The nights per reservation. Last room value is the mechanism behind length-of-stay pricing at larger hotels.
Compression night
A date where market demand exceeds supply. Where thresholds are highest and a modest long stay costs the most.
Revenue management system
Software that decides what the rate should be. Enterprise products compute these thresholds continuously, which is what makes formal last room value practical at scale.