The quality of a landlord's response depends almost entirely on the quality of the brief that reaches them. When occupier teams learn how to write a facility requirements summary landlords can answer clearly, they eliminate the rounds of clarification that delay shortlisting, compress the negotiation timeline, and position themselves as serious, credible counterparties before a single tour is booked.
Why Most Requirements Summaries Fail Before They Leave the Building
A poorly drafted requirements document creates ambiguity at the worst possible moment — when a landlord or their leasing agent is deciding whether to put together a serious counter-proposal or move on to a more legible opportunity. Vague size ranges, undefined use categories, and missing critical-date signals force the landlord to guess, and guesses produce proposals that cannot be compared on a like-for-like basis.
The failure is rarely intentional. Most occupier teams assemble requirements in conversation rather than in writing, then circulate a summary that reflects the conversation's looseness rather than the decision's precision. What reads as flexible thinking internally reads as an uncommitted tenant externally.
The discipline of writing a requirements summary is not bureaucratic overhead. It is a professional translation exercise — converting internal business intent into the language of property: area, configuration, term, commencement, and covenant.
Establishing the Business Context First
Before any square footage appears on the page, the requirements summary needs a short business-context section. This section answers why the occupier is in the market at all — a lease expiry, a headcount change, a consolidation strategy, an expansion into a new geography. Landlords who understand the driver can calibrate their response to the occupier's real constraints, not just their stated metrics.
The business context should be one to three sentences — not a corporate history. Something as direct as "lease expiry in fourteen months, current building cannot accommodate projected headcount growth" gives the reader the urgency signal, the timeline pressure, and the space-driver in a single breath.
Covenant information belongs here too. Landlords will conduct their own diligence, but naming the entity, its trading history, and the jurisdiction of incorporation at the outset removes a friction point and signals transparency. Where the occupier is a subsidiary, clarifying whether the parent will guarantee the lease is worth a sentence rather than leaving it as an open question for negotiation.
This context section also sets the register for the whole document. It frames the occupier as a decision-ready counterparty rather than an early-stage enquirer, which affects how landlords prioritise their response queue.
Defining the Space Requirement with Enough Precision to Be Useful
The area requirement is usually the first number a landlord reads, and it is frequently the least useful number in the document. A range like "15,000 to 30,000 square feet" tells a leasing agent almost nothing about which floors to price, which buildings to include, or how hard to compete for the occupier's attention.
A better approach splits the area requirement into three components: a minimum threshold below which the space cannot function, a target that reflects the headcount and density model, and a maximum above which the occupier's economics break down. These three numbers come from a workspace utilisation model, not a gut estimate, and that distinction matters when landlords push back on the range.
Measurement standard is not optional. Whether the requirement is stated as rentable area, usable area, or net internal area affects the economic comparison between buildings using different measurement conventions. Specifying the standard — and noting whether the occupier will apply their own de-rating factor for efficiency — avoids a common source of like-for-like error when comparing proposals.
Stacking and configuration notes belong in this section too. If the occupier needs contiguous floors, requires a minimum floor plate of a certain size, or needs above-grade loading access, those constraints should be stated as requirements rather than surfaced during due diligence. Configuration constraints eliminate non-compliant buildings early and save every party time.
Specifying Location Parameters Without Narrowing Unnecessarily
Geography is one of the most contested sections of a requirements summary. Occupier teams often arrive at a geographic preference through internal politics rather than data — a senior stakeholder lives near one corridor, a recruitment team has a preference for a transit node, or historical habit has crystallised into an apparent requirement.
A transit connectivity requirement tied to a commuter-shed analysis is a constraint. A preference for a specific street address because the current office is there is a preference. Landlords who understand which is which can offer genuine alternatives without wasting time on proposals the occupier will never consider.
Competitive distance from key clients, suppliers, or partner offices is a legitimate location parameter that is often omitted. If proximity to a specific cluster of relationships is strategically material, state it as such. A radius from a transit interchange is easier to operationalise than a neighbourhood name, which means different things to different landlords depending on where their stock sits.
Exclusion zones matter too. If regulatory constraints, brand positioning, or security requirements preclude certain submarkets, say so early. A landlord who discovers a submarket exclusion after pricing a full proposal feels their time has been wasted, and that feeling colours the subsequent negotiation.
Describing Technical and Operational Requirements in Landlord Language
Technical requirements are where most requirements summaries lose specificity at the worst possible time. Occupier teams understand what they need operationally but often state it in facility-management terminology that leasing agents cannot translate into building specification without calling the facilities team.
Power density requirements should be stated in watts per square foot or kilowatts per floor, not in terms of internal IT architecture. Cooling requirements should reference the load per rack or the total tonnage, not the number of servers. Telecoms redundancy should specify the number of diverse paths required. These numbers come from the occupier's infrastructure team and should be validated before the brief leaves the building.
Floor loading is a frequent omission. Where the occupier operates equipment, storage, or specialised workstations that exceed standard commercial floor loading, the capacity requirement should be stated in kilopascals or pounds per square foot. A landlord who discovers a floor loading issue after heads of terms are signed faces a costly retrofit conversation that neither party wanted.
Accessibility standards, welfare provision, and minimum ceiling heights all belong in this section. Where applicable, stating the required clear height under beam — rather than the slab-to-slab dimension — avoids the disappointment of discovering that a notionally compliant building is operationally unsuitable after fitout calculations are run.
Setting Out Term, Commencement, and Break Requirements
A landlord cannot price a proposal without knowing what term structure the occupier is offering. Lease term, commencement target, and break options are not negotiating positions to be withheld — they are inputs that determine the landlord's economic model, the incentive package, and the risk allocation between the parties.
The requirements summary should state the target lease term in years, the earliest acceptable commencement date, and the latest acceptable commencement date. It should also indicate clearly whether a break option is a firm requirement or a preference the occupier would trade in exchange for a better incentive package. Making that distinction explicit saves a cycle of back-and-forth that commonly delays heads of terms.
If breaks are required, stating the target break date and whether the occupier will accept a penalty-free break or expects a rolling break provision narrows the structural conversation immediately.
Rent-free and fitout contribution expectations are not premature to include at this stage. A landlord who knows the occupier expects a market incentive package can build a headline rent that makes the economics work rather than creating an adversarial negotiation over allowances later. The requirements summary is not a negotiating document, but it is an honest one.
Handover condition is a close cousin of term structure. Whether the occupier needs a fully fitted space, a Category A shell, or a bare shell with landlord contribution shapes the landlord's proposal in ways that are hard to retrofit after the initial response. State the required handover standard and the occupier's fitout timeline so landlords can align the rent-free period to the actual occupation programme.
Building Sustainability and Health Credentials
Sustainability requirements have moved from optional preference to procurement threshold for many occupier categories. A requirements summary that omits energy performance, certification target, and embodied carbon position is increasingly read as an indicator that the occupier has not stress-tested their own ESG commitments against their real estate decisions.
Where an occupier has a specific energy performance standard — whether tied to a certification scheme, a scope 2 target, or a building performance standard — that requirement should be stated explicitly. Landlords who operate high-performance buildings need to know whether the occupier will value that asset, and landlords who cannot meet the standard should know early rather than late.
Health and wellbeing credentials — air quality monitoring, biophilic design elements, active travel infrastructure — are increasingly part of the tenant value proposition that landlords use to justify premium rents. Stating these requirements signals the market segment the occupier is targeting and helps landlords position their offering accordingly.
Where the occupier operates under a net-zero commitment with a specific target year, the requirements summary should reference that commitment and ask landlords to demonstrate how their building aligns with or supports it. This is not aspirational language — it is a material due diligence question that affects the lease's long-term risk profile.
Pricing Expectations and Economic Framework
Stating a target occupancy cost range is uncomfortable for some occupier teams, but it is professionally responsible. A landlord who spends three weeks pricing a proposal only to discover the occupier's budget ceiling is thirty percent below their asking rent has not been well served by the process, and neither has the occupier.
Rates, service charge, insurance, and car parking costs are material to the comparison between buildings and between markets, and an occupier who benchmarks only headline rent will discover those omissions when comparing lease analysis across a shortlist.
The requirements summary does not need to include an NPV model, but it should indicate that the occupier will evaluate proposals on a total-cost, discounted basis. This signals analytical sophistication and discourages landlords from constructing proposals designed to look competitive at the headline level while embedding cost elsewhere. Evaluating proposals on a discounted, all-in basis is a well-established approach in occupier advisory and allows unlike lease structures — varying terms, commencement dates, and incentive packages — to be compared on a consistent economic footing.
Where the occupier is evaluating owned versus leased scenarios, the requirements summary is not the place for that analysis — but acknowledging that the brief sits within a broader facility-planning exercise that includes own-versus-lease consideration can usefully inform how landlords structure their flexibility offers.
Building the Comparison Scoring Framework
A requirements summary is most useful when the occupier team has already built the scoring framework they will use to evaluate responses. Publishing the weighted criteria alongside the requirements document is unusual, but it is a powerful signal of serious intent and analytical rigour.
A property evaluation scoring framework typically covers several domains relevant to the occupier's priorities. Common domains include location and connectivity, building specification and configuration, economic competitiveness, and landlord service quality and covenant strength. Each domain carries a weight that reflects the occupier's strategic priorities, and each criterion within a domain carries a sub-weight.
Disqualifying criteria should be identified separately from scored criteria. Minimum floor plate, specific transit access, power density, and lease term structure are common disqualifiers. Labelling these as mandatory — meaning the building is removed from the shortlist if it fails on any one of them, regardless of its score in other domains — prevents a landlord with an outstanding location from spending resources on a submission that will fail on a technical constraint they were never told about.
Sharing the scoring framework with landlords is not a standard practice in all markets, but where the occupier team is running a structured selection process, it creates transparency that improves the quality of submissions and reduces the time spent on proposals that cannot succeed.
Structuring the Document for Landlord Response
The physical structure of the requirements summary affects how quickly landlords can respond. A document that buries the commencement date on page seven and the floor loading requirement in a footnote forces the reader to work through the whole brief before they know whether their building is eligible. That friction reduces the quality and speed of the responses the occupier receives.
A well-structured requirements summary opens with a one-page executive brief covering the entity, the driver, the space quantum, the target location, the lease term, and the economic framework. The body of the document then provides the detail behind each of those parameters in the order the landlord needs to work through them: location, then building specification, then area, then term, then economic structure, then sustainability and health.
Each section should end with a clear statement of what the landlord is being asked to provide in response. If the occupier needs floor plans with proposed demise highlighted, ask for that. If the occupier needs a heads of terms draft alongside the commercial proposal, say so. Response instructions that are embedded in the brief rather than bolted on as a covering email reduce the chance of incomplete submissions.
Version control matters for large processes where the brief is updated during the market engagement. A reference date on each version and a clear change log between versions prevents landlords from pricing against superseded requirements, which produces incomparable proposals and forces a second round of submissions.
Separating Non-Negotiable Constraints from Preferences
One of the most consequential distinctions in a requirements summary is the line between what the occupier must have and what the occupier would prefer to have. When those two categories are written in the same register, landlords cannot tell them apart, and the occupier receives proposals that satisfy neither.
The requirements summary should distinguish between non-negotiable location constraints — a maximum distance from a specific transit hub, for example, or exclusion from a named submarket — and location preferences that the occupier would value but would trade for a compelling economic offer. That distinction does real work in the market engagement. It tells landlords where they have room to compete and where they do not.
The same principle applies to building specification. A minimum floor loading requirement is non-negotiable. A preference for a south-facing outlook is not. When both appear in the same list without differentiation, landlords either over-engineer their response or underestimate the importance of the hard constraint.
Advisers who help occupier teams make these distinctions explicit before the brief is distributed often find that the process of categorisation itself surfaces internal disagreements about what the requirement actually is. A stakeholder who insists a certain neighbourhood is mandatory may be expressing a preference tied to a commute rather than a business requirement. Working through that distinction before the brief is released is far less costly than discovering it after proposals arrive.
Reviewing the Brief Before It Leaves the Building
A requirements summary should go through at least two internal review cycles before distribution. The first review is a technical check: does every figure come from a validated source, is the measurement standard consistent throughout, and have the technical requirements been signed off by the occupier's infrastructure and facilities teams? The second review is a readability check: can a leasing agent who has never spoken to the occupier team understand the brief completely from the document alone?
Distributing the brief through a controlled channel with read confirmation gives the adviser team confidence that every landlord has received the same version at the same point in the process. It also creates a record for the transaction file that becomes important if disputes arise about what was disclosed and when.
The brief should include a submission deadline and a point of contact for clarification questions. Landlords who have a specific clarification channel are less likely to call the occupier directly, which protects the adviser relationship and keeps the market engagement consistent across all respondents.
Connecting the Requirements Summary to the Transaction
The requirements summary is not a standalone document. It is the opening entry in a chain of documents that runs through the shortlist, the heads of terms, the lease, and ultimately the portfolio record. Teams that treat the requirements document as the first formal record of a transaction — rather than an informal internal summary — tend to run cleaner processes because every subsequent decision can be traced back to an agreed starting point.
The requirements summary also serves advisers directly.
That access model is consistent with how many occupier advisory mandates are structured — project-specific, outcome-focused, and time-bounded.
The operator of the platform is ADVANTAGE AI LLC, a Delaware limited liability company, which has positioned Advantai as a tool that earns its place in a transaction through demonstrated utility.
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.