What’s really in the building? Site assessments for multi-site expansion

Your real estate team is three weeks from signing a lease. The opening date is already in the board deck.

You didn’t pick the site and you didn’t set the date. But you’re the one who has to know whether the space can actually deliver on the program. And the drawings you’d normally rely on either don’t exist or can’t be trusted to be accurate. So how do you assess the siteʼs viability?

To answer that, you need real answers to basic questions. What’s the electrical service size? Will the existing HVAC carry the new load? What shape is the roof actually in?

It used to be a retailer would pick a market, walk a handful of sites, run feasibility, then scan. The deal team was the one setting the pace. But these days you don’t get one site at a time. You get fifty maybes, each needing a go/no-go. And real estate and store planning teams don’t have the people to get an engineer, an MEP lead and a roofer out to all of them.

That’s why the market has moved toward accurate, digitized site assessments

Where most site assessments fall short

Existing condition surveys and property assessments are supposed to give expansion teams a baseline for a fast go/no-go. But in reality a lot of them donʼt. Common patterns:

• Partial site data. The survey is built to answer one person’s question. It wasn’t scoped with the rest of the team or adjacent stakeholders in mind. So they can’t use it, and you end up paying to send someone back out later.
• Lack of trust. Everyone is forced to re-verify everyone elseʼs work to protect themselves, because they donʼt have data they can trust.
• Guessing what the building has. Checking the actual electrical service takes an engineer visit or a records request from the utility. Thatʼs really hard to do across 50 candidate sites, so the early go/no-go decisions tend to run on broker packages, or on assumptions around what a building like this usually has vs. the actual truth.

A week waiting on feasibility data is a week of leverage you lose negotiating. On one site itʼs annoying. Across a portfolio of fifty candidate sites a year, it becomes a pretty big deal.

The good news is none of this is a tech problem. It comes down to how the assessment is scoped and whoʼs doing it.

The right team, the right data, at the right time

What changes the equation is a team that knows what each stakeholder needs before it walks the site, and captures it once.

We call this reality capture (not scanning) for a reason. A scan gives you geometry, which is useful for the architect but useless to the engineer. Reality capture also includes decision data – it documents the existing electrical, HVAC, roof condition, MEP. Which makes it useful both for go/no-go and for the design team later. And because it all lives in one place, the architect, engineer and GC are working from the same current picture of the building.

That’s where trust comes from: the right team providing the right data at the right time. People stop waiting on each other and stop re-verifying each other’s work. And with trust comes speed.

It shows up (at least) three places:

1. Communication. When you ask a question, you get an answer the same day. Thereʼs no longer a silo between the team that captured the building and the team that is designing inside it. And you donʼt get fifty follow-up questions.
2. Delivery. Youʼre able to do a single site visit and get the full capture. The architect and engineer and GC are all able to pull from one data set in parallel. So handoffs that used to take weeks now are delivered on the date promised.
3. Information. Different team members need different views of the building. That same capture can be delivered to people in the format that works best for them. So the exec making a decision at the portfolio level might get a one-link walkthrough, while an operations lead might get a 2D floorplan in Bluebeam.

What this looks like in practice

We were recently working with a national retail operator evaluating an existing big-box location for conversion. The lease was close to signed. But during the capture walk, a ceiling tile looked off. Our team popped it and found black mold, which came from a roof leak above a section of the building the landlord hadn’t disclosed.

Landlords rarely let anyone up there (nobody wants the liability of a stranger walking their roof), so this wasnʼt unusual. But it means deals routinely move forward without anyone really knowing the situation. We flew drones up there, and the drone pass confirmed that the roof above that lease was failing.

The finding didn’t kill the deal. But the owner was able to go back with documented condition data and renegotiated the terms.

The capture was also useful after the fact. The same dataset fed the architect’s existing-conditions model and the engineer’s MEP baseline. They didnʼt have to do another site visit. The design team used the same capture data which allowed them to start the following week.

If you have a site in the pipeline

The fastest way to evaluate this is on a real building. Send us one candidate site and we’ll capture it: one visit, full existing conditions, delivered in the formats your team already uses. You can reach out and weʼll be happy to chat with you about this.

If you’d rather see before you commit, ask for a sample deliverable from a comparable project and judge the output directly.