A real estate committee presentation works best when it answers one question before the committee can ask it: "Where did this number come from, and can I trust it?"
That question surfaces in different forms—a CFO asking about the revenue assumption, a board member questioning the trade area boundary, a CEO who remembers the last site that underperformed. Every version of it is asking the same thing: show me the reasoning, not just the answer.
This guide covers how to structure site analysis for committee review, what to include in the room versus the appendix, and how to handle the questions that derail otherwise strong recommendations.
What a Real Estate Committee Actually Needs
Before building your deck, understand what drives committee dynamics. Most real estate committees meet monthly. They review multiple sites in a single session. The members range from CFOs and CEOs who care about portfolio economics to operations and finance leads who want to know if the build cost pencils out.
A well-structured real estate committee presentation gives each of those people exactly what they need and does not waste the room's time with methodology that belongs in an appendix.
The core elements every committee expects:
- The recommendation, up front. Approve, decline, or defer — stated in the first thirty seconds. Everything that follows is evidence, not suspense.
- The site score and what drove it. If you use a scoring framework, the committee needs to see the key inputs, not just the output. Foot traffic ranking, trade area demographics, competitive density, and accessibility together explain a score. A number alone does not.
- A demand forecast with a range. Not a single point estimate. A projected revenue range with the variables that would move it up or down — that is what finance needs to model occupancy cost as a percentage of expected sales.
- Analog comparisons. Two or three existing portfolio locations with similar trade area profiles and their actual performance. This converts your model output into a track record.
- The cannibalization check. Any portfolio location within the trade area's draw radius, and the projected impact on existing revenue. Committees have been burned by new stores that looked great in isolation and undercut a top performer. Get ahead of it.
- The biggest risk. State the primary downside scenario clearly and explain why you believe the site still clears the hurdle.
If your analysis covers all six, you will walk out with a decision. If you skip cannibalization or present only a point estimate on revenue, expect the meeting to end with a list of follow-up items.
How to Structure the Deck
The structure that survives committee review the most consistently is the same one that works in any high-stakes decision context: recommendation first, evidence second, risk third.
Slide 1: Recommendation and rationale. Three to five sentences. The site name, market, your recommendation, and the one or two factors that drove it. If the score is high because trade area income is in the top quartile and cannibalization is zero, say that explicitly.
Slides 2–4: Site evidence. Score summary with the top-moving variables. Trade area map with the draw boundary and any existing portfolio locations marked. Foot traffic trend for the site if available.
Slide 5: Demand forecast. Revenue range (base and stress case), occupancy cost as a percentage of base-case revenue, and the forecast's primary assumption. Be specific about what has to be true for the base case to hold.
Slide 6: Analog comparisons. A table: analog location, trade area similarity score or characteristics, actual revenue at stabilization, and any notable differences from the proposed site. Three analogs is enough.
Slide 7: Risks and mitigations. The one or two scenarios where this site underperforms, and what you would do differently if those scenarios materialized. Showing that you have thought through the downside builds more confidence than presenting only upside.
Appendix: Full model output, raw foot traffic data, demographic tables, zoning confirmation, lease economics detail. Everything the committee can request but does not need to sit through.
How to Present a Site Score
A score is only useful to a committee if it connects to something they can evaluate. The five-lenses framework for site scoring gives each input a visible weight — but even with a transparent model, the committee needs you to translate the output.
The right framing is comparative: "This site scores in the 78th percentile of all locations we have evaluated. The two locations closest to it in score were [Market A] and [Market B]. Both are meeting revenue projections at 18 months."
That statement does three things: it establishes what the score means relative to your portfolio, it connects the model to outcomes, and it sets an expectation that you track forecast accuracy. That last point matters more than most teams realize.
Avoid presenting a score in isolation and then moving on. The committee will either not know what to do with it or challenge it. Give them the context to evaluate it themselves.
When the committee asks about the underlying data
"Where is that number from?" is one of the most common questions in a real estate committee presentation. Conducting a proper site audit before the committee meeting means you can answer it in detail — the data vintage, the source, how it compares to your internal records if you have them.
Committees that do not trust the underlying data will not approve the site regardless of the score. Knowing your data sources by name, not just category, is a non-trivial edge in the room.
The Cannibalization Conversation
Cannibalization kills otherwise strong approvals. The question is not whether a new location will pull some volume from nearby stores — it almost always will to some degree. The question is whether the net portfolio impact is positive.
A complete cannibalization analysis shows:
- Which existing locations are within the new site's trade area draw
- The projected traffic overlap percentage
- The estimated revenue transfer to the new location
- The net portfolio revenue impact
If the new location adds portfolio revenue after accounting for the transfer, say so explicitly. If it is roughly neutral but strategically necessary (defending a market from a competitor, securing a high-visibility anchor), make that case. What you cannot do is skip this slide. A committee member who sees a nearby portfolio store on the map and does not see cannibalization analysis in the deck will ask why.
Transparent site scoring makes this conversation easier because every variable is visible. When a committee member asks why the trade area boundary was drawn at a certain radius, you can show the methodology rather than defend a number that appeared from a model they cannot inspect.
Handling the Hard Questions
Real estate committee presentations are not just data reviews. They are career-risk assessments for the people in the room. The CFO's question about the revenue assumption is also a question about whether they can defend this to the board. The CEO's question about market timing is also a question about whether this team has thought through the macro.
A few patterns that help:
On revenue assumptions: State the assumption, trace it to an analog, and explain what would have to change to move it materially. "Our base case assumes AUV consistent with [Analog A and B]. If the trade area income proves softer than modeled — which could happen if the new development on Route 9 draws income cohorts away — we'd expect the low end of the range."
On model accuracy: If you have a track record to cite, use it. Showing that your previous committee approvals have come in at or above forecast changes the whole dynamic of the conversation. It converts methodology questions into performance questions, which are easier to answer.
On competitive risk: Name the competitors you have modeled, how close they are to the site, and what the traffic data shows about their draw relative to yours. Vague "competitive analysis" rarely satisfies a CFO. Specific competitor names, distances, and traffic comparisons do.
On questions you cannot answer in the room: Flag it and commit to a date. "That is from our platform's census layer — I'll confirm the vintage and get it to you by Thursday." Specificity about the follow-up builds more trust than a hedged answer that sounds like you are buying time.
Building Your Committee Approval Track Record
The most durable asset in real estate committee dynamics is a track record of accurate forecasts. Teams that submit performance follow-ups — actual revenue against projected revenue at 12 and 24 months — earn faster approvals and more latitude on close calls.
Most real estate teams do not do this. They approve the site, open the store, and move on to the next committee cycle without ever connecting the model to the outcome. That gap is exactly why so many committees remain skeptical of site scoring regardless of how good the methodology is.
A simple cadence: six to twelve months after a new location opens, bring a one-page note to the next available committee meeting. Site name, projected revenue range, actual revenue, and whether the key assumptions held. Three to four of these notes accumulates a performance record that shifts the committee from skeptics to advocates.
Connecting Analysis to Decision Speed
One underappreciated cost of a weak committee presentation is deal velocity. A presentation that leaves too many open questions generates follow-up loops that can push a site decision past the broker's offer window. Multi-site evaluation workflows that produce committee-ready outputs at the end of each screening cycle compress that cycle significantly.
The committee meeting is not the end of the site selection process — it is the output of it. If the analysis going into the meeting is thorough, the meeting itself should be short. If the meeting regularly runs long, that is a signal that the pre-committee analysis is leaving too many questions unanswered.
What Good Looks Like
The committee presentations that move fast share a few characteristics: the recommendation is clear before the second slide, every score connects to an analog outcome, the cannibalization analysis is present and quantified, and the presenter knows their data sources by name.
The ones that stall usually have the same problem: too much information without enough structure, or a recommendation buried under methodology the committee has to dig through to find.
The goal is to give every person in the room — the CFO, the CEO, the ops lead, the board observer — exactly what they need to say yes with confidence. That means doing the work before the meeting so the meeting itself can be a decision, not a discovery session.