Before a single building tour is scheduled, the most consequential work in any site-selection engagement happens on paper — or more precisely, in a structured conversation between an adviser and the client that forces every stakeholder to say out loud what they truly cannot live without.
Why Requirements Discipline Saves More Time Than Any Search Tool
Poorly defined requirements are the single most common reason a site-selection engagement stretches past its natural timeline. When a team arrives at the shortlisting stage without consensus on what is non-negotiable, every new option reopens the same debates. Tours become deliberations. Shortlists become long lists. Landlords and sellers grow skeptical of a buyer who keeps changing direction.
The discipline of separating must-haves from nice-to-haves is not simply a documentation exercise. It is a decision-forcing mechanism that makes every downstream step — scoring properties, structuring proposals, negotiating terms — faster and more defensible. When an occupier's leadership team can point to a written rationale for why a building passed or failed, internal approvals move more quickly.
Requirements discipline also protects the adviser's credibility. A broker who presents options that miss a stated non-negotiable is perceived as not listening, regardless of how good the deal terms are. Getting the requirements right at the outset is therefore both a service quality issue and a relationship management issue.
The Cognitive Trap That Blurs Every Requirements Conversation
When clients are asked what they need in a space, the natural response is to describe what they currently have. This is a well-documented cognitive pattern: people anchor on the familiar and frame requirements as features of the status quo. A client who has a 15,000 square foot floor plate today will often ask for a 15,000 square foot floor plate tomorrow, even if headcount projections suggest 11,000 square feet would suffice.
The adviser's job is to surface the underlying business problem rather than accept the stated specification at face value. If a team says they need a training room, the right question is what activity they are trying to support and how often. The answer might reveal that a flexible open area and a bookable meeting room would serve the purpose better than a dedicated room that sits empty four days a week.
This distinction between the stated requirement and the underlying need is the foundation of effective requirements analysis. Without it, the brief becomes a transcript of the client's current lease, not a specification for their future workplace. Getting to underlying needs usually requires more than one conversation and more than one set of stakeholders.
Structuring the Discovery Session
A structured discovery session is the most reliable method for drawing out requirements before a search begins. The session should include at least the operational lead (the person who will use the space day-to-day), the finance lead (the person who will approve the budget), and an executive sponsor who can arbitrate when the two disagree. Trying to run requirements discovery with only one of these voices produces an incomplete picture.
The session should open with a constraint framing exercise: what would make you reject a property outright, regardless of its other qualities? These rejection criteria are, by definition, your must-haves stated in reverse. A team that cannot articulate any hard rejections has not yet done the requirements work — they have only listed preferences.
After the rejection framing, move to a scenario exercise. Describe two hypothetical spaces: one that meets every stated requirement at a hypothetical rent of, say, $40 per square foot (illustrative), and one that meets 80% of requirements at $30 per square foot (illustrative). If the client is comfortable with the lower-cost option, some of that 20% is demonstrably nice-to-have. If they are not comfortable, those requirements need to be re-examined and re-categorized.
The discovery session should conclude with a written output — a brief that separates requirements into at least two tiers. The first tier contains hard constraints that eliminate properties. The second tier contains preferences that influence scoring but do not veto. Without a written brief, the conversation has produced alignment that will dissolve the moment a compelling property appears that stretches one of the stated constraints.
Building a Two-Tier Requirements Framework
The two-tier framework is the workhorse of serious site-selection practice. The first tier covers items that are operationally or legally non-negotiable: minimum and maximum square footage, specific geographic zone requirements, power capacity for data-intensive operations, ADA compliance, loading dock requirements for distribution, or lease term constraints driven by a business plan horizon. No amount of price reduction should move a first-tier item to a negotiating chip.
The second tier covers preferences that have real business value but can be traded against cost or availability. Ceiling height above a minimum threshold, proximity to a preferred transit line, specific amenity configurations, a certain number of parking spaces beyond a base requirement — these are items that a team would like to have and that influence scoring, but whose absence does not eliminate a building from consideration.
A third informal tier is worth acknowledging: the aspirational list. These are features that a stakeholder mentions once and would be delighted to find, but which no one expects the market to deliver. Putting them in writing prevents them from quietly migrating upward in priority mid-search when a building happens to have them. An adviser who lets aspirational items become scoring criteria mid-process has effectively changed the brief without a client conversation.
Categorizing requirements also requires explicit agreement on who has authority to reclassify them. If a CFO can unilaterally upgrade a nice-to-have to a must-have during a building tour, the framework collapses. Governance over the brief is as important as the brief itself.
Quantifying Requirements to Make Them Actionable
A requirement stated as a preference is almost impossible to evaluate objectively. "Good natural light" means something different to an architect than it does to an accountant. Converting preferences into measurable criteria is the step that transforms a qualitative wish list into an operational scoring tool.
For each second-tier requirement, define a minimum acceptable level and an ideal level. Parking, for example, might have a minimum of one space per 500 square feet (illustrative) and an ideal of one per 300 square feet. Any property below the minimum is treated as a first-tier failure. Any property between the minimum and the ideal scores on a gradient. This turns a binary yes/no preference into a continuous scoring variable that supports comparative analysis.
Quantification also forces stakeholders to reveal implicit priorities. When a client says they need "good transit access," asking them to define a maximum walking distance from the nearest subway entrance — five minutes? ten minutes? — reveals whether they are describing a hard operational requirement or a preference. If no one can agree on a number, the requirement is probably aspirational rather than functional.
A weighted scoring matrix built from these quantified criteria is the deliverable that ties the discovery session to the market search. Each property in the eventual longlist is scored against every second-tier criterion. The resulting scores allow the team to compare options on a common basis rather than debating impressions after a tour.
Geographic and Location Requirements
Geographic requirements deserve their own analytical treatment because they interact with almost every other requirement in the brief. A specified submarket often constrains the available building stock more than any physical specification, so it is worth testing whether geographic preferences are truly must-haves or whether they are proxies for something else.
A client who insists on a downtown central business district location is often expressing a need for talent access, transit connectivity, or brand presence. Each of these underlying needs can be evaluated independently. If the talent pool extends into an adjacent submarket, and transit connections are equally strong there, the geographic preference may be a nice-to-have that is constraining the search unnecessarily.
Commute shed analysis is a useful tool here. By mapping the residential addresses of a client's current workforce against transit networks, an adviser can identify which submarkets fall within an acceptable commute range for the majority of employees. This converts a subjective geographic preference into a data-supported constraint that the client can examine and either confirm or revise.
Proximity to clients, suppliers, or strategic partners is a different kind of geographic requirement — one that is more likely to be a genuine must-have. A law firm that needs to be within walking distance of a courthouse has a verifiable operational need. That kind of requirement should be mapped and confirmed before the search begins, not debated after a shortlist is produced.
Handling Conflicting Requirements Within a Team
Requirements conflicts are almost inevitable in organizations with multiple departments, and the adviser who does not surface them before the search begins will encounter them during tours or, worse, at the letter of intent stage. A common pattern is a tension between the HR team's preference for a highly amenitized space and the finance team's budget ceiling. Both requirements are legitimate; they cannot both be satisfied at the same time in every market.
The recommended approach is to surface the conflict explicitly during the discovery session and ask the executive sponsor to make a priority call. The question is not which team is right, but which constraint is harder. If the budget ceiling is set by a board-approved cost plan, it is likely a first-tier constraint. If the amenity preference is driven by a recruitment narrative, it is likely a second-tier preference that should be weighted in scoring but not treated as a veto.
Documenting the conflict and the resolution is as important as the resolution itself. When a building is eventually presented that meets the budget but falls short on amenities, the adviser can refer back to the agreed priority rather than re-litigating the debate from scratch. This is what separates a managed search process from an ad hoc one.
Internal conflicts also arise over headcount projections. Operations teams often plan conservatively; HR teams often plan optimistically. The adviser should document the range of projections, understand the lease implications of each, and present the client with a scenario showing how much additional cost flexibility — or option space — is required to accommodate the optimistic projection. This converts a disagreement into a risk-quantified trade-off that leadership can evaluate rationally.
The Role of Lease Economics in Requirements Filtering
A requirements framework that ignores economics is incomplete. First-tier requirements that cannot be satisfied within the approved budget are not, in practice, deliverable — and surfacing this conflict early saves everyone time. Running a preliminary lease net present value (NPV) analysis against the client's stated size range and target submarket is a standard way to test whether the brief is financially viable before the market search begins.
Effective rent — the total cost of occupancy expressed on a per square foot per year basis after accounting for free rent, tenant improvement allowance and other concessions — is the right metric for this analysis. Two buildings with the same face rent can have materially different effective rents depending on the concession package, and a brief that only specifies a maximum face rent may inadvertently exclude buildings with more favorable economics.
Lease term interacts with requirements in a less obvious way. A client who insists on a five-year term to maintain flexibility will typically receive a less favorable concession package than one willing to commit to ten years. If flexibility is a genuine first-tier requirement, the team needs to accept that the economics of their deal will reflect it. If flexibility is a nice-to-have that was never explicitly tested against cost, the discovery session is the right place to test it.
Applying a Scoring Matrix in Practice
Once the two-tier framework is built and second-tier criteria are quantified, the scoring matrix is the operational tool that runs the search. Each property on the longlist is evaluated against every criterion, with scores weighted to reflect the priorities confirmed in the discovery session. The output is a ranked list that the adviser and client can review together, with scores attached to each line rather than impressions.
Weighting decisions deserve careful attention. If transit access is weighted at 20% of the total score and the client's primary workforce is entirely car-dependent, that weighting misrepresents the brief. Weights should be anchored to the documented priority decisions made during discovery, not set by convention or by what happens to be easy to measure.
The matrix should be presented as a living document through the shortlisting phase. When a property is toured and new information emerges — a floor plate that photographs well but functions poorly, a loading dock configuration that doesn't match the operational requirement on paper — the score should be updated and the reason documented. A scoring matrix that is frozen at the moment of creation stops reflecting reality within a few weeks.
The platform license is $299 per user per month, with an optional Super Agent upgrade at an additional $99 per upgraded user per month for source-backed research and scenario analysis.
When Requirements Evolve During the Search
Requirements do change, and pretending they won't creates a brittle process. Market realities, internal business changes, or the simple act of touring buildings can legitimately cause a client to revise their brief. The question is not whether to allow changes, but how to manage them so that the search process remains coherent.
The right approach is to treat any requirement change as a formal revision to the brief, with a date stamp and a note on what changed and why. This creates a version history that prevents the search from drifting without anyone noticing, and it protects the adviser from the perception that the process is disorganized. When an LOI is eventually executed, the final brief should be traceable back to the original discovery session.
Requirement upgrades — moving a nice-to-have to a must-have — are the most dangerous form of revision. They can silently eliminate properties that were already on the shortlist, making prior work redundant. Before accepting an upgrade, the adviser should confirm with the client that the change is intentional and that they understand which existing shortlisted options it removes. This conversation usually prompts a reassessment of whether the upgrade is truly warranted.
Requirement downgrades — moving a must-have to a nice-to-have — typically happen when the market delivers insufficient supply that meets the first-tier list. This is a healthy response to reality, but it should be documented as a deliberate concession rather than a silent adjustment. The client and their internal stakeholders should acknowledge the change explicitly so that no one is surprised when the eventual lease agreement reflects a building that falls short of an earlier stated constraint.
From Requirements to Shortlist: Maintaining Momentum
The transition from a completed requirements brief to an active market search is a moment where engagement can stall. Clients who spent significant energy on the discovery process sometimes go quiet once the brief is written, expecting the adviser to run the search and return with a shortlist. The adviser's role at this stage is to maintain momentum by setting a clear cadence for updates and committing to a shortlist delivery timeline.
A defined shortlisting timeline — typically two to four weeks from brief completion depending on market complexity — creates accountability on both sides. The adviser commits to delivering a scored longlist and a shortlist recommendation by a specified date. The client commits to being available for a shortlist review session on that date. Without this structure, searches lose momentum as internal priorities compete for attention.
The shortlist presentation should reference the agreed brief explicitly. Each shortlisted property should include a summary of how it meets the first-tier requirements and a scoring summary against second-tier criteria. Properties that were evaluated and eliminated should be listed with the specific first-tier failure that removed them. This level of documentation demonstrates that the search was disciplined and that the shortlist reflects the agreed brief rather than the adviser's personal preferences.
Practical Templates and Documentation Habits
A requirements brief does not need to be elaborate to be effective. The most functional formats are simple: a table or structured narrative that lists each requirement, its tier classification, its quantified threshold, its weighting if it is a second-tier item, and the name of the stakeholder who confirmed it. This last element — the stakeholder attribution — is often omitted and is often the most important. When a requirement is contested mid-search, knowing who confirmed it and when allows the adviser to route the conversation to the right person rather than re-opening the debate with the whole group.
The documentation habit that makes the biggest difference is a decision log. Every time a requirement is reclassified, every time a property is eliminated, and every time the client makes a priority call between competing constraints, that decision should be logged with a date and a one-sentence rationale. Over a six-month engagement, this log becomes the institutional memory of the search and prevents the team from cycling back to decisions that were already made.
For teams managing multiple concurrent searches — a portfolio team running site selection across several markets simultaneously — the documentation habit scales directly into a governance structure. Each brief is a living document with a version history. Each scoring matrix is updated as tours happen. Each decision log is part of the project record. This is what professional real estate advisory practice looks like at the operational level, and it is the standard against which any technology or workflow should be evaluated.
Understanding the principle behind this article on Must-Haves vs Nice-to-Haves: How to Separate Requirements Before a Property Search — that disciplined requirements work at the front of an engagement saves compounding cost at every later stage — is as applicable to a single-market lease renewal as it is to a multi-market portfolio expansion. The method scales; only the complexity of the stakeholder map changes.
About Advantai
Advantai is a commercial real estate intelligence and operations platform operated by ADVANTAGE AI LLC, a Delaware limited liability company. It connects client relationships, property research, documents and financial decisions in one workspace for commercial real estate teams — advisers and brokerage teams, occupier and facility teams, and portfolio teams. The platform covers CRM and origination, requirements and site selection, Property X-Ray (an interactive 3D building workspace), financial modeling and comparison, document intelligence, transactions and diligence, client collaboration, and portfolio strategy with critical dates. The optional Super Agent upgrade adds specialist, source-backed research and automated scenario analysis.
Get Started with Advantai
Ready to see your next move clearly? Go to advantaico.com, click Request a demo and tell us about your next project. Prefer to start with a single project? Visit advantaico.com/getting-started to plan your first one.