September 19, 2026 · Tupll
How Real Estate Teams Can Build an Evidence Package for Investment Committee Approval
An investment committee does not approve sites. It approves arguments. The site you believe in only gets built if the evidence supporting it survives the room: the skeptical CFO, the board member who remembers the last underperformer, the operator who trusts nothing without a number behind it.
Most site recommendations fail that room not because the site is wrong but because the evidence is thin. Here is what a package that survives looks like.
The four layers of a defensible package
The market case. Why this market at all: demand composition, workforce and economic base, and how the market scores against the alternatives you rejected. Rankings beat adjectives. "Highest-scoring of eleven candidate markets on our weighted model" opens a very different conversation than "strong growth corridor."
The site case. Why this location within the market: a predicted performance score built from the variables that drive your operation, with the reasoning visible. The committee should be able to see which factors carried the weight and ask why. A number that cannot be interrogated is a number that gets discounted.
The network case. What this addition does to everything you already operate: cannibalization exposure, coverage gaps closed, portfolio-level revenue with and without the site. Committees increasingly ask this question; packages that answer it before it is asked read as rigorous.
The validation case. Why anyone should believe the model at all: how it was built, what it was trained on, and how its past predictions compared to actual outcomes. If a year-one look-back exists, lead with it. Nothing disarms skepticism like "here is what we predicted last time, and here is what happened."
Anticipate the three killer questions
Every committee eventually asks some version of these. Where did this number come from? What would have to be true for this to fail? What did we almost pick instead, and why didn't we?
Write the answers into the package before the meeting. The first is answered by transparent methodology. The second by scenario ranges rather than a single point estimate. The third by showing the scored alternatives, which demonstrates the recommendation was a selection, not a rationalization.
Form matters less than traceability
The deliverable itself can be simple: a scored shortlist, a market heat map, scenario forecasts, an executive summary. What makes it an evidence package rather than a pitch is traceability. Every claim connects to a source, every score connects to a method, every method connects to a validation. When a committee member pulls any thread, something solid should be on the other end.
Teams that operate this way discover a second-order benefit: approvals accelerate. Once a committee has seen the standard, and seen a prediction verified against reality, the debate shifts from "do we trust this?" to "which of these do we do first?" That is what evidence is for.