Guide
Real Estate Sensitivity Analysis Explained
Real estate sensitivity analysis measures how much a deal's return metrics — IRR, equity multiple, cash-on-cash, DSCR — change when you flex one or two key assumptions, such as exit cap rate or rent growth, while holding everything else constant. It answers the question that a single base-case pro forma cannot: how wrong can I be about my biggest assumptions before this deal stops working? The output is a sensitivity grid (data table) that maps return outcomes across a range of inputs so you can see the deal's breakeven points and downside exposure at a glance.
What sensitivity analysis is (and how it differs from scenario analysis)
Sensitivity analysis isolates the effect of a single variable — or two variables in a grid — by moving it across a defined range while every other assumption stays fixed. It tells you the marginal impact of being wrong about one input. That isolation is the point: if you flex ten things at once you cannot tell which one broke the deal. Scenario analysis, by contrast, bundles several correlated assumptions into named cases (base, downside, recession) that move together — for example, a downside case where rents soften, vacancy rises, and exit cap expands simultaneously. Monte Carlo simulation goes further, drawing thousands of random combinations from probability distributions. All three are complementary. Sensitivity analysis is the diagnostic that tells you which variables even deserve a scenario or a distribution.
- •Sensitivity: one or two variables flexed independently — isolates marginal impact
- •Scenario: several linked assumptions moved together as a named case
- •Monte Carlo: thousands of randomized draws producing a probability distribution of outcomes
The variables that actually move CRE returns
Not all inputs matter equally. In most value-add and core-plus deals, a short list of assumptions drives the overwhelming majority of return variance, and those are the ones worth gridding. Exit cap rate is almost always the single most powerful lever on IRR and equity multiple because it capitalizes stabilized NOI into a terminal value that often represents the largest cash flow in the entire hold. A 50-basis-point move in exit cap can swing IRR by several hundred basis points. Rent growth and stabilized occupancy drive NOI, which compounds through both interim cash flow and the exit. On the financing side, interest rate and loan proceeds (via LTV/LTC and DSCR/debt-yield constraints) reshape levered returns and can trip covenants. Entry price, renovation cost and timeline, and hold period round out the list. Operating-expense inflation and exit selling costs matter but are usually second-order.
- •Exit cap rate — typically the highest-impact driver of IRR and equity multiple
- •Rent growth and stabilized occupancy — compound into both interim NOI and exit value
- •Interest rate and loan proceeds — reshape levered returns and can breach DSCR/debt-yield covenants
- •Entry price / going-in basis — sets the denominator for every return
- •CapEx budget and renovation timeline — delays push out stabilization and lease-up
- •Hold period — interacts with cap-rate cycle timing and cost of capital
How to read a two-variable sensitivity grid
A two-variable sensitivity table (in Excel, a Data Table) puts one variable across the columns and a second down the rows, with the chosen output metric — say levered IRR — in each cell at the intersection. The center cell is your base case; everything around it shows how the metric responds as the two drivers move. Read it in three passes. First, find your base case and confirm it matches your headline pro forma number. Second, read across and down to gauge slope: if IRR collapses quickly as you move a few columns to the right, that variable is a major risk; if the row is nearly flat, the deal is insensitive to it. Third, trace the isocurve — the diagonal band where the metric crosses a decision threshold such as your hurdle rate, a 1.25x DSCR floor, or breakeven. That band is your margin of safety. A grid where the base case sits near a red threshold, with the failure zone only one or two increments away, signals a deal that leaves no room for error. Color-scale (heatmap) shading makes those cliffs obvious at a glance.
- •Columns = variable A, rows = variable B, cell = the output metric at that intersection
- •Center cell should reconcile exactly to your base-case pro forma
- •Steep gradient across a row/column = high sensitivity; flat = low sensitivity
- •The threshold band (hurdle, DSCR, breakeven) shows how much room the deal has before it fails
Turning the grid into a decision
A sensitivity grid is a risk-communication tool, not just a math exercise. The goal is to translate it into thresholds an investment committee can act on. Identify the breakeven value of each key driver — the exit cap at which IRR hits the LP hurdle, the interest rate at which DSCR falls to the loan covenant, the rent growth needed to clear promote. Then compare those breakevens to what the market is actually pricing and to the historical range of the variable. The crucial discipline is honesty about the base case. If you have to assume exit cap compression (selling at a lower cap than you bought) or above-trend rent growth just to reach target returns, the grid will expose it as a deal that only works in the optimistic corner. Institutional underwriting convention is to expand the exit cap 25-50 bps above the going-in cap and to test rent growth at or below submarket trend, then confirm the deal still clears hurdles. A deal that survives a conservative grid is far more defensible in an IC memo than one that requires the tailwinds to break your way.
Doing this in Origentic
Origentic runs scenarios plus two-variable sensitivity on the same deterministic calc engine that produces your base-case underwriting, so the grid and the pro forma always reconcile — every cell traces back to the same verified math rather than a separately maintained spreadsheet. You can flex drivers like exit cap rate, rent growth, interest rate, and loan proceeds across the full model — including the GP/LP equity waterfall and debt-sizing constraints — and export the resulting grid into a white-label branded IC memo. Because the engine is deterministic and tested against a frozen vector suite, the sensitivity outputs are reproducible: the same inputs always return the same numbers, which is what an investment committee needs when it stress-tests your assumptions live. Origentic is free to start; paid plans are flat-priced from $89/month.
Step by step
- 1
Lock a clean base case
Build and verify your base-case pro forma first. Every number should tie out and have a source, because the center of your sensitivity grid must reconcile exactly to your headline IRR, equity multiple, and DSCR.
- 2
Pick the output metric
Choose the return or coverage metric the grid will report — typically levered IRR or equity multiple for equity investors, or DSCR / debt yield when the question is loan sizing and covenant risk.
- 3
Select the two highest-impact drivers
For most CRE deals, pair exit cap rate with one NOI driver (rent growth or stabilized occupancy) or with entry price. These two axes usually explain the majority of return variance.
- 4
Define realistic ranges and increments
Set ranges around the base case using market evidence, not symmetric guesses. Convention is to test exit cap 25-50 bps above going-in and rent growth at or below submarket trend, in even increments (e.g., 25 bps caps, 50 bps growth).
- 5
Build the grid
Put variable A across the columns and variable B down the rows, with the output metric recomputing in each cell (an Excel Data Table, or the built-in two-variable sensitivity in a purpose-built engine). Confirm the center cell equals your base case.
- 6
Apply threshold shading and find breakevens
Color-scale the grid and mark the band where the metric crosses each decision threshold — LP hurdle, 1.25x DSCR, breakeven. Identify the value of each driver at which the deal fails.
- 7
Measure the margin of safety
Count how many increments separate your base case from the failure zone. A deal that only works in the optimistic corner — requiring cap compression or above-trend growth — is flagged here, before the IC does it for you.
- 8
Document it in the IC memo
Carry the grid and its breakevens into the investment-committee memo so reviewers can see the downside quantitatively, and note which assumptions the deal is most exposed to.
Frequently asked questions
- What is the difference between sensitivity analysis and scenario analysis?
- Sensitivity analysis flexes one or two variables independently while holding everything else constant, isolating the marginal impact of each. Scenario analysis moves several correlated assumptions together as a named case (base, downside, recession). Sensitivity tells you which variables matter; scenarios tell you what a coherent bad outcome looks like.
- Which variable has the biggest impact on IRR in a real estate deal?
- For most hold periods, the exit cap rate is the single most powerful driver because it capitalizes stabilized NOI into a terminal value that is usually the largest cash flow in the deal. A 25-50 bps change in exit cap can move IRR by several hundred basis points, which is why it belongs on nearly every sensitivity grid.
- How do you read a two-variable sensitivity table?
- One variable runs across the columns, a second down the rows, and each cell shows the output metric (e.g., IRR) at that intersection, with the base case in the center. Read the slope across rows and columns to see sensitivity, then find the diagonal band where the metric crosses a threshold like your hurdle rate or DSCR floor — that band is your margin of safety.
- What ranges should I use for a sensitivity analysis?
- Anchor ranges to market evidence, not symmetric guesses. Institutional convention is to expand the exit cap 25-50 bps above your going-in cap and to test rent growth at or below submarket trend, then confirm the deal still clears its hurdles. If it only works in the optimistic corner, that is a finding, not a range to widen.
Keep exploring