When stabilised projections look certain. Underwrite ranges and run sensitivity cases

Stabilised is a label, not a fact

Most hotel underwriting fails in a predictable way. The model is clean, the stabilised year is coherent, the exit looks rational, and everyone can repeat the same number in the investment committee. Then reality arrives. Demand, rate, and costs do not move in a single line. Stabilisation takes longer than planned, or it arrives in a different shape than assumed. The result is not just a miss versus budget. It is a miss versus value.

Owner-side underwriting is not about proving a base case. It is about proving the deal survives a range of plausible outcomes and still delivers acceptable owner cash outcomes.

If a stabilised projection looks certain, treat that as a warning sign. Certainty is usually the output of hidden assumptions, not the output of risk work.

First, define what “stabilised” means in this deal

“Stabilised” is often used as shorthand for “Year 3” or “Year 4”. That is not a definition. It is a calendar.

A definition has conditions. Owners should require the underwriting to state what must be true for the asset to be considered stabilised, in operational terms, not just in model terms. For example:

• Demand is no longer in a ramp shaped by launch effects, major repositioning, or temporary demand sources.

• Average Daily Rate (ADR) is supported by product-market fit, not by tactical discounting.

• Segment and channel mix are not in structural transition.

• Cost ratios reflect the service level actually required to hold the rate, not a temporary suppression of payroll or maintenance.

• Capital spending is not being deferred to “after stabilisation” while simultaneously claiming stabilised earnings.

This matters because valuation is usually anchored to a stabilised earnings proxy. In VALCLEF vocabulary, call that Stabilised Earnings for Valuation (SEV). SEV is not “whatever the model says in Year 3”. It is the earnings level you believe is maintainable under a stable operating pattern.

If SEV is not explicitly defined, the underwriting is not anchored. It is just a story.

Then, bridge SEV to the cash the owner actually receives

Many stabilised models feel safe because they stop at operating profit. Owners do not live at operating profit. Owners live at cash.

That is why SEV must be bridged to Owner Free Cash Flow (OFCF) at stabilisation. Owner Free Cash Flow (OFCF) is the cash that reaches the owner after the economic and contractual realities are applied. The exact definition will vary by structure, but the bridge must make the main leak points explicit:

• Management and franchise fees, including any non-obvious fee bases.

• Reserve for replacement (often framed as FF&E reserve) and whether it is funded, restricted, and actually used.

• Timing of owner capital expenditure that is essential to sustain the earnings level being claimed.

• Working capital realities, especially if the pro forma assumes perfect cash conversion.

• Any fixed owner costs that do not flex with occupancy (taxes, insurance, certain service contracts).

A stabilised year can look healthy at Gross Operating Profit (GOP) and still be fragile at OFCF. That fragility is exactly what refinancing and hold-period value will punish.

Replace point underwriting with range underwriting

A point estimate is not underwriting. It is a single bet.

Owners should underwrite ranges for the drivers that actually break hotel deals. This is not about building a complex model. It is about making uncertainty explicit, then checking whether the deal holds.

Start with a disciplined set of ranges:

Topline range

• Occupancy range anchored to demand volatility, not to a smooth ramp.

• ADR range anchored to price resistance, not to perpetual growth.

• Mix risk, especially if the base case requires a specific segment (group, corporate, wholesale) to behave perfectly.

• Channel cost exposure, because distribution cost can destroy margin even when RevPAR looks acceptable.

Profit conversion range

• Margin variability is not just “a percent of revenue”. It is a reflection of labour structure, service level, and operating model.

• Drop-through should be stated clearly. Drop-through to GOP and drop-through to OFCF are not the same thing. Owners should care about both.

Undistributed and non-operating pressure range

• Payroll rigidity and wage inflation.

• Utilities volatility and the ability (or inability) to pass it through rate.

• Insurance and property taxes, which can reprice sharply and are often under-assumed.

Owner cash items range

• Reserve contribution levels and the reality of CapEx need.

• Timing of capital works that are required to sustain the brand position or avoid degradation of rate.

• Any fees that behave like fixed charges in a downturn.

The output should be ranges for SEV and OFCF, not only ranges for RevPAR. RevPAR is an input. OFCF is the owner outcome.

Sensitivity is useful, but cases are what make it real

A sensitivity grid tells you what happens when one variable moves. It is helpful, but hotels rarely fail one variable at a time. Owners need a small set of internally consistent cases that represent operating realities.

A practical case set is usually enough:

• Demand shock case (occupancy-led)
  Occupancy falls and takes time to recover. Rate follows with a lag. This tests whether the cost base is truly flexible and whether OFCF remains positive after fees and reserve logic.

• Rate ceiling case (ADR underperforms)
  Occupancy holds reasonably, but ADR cannot be pushed to the base case. This is common when competitive supply, product quality, or brand positioning do not support the promised rate premium.

• Cost shock case (wage and utilities inflation)
  Topline is acceptable, but costs inflate faster than revenue. This tests the realism of margin assumptions and whether “stabilised margins” are earned or simply declared.

• Mix shift case (segment and channel reset)
  The hotel trades, but the mix changes. Group evaporates, or corporate demand does not return, or leisure replaces at different contribution quality. This is where many “stabilised” pro formas silently break.

• Stabilisation delay case (time risk)
  The earnings level is plausible, but it arrives later. This is often the most damaging case for equity because it compresses hold-period OFCF and pushes CapEx into the wrong years.

Each case should produce two outputs that owners can defend: the stabilised SEV in that case, and the OFCF profile that the owner actually experiences across the hold.

Tie ranges and cases to capital structure, not just value

Value is not the only constraint. Bankability is a separate test and it is sensitive to different mechanics.

Owners should translate each case into lender language:

• DSCR headroom under realistic debt service, not just under base case EBITDA.

• Debt yield reality, especially when replacement reserve is treated as a real economic drag.

• Covenant breakpoints and the time profile of risk, because timing is often the true killer, not the ultimate stabilised year.

This is where “stated but not funded” reserve assumptions become dangerous. If the model assumes a reserve line but the business cannot fund it without breaking covenants, the underwriting is not robust. It is aspirational.

Good underwriting shows where the pressure lands first: fees, reserve, CapEx, or debt service. Owners need that map before signing.

The owner outputs that should be non-negotiable

If you want this Insight to change behaviour, it needs a tight owner checklist. Owners should require the underwriting pack to include:

• A declared stabilisation definition. Conditions, not calendar.

• SEV range and OFCF range, with clear bridges between operating profit and owner cash.

• A small set of cases that describe real operating states, each translated into OFCF and covenant headroom.

• The top sensitivities ranked by impact on OFCF and on lender tests.

• Owner levers by category: price, structure, CapEx sequencing, contract economics, or time.

• Trigger points for post-close governance. What metric movement tells you which case is forming, and what decision follows.

This is how underwriting becomes a control tool. It stops being a spreadsheet you file away after closing.

Closure: robustness is what you are buying

A stabilised projection can be precise and still be wrong. Owners do not need more precision. Owners need more robustness.

Underwriting ranges and running sensitivity cases is not about pessimism. It is about avoiding false certainty, protecting equity, and aligning price and structure to the real risk surface of the asset.

If the deal only works in one stabilised story, it is not a base case. It is a fragile bet.