The question of Who Should Own Facility Requirements: Real Estate, Operations or Facilities is one of the most persistently contested governance problems in corporate occupancy. Organizations regularly arrive at lease decisions, capital projects and portfolio restructuring exercises with no shared definition of who holds the pen on requirements — and the consequences are expensive. Requirements that drift, scope that inflates, and properties that technically satisfy a brief but never fully serve the business are all symptoms of the same accountability gap.
Why Ownership Questions Arise in the First Place
Facility requirements rarely belong to a single discipline by nature. They sit at the intersection of legal obligation, operational workflow and physical space — three domains that report to different executives, operate on different planning cycles and use different success metrics.
The real estate function measures in lease years, rent per square foot and portfolio cost. The operations function measures in throughput, headcount productivity and service continuity. The facilities function measures in asset condition, compliance status and maintenance cost. When a requirement has to satisfy all three simultaneously, no single owner feels fully empowered to make the call.
This structural ambiguity tends to surface at moments of urgency: a lease expiration approaching faster than the business anticipated, a workforce expansion that outpaces existing square footage, or a regulatory requirement that forces a reconfiguration. Under time pressure, ownership defaults to whoever is loudest rather than whoever is most qualified.
Understanding the structural source of the problem is the prerequisite for solving it. The answer lies not in assigning all facility planning authority to one department, but in defining which function owns which layer of the requirement — and holding each layer to a documented, reviewable standard.
Decomposing What "Facility Requirements" Actually Means
Before ownership can be assigned, the term itself needs decomposition. A facility requirement is not a single document — it is a hierarchy of specifications that range from portfolio-level strategic intent down to room-by-room technical detail.
At the top of the hierarchy sits the portfolio mandate: the business decision about what kind of presence the organization needs in a market, for how long and under what financial parameters. Below that sits the operational brief: what activities will occur in the space, how many people need to be accommodated, how those activities relate to one another and what adjacencies are non-negotiable. Further down sits the technical specification: structural loading, power density, HVAC capacity, accessibility compliance, security zoning and all the physical attributes that determine whether a building can actually host the operational brief.
Most ownership disputes conflate these layers because organizations try to draft them as one document. A single requirements sheet that asks the broker to find space while also specifying server room cooling loads is asking one document to serve three different audiences. Separating the hierarchy is the first methodological move that makes ownership tractable.
The Real Estate Function's Natural Domain
Real estate, in the corporate context, operates at the portfolio and economic layer. It holds the relationships with landlords, the knowledge of lease structures, the financial modeling tools needed to compare lease versus purchase, and the timeline discipline that comes from managing critical dates across a multi-location portfolio.
For these reasons, real estate is the natural owner of the portfolio mandate layer. It should define the market, the tenure target, the economic boundary conditions (a target net present value, an effective rent ceiling, or a capital expenditure limit labelled as hypothetical for illustration) and the strategic flexibility provisions the business requires in the lease — expansion options, termination rights, sublease rights.
What real estate typically cannot own with authority is the operational brief. A leasing adviser or corporate real estate director rarely has deep visibility into how a manufacturing cell flows, how a clinical team moves between examination rooms, or how a contact centre's noise zoning affects productivity. Asking real estate to author the operational brief without operations input produces a requirement that is commercially sensible but operationally inadequate.
The practical consequence is that real estate should receive the operational brief as a validated input rather than generating it. This shifts real estate into a translation role: taking the business's operational needs and converting them into site selection criteria, lease term requirements and financial parameters that can be tested against the market.
The Operations Function's Natural Domain
Operations owns the work. It understands headcount trajectories, workflow dependencies, technology footprints and the service levels the business has committed to deliver. For these reasons, operations is the natural owner of the operational brief layer.
Producing a credible operational brief requires operations to answer a specific set of questions with measurable answers. How many people need to be in the space on peak days, not average days? Which teams must be physically adjacent to one another to reduce handoff latency? Which activities require controlled or segregated environments? What technology infrastructure (power, network, cooling) is non-negotiable versus preferred? What growth assumptions should the brief be sized to accommodate, and over what time horizon?
These are not abstract questions. They require operations to consult with technology, HR, compliance and business unit leadership — often simultaneously. This is why the operational brief takes longer to produce than most real estate timelines budget for. Real estate teams are often ready to tour buildings before operations has finished answering the adjacency question.
The operations function should also own the criteria-weighting step. When a site selection scoring matrix is built, operations should assign the relative weight to each criterion — not real estate. Real estate can advise on which criteria are commonly achievable in the target market, but the ranking of priorities belongs to the function that will live with the consequences.
The Facilities Function's Natural Domain
Facilities management sits closest to the physical asset. It carries institutional knowledge about how buildings actually perform over time: where HVAC capacity is routinely undersized, where power infrastructure fails to meet density requirements, where a building's age creates hidden compliance obligations. This knowledge does not appear in a lease abstract or a broker's market survey — it lives in the facilities team's operational history.
For this reason, facilities is the natural owner of the technical specification layer. The facilities team should validate that any shortlisted property can physically support the operational brief. This is not a checkbox review; it is a structured due diligence step that should happen before a letter of intent is signed, not after.
The technical specification checklist that facilities produces should be tied directly to each item in the operational brief. If operations has specified a server room that requires a hypothetical 200-kilowatt UPS and N+1 cooling redundancy (as an illustrative example of the specificity required), facilities should be able to confirm which shortlisted properties have the base building infrastructure to support that requirement and which will require capital investment to reach it. That capital cost feeds back into the real estate team's financial model, connecting all three layers.
Facilities also owns the transition and handback layers. The requirements for how a space will be delivered, commissioned, maintained and eventually vacated are facilities responsibilities that real estate and operations rarely have the expertise to define. Including these layers in the original requirements document prevents costly scope gaps at project completion.
Building the Governance Model: RACI Applied to Requirements
Once the three natural domains are mapped, the governance structure can be formalized using a RACI assignment — Responsible, Accountable, Consulted, Informed — applied at each layer of the requirements hierarchy. This is not a new framework, but it is rarely applied with the specificity that facility planning requires.
For the portfolio mandate, real estate should be Accountable, the CFO or head of corporate services should be Consulted, and operations and facilities should be Informed of the financial and tenure parameters. For the operational brief, operations should be Accountable, with real estate and facilities Consulted to ensure the brief is commercially feasible and technically deliverable. For the technical specification, facilities should be Accountable, with operations Consulted on prioritization and real estate Informed to update financial assumptions.
The RACI must specify decision rights, not just involvement. "Consulted" means the accountable function cannot proceed to the next stage without receiving and formally acknowledging that input. This is the mechanism that prevents real estate from touring properties before the operational brief is complete.
Escalation paths also need to be defined in advance. When operations and facilities disagree about whether a technical requirement is mandatory or aspirational, who resolves the dispute? The answer should be documented before the requirement is ever drafted — not negotiated in the middle of a site tour or an LOI negotiation.
The Brief as a Living Document with Stage Gates
Requirements governance fails when the brief is treated as a one-time deliverable rather than a living document managed through stage gates. Facility planning unfolds over months, and the business context changes. A brief written twelve months before occupancy that is never formally updated has usually been rendered partially obsolete before the space is ever occupied.
The stage-gate model assigns a formal review of the requirements document at each major decision point in the facility planning process. The first gate is market entry: before a broker is briefed or a market survey is commissioned, the portfolio mandate and operational brief should be signed off by real estate, operations and facilities respectively. This signature is not ceremonial — it commits each function to the parameters on the page.
The second gate is shortlist: before properties are toured, facilities should have completed a desk-top technical screen of each candidate. Properties that fail critical technical thresholds should be removed from the shortlist rather than carried forward with a note. Carrying forward properties that cannot meet requirements inflates the negotiating process and wastes transaction resources.
The third gate is final selection: before an LOI is issued, the full requirements document — portfolio mandate, operational brief and technical specification — should be reviewed against the chosen property and any gaps formally documented. These gaps become the negotiating agenda: what the landlord must deliver, what the tenant will self-fund, and what has been accepted as a compromise with a documented rationale.
The fourth gate is practical completion: before the business occupies the space, facilities should conduct a requirements-against-delivery audit. Every item in the technical specification should be signed off as delivered, deferred with a remediation schedule or accepted as a permanent variation. This closes the loop and creates the record that facility management teams need for ongoing maintenance planning.
Handling Contested Requirements: A Resolution Protocol
Even with clear ownership layers and a RACI in place, contested requirements will arise. Operations may specify a feature that facilities considers technically impossible within the building's constraints. Real estate may present a market reality that makes part of the operational brief economically unachievable. These are normal tensions — the resolution protocol determines whether they produce good decisions or paralysis.
The first step is to surface the contest formally. Many disputed requirements circulate informally for weeks before they are documented. The governance process should include a formal requirements issue log — a structured record of every item that one function has flagged as contested, the position of each party and the date the issue was raised. Unlogged disputes are invisible to leadership and cannot be escalated or resolved systematically.
The second step is to classify each contested item by type. A requirement that is contested because of a technical constraint is different from one contested because of budget pressure, which is different again from one contested because two functions simply have different preferences. Each classification requires a different resolution path: technical constraints go to an independent assessor, budget constraints go to the financial model and up to CFO approval, preference disputes go to the accountable owner at the relevant layer.
The third step is to document the resolution and its rationale. The record of what was decided and why is the artifact that prevents the same argument from recurring at the next project. Organizations that maintain a requirements decision log across multiple projects develop institutional knowledge that reduces dispute frequency over time.
Coordinating Across Timelines: The Calendar Problem
One of the most practical obstacles to good requirements governance is timeline misalignment. Real estate operates on lease market timing — the best opportunities are not available on the date that best suits the business's internal planning cycle. Operations typically plans headcount and workflow changes on an annual budget cycle. Facilities plans maintenance and capital works on a long-horizon asset plan.
These three cycles rarely align naturally, which means requirements governance must include a shared critical-date calendar that works backward from the lease event. The lease expiration or target occupancy date is the anchor. From that date, every stage gate, every review deadline and every function's contribution is mapped backward in time.
The practical implication is that the operational brief should be initiated significantly earlier than most organizations begin it. If the target occupancy date is eighteen months away and the technical specification validation typically takes three months, the operational brief must be complete before month fifteen. That means the brief must be initiated well before month twelve — which means the discussion about requirements ownership must happen in month one, not month ten.
Integrating the Requirements into the Financial Model
Requirements governance is not complete until the outputs of each layer are integrated into the financial model that will drive the final decision. This is where the connection between facility planning and capital allocation becomes explicit.
The portfolio mandate sets the financial envelope: a target effective rent, a capital expenditure ceiling, and a tenure that matches the business's strategic planning horizon. The operational brief converts into a size requirement — usable square footage, efficiency ratio, and a tolerance for surplus space during a ramp period. The technical specification converts into a capital cost: the delta between what the base building offers and what the operational brief requires, expressed as a fit-out cost or a landlord incentive requirement.
When these three inputs are assembled into a single financial model, the real estate function can calculate the total economic cost of occupancy — not just the rent, but the all-in cost that reflects both the lease terms and the capital required to make the space operationally viable. This is the number that should drive the final selection decision, not the headline rent.
Applying the Framework When Organizational Lines Are Blurred
Many organizations operate with structures where real estate, operations and facilities are not distinct functions. In smaller enterprises, one person may hold all three responsibilities. In decentralized corporations, business units may control operational decisions while a central team holds the lease portfolio. The framework still applies — it simply maps to roles rather than departments.
The key is to ensure that all three layers of the requirements hierarchy are explicitly assigned to named individuals with documented authority, regardless of how those individuals are organized on the org chart. A single person who holds responsibility for all three layers must still maintain the discipline of separating the layers and completing each in sequence, because the intellectual work of each layer is genuinely different.
For decentralized organizations, the additional challenge is that business units may resist central real estate's authority over the portfolio mandate layer. The resolution is to define the portfolio mandate layer as a financial governance matter rather than an operational one. Business units own the operational brief; central real estate and finance own the economic boundary conditions within which the brief must be satisfied. This distinction preserves business unit autonomy over how they work while maintaining corporate discipline over what they spend.
Building Institutional Memory Across Projects
A requirements framework only compounds in value if its outputs are retained and made accessible for future projects. Organizations that treat each facility project as a standalone exercise re-litigate ownership disputes, re-negotiate criteria weights and re-draft specifications from scratch every cycle. The institutional memory built into a well-documented requirements process is a competitive asset in real estate markets where speed and clarity of brief give tenants negotiating advantage.
The document set to retain after each project includes the signed portfolio mandate, the operational brief with its criteria-weighting rationale, the technical specification and the resolution log for contested requirements. Together these documents allow the next project team to understand what the organization decided, why it decided it, and what tradeoffs were accepted. They also provide the baseline against which the next brief can be updated rather than rewritten.
The Escalation Path to Leadership
Regardless of how well the framework is designed, some requirements decisions will need executive escalation — specifically, decisions where the financial parameters set by real estate conflict with operational requirements that operations is unwilling to compromise. These moments are governance tests, not governance failures. The framework's job is to route them cleanly.
The escalation path should be defined in the governance charter before any project begins. A practical structure routes contested items first to a requirements steering group that includes the senior leads from each of the three functions. If resolution cannot be reached at that level within a defined window (five business days, for example), the item escalates to the executive sponsor — typically the CFO, COO or Chief Administrative Officer, depending on the organizational context.
The escalation record is as important as the resolution. Documenting what went to leadership, what decision was made and on what basis creates the precedent that guides lower-level decisions on future projects. Organizations that manage escalation informally find that similar disputes recur because there is no institutional record of how they were previously resolved.
Delivering Requirements Clarity to External Partners
The final stage of requirements governance is communication to external partners: brokers, landlords, project managers and fit-out contractors. The quality of this communication determines whether the internal discipline of the framework produces external results.
A well-structured requirements package for an external broker should include the portfolio mandate in summary form — market, size range, tenure target and economic parameters — and the operational brief in enough detail that the broker can screen properties credibly before touring. The technical specification is typically shared with landlords and their technical teams after shortlisting, not before, because it contains sensitive operational details.
Brokers who receive clear, layered requirements documents consistently deliver better shortlists because they can apply the criteria in advance rather than discovering incompatibilities on site visits. The requirements package also improves landlord negotiations because it gives the tenant a documented, internally-approved position from which to negotiate, rather than a position that shifts as internal stakeholders re-litigate the brief in real time. This clarity, built through disciplined ownership and stage-gate governance, is ultimately what the framework delivers — not just internally, but in every external relationship the facility planning process depends on.
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.