When a project could go in more than one place, the comparison is where the decision quietly gets made. Set it up carelessly and it picks the winner before the sites are even scored. Here is how an honest comparison works, and when a lead is stable enough to act on.
Most site comparisons look objective and are not. Each candidate gets scored on slightly different assumptions, the numbers that flatter the preferred location are the ones that make it into the table, and the site someone already wanted comes out ahead. The math is real; the setup decided the answer. The first job of an honest comparison is to take that freedom away from whoever built the spreadsheet.
The fix is to hold everything constant except the location. We re-solve the same project at each candidate site, pull the same public data for each region, and run each one through the same method gates. When the inputs are identical, the differences that remain describe the sites rather than the analyst. That is the only way a ranking means what it appears to mean.
A comparison will almost always produce a leader. The question that matters is whether that lead would survive being questioned. Margins are often thin, and a small, defensible change in an assumption can move a different site to the top. Before we call anything a recommendation, we measure how stable the ranking is across the range the inputs could plausibly take. A lead that only holds under one exact set of numbers is a provisional leader, and we label it that way.
When a ranking is close, the flip condition is worth more than the ranking. It states exactly what would have to change for another site to win: a shift in the capture rate, a different labor assumption, a housing constraint that turns out to be real. That tells a sponsor where the decision is fragile and which one or two things are worth verifying before money moves, instead of paying for full diligence on every site at once.
It is tempting to pick the site with the largest headline impact. A large impact number describes activity, and the right site is the one where the project also pencils, the region can absorb it, and the recommendation holds up when a lender or a council pushes on it. A comparison that leads with the biggest number, and stops there, is answering an easier question than the one being asked.
Site comparison is sharpest along a corridor, where candidate locations share a market and a road. A project weighing towns along US Highway 97, from the Mount Shasta gateway up to the Columbia, is a natural comparison: the same project, several real sites, one connected region. That is what a corridor study does, and it withholds a selected site until the ranking is stable enough to name one.
Weighing more than one site? Tell us the project and the candidate locations, and we will compare them on the same evidence and show you where the lead is solid and where it is still too close to call.
Start a conversation