Rate volatility has become a permanent fixture in development underwriting, not a temporary complication. We've watched deals that looked comfortably feasible at a 6% construction loan rate turn marginal the moment that same loan repriced 150 basis points higher during a delayed closing. Interest rate stress testing isn't a nice-to-have anymore; it's the difference between a feasibility model that holds up under scrutiny and one that quietly falls apart when conditions shift.
This isn't about running one downside case and calling it done. It's about building a model architecture that treats rate movement as a variable worth interrogating from multiple angles, because that's exactly how lenders, investment committees, and equity partners are already looking at deals.
Why Interest Rate Stress Testing Matters More Than It Used To
For most of the 2010s, base rates barely moved enough to change a deal's outcome. A feasibility analyst could run a single interest rate assumption, lock it into the pro forma, and move on. That approach doesn't survive contact with the current environment.
Construction loans are typically floating-rate, tied to SOFR or a local base rate plus a spread. Between loan commitment and construction completion, the base rate can move meaningfully, and unlike a fixed-rate permanent loan, there's no ceiling protecting the deal unless a rate cap has been purchased. A feasibility model that only reflects today's rate is really only telling part of the story.
Interest rate stress testing forces the model to answer a harder question: Does this deal still clear its return hurdles if rates move against us during the hold period? If the answer is no, that's information the sponsor needs before signing a loan commitment, not after.
Where Rate Sensitivity Actually Hits the Pro Forma
Rate movement doesn't touch a feasibility model in just one place. It ripples through several line items at once, and treating them separately can understate the real impact.
Construction interest. This is the obvious one. A 100-200 basis point swing on a drawn construction loan over an 18-24 month build changes carrying costs enough to move project margin by several points, depending on leverage and draw schedule.
Debt yield and refinance risk. Even if construction financing gets locked at a workable rate, the exit assumption on permanent debt often doesn't. Many deals get underwritten assuming a refinance at stabilization, and if rates are higher at that point than they were at underwriting, the achievable loan proceeds shrink sometimes enough to trigger a cash-in refinance the sponsor didn't budget for.
Exit cap rates. Cap rates and interest rates aren't perfectly correlated, but they move in the same general direction often enough that a rate stress test without a corresponding cap rate stress test tells an incomplete story. Modeling higher debt costs alongside stable exit cap rates tends to overstate feasibility.
Absorption and sales velocity. For-sale residential deals feel rate movement through buyer financing costs, not just sponsor financing costs. Higher mortgage rates slow absorption, which extends the hold period, which increases carrying costs a compounding effect that a static rate assumption misses entirely.
Building a Stress Testing Framework That Holds Up
A workable framework doesn't need to be complicated. It needs to be systematic enough that every deal gets the same rigor, regardless of how confident the team feels about the base case.
Start with a rate ladder, not a single scenario. Running base, +100bps, +200bps, and +300bps scenarios gives a committee something concrete to react to. Some teams also run a -100bps case, since understanding upside isn't purely academic when it comes to negotiating debt terms.
Separate construction-period rate risk from permanent-period rate risk. These have different hedging options and different implications. A rate cap addresses construction exposure; it does nothing for refinance risk at stabilization. Modeling them as one blended assumption hides which risk is actually driving the outcome.
Tie debt yield covenants to the stress case, not just the base case. Many construction and bridge loans include debt yield or DSCR covenants that get tested at various points in the deal. A model that only checks covenant compliance under the base rate assumption isn't actually stress testing anything it's just confirming what everyone already assumed.
Model the draw schedule realistically. Interest is charged on drawn balances, not committed amounts, so a construction loan stress test needs an accurate draw curve to mean anything. A flat-line assumption of full drawdown from day one will overstate interest costs early and understate them later, which throws off the timing of when covenant stress actually shows up.
Run the sensitivity on IRR and equity multiple, not just yield-on-cost. Yield-on-cost tells you about the asset. IRR and equity multiple tell you what the sponsor and investors actually experience, including the timing effects of a longer hold or a smaller refinance. Both matter, but committees increasingly want to see the investor-level number stressed, not just the project-level metric.
Where Analysts Tend to Get This Wrong
A few patterns show up repeatedly in feasibility work around rate risk.
The most common mistake is treating a rate cap as if it eliminates risk rather than limiting it. A cap protects against movement above the strike, but the premium cost and the strike level itself still need to flow through the model. Some analysts model the cap's existence without modeling its cost or its ceiling accurately.
Another recurring issue is stress testing rates in isolation from timeline risk. Rate increases and construction delays tend to show up together supply chain issues, permitting delays, and rate volatility often share the same macro backdrop. A model that stresses rate alone, holding the timeline constant, tends to be optimistic.
Static exit cap rate assumptions paired with dynamic rate stress testing is another gap worth watching for. If the model assumes rates rise but exit cap rates stay flat, that's an internal inconsistency that a sharp reviewer on an investment committee will catch quickly.
Workflow and Tooling Considerations
Manually rebuilding a pro forma for each rate scenario doesn't scale, especially across a portfolio of deals in different stages. Most teams handle this with a base model that has rate as a clearly isolated input, then use data tables or scenario managers in Excel to generate the ladder without duplicating the entire model structure.
This is one area where feasibility platforms have made a real difference in workflow speed. Tools like feasibilitypro.ai build sensitivity and scenario analysis directly into the model structure, which removes the need to maintain parallel spreadsheet versions for each stress case a common source of version-control errors when this is done manually. Other platforms in the space, including Deepblocks and Northspyre, take similar approaches to scenario management, though the depth of construction-period versus permanent-period rate modeling varies by tool. Teams using EstateMaster or Aprao for the core financial model sometimes layer a separate stress testing workbook on top, which works but adds a reconciliation step that's easy to skip under deadline pressure.
Whichever approach a team uses, the underlying discipline matters more than the tool. A rate stress test built into a single flexible model, updated consistently across the pipeline, tends to catch problems that a one-off spreadsheet exercise misses.
Bringing Rate Risk Into the Committee Conversation
The real value of interest rate stress testing shows up in how it changes the conversation with lenders and investment committees. A deal presented with a single rate assumption invites the question, "What if rates move?" A deal presented with a rate ladder already answers that question, and it tends to build more confidence in the sponsor's underwriting discipline than any single strong base case number could.
It also changes deal structuring conversations earlier. Knowing that a project fails its return hurdle at +200bps might push a sponsor toward purchasing a rate cap, negotiating a longer rate lock, or adjusting leverage before the loan is even committed decisions that are far easier to make during underwriting than after breaking ground.
What does the stress testing process look like on your deals how many rate scenarios do you typically run before taking a model to committee, and has that number changed over the past couple of years?
Top comments (0)