Why the Brief Shapes Every Decision That Follows
When a business unit submits a space request, what lands on a corporate real estate team's desk is rarely a brief — it is usually a conversation fragment, a headcount number, and a move-in date someone already told HR. The gap between that opening conversation and a defensible real estate decision is exactly where projects go sideways. Understanding which data points to collect before any search begins is the discipline that separates reactive order-taking from genuine strategic counsel. The seven data points below are the structured intake framework that experienced advisers and corporate real estate leads use to convert a vague request into a decision-ready requirement.
Why a Structured Intake Process Matters for Corporate Real Estate
A structured intake is not bureaucracy for its own sake. When a business unit's request is captured informally, the downstream effects compound: the search runs too wide, the financial model rests on assumptions nobody verified, and the final recommendation is harder to defend at the approval stage.
The intake also creates the audit trail that protects both the adviser and the occupier. If a business unit later claims the space is too small or in the wrong submarket, a documented brief with signed-off assumptions is the clearest way to demonstrate that the original requirement was faithfully translated into a search and a recommendation.
Corporate real estate leaders who have managed large portfolios across multiple business units will recognize another benefit: the structured intake forces the requesting unit to think clearly. Headcount projections get stress-tested, the difference between preferred and required amenities becomes explicit, and parking ratios that seemed non-negotiable often turn out to be flexible once cost implications are visible.
The 7 Data Points to Collect When Business Units Request New Space framework below treats each data point as a decision variable, not a form field. The goal is to collect information at the level of specificity that allows a financial model, a search, and a recommendation to be built without returning to the business unit for clarification every other week.
Data Point One — Headcount and Growth Trajectory
Headcount is the foundation of any space requirement, but raw headcount is almost never sufficient on its own. The question is not how many people work in the business unit today; it is how many people will be working there at the end of the lease term, under what conditions, and with what confidence.
A lease signed for a hypothetical example of fifty people today, with a five-year term and no expansion option, that is actually housing ninety people by year three has already failed the occupier. Collecting the base headcount, the anticipated headcount at lease expiration, and the confidence interval around that projection are all part of the same data point.
Growth trajectory also needs to reflect the nature of the headcount. A team of field-based account managers who are in the office two days a week occupies space fundamentally differently from a team of developers or traders who are present every day. The head-to-workstation ratio and the utilization model belong in this same intake question, because they drive net square footage far more directly than raw headcount does.
The business unit lead often provides a single headcount number and treats it as a fixed variable. The adviser's job is to push for a range — a base case, a downside, and an upside — and then to establish whether the lease structure should include contraction or expansion provisions to accommodate that range without committing to square footage that may never be used.
Data Point Two — Lease Term and Timing Constraints
The required occupancy date and the acceptable lease term are two of the most consequential constraints in any brief, and they interact in ways that business units rarely anticipate. A short required lead time collapses the negotiating window and may eliminate build-to-suit options entirely. A long preferred lease term may conflict with the organization's portfolio strategy if other leases in the same submarket are expiring at different times.
Timing constraints also need to capture the current lease situation. If the business unit is relocating from an existing location, the adviser needs to know the current lease expiration date, the notice provisions, and any holdover risk. A business unit that requests a new space with a six-month lead time, while sitting on a lease with a twelve-month notice obligation, is already in holdover territory if no one catches it early.
The preferred lease term is distinct from the maximum acceptable term. Many business units express a preference for shorter commitments without understanding the rent premium a landlord will typically impose on a three-year lease versus a seven-year lease. Collecting the preferred term alongside the absolute maximum and minimum gives the adviser the range needed to model the trade-off between flexibility and cost — a trade-off that should be surfaced in the brief, not discovered mid-negotiation.
Data Point Three — Space Configuration and Use Requirements
Headcount and lease term establish the size and duration of the requirement. Space configuration determines whether a given building can actually satisfy the brief. Configuration data should capture the mix of enclosed offices, open workstations, conference and collaboration rooms, quiet zones, and any specialized infrastructure requirements such as server rooms, trading floors, lab space, or reception areas.
Configuration requirements often carry departmental politics. A business unit lead may request a certain ratio of private offices because that is what the team has today, not because that ratio reflects how the team actually works. The intake process should probe whether configuration preferences are operational requirements or legacy habits, because that distinction has direct implications for the search and for the lease negotiation over tenant improvement allowances.
Specialized infrastructure can disqualify buildings entirely if not captured early. A team that requires raised floor space for server equipment, or backup power with specific generator capacity, cannot be placed in a standard Class B office floor without significant capital expenditure. These requirements need to be on record before a submarket or building shortlist is ever constructed, not discovered during diligence.
Amenity requirements also belong in this data point: food service access, fitness facilities, bike storage, loading dock access for equipment delivery, or proximity to specific transit lines. The adviser's job is to separate required amenities from preferred ones, because the two carry very different implications for how aggressively a building can be filtered out of the search.
Data Point Four — Geographic Parameters and Submarket Preferences
Location preferences need to be decomposed into their underlying drivers to be useful. A business unit that says "we want to be downtown" may actually be expressing a talent acquisition concern, a client proximity preference, or simply institutional habit. Understanding which driver is at work determines how much flexibility exists and what alternatives the adviser can legitimately propose.
The intake should capture specific submarkets that are preferred, any submarkets that are excluded and why, proximity requirements to specific anchors (a client campus, a transit hub, a university, a port), and commute-shed implications for existing staff. A workforce that is currently centered on a northern suburb will face a genuinely different commute impact from a downtown relocation than one whose staff is already distributed across the metro.
Geographic parameters also need to reflect portfolio context. If the organization already has a lease expiring in one submarket, consolidating into the same submarket for the new requirement may carry cost and coverage benefits that are only visible if someone is looking at the full portfolio, not just the individual request. This is where portfolio strategy intersects with individual requirement intake, and where a connected view of existing obligations and new requirements prevents suboptimal decisions.
Data Point Six — Decision Process and Stakeholder Map
Knowing what space is needed is only useful if the adviser also knows who approves it. The intake process should produce a clear stakeholder map: who owns the requirement from the business unit side, who must approve the final recommendation, what approval thresholds exist, and what the board or committee review process looks like for a commitment of this size and duration.
Approval processes in large organizations can easily consume sixty to ninety days between final proposal and executed lease — longer if legal review cycles, committee schedules, or board calendar constraints apply. That timeline needs to be built into the project plan from day one, not discovered when a landlord is pressing for a decision and the internal process has only just started.
The stakeholder map should also capture dissenting voices. If the CFO is skeptical of the location preference or the head of HR has a competing initiative that affects headcount assumptions, those perspectives are better surfaced in the intake than encountered as objections at the approval stage. Part of the adviser's value is running the stakeholder landscape in parallel with the property search, so that internal alignment is built as options are narrowed rather than attempted all at once at the end.
Data Point Seven — Existing Lease Obligations and Portfolio Connections
No space request exists in isolation. Every new requirement has a relationship to the organization's existing portfolio, and failing to map that relationship early produces duplicated costs, stranded space, and misaligned critical dates. The final data point in the intake framework is a complete picture of how the new requirement connects to existing obligations.
This means identifying the current space the business unit occupies, the remaining term and notice provisions on that lease, any sublease rights or early termination options, and the condition of the existing space relative to its lease surrender requirements. A business unit that wants to move in twelve months may be sitting on a lease with an eighteen-month notice clause and no early termination right — a fact that reframes the entire project if discovered on day one rather than month six.
The portfolio connection also includes other leases in the same building or the same submarket that may be expiring within a window that makes consolidation viable. When multiple business units are projecting growth in overlapping geographies and timelines, the adviser who has mapped all of those lease expirations and requirement windows simultaneously is in a position to suggest a consolidation or a master lease negotiation. That position is only reachable if structured intake data has been collected across the portfolio, not just for the single request at hand.
Turning the Seven Data Points into a Defensible Brief
Collecting the seven data points is the diagnostic phase. The next step is converting the collected inputs into a brief that can drive a submarket analysis, a building shortlist, a financial model, and a recommendation to the approving authority. The brief should state the requirement in quantified terms: a size range derived from headcount and configuration assumptions, a submarket or geographic zone, a lease term range, a budget expressed in rent per square foot or cost per person, and the occupancy date range.
The brief also needs to document its own assumptions explicitly. If the headcount projection assumes a particular hiring plan that is contingent on a business line approval, that contingency belongs in the brief. If the preferred submarket reflects a talent strategy that is under review, that uncertainty belongs in the brief. The document is not just a requirement statement — it is an audit trail of what was known, what was assumed, and what was validated at the time the search was initiated.
A brief built on all seven data points also makes scope management straightforward. When a business unit later requests a change — a larger size, a different submarket, an earlier occupancy date — the adviser can trace exactly which assumption changed, model the cost and schedule implications, and present the change as a decision for the approving authority rather than absorbing it silently into the search.
Common Gaps That Invalidate the Brief
Even experienced teams miss certain gaps in the intake. The most common is treating the headcount projection as a point estimate when it is actually a distribution. A business unit that projects fifty people in year three with reasonable confidence has a very different space requirement than one that projects fifty people but acknowledges a plausible range from thirty to eighty. Collecting the range and the confidence level is what allows the adviser to structure the lease — term, expansion options, contraction rights — to match the actual risk profile.
A second common gap is failing to separate the occupancy date from the lease commencement date. If a business unit needs to be physically operational by a certain date, that date drives construction scheduling, permitting timelines, and furniture procurement, which all need to be traced backward from the occupancy date to establish the latest possible date for lease execution. Confusing occupancy date with lease commencement date by even thirty days can push an entire project into holdover territory or force a costly temporary accommodation.
A third gap is assuming that the business unit lead has authority to approve the brief. Collecting the stakeholder map explicitly, rather than assuming it, is what prevents the adviser from delivering a recommendation to someone who cannot approve it. The brief should be signed off at the right level before the search begins, not presented to a committee who is seeing the requirement for the first time alongside a proposed solution.
How Advisers Use Intake Data to Build a Search Strategy
With all seven data points documented and validated, the search strategy writes itself more clearly than it does from an informal conversation. The submarket analysis can be scoped to the geographies that meet the location parameters. The building search can be filtered by configuration requirements and infrastructure needs. The financial model can be built on the validated budget and term parameters rather than on assumptions that will need to be re-verified later.
How Intake Data Informs Portfolio Strategy Over Time
The intake process for a single requirement is also the building block of a long-term portfolio strategy. Which submarkets are business units gravitating toward? Where are headcount growth assumptions concentrated? Which lease terms are clustering in ways that will create a wall of expirations in a specific year?
Structured intake records, accumulated across requirements over time, make these patterns visible in a way that informal request handling does not. An organization that consistently documents the structured inputs behind each requirement builds an internal dataset that can support consolidation planning, flexible workspace strategy decisions, and capital allocation — none of which is achievable when requests have been handled through ad hoc conversations that left no structured record.
The difference is not analytical sophistication — it is whether the underlying requirement data was captured in a queryable, structured form in the first place.
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.