Menu
Log in



Log in

2 Process

Phases, Steps and Tasks that Drive Decision Making


Introduction

Life Cycle Framework

Strategic Predesign Turns Strategy into Decisions

Decisions

1. Macro-level decisions

2. Phase-level decisions

Final Authorization Gate—Business Case and Owner Decision

The Process Creates Value By

1.0 Strategic Planning Phase – Begin with Strategy

1.1 Executive Vision – A Compelling Image of a Desirable Future State

1.1.1 Vision Session – Establish a Shared Direction

1.1.2 Understand the Strategic Context – Competitive Forces Shaping the Organization

1.1.3 Translation of Organizational Strategy into Facilities Initiatives

1.1.4 Selecting Facility Options

1.1.5 Plan for Change – Expand, Optimize, Contract, Integrate

1.1.6 Match Growth to Demand and Resources

1.1.7 Optimize Existing Resources and Work Processes

1.1.8 Plan Contraction in Its Market Context

1.1.9 Integrate Merger and Acquisition (M&A) Facilities

1.2 Portfolio Analysis

1.2.1 Digital Information and AI Operating Model

1.2.2 Sector-Specific Projections

1.2.3 Supply Capacity and Portfolio Diagnostics

1.2.4 Occupant Experience and Utilization Feedback Loop

1.2.5 Stakeholder Alignment & Business Unit Review

1.2.6 Strategic Challenge

1.2.7 Scenario Planning – Develop and Evaluate Alternative Futures

1.2.8 Strategic Budget Model Development (CAPEX, Rent, OPEX)

1.2.9 Project Sponsor Review, Buy-in and Approval to Proceed

1.3 Prepare the Business Case – the Investment Decision

1.3.1 Executive Summary

1.3.2 Problem or Opportunity Statement

1.3.3 Strategic Alignment

1.3.4 Analysis of Alternatives

1.3.5 Financial Assessment and ROI

1.3.6 Risk Analysis and Mitigation

1.3.7 Implementation Roadmap

1.3.8 Secure Documented Sponsor Sign-off

1.3.9 Review and Update the Business Case

2.0 Real Estate Phase

2.1 Location Strategy and Site-Selection Criteria

2.1.1 Real Estate Strategy

2.1.2 Location and Site-Selection Criteria

2.2 Market Survey and Technical Due Diligence

2.2.1 Identify and Screen the Long List of Properties

2.2.2 Create a Shortlist and Conduct Site Visits

2.2.3 Coordinate Specialist Due Diligence

2.2.4 Document Upgrades, Responsibilities, Dependencies, and Risks

2.2.5 Define IT Infrastructure and ISP Requirements

2.2.6 Alternatives Evaluation and Business Case Development


2.3 Transaction Readiness and Lease Negotiation

2.3.1 Confirm the Preferred Alternative and Authority to Negotiate

2.3.2 Negotiate Commercial and Delivery Terms

2.3.3 Confirm Decision Gates and Commitment Authorization

2.3.4 Prepare the IT Consultant and Integrator Bid List

2.3.5 Update the Business Case and Maintain Decision Records

2.3.6 Real Estate Phase Completion and Transition to Project Definition

3.0 Project Definition Phase

3.1 Project Management Team

3.1.1 Assign Project and Information Technology Managers

3.1.2 Define and Procure Specialist Services

3.1.3 Establish the Common Data Environment and Information Responsibilities

3.1.4 Establish Clear Governance and Accountability

3.1.5 Project Charter

3.2 Translating Business Priorities into a Program of Requirements (POR)

3.2.1 Master Planning and Prototype Design

3.2.2 Stages of Programming

3.2.3 Workplace Standards, Performance Targets and Design Criteria

3.2.4 Comprehensive Set of Considerations

3.2.5 Information Index – Organizing and Classifying Information

3.2.6 Information Display and Validation

3.2.7 Programming is a Participatory Process

3.2.8 False Harmony—Agreement by Default

3.2.9 Organize the Process for Decision Making

3.2.10 Communication

3.2.11 Process Steps – Establish Goals

3.2.12 Discover Concepts

3.2.13 Testing Goals and Concepts

3.2.14 Functional Relationships

3.2.15 Collect and Analyze Facts

3.2.16 Managing Collected Information

3.2.17 Factual Information Checklist

3.2.18 Sustainability and Energy Consumption

3.2.19 Determine Needs

3.2.20 State the Problem

3.3 Align Delivery and Procurement with Project Objectives

3.3.1 Project Delivery Methods

3.3.2 Procurement Process

3.3.3 Requirement Definition and Sourcing Strategy

3.3.4 Solicitation (RFQs and RFPs)

3.3.5 Evaluation and Selection

3.3.6 Contract Negotiation and Award

3.3.7 Contract Administration and Post-Project Review

3.3.8 Project Readiness Review

3.3.9 Review and Approval

Work Breakdown Structure Schedule

1.1 Strategic Planning

1.2 Real Estate

1.3 Project Definition


Introduction

This chapter describes the strategic predesign process in three phases: strategic planning, real estate, and project definition. It helps owners determine why action is needed, where investment should occur, what must be defined, and whether the proposed investment should proceed. The process is scalable and iterative. Its scope, level of detail, expertise, and stakeholder engagement should reflect the assignment’s scale, complexity, risk, and degree of change.

Use this chapter at two levels. Owners and sponsors can begin with Decisions and Final Authorization Gate—Business Case and Owner Decision, then use Sections 1.3, 2.3, and 3.3.8–3.3.9 to review the evidence and approvals required to advance.

Practitioners can follow the detailed Strategic Planning, Real Estate, and Project Definition sections to develop that evidence. The Work Breakdown Structure Schedule at the end provides an activity-and-output reference for organizing the work.

Life Cycle Framework

An enterprise’s built-environment ecosystem includes strategic predesign, design and construction, and facility operations. Strategic predesign connects these components to the enterprise’s operations and strategy.

Strategic Predesign Turns Strategy into Decisions

Strategic predesign translates organizational strategy into an evidence-based investment decision through three connected phases and nine steps. The process is iterative rather than strictly sequential: findings may require the team to revisit earlier assumptions, requirements, or alternatives. When no real estate decision is required, an initiative may move directly from Strategic Planning to Project Definition. The process culminates in the Project Readiness Review, where the owner determines whether the proposal is sufficiently justified, feasible, and defined to proceed.

The business case develops across all three phases and supports the final Project Readiness Review. Transactions or procurement approvals remain separate authorization decisions.

Decisions

Each phase of strategic predesign—Strategic Planning, Real Estate, and Project Definition—advances through decisions and approvals that establish direction, confirm commitments, and authorize subsequent work. Macro-level decisions establish the overall direction; phase-level decisions translate that direction into specific approvals. The decision groups below identify the numbered steps that develop their evidence. One step may support more than one decision group. The strategic planner, portfolio and asset manager, and project manager lead the evidence and recommendations in their respective phases. The sponsor decides within delegated authority; matters beyond that authority go to the chief executive officer or administrator, or the applicable governing authority. Advisors and consultants support recommendations but do not replace owner decision authority.

1. Macro-level decisions

Across the Strategic Planning, Real Estate, and Project Definition phases, leaders decide:

  • A.     What organizational need should be addressed?
  • B.     Which alternatives should be pursued, including no project or deferral?
  • C.    What criteria, constraints, and evidence should guide the alternatives and, where required, the real estate choice?
  • D.     Should the initiative proceed, and if so, how—with an approved rationale and requirements for design?

2. Phase-level decisions

The following ten decision groups support the three-phase process. They are approval groupings, not additional process steps: the first nine establish the direction, commitments, requirements, and procurement decisions needed for the tenth—authorization to proceed with design. Construction and other subsequent execution activities remain subject to their applicable authorizations.

  • 1.      Frame the Problem — Step 1.1 Executive Vision:
  • a.      Decide what problem or opportunity to address.
  • b.      Approve the decision’s scope and criteria for success.
  • c.      Accept the existing-condition baseline and validated need.
  • d.      Determine whether the evidence is sufficient or further investigation is needed.
  • e.      Identify the decision authority, required reviewers, and escalation route.
  • 2.      Select a Portfolio Strategy — Step 1.2 Portfolio Analysis:
  • a.      Decide on a portfolio strategy,
  • b.      Approve the investment priorities,
  • c.      Approve the critical milestone dates for completion.
  • d.      Approve resource allocations and initiative sequencing.
  • e.      Resolve dependencies and competing priorities.
  • f.        Select contingencies and triggers for reconsidering the strategy.
  • 3.      Approve the Business Case — Step 1.3 Prepare the Business Case:
  • a.      Approve the initial business case as the basis for the next authorized phase; maintain it as a controlled, evolving decision record.
  • b.      Accept the appraisal assumptions, planning horizon, and treatment of lifecycle costs and benefits.
  • c.      Confirm affordability and funding assumptions for the commitment requested.
  • d.      Accept residual risks and contingency arrangements.
  • e.      Assign benefits to owners and monitoring measures.
  • f.        Authorize the next phase and its scope and resource limits. If no real estate decision is required, proceed directly to Project Definition.
  • When a real estate decision is required, use decision groups 4–6. These are not a requirement to complete a transaction before Project Definition: where critical uncertainty requires project definition, authorize that work before an irreversible property commitment. Revisit affected approvals when later findings materially change the accepted baseline.
  • 4.      Approve Search Criteria and Short List — Steps 2.1 Location Strategy and Site-Selection Criteria and 2.2 Market Survey and Technical Due Diligence:
  • a.      Before candidate evaluation, approve the criteria, mandatory eligibility thresholds, preference weights, evidence baseline, scoring scales, and evaluation method under Section 2.1.2. Apply that controlled framework to the market survey and shortlist.
  • b.      Approve the recommended short list of properties for further investigation and due diligence.
  • c.      Determine which candidates are excluded and why.
  • d.      Authorize the scope of further investigations and required specialist contributions.
  • 5.      Select the Preferred Property and Authorize Negotiation — Step 2.2 findings and Sections 2.3.1–2.3.2:
  • a.      Select the preferred property
  • b.      Accept the comparative appraisal and preliminary accommodation findings, including their limitations.
  • c.      Decide whether unresolved findings prevent selection or permit conditional selection.
  • d.      Establish negotiation boundaries and matters requiring further authorization.
  • e.      Authorize negotiation of price, terms, conditions, delivery responsibilities, and occupancy timing within the approved boundaries; negotiation approval is not property-commitment authority.
  • 6.      Authorize Property Commitment and Phase Handoff — Sections 2.3.3–2.3.6:
  • a.      Approve the business case updated by the portfolio and asset manager with real estate findings and the proposed commitment.
  • b.      Accept due-diligence findings and responses to material deficiencies. Resolve critical requirements, feasibility, affordability, timing, and risk uncertainty through Project Definition before irreversible commitment where needed.
  • c.      Authorize the exact binding commitment, funding obligations, conditions, and execution authority.
  • d.      Assign contractual obligations and critical-date responsibilities.
  • e.      When evidence, requirements, costs, timing, risks, or authority materially change, decide whether to reaffirm, revise, restrict, or withdraw the affected approval
  • f.        Execute the sale contract or lease only through the authorized signatory and within the exact approved commitment and conditions.
  • g.      Authorize the next work or phase within defined limits; preparing an IT consultant or integrator bid list or proposed supplier selection does not authorize procurement.
  • h.      Approve handoff of the authorized business case, preliminary requirements, alternatives appraisal, feasibility evidence, cost and schedule ranges, commercial terms, decision record, and risk register; assign and accept outstanding actions.
  • 7.      Authorize Project Definition — Step 3.1 Project Management Team:
  • a.      Authorize the Project Definition mandate, work scope, resource limits, governance, and organizational responsibilities; this approval may precede property commitment when needed to resolve critical uncertainty.
  • b.      Assign the project team.
  • c.      Approve the project charter as the controlled mandate and authorization for the project manager and team.
  • d.      Establish delegated decision limits and mandatory concurrence requirements.
  • e.      Approve specialist scopes and coordination responsibilities.
  • f.        Approve the organizational change-management plan and its funding.
  • g.      Establish applicable information and AI-use controls where relevant.
  • 8.      Approve Program of Requirements (POR) — Step 3.2 Translating Business Priorities into a Program of Requirements:
  • a.      Resolve essential needs versus enhancements and requirement conflicts.
  • b.      Confirm applicable mandatory obligations and owner-selected performance targets.
  • c.      Approve the program of requirements (POR) as the basis of design.
  • d.      Approve the reconciled scope, budget, site, and schedule baseline. If definition reveals a material mismatch, refer it to the sponsor to revisit the affected strategic or real estate approval before proceeding.
  • e.      Assign acceptance measures and later verification responsibilities.
  • 9.      Approve Delivery Strategy and Service Procurement Gates — Step 3.3 Align Delivery and Procurement with Project Objectives, particularly Sections 3.3.1–3.3.7:
  • a.      Approve the project delivery and sourcing strategy aligned with the POR, budget, schedule, risk tolerance, and responsibility boundaries.
  • b.      Confirm the contract and payment assumptions, funding, procurement procedure, and delegated authority required for each service package.
  • c.      Approve the solicitation scope, published evaluation criteria, selection procedure, and budget limits before going to market.
  • d.      Authorize issuance of RFQs or RFPs for the specified services; solicitation approval does not authorize selection or award.
  • e.      Approve provider selection against the published criteria and the negotiated award terms through the applicable approval process.
  • f.        Separately authorize contract award after confirming scope, funding, and delegated authority.
  • g.      Confirm contract-execution authority, specified service limits, and applicable notice-to-proceed requirements. Award or execution does not automatically authorize construction or subsequent phases; early preconstruction services require their own authorization.
  • 10. Authorization to Proceed with Design — Sections 3.3.8 Project Readiness Review and 3.3.9 Review and Approval:
  • a.      Approve the final business case reconciled by the project team with the charter, POR, scope, budget, schedule, risk, and delivery and information plans.
  • b.      Accept the steering committee’s readiness findings and sponsor’s recommendation, including the status of every condition and the required action and accountable owner for each gap.
  • c.      Decide whether to authorize, authorize with conditions, modify, defer, return for analysis, or refuse.
  • d.      Specify permitted work, funding limits, unresolved conditions, closure authority, and deadlines.
  • e.      Assign handoffs, monitoring, and reassessment responsibilities.
  • f.        Issue a notice to proceed with design only when the authorized owner decision and applicable contractual conditions permit that specified work; construction requires separate applicable authorization.

Final Authorization Gate—Business Case and Owner Decision

The business case develops throughout all nine steps. At the final authorization gate—the Project Readiness Review—the team brings the evidence together to determine whether the proposed investment is justified, feasible, and sufficiently defined to proceed to design. The owner then decides whether to advance, under what conditions, and assigns  outstanding actions for resolution. This decision does not replace earlier approvals for property commitments or authorize every subsequent execution activity.

The review should address:

  • Strategic fit: Does the proposal address the organizational need and intended outcomes?
  • Alternatives and value: Why is the proposed approach preferred? Has the owner considered modifying, deferring, or not proceeding where appropriate?
  • Defined investment: Are requirements, scope, quality, schedule, budget, funding and delivery approach sufficiently clear?
  • Feasibility: Are technical, operational, financial, schedule, regulatory and organizational conditions understood?
  • Uncertainty and risk: Which assumptions or issues remain unresolved, and what conditions or risk mitigation measures are needed?
  • Authority and next actions: Who makes the decision, what is being authorized, and how will the decision be recorded and carried forward?

The owner may authorize the project, authorize it with conditions, modify it, defer it, request further analysis, select another alternative or decide not to proceed. The owner should document the decision and its rationale, together with any conditions and responsibilities.

The gate encompasses all nine process steps. It confirms the business case and feasibility developed through the process. It does not replace earlier approvals needed for commitments, such as a property transaction.

The Process Creates Value By

ALIGNING

DECISIONS

Analyze needs

Integrate Information

Align stakeholders

Define requirements


REDUCING UNCERTAINTY

Avoid false starts

Reliable forecasts

Test feasibility

Evaluate alternatives


IMPROVING

OUTCOMES

Reduce risk

Improve delivery

Meet expectations

Create greater value


1.0 Strategic Planning Phase – Begin with Strategy

The Strategic Planning Phase defines what the organization mustachieve before assuming a real estate, building, or workplace solution. The team clarifies the organization’s vision, mission, goals, and strategies; determines how real estate, buildings, and workplaces can support those priorities; and identifies the implementation steps, resources, and measures of success needed to put the strategy into practice. For private-sector organizations, the strategy should supportcustomer satisfaction and demand for products or services. For public-sector organizations, it should meetconstituent needs and usepublic funds effectively. The strategic planner leads the phase and is accountable to the project sponsor. Strategic advisors and business consultants support the planner with market and industry research, organizational and operating-model analysis, financial and scenario analysis, stakeholder facilitation, benchmarking, and preparation of the business case. The planner directs their work, integrates their findings with internal knowledge, resolves conflicts among recommendations, and remains accountable for the planning conclusions presented to the sponsor. The phase concludes with the planner’s presentation of evidence-based facilities decisions for sponsor validation and authorization of the next phase.

During strategic predesign, the strategic planner connects organizational strategy, facilities decisions, planned implementation commitments, and measures of success. The strategic planner defines how the organization will assess each project’s results against its original objectives and use those findings to guide future planning. The project sponsor reviews the strategic planner’s recommendations, resolves issues within the sponsor’s authority, and escalates decisions that require chief executive officer or administrator approval.

1.1 Executive Vision – A Compelling Image of a Desirable Future State

Executives or administrators should establish and communicate a compelling vision of the desired future state. A shared vision helps people understand how their roles contribute to organizational priorities, supports aligned decision-making, and focuses action on long-term value. Effective implementation of a vision includes the following practices:

  • Clarity Over Complexity: The end-state vision must be easily understood, memorable, and translatable across all levels of the organization.
  • Decentralized Autonomy: Once the vision is internalized by teams, executives must trust individuals and cross-functional groups to self-direct their tactical decisions in alignment with that shared outcome.
  • Continuous Communication: A vision cannot be a one-time announcement; leadership must continually tie day-to-day progress back to the overarching end-state to maintain momentum and focus.

1.1.1 Vision Session – Establish a Shared Direction

The strategic planner may lead a vision session with facilitation and research support from strategic advisors or business consultants. These providers help structure the inquiry, prepare relevant evidence, facilitate executive and stakeholder discussions, test assumptions, and document agreed outcomes without taking ownership of the organization’s decisions. The strategic planner brings together executives, critical stakeholders who share responsibility for outcomes, and the implementation team to articulate expectations, ambitions, and aspirations for the future. Participants clarify the mission, describe the desired end state, align goals and objectives, and explore concepts, ideas, and strategies without prematurely committing to a preferred solution. The strategic planner encourages open inquiry, makes differing expectations and priorities explicit, and resolves issues that could impede progress. When participants cannot resolve an issue, the strategic planner documents it and refers it to the project sponsor for decision or escalation. The resulting shared direction gives the team a clear basis for subsequent planning and implementation, identifies objectives and possibilities for further consideration, and assigns follow-up responsibilities.

1.1.2 Understand the Strategic Context – Competitive Forces Shaping the Organization

Before proposing a facilities solution, the strategic planner assesses the industry structure and external forces that can affect demand, profitability, resources, operating priorities, and the organization’s ability to create value. The strategic planner may use Michael Porter’s Five Forces framework as disciplined organizational assessment method and combine it with internal analysis, scenario planning, stakeholder input, and consideration of regulatory, technological, and social change.

Porter introduced the framework in “How Competitive Forces Shape Strategy” in 1979 and reaffirmed and extended it in “The Five Competitive Forces That Shape Strategy” in 2008. You can apply the framework to both private and public sector organizations. It explains how industry or jurisdictional structure influences long-run profitability or efficiency and how the value created within an operating environment is divided among competitors, suppliers, buyers, new entrants, and substitutes.

  • 1.      Threat of new entrants: The likelihood that new competitors can enter and erode margins or resources, considering barriers such as scale economies, capital requirements, customer or servicing switching costs, access to distribution, proprietary data, regulation, and network effects.
  • 2.      Bargaining power of suppliers: The ability of suppliers—including labor, landlords, cloud providers, specialized technology vendors, and infrastructure providers—to raise prices, restrict capacity, or shape terms.
  • 3.      Bargaining power of buyers: The ability of customers, constituents or clients to demand lower prices, higher quality, greater transparency, or more favorable terms.
  • 4.      Threat of substitutes: The availability of different products, services, technologies, or operating models that satisfy the same underlying need.
  • 5.      Rivalry among existing competitors: The intensity of competition through price, service, innovation, capacity, marketing, speed, and differentiation.

Competitive Force

Business Evidence

Digital & Platform Evidence

Potential Facilities Implications

Threat of new entrants

Capital intensity, scale, brand, regulation, and distribution access

Network effects, proprietary data, ecosystem access, interoperability, switching costs, and cloud-enabled speed to market

Favor scalable capacity, flexible commitments, rapid deployment, and access to talent and digital infrastructure.

Supplier power

Concentrated suppliers, scarce labor, specialized input, and limited alternatives

Cloud and AI infrastructure, specialized chips, proprietary APIs, data providers, platform rules, and critical technical talent

Identify infrastructure dependencies, resilience requirements, geographic concentration risk, and options for redundancy or substitution.

Buyer power

Purchase volume, price sensitivity, information, and low switching costs

Algorithmic comparison, digital transparency, low-friction switching, procurement platforms, and direct customer feedback

Support customer collaboration, service delivery, experience testing, and rapid adaptation without assuming that prestige space creates loyalty.

Threat of substitutes

Alternative products or services that meet the same need

Automated workflows, AI-enabled services, cross-industry platforms, remote delivery, and new consumption models

Prioritize adaptable space, prototyping, research, learning, and operational flexibility over fixed assumptions about work or service delivery.

Rivalry among competitors

Price competition, capacity growth, advertising, service levels, product differentiation, regulatory restrictions and politics

Rapid feature imitation, data-driven personalization, ecosystem lock-in, continuous releases, and winner-take-most dynamics

Align facilities with distinctive capabilities, workforce effectiveness, operating efficiency, and speed—not with competitor amenity checklists.  Seek regulatory changes, variances, exemptions

The strategic planner should define the relevant market carefully and examine how digital technologies change the expression of each force. In platform and ecosystem businesses, competitors, suppliers, buyers, and complementors may occupy more than one role, and value may be created across several connected markets or jurisdictions. Network effects, multihoming, interoperability, data access, platform governance, and switching costs can strengthen or weaken entry barriers and bargaining power. Developers, channel partners, technology integrators, and other providers of complementary products can increase the value of a platform while also influencing dependence, switching costs, and bargaining power. Analyze them explicitly when the organization competes through an ecosystem.

Use competitive analysis to identify organizational capabilities and constraints before proposing physical responses. For each material force, document the evidence, expected change, strategic implication, and facilities requirement. Possible responses may involve location, capacity, lease flexibility, specialized environments, collaboration or learning settings, technology infrastructure, resilience, or portfolio options.

1.1.3 Translation of Organizational Strategy into Facilities Initiatives

Using the competitive analysis, classify each business / service unit’s strategic position and priorities for allocating resources. This approach compares units on a matrix with two dimensions: the potential of the market and the potential of the business / service unit within that market.

The matrix helps identify where to invest resources by distinguishing three strategic positions: harvest, hold, or build. These indicate whether to draw value from existing investments, maintain the current position, or invest in growth. Use the supporting facilities strategy matrix to translate the business / service unit positions into options about sites, buildings, and workplaces.  

1.1.4 Selecting Facility Options

Evaluate the facilities options against organizational priorities and select the combination that supports each business / service unit’s direction: expansion, optimization or contraction. Each decision then will have a clear connection to the strategy it supports.

1.1.5 Plan for Change – Expand, Optimize, Contract, Integrate

Determine whether each business unit should expand, optimize existing resources, or contract. A merger or acquisition is a major change event rather than a single portfolio outcome; it may create simultaneous needs for growth, consolidation, divestment, relocation, and workplace integration. Consider four key resources—people, technology, space, and place (location)—and vary their mix according to each unit’s strategic position.

Plan for both sudden and gradual change. Mergers, acquisitions, and divestitures can create abrupt shifts in portfolio capacity, location requirements, ownership obligations, operating models, and workplace standards. Changes in demand, staffing, technology, business strategy and political leadership can alter facilities needs over time. Use scenarios, decision gates, and phased implementation to determine how the portfolio can adapt while maintaining business continuity.  Whatever the situation, the strategic planner should define the response for each unit and locationrather than assume that the entire organization is moving in one direction.

1.1.6 Match Growth to Demand and Resources

For expansion, establish how much capacity is needed and when it must be available. Growing business units may need capacity ahead of demand to avoid missed opportunities. Evaluate how much space to buy, build or lease, and plan growth in increments that can adjust to cash flow and business cycles.

1.1.7 Optimize Existing Resources and Work Processes

For optimization, assess how existing facilities and resources can better support the organization’s work process. Consider the following ways to improve resource use and work processes:

– Consolidate fragmented space into fewer locations

– Relocate existing business / service units to new locations

– Retrofit facilities to take advantage of new technologies

– Put assets to their “highest and best use” - the most appropriate and valuable use

– Improve distribution logistics or networks

– Improve work processes and how work is organized

– Maximize the use or reuse of existing space

1.1.8 Plan Contraction in Its Market Context

For contraction, identify surplus facilities, opportunities to use remaining space more effectively and contingency options. Assess whether facilities can be sold or subleased under prevailing market conditions. Do not assume that surplus space can be released quickly or easily.

1.1.9 Integrate Merger and Acquisition (M&A) Facilities

For each facility in a combined portfolio, evaluate operational criticality, condition, capacity, utilization, location, contractual obligations, adaptability, transition cost, and continuity risk before recommending retention, repurposing, consolidation, relocation, or disposition.

The strategic planner leads a coordinated facilities-integration strategy for a proposed merger or acquisition and connects transaction objectives, portfolio evidence, operational requirements, workforce considerations, and implementation risk. Before recommending expansion, optimization, consolidation, relocation, or disposition, the strategic planner directs the following analysis of the combined facilities portfolio and presents the findings to the project sponsor.

Portfolio Synergy and Consolidation Assessment

Audit and document facility conditions, capacity, utilization, operating costs, and lease or ownership obligations across both organizations to identify duplication, constraints, and potential synergies.

Test alternative portfolio configurations across short-, medium-, and long-term planning horizons—for example, one year, two to three years, and four to ten years—to identify a target portfolio that improves operational efficiency while maintaining business continuity and essential public or customer services.

Quantify proposed footprint changes, consolidation opportunities, one-time implementation costs, recurring savings, and flexibility requirements so that portfolio decisions balance capital constraints, operational needs, and long-term agility.

Operational Due Diligence and Facilities Alignment

Evaluate facility condition, deferred maintenance, code and accessibility compliance, building systems, environmental conditions, and technology infrastructure early enough to identify liabilities and required investment.

Assess geographic distribution in relation to customers, workforce availability, transportation, supply chains, critical operations, and business-continuity requirements to determine whether the combined portfolio supports the integration strategy.

Classify facilities by operational value and adaptability, distinguishing standardized workplaces from specialized research and development, production, cultural, or public-facing facilities. Use the classification, together with condition, cost, location, and business requirements, to support retain, repurpose, consolidate, or divest decisions.

Change Management and Cultural Integration Plans

Translate the combined organization’s operating model, employee experience goals, and cultural objectives into workplace standards and design criteria. Identify where common standards are required and where political, business, regional, or regulatory differences justify variation.

Sequence facility transitions, relocations, consolidations, and closures around operational dependencies, workforce needs, approvals, and business-continuity requirements. Communicate timing, decision points, responsibilities, and support resources clearly.

Establish baseline measures and key performance indicators (KPIs) before implementation, then evaluate whether the integrated portfolio achieves the approved cost, utilization, operational, employee-experience, and cultural outcomes. Use the findings to adjust the portfolio and inform future integration decisions.

1.2 Portfolio Analysis

1.2.1 Digital Information and AI Operating Model

The strategic planner establishes the information and artificial-intelligence operating model for strategic predesign and submits it to the project sponsor for approval. The model identifies the decisions to support, authoritative internal and external sources, data owners and stewards, common definitions, quality thresholds, refresh cycles, permitted uses, retention requirements, access controls, and evidence needed to reproduce material analyses. The strategic planner treats documents, datasets, geospatial layers, models, assumptions, prompts, code, and analytical outputs as governed project information rather than informal working files.

The strategic planner uses enterprise architecture and a federated data approach to connect approved systems-of-record without creating unnecessary duplicate repositories. The team may combine human-resources, finance, portfolio, lease, facilities, maintenance, workplace, security, sustainability, building-automation, customer, and operational data through governed application programming interfaces, data pipelines, semantic models, or controlled extracts. The team maintains lineage from each decision metric to its source, transformation, owner, date, and confidence level, and preserves immutable snapshots of the evidence used at each decision gate.

The strategic planner uses AI only for defined, risk-proportionate tasks such as document classification, entity extraction, semantic search, summarization, anomaly detection, forecasting, scenario generation, and comparison of alternatives. A named human remains accountable for every material output. The team verifies claims against authoritative sources, evaluates accuracy and bias, protects confidential and personal information, records the model and version, prompt or workflow, input sources, date, reviewer, limitations, and approval, and provides a non-AI fallback when the organization cannot validate or safely operate the AI-enabled process.

With the information and AI operating model established, the strategic planner uses the governed evidence to forecast organizational demand. The following work connects the information framework to long-range requirements, financial assumptions, and workforce projections.

Establish a rigorous, multidimensional view of future organizational requirements over an appropriate long-range planning horizon, typically three to ten years. State the assumptions, scenarios, sources, and level of confidence used in the forecast.

Partner with Finance to align revenue projections, business-line growth plans, margin targets, capital expenditure (CAPEX) limits, and affordability assumptions with the demand forecast.

Collaborate with HR to map headcount growth, attrition rates, and remote/hybrid work distributions down to the business unit level.

1.2.2 Sector-Specific Projections

The strategic planner does not determine facility capacity by headcount alone. Depending on the organization’s sector, forecasts of production, service demand, population, enrollment, patient volume, or other relevant demand measures provide additional bases for establishing required capacity.  For example:

  • ·       Manufacturing and service centers: Define the unit of production or service used to measure capacity, then obtain the business unit’s long-range forecast in that unit. Use the forecast to establish the facilities capacity required over the planning horizon.
  • ·       Public Sector/Municipalities: Incorporate municipal demographic and population growth forecasts.
  • ·       Higher Education: Integrate student enrollment, faculty growth, and academic program shifts.
  • ·       Healthcare: Factor in patient volume trends, service-line expansion, and technological shifts in care delivery.

1.2.3 Supply Capacity and Portfolio Diagnostics

Use strengths, weaknesses, opportunities, and constraints (SWOC) analysis to examine individual properties. In the property review, constraints identify limits affecting suitability, feasibility, or commitment. Audit existing physical assets to evaluate capacity, operational efficiency, and contractual obligations.

Measure actual spatial occupancy versus design capacity across all properties using Integrated Workplace Management Systems (IWMS) and utilization metrics.

Assess physical assets against enterprise design standards, technological infrastructure readiness, functional adequacy, and environmental/ESG compliance.

Review lease administration reports to track critical real estate triggers, including hard expiration dates, renewal option windows, contraction rights, and financial liabilities.

1.2.4 Occupant Experience and Utilization Feedback Loop

Quantify employee sentiment, workplace effectiveness, and physical friction points through structured surveying.

Execute annual standardized occupant surveys measuring satisfaction with workplace services, acoustic comfort, technology reliability, and collaborative spaces.

Aggregate survey results into a comparative property index to rank portfolio assets from highest to lowest performing, highlighting properties requiring immediate intervention.

1.2.5 Stakeholder Alignment & Business Unit Review

Reconcile quantitative portfolio data with qualitative leadership insights through structured stakeholder engagement.

Meet directly with operational leaders to uncover uncaptured business needs, workflow bottlenecks, and localized growth plans.

Cross-reference operational feedback with portfolio analytics and workplace evaluations to brainstorm potential real estate initiatives (e.g., consolidation, relocation, renovation, or hybrid optimization).

1.2.6 Strategic Challenge

Synthesize the data streams into a clear, bound definition of the strategic challenge facing the enterprise. Compare long-range demand forecasts against current supply capacity to identify quantitative and qualitative deficits.

Compare the identified organizational needs with the capabilities and constraints of the existing built environment. State the gap as a bounded problem—for example, reconciling hybrid work adoption with inflexible long-term lease obligations or addressing functional adequacy gaps in regional R&D hubs—without selecting a solution prematurely. Use the problem statement to inform scenario evaluation and business case development.

1.2.7 Scenario Planning – Develop and Evaluate Alternative Futures

Scenario planning begins with a bounded problem and common assumptions, develops distinct alternative futures, tests each alternative against the same operational, workplace, location, delivery, financial, and risk criteria, and concludes with a documented recommendation and unresolved conditions.

Use scenario planning to establish a defensible direction before committing to real estate decisions. Within defined problem boundaries, compare how alternative real estate strategies, building prototypes, hybrid work models, and operational responses perform under different future conditions. Evaluate them against explicit criteria for workplace and cultural requirements, financial implications, and risks. The strategic planner translates the comparative findings into an evidence-based recommendation for executive review, sponsorship, and subsequent implementation. Scenario planning tasks encompass:

  • ·       Define the Problem Boundaries: Define the parameters each scenario must address, including headcount growth, geographic location, work process and styles, functional facility adequacy, real estate requirements, and capital expenditure (CAPEX) and time frame constraints.
  • ·       Establish the existing situation: Prepare an analysis of strengths, weaknesses, opportunities, and threats (SWOT) for the existing situation. Use that analysis as the baseline for comparing alternatives.
  • ·       Develop Alternative Futures: Develop distinct operational scenarios, such as a return to pre-COVID baselines, moderate hybrid models, or aggressive flexible models, and evaluate staying in place versus relocating.
  • ·       Compare Scenarios: Evaluate each alternative consistently:
  • o   Workplace Experience and Culture: Assess how well the workplace experience aligns with organizational maturity.
  • o   Location Strategy: Compare single-location, split campuses, and new .
  • o   Project delivery options: Compare traditional design-bid-build, construction manager at risk, design-build, design-build-leaseback, and public-private partnership strategies.
  • o   Advantages and Disadvantages: Weigh capital and operating expenditures, lease terms and conditions, space efficiency, timeline, and change management requirements.
  • ·       Assess Financial Implications and Risk: Evaluate high-level capital and operating expenditures, cash flow implications, and technical due diligence findings.
  • ·       Recommend a path to action: Present leadership with an evidence-based recommendation that states conditions and unresolved issues, secures project sponsorship, and guides site selection, lease negotiations, and project definition.

1.2.8 Strategic Budget Model Development (CAPEX, Rent, OPEX)

Translate spatial requirements, market options, and workplace strategies into a multiyear financial model to assess the plan’s economic viability. Use financial scenario modeling and discounted cash flow (DCF) analysis at a level proportionate to the initiative’s scale, complexity, and risk. Where available, use Integrated Workplace Management Systems (IWMS) cost data to support and reconcile the estimates.

Partner with Finance and procurement teams to estimate upfront project costs, including tenant improvements (TI), architectural/engineering fees, IT/AV infrastructure build-out, furniture, fixtures, equipment (FF&E), and contingency reserves.

Analyze base rent schedules, escalation clauses, free-rent concessions, and landlord tenant-improvement allowances across alternative lease scenarios or renewal options.

Estimate ongoing operational costs (OPEX), including facilities management, maintenance, utilities, cleaning, security, property taxes, and operating expense pass-throughs.

Consolidate capital expenditure (CAPEX), rent, and operating expenditure (OPEX) into a cash-flow model of total cost of operation (TOC) over the lease term or asset holding period. Compare alternatives using net present value (NPV) on that common basis.

1.2.9 Project Sponsor Review, Buy-in and Approval to Proceed

The strategic planner obtains formal validation from the project sponsor and business-unit, or political leaders. The strategic planner confirms that the business case supports advancement to real estate evaluation or, when the initiative requires no real estate decision, to project definition.

The project sponsor records the approved direction, authorized next-phase work, conditions, and unresolved issues. This approval does not replace transaction authorization or the final Project Readiness Review before design.

Package the findings from the portfolio analysis, demand forecasts, spatial programming, and financial budget models into an executive-ready proposal.

Review the proposed options, trade-offs (e.g., cost vs. functionality), risks, and qualitative benefits directly with project sponsors and key business leaders.

Assess the initiative against enterprise-wide investment criteria and risk thresholds.

1.3 Prepare the Business Case – the Investment Decision

The business case is not a one-time deliverable. It begins with the strategic need and alternatives, incorporates property and feasibility evidence during the Real Estate Phase, and is reconciled with the program, budget, schedule, risk, and delivery strategy before the Project Readiness Review.

The strategic planner concludes the Strategic Planning Phase by preparing the initial business case as a decision-support document and scales its format to the organization and the investment. The business case remains a controlled, evolving record through the Real Estate and Project Definition phases: the portfolio and asset manager updates it with real estate findings, and the project team reconciles it with the defined requirements, budget, schedule, risk, and delivery strategy. The strategic planner supports continuity of the strategic rationale across these updates. A comprehensive business case typically includes:

1.3.1 Executive Summary

A concise overview of the proposal’s expected outcomes, and the final recommendation.

1.3.2 Problem or Opportunity Statement

The strategic driver behind the initiative (e.g., operational inefficiency, regulatory change, or market expansion).

1.3.3 Strategic Alignment

How the project supports the organization's overarching goals and long-term strategy.

1.3.4 Analysis of Alternatives

Evaluation of multiple options (e.g., build vs. buy, different locations, or phased approaches) compared against common criteria.

1.3.5 Financial Assessment and ROI

Cost estimates, revenue projections, cash flow forecasts, return on investment (ROI), and payback periods.

1.3.6 Risk Analysis and Mitigation

Identification of potential roadblocks—such as schedule delays, financial exposure, or stakeholder resistance—along with mitigation strategies.

1.3.7 Implementation Roadmap

A high-level timeline, resource requirements, governance structure, and key decision gates.

1.3.8 Secure Documented Sponsor Sign-off

Secure documented sponsor sign-off on the preferred planning direction, authorized next-phase work, and any conditions or unresolved issues. Transition from portfolio planning to real estate evaluation or project definition, as appropriate.

1.3.9 Review and Update the Business Case

Review and update the business case throughout the real estate and project definition phases, through the Project Readiness Review and authorization to proceed.


2.0 Real Estate Phase

The Real Estate Phase determines whether, where, and under what conditions a real estate intervention can meet the organization’s needs. The real estate team translates approved strategic-planning outcomes into an evidence-based real estate direction and, when required, conducts location, site, or property selection and an acquisition or lease transaction. The portfolio and asset manager leads the phase and reports to the project sponsor, who reports to the chief executive officer or administrator. Real estate advisors provide market intelligence, location strategy, brokerage, property identification, financial and occupancy analysis, transaction structuring, due-diligence coordination, and lease or acquisition negotiations. The portfolio and asset manager defines the assignment, directs and evaluates the advisors’ work, integrates specialist findings, manages conflicts of interest, and remains accountable for the recommendation to the project sponsor.

2.1 Location Strategy and Site-Selection Criteria

To prepare for a property search, the portfolio and asset manager directs the real estate advisor to develop market and location evidence, identify feasible search areas, and test ownership, lease, renovation, relocation, and flexible-occupancy options. The advisor helps translate the approved strategy and preliminary requirements into measurable location, site, and property criteria; recommends market-survey and scoring methods; and identifies information gaps and specialist investigations. The portfolio and asset manager validates the criteria with internal stakeholders, obtains the required approvals, and controls their use throughout the long-list, shortlist, due-diligence, and recommendation process.

2.1.1 Real Estate Strategy

Based on the organizations’ use, the real estate team classifies the enterprises assets as core or flagship properties, operational hubs, flexible or swing space, or candidates for monetization or disposition.

Using the classification, they evaluate capacity, occupancy, utilization, performance, and geographic overlap to identify colocation, subleasing, consolidation, or footprint reduction that would optimize the portfolio.

Finally, they analyze the financial implications of capital allocation, control, flexibility, residual value, and stability over a common planning horizon to determine if the organization should own or lease the existing properties and properties under future consideration.

The real estate team develops real estate strategies that connect the approved strategic facilities direction with portfolio, location, and property decisions and presents those strategies to the project sponsor.

2.1.2 Location and Site-Selection Criteria

After the project sponsor validates the real estate strategy, the portfolio and asset manager and real estate advisor confirm the business problem, intended outcomes, demand range, affordability limits, schedule, risk tolerance, decision authority, and measures of success. They document the strategy assumptions and determine whether the organization should optimize existing space, renovate, relocate, use flexible occupancy, or begin a location and property search.

The team then translates the approved strategy into preliminary requirements statement and a structured hierarchy of location, site, and property criteria. The brief defines functional and spatial needs, workforce and customer access, capacity and utilization, technology and security, utilities and digital connectivity, accessibility, sustainability, resilience, business continuity, regulatory constraints, timing, and financial objectives. The team distinguishes mandatory requirements from preferences, defines measurable indicators and acceptable ranges, and assigns evaluation weights before reviewing alternatives.

To prepare the criteria for use, the portfolio and asset manager establishes the evidence plan and data register. The register identifies authoritative internal records and external sources for labor markets, demographics, customers, transportation, supply chains, utilities, broadband, climate and natural hazards, environmental conditions, adopted plans, zoning, entitlements, incentives, market availability, costs, and regulatory requirements. For each source, the team records ownership, permitted use, coverage, date, method, resolution, limitations, and reviewer; reconciles conflicts; documents uncertainty; and preserves the evidence baseline used to evaluate alternatives.

The team then defines the evaluation method, scoring scale, financial logic, risk framework, and analytical tools before the market search begins. The team may use geographic information systems, portfolio analytics, scenario models, and controlled AI-assisted workflows to organize evidence, compare criteria, and test sensitivity, but qualified specialists validate legal, environmental, engineering, valuation, and other high-consequence findings. The team records assumptions, data and model versions, calculations, reviewers, and material limitations so another reviewer can reproduce the analysis.

Before reviewing candidate locations or properties, the portfolio and asset manager tests the criteria with strategic planning, finance, operations, facilities, information technology, human resources, legal, security, and affected business units. The team resolves overlaps and conflicts, confirms that each criterion relates to an approved objective or risk, and tests the framework against representative scenarios without allowing a favored property to redefine the strategy. The portfolio and asset manager submits the criteria, weights, evidence baseline, and evaluation method to the project sponsor for approval and escalates decisions beyond the sponsor’s authority to the chief executive officer or administrator.

After approval, the portfolio and asset manager issues the criteria and supporting requirements as the controlled basis for the market survey. The evaluation package identifies mandatory screening thresholds, weighted comparison criteria, evidence requirements, scoring instructions, decision gates, required specialist reviews, and the process for recording exceptions or revising assumptions. The real estate team applies the same framework to the long list, shortlist, site visits, technical due diligence, financial analysis, and final recommendation so that market evidence informs the strategy without replacing it.

2.2 Market Survey and Technical Due Diligence

The real estate team will narrow the long list to a shortlist and then to a preferred property by applying approved mandatory constraints, weighted preferences, market evidence, technical due diligence, financial analysis, and authorization requirements consistently at each stage.

2.2.1 Identify and Screen the Long List of Properties

The portfolio and asset manager engages qualified brokerage or real estate advisers to identify a long list of properties and assess each property against the approved functional, cultural, financial, and location criteria. The real estate team screens the long list, creates a shortlist, and arranges site visits with the project sponsor, affected business leaders, and appropriate technical specialists.

2.2.2 Create a Shortlist and Conduct Site Visits

Use market-survey and site-visit findings to screen each property against the preliminary requirements, including availability, occupancy timing, commercial terms, functional fit, accessibility, infrastructure, and material risks. Record the evidence supporting each assessment and the reasons for excluding alternatives. Maintain credible fallback options while conducting detailed feasibility and due diligence on the preferred property.

2.2.3 Coordinate Specialist Due Diligence

The portfolio and asset manager directs the real estate advisor to coordinate qualified legal, environmental, survey, architecture, engineering, technology, valuation, and other specialists according to the approved due-diligence plan. The real estate advisor assembles and tracks the investigations, identifies inconsistencies and unresolved matters, and integrates the findings into the property comparison and transaction strategy. Architecture and engineering specialists assess property capacity, accessibility, major building systems, utility and technology infrastructure, code implications, and suitability for the preliminary requirements. Legal and other qualified specialists review zoning, land-use and entitlement requirements, environmental conditions, title and survey matters, contractual constraints, and approval timelines. The portfolio and asset manager evaluates the combined findings, determines whether the evidence supports continued consideration, and presents material risks and required decisions to the project sponsor.

2.2.4 Document Upgrades, Responsibilities, Dependencies, and Risks

Document required upgrades, landlord and tenant responsibilities, access requirements, delivery dependencies, and unresolved issues. For each material risk, assess likelihood and potential effects on feasibility, cost, schedule, operations, and business continuity; assign an accountable party and define the resolution or mitigation required before commitment. Carry residual risks into the risk register with explicit decision requirements.

2.2.5 Define IT Infrastructure and ISP Requirements

For information technology, define infrastructure and service requirements, planning guidelines, a high-level scope of work (SOW), budget assumptions, and schedule dependencies. Evaluate internet service provider (ISP) options against those requirements and the occupancy schedule. Treat any proposed ISP letter of intent (LOI), service order, or other commitment as subject to the organization’s authorization, procurement, and legal-review requirements rather than as an automatic outcome of technical due diligence.

Scale due diligence to the financial, legal, operational, environmental, and technical exposure and to the reversibility of the proposed decision. Resolve critical uncertainties before commitment, and document and authorize residual risks.

2.2.6 Alternatives Evaluation and Business Case Development

Use the market survey and technical due diligence findings to update the business case. Carry forward the same requirements baseline and decision criteria so that property-specific findings inform, rather than replace, the organizational objectives.

Develop feasible alternatives, including staying and renovating, relocating, hub-and-spoke models, and flexible multi-location arrangements. Include an existing-space optimization or no-project baseline where credible. Compare alternatives against the same demand assumptions, planning horizon, success criteria, and decision criteria. Use future scenarios to test how changes in growth, attendance, delivery timing, and market conditions affect operational resilience and the preferred alternative.

Update the space calculator and prepare preliminary test fits and blocking and stacking plans to assess whether the preferred alternative can accommodate the preliminary requirements. Where appropriate, prepare a site opportunity plan to test the property's suitability. Use these studies to confirm feasibility rather than prescribe detailed design. Develop a preliminary project scope, occupancy schedule, and high-level capital expenditure (CAPEX) estimate from the findings.

Compare CAPEX, operating expenditure (OPEX), lease commitments, and potential business disruption costs over a common planning horizon. Include fit-out, relocation, temporary accommodation, incentives, contingencies, and end-of-term obligations where applicable. Evaluate the resulting cash flows using a consistent net present value basis. Distinguish verified inputs from estimates and use sensitivity testing to show uncertainty. Present affordability, lifecycle value, qualitative benefits, and material trade-offs together in the business case; the lowest rent is not necessarily the best strategic outcome.

Develop financial models that account for the total cost of occupancy (TOC) including capital expenditure (CAPEX), operating expenditure (OPEX), rent and lease obligations, taxes, maintenance and replacement costs, tenant-improvement allowances, incentives, and end-of-term obligations over a common analysis period.

Evaluate exit rights, expansion and contraction options, renewal and termination provisions, phased development triggers, and other mechanisms that allow the portfolio to respond to changes in demand, funding, or organizational priorities.

Determine the highest and best use of the properties by evaluating legally permissible, physically possible, financially feasible, and maximally productive uses of the property. Consider adaptive reuse, increased density, air-rights development, or disposition of surplus land only when supported by market, regulatory, technical, and financial analysis.

Reconcile operational fit, accessibility, sustainability, resilience, and user needs with affordability and the occupancy schedule. Account for approvals, required upgrades, fit-out, and transition dependencies when testing deliverability. Include a decommissioning plan for the current space where applicable. Upload the decommissioning plan into the project folder.

The portfolio and asset manager tests how space capacity, occupancy arrangements, and commercial terms respond to changing business needs. The portfolio and asset manager compares the cost and practicality of expansion, contraction, and other flexibility provisions under the demand scenarios rather than treating flexibility as an unqualified benefit. Based on the analysis, the portfolio and asset manager submits the Real Estate Approval Request to the project sponsor, who decides within delegated authority or seeks approval from the chief executive officer or administrator.

2.3 Transaction Readiness and Lease Negotiation

2.3.1 Confirm the Preferred Alternative and Authority to Negotiate

Before negotiations begin, confirm approval of the preferred alternative and the authority to negotiate. Translate that direction into proposed commercial terms, including contraction and expansion rights, renewal options, and termination clauses where achievable. Evaluate those provisions against the operational flexibility established in the business case.

2.3.2 Negotiate Commercial and Delivery Terms

Address delivery condition, access for investigations and fit-out, improvement responsibilities, and occupancy timing. Have qualified legal and real estate advisers assess the terms and any conditions needed to protect unresolved feasibility requirements. Negotiation supports the strategy; it does not substitute for technical validation or project definition.

2.3.3 Confirm Decision Gates and Commitment Authorization

Different approvals authorize different commitments. The portfolio and asset manager should tie strategic direction, real estate negotiation, property commitment, project definition, procurement award, and transition to design to a named executive, defined evidence, recorded conditions, and the limits of the authority granted.

Use explicit decision gates to confirm executive alignment on the preferred alternative, establish financial authority, and determine readiness to issue letters of intent (LOIs) or execute leases. Assess the binding effect of proposed documents with legal counsel rather than assuming an LOI is nonbinding.

Authorize commitment only when requirements, feasibility, affordability, schedule, and material risks have been reviewed and accepted. Where project definition is needed to resolve critical uncertainty, complete that work before an irreversible commitment.

2.3.4 Prepare the IT Consultant and Integrator Bid List

Prepare an IT consultant and integrator bid list aligned with the high-level SOW. Document the status of any ISP order and its relationship to the fit-out and occupancy schedule. Place orders only after the appropriate authorization; preparation of a bid list or proposed supplier selection does not authorize procurement itself.

2.3.5 Update the Business Case and Maintain Decision Records

The portfolio and asset manager updates the business case and presents it to the project sponsor for approval. The portfolio and asset manager records the sponsor, authorized executive, approval thresholds, agreed evaluation weights, and conditions for proceeding, revising, deferring, or stopping. The project sponsor decides within delegated authority and seeks approval from the chief executive officer or administrator when required. A board, legislature, governor, or municipal authority may also hold approval-authority under applicable governance requirements.

Maintain the decision record, assumptions register, and risk register throughout the phase so that each approval and the rationale for the preferred alternative remain traceable.

2.3.6 Real Estate Phase Completion and Transition to Project Definition

The portfolio and asset manager recommend advancement when the evidence supports the preferred alternative and the updated business case. The project sponsor reviews the recommendation and obtains approval from the chief executive officer or administrator when required by the organization’s authority thresholds.

The portfolio and asset manager transfers the authorized business case and supporting baseline to the project manager. The handoff includes the strategic objectives and success criteria; preliminary requirements brief and demand assumptions; alternatives evaluated and selection rationale; site and building feasibility findings; cost and schedule ranges; proposed or authorized commercial terms; decision record; and risk register with unresolved matters, responsible parties, and required decisions. The portfolio and asset manager also prepares the IT consultants and integrators bid list.

During project definition, the project manager develops the preliminary requirements brief into the program of requirements and reconciles scope, performance requirements, budget, schedule, risk, and delivery approach against the accepted baseline. The steering committee reviews material trade-offs. If the work reveals a material mismatch, the project manager reports it to the project sponsor, who directs the team to revisit the real estate decision before proceeding and escalates the matter to the chief executive officer or administrator when required.

Prepare internal communication announcing the property selection decision and consider a press release where the project is significant to the community.

Advance with an authorized direction, agreed requirements baseline, credible cost and schedule ranges, and assigned responsibility for open issues. Carry the intended outcomes and success criteria into the project definition phase.

3.0 Project Definition Phase

The Project Definition Phase brings governance, programming, workplace, technology, and technical work together for the Project Readiness Review and the sponsor’s recommendation on whether to authorize transition to design. Construction remains subject to its separate applicable authorizations. The project manager leads the phase and reports to the project sponsor. A steering committee oversees the phase; both the sponsor and the steering committee report to the chief executive officer or administrator. Programming and workplace consultants facilitate stakeholder engagement, analyze work processes and utilization, develop space and performance requirements, test workplace concepts, and prepare the Program of Requirements. IT and audiovisual consultants define digital, network, collaboration, security, integration, and technology-room requirements and coordinate them with the program, budget, schedule, and procurement plan. Architecture and engineering specialists test feasibility, codes, site and building constraints, system capacity, resilience, sustainability, cost, and constructability without prematurely converting programming requirements into a preferred design. The project manager defines each provider’s scope, coordinates interfaces, resolves gaps and overlaps, integrates deliverables, and remains accountable for the project-definition recommendation.

3.1 Project Management Team

3.1.1 Assign Project and Information Technology Managers

The project sponsor assigns a project manager and an information technology manager to the initiative. The project manager leads the phase, reports to the sponsor, and coordinates enterprise participants and external service providers. Based on the project’s scale and risk, the project manager defines and procures the required programming, workplace, IT/AV, architecture, engineering, cost, scheduling, security, sustainability, and other specialist services. The project manager confirms responsibility boundaries, deliverables, interfaces, reliance on owner-provided information, review procedures, and decision authority before work begins. External providers advise, analyze, facilitate, and prepare deliverables within their contracted scopes; they do not replace owner decisions or the project manager’s accountability. The project manager holds the kickoff meeting, reviews the schedule, and assigns roles and responsibilities. The steering committee oversees alignment with scope, budget, schedule, risk, and organizational priorities.

3.1.2 Define and Procure Specialist Services

For major projects, define the technical scope of work (SOW) and begin the request for proposals (RFP) process for an external project manager or owner’s project manager (OPM), programming consultant, and IT consultant or systems integrator. Evaluate the proposals, select the preferred providers, negotiate agreements, and obtain the required approvals before award.

3.1.3 Establish the Common Data Environment and Information Responsibilities

 The project manager establishes a common data environment within the enterprise’s approved project and information-management platforms. The environment becomes the controlled point for project documents, records, models, issues, decisions, schedules, costs, risks, and approved datasets while source systems remain authoritative for their domains. The project manager defines information states and status codes, naming and classification rules, metadata, version and revision control, review and approval workflows, retention, audit history, and role-based access. The project manager authorizes team access, publishes the governance model and charter, and prohibits email attachments or personal storage from serving as the project record.

The project manager appoints an information manager or assigns equivalent responsibilities. That role maintains the project information standard, data dictionary, system integration map, information-delivery plan, model and document exchange requirements, quality rules, and handover requirements. The team defines organizational, asset, project, and exchange information requirements at the level needed for each decision and avoids collecting data with no identified user, purpose, owner, or maintenance plan.

The project manager requires open, machine-readable exchanges where practical so information can move among authoring, analysis, construction, and operations platforms without dependence on a single vendor. The team specifies stable identifiers and interoperable formats for building, geospatial, schedule, cost, issue, asset, and document information; validates exchanges automatically against defined information requirements; and retains the native files, open exchanges, validation reports, and approved published records needed for future use.

3.1.4 Establish Clear Governance and Accountability

The project manager establishes the governance framework for project definition and documents who recommends, agrees, performs, provides, and decides at each critical milestone. The project manager reports to the project sponsor and works under steering committee oversight. The sponsor decides matters within delegated authority; the steering committee oversees scope, budget, schedule, risk, and cross-functional alignment; and both the sponsor and steering committee refer matters beyond their authority to the chief executive officer or administrator.

The project manager formalizes this framework by aligning real estate, human resources, information technology, finance, legal, security, workplace operations, and external partners around defined responsibilities and shared decision procedures. Using a RAPID matrix, the project manager assigns decision roles, establishes escalation paths and reporting intervals, integrates major milestones and critical-path dependencies into the master schedule, and places decision gates where the project requires sponsor, steering-committee, or executive action. The project sponsor and participating business units then confirm the project mandate, business case, objectives, success criteria, scope boundaries, resource limits, and initial authority delegated to the project manager. The project manager records these agreements—together with the governance structure, milestone schedule, decision rights, and approval requirements—in the project charter and submits it to the project sponsor for approval. The approved charter becomes the formal authorization and baseline described in the following section.

3.1.5 Project Charter

A project charter is a concise executive document that formally authorizes a project and gives the project manager and team authority to apply organizational resources to the initiative. It serves as the foundational agreement among the project sponsor, executive management, and project team by documenting the project mandate, objectives, scope boundaries, and high-level governance. A comprehensive project charter typically contains:

  • Project Purpose and Business Case: The underlying strategic drivers, market needs, or portfolio deficits (identified during the portfolio analysis phase) that justify the initiative.
  • Project Objectives and Success Criteria: Measurable targets regarding schedule, budget, functional adequacy, and strategic alignment.
  • Scope Boundaries: High-level definitions of what is included in the project and, equally important, what is explicitly excluded to prevent scope creep.
  • Milestones and Master Schedule: High-level phase gates, target completion dates, and decision checkpoints.
  • Financial Parameters: Approved initial capital expenditure (CAPEX) limits and high-level operating cost expectations.
  • Roles and Governance: Identification of key project sponsors, executive leadership, and accountability frameworks (such as RACI or RAPID matrices).

The project charter connects strategic planning to project execution in three ways. First, it records the project mandate. During predesign, the team evaluates competing ideas and portfolio scenarios; once the authorized executive approves a preferred scenario, such as headquarters relocation or major modernization in place, the charter records that decision. It provides the authorized baseline for detailed architectural programming, space standards, technical requirements, and the Program of Requirements, keeping subsequent work aligned with the original business objectives while the team controls and documents approved changes. Second, it establishes coordination authority. The charter gives the project manager and owner’s project manager (OPM), where engaged, organizational authority to coordinate real estate, IT, HR, finance, and legal and to initiate authorized procurement of external design, planning, and consulting services. Third, it provides a governance and scope-control reference. As the team evaluates options and stakeholder feedback, the charter helps determine whether proposed changes remain within authorized parameters. Changes affecting the mandate, scope, budget, schedule, or other controlled baselines follow the established approval process. The project manager submits the charter to the executive sponsor for review and approval.

3.2 Translating Business Priorities into a Program of Requirements (POR)

Programming translates business drivers into spatial, qualitative, and quantitative requirements that define the design problem and establish the project’s scope, budget, schedule, and performance expectations.

Programming is a systematic process of inquiry that produces a statement of the problem to solve and the requirements a solution must meet. The process applies to defining planning, building or workplace problems depending on the nature of the strategic initiative.

The project manager determines how the team will perform programming under the approved delivery approach. A programming consultant may lead the inquiry and prepare the Program of Requirements; a workplace consultant may analyze work patterns, utilization, standards, employee experience, and change implications; and IT/AV consultants may develop technology, connectivity, collaboration, security, and support requirements. Architecture and engineering specialists review the evolving program for technical feasibility, regulatory implications, system capacity, site and building constraints, sustainability, resilience, and coordination needs. The owner may retain these providers separately, include some services within the architectural provider’s scope, or use qualified internal resources. In every arrangement, the project manager coordinates the scopes, confirms that specialist recommendations reconcile with one another and with the business case, and ensures that the owner reviews and approves the Program of Requirements before design proceeds. The Problem Seeking method distinguishes programming from design: the programming team analyzes and defines the problem, while the design team synthesizes possible solutions.

The Problem Seeking method of programming involves five steps and four considerations. The five steps are:

  • 1.      Establish Goals
  • 2.      Collect and Analyze Facts
  • 3.      Test and Evaluate Concepts
  • 4.      Determine Needs
  • 5.      State the Problem

The process is adaptable to public- and private-sector projects and can address a wide range of factors that influence planning and design of the built environment. It applies across sectors, industries, and building types. Its effectiveness depends on disciplined analysis of four major considerations: function, form, economy, and time—which organize the information needed to define the problem. The problem statement connects programming and design -- concludes programming, initiates design inquiry, and provides the basis for evaluating design alternatives and the preferred solution.

3.2.1 Master Planning and Prototype Design

The project managementteam may undertake a master plan or campus plan before designing a specific building or complex. A governingboard or public authority mayrequire a comprehensive plan before approving an individualproject. The process resemblesstrategic planning, but its scope and level of detail arespecific to thesite and user population. Programming defines the problem; planning then develops, evaluates, and synthesizes alternatives into a recommended plan.

A master plan may address a new site or update an existing campusplan. An owner developing an innovative or repeatable facility may also create a prototype to test the concept, delivery approach, and economic feasibility before broader implementation. This approach is common among owners and agencies with recurringbuilding typesor a strategy that substantially changes how work is performed or the workplace is organized. A pilot project can test effectiveness before a larger-scale rollout.

3.2.2 Stages of Programming

Programming increases in specificity as the decision process progress. Strategic planning defines organizational and portfolio needs; the Real Estate Phase develops the preliminary requirements brief and site-selection criteria; master planning applies requirements at the site or campus scale; schematic design programming establishes the program of requirements for buildings or workplaces. Based on the completion of schematic design, design development programming refines systems, rooms, furniture, and equipment requirements within an established design context. The planning, real estate or project team uses programming at several stages of strategic predesign, with each stage addressing a different scope and level of detail. Five common program types are the strategic planning program, real estate requirements brief and site-selection criteria, master plan program, schematic design program, and design development program.

Programming istherefore a multistage requirements-definition process whose scope changes with its application. In the Strategic Planning Phase, it supports organizational and portfolio decisions. In the Real Estate Phase, it produces a preliminary requirements brief, including demand forecasts, macro-level space requirements, qualitative objectives, and site-selection criteria that support comparative feasibility testing. In the Project Definition Phase, schematic design programming develops the program of requirements needed for the decision to proceed to design and the requirements for design. Master plan programming applies similar methods at the site or campus scale and addresses land use, site-area requirements, parking, building footprints, and related infrastructure. Design development programming occurs later, within an established design context, and refines building-systemcriteria and room-level furniture and equipment requirements. Building type specialists, architectural and engineering teams typically perform it, although some public-sector owners require both schematic design and design development programs before selecting the design team.

3.2.3 Workplace Standards, Performance Targets and Design Criteria

Organizations with large property portfolios may establish workplace standards, performance targets, design criteria, and IT infrastructure guidelines for use across their properties and capital projects. The project manager should adapt these requirements where necessary to local codes, climate, culture, operations, and project conditions.

Workplace Standards and Spatial Benchmarks

Workplace standards define how space is allocated, structured, and utilized across the real estate portfolio to support brand consistency, cost control, and equity for employees. Allocation benchmarks may address area per employee—for example, an illustrative density range of 150–200 sq. ft. per person—ratios of open-plan seating to enclosed private offices, and workstation footprints such as benching dimensions. Standards may also specify a modular kit of parts: furniture, partition types, lighting, and power/data modules that can be reconfigured, reordered, and deployed across regional offices without redesigning from scratch. Guidelines for focus rooms, huddle spaces, medium and large conference rooms, and social hubs coordinate collaboration settings with acoustic and technology requirements. These benchmarks and components operate within a framework that permits authorized deviations for local cultural norms, statutory requirements such as building codes or accessibility laws, and regional work styles; they are not identical requirements for every location.

Performance Targets and Operational Metrics

Performance criteria provide quantitative benchmarks for evaluating whether the workplace supports organizational goals, sustainability commitments, and financial efficiency. Utilization criteria address peak-to-average occupancy, badge-in data tracking, and the use of meeting rooms versus individual desks. A target such as 70% to 80% active utilization during core hours is an example of a dynamic utilization target, not a universal requirement; the project’s criteria define the applicable target and its measurement basis. Indoor Environmental Quality (IEQ) criteria address a different question: the conditions needed for occupant health and comfort. These include:

  • ·       Thermal Comfort: Strict indoor temperature and relative humidity bands (e.g., ASHRAE standards).
  • ·       Indoor Air Quality (IAQ): Minimum fresh-air exchange rates (CFM per person),  threshold limits, and particulate filtration standards (MERV ratings).
  • ·       Acoustical Performance: Ambient noise criteria (NC ratings) and speech privacy metrics (such as Sound Transmission Class or Privacy Index ratings) for open vs. closed spaces.
  • ·       Lighting Quality: Target foot-candles (lux levels) for task lighting and integration of circadian lighting design strategies.

Finally, the targets include key performance indicators (KPIs) such as Energy Use Intensity (EUI targets measured in ), carbon emission caps, water usage efficiency, and waste diversion rates to meet corporate ESG (Environmental, Social, and Governance) goals.

Design Criteria and Building Systems Guidelines

Design criteria outline the minimum acceptable technical specifications and performance thresholds for core building engineering and architectural systems in new construction or major capital projects.  The criteria include:

  • Architectural and Structural Systems: Specifications for interior finishes, durability ratings, ceiling heights, floor-load capacities for high-density filing or server rooms, and compliance with accessibility guidelines (e.g., ADA).
  • HVAC (Mechanical) Systems: Guidelines for zoning, system redundancy, control sequences, filtration, and ventilation capacity to handle dense meeting room configurations and varying occupancy loads.
  • ·       Plumbing and Fire Protection Systems: Standards for water supply, sanitary and storm drainage, efficient fixtures, leak detection, sprinkler and standpipe coverage, fire-water supply, and coordination with fire alarm and emergency systems.
  • Electrical and Lighting Systems: Standards for power distribution density (watts per square foot), emergency power backup (generators/UPS), lighting control systems (occupancy sensors, daylight harvesting), and sub-metering infrastructure for tracking energy usage.
  • IT, Telecommunications and AV Infrastructure: Comprehensive cabling guidelines (Category 6A/fiber optics), telecommunications room (TR/MDF) spatial and cooling standards, enterprise Wi-Fi coverage density, and standardized audio-visual configurations for hybrid collaboration spaces.
  • Life Safety and Security Systems: Minimum acceptable requirements for fire alarm systems, sprinkler coverage, smoke evacuation, access control integration (card readers, biometric entry), and CCTV coverage across portfolio assets.

3.2.4 Comprehensive Set of Considerations

Programming involves a comprehensive analysis of the design problem through four major considerations: function, form, economy, and time. Each consideration includes three keyword subcategories that help organize inquiry and information:

Function

  • ·       People
  • ·       Activities
  • ·       Relationships

Form

  • ·       Site
  • ·       Environment
  • ·       Quality

Economy

  • ·       Initial Budget
  • ·       Operating Costs
  • ·       Life Cycle Costs

Time

  • ·       Past
  • ·       Present
  • ·       Future

Function addresses what will happen in the building and the relationships among people, activities, and spaces. Form addresses the site, the physical and psychological environment, and the desired quality of space and construction. It describes what users will perceive and experience. Economy addresses the initial budget, operating costs, life-cycle costs, and the relationship between cost and quality. Time addresses historical influences, present conditions, anticipated change, phasing, and future requirements.

3.2.5 Information Index – Organizing and Classifying Information

The Information Index is a matrix combining five programming steps—establish goals, collect and analyze facts, test and evaluate concepts, determine needs, and state the problem—with four considerations—function, form, economy, and time. Keywords assigned to each cell guide the questions asked and the information collected. At every programming step, use the four considerations to investigate the project and develop its requirements. The index provides a repeatable checklist for generating questions, locating pertinent information, organizing evidence, validating findings, and developing the program requirements.

The programmer uses these keywords as heuristics to draw on experience and project context, generate questions, and identify relevant information. Some information comes from research and analysis, such as code or site analysis. Organizational leaders, end users, and internal service providers contribute qualitative goals, operational concepts, and quantitative inputs such as headcount, seat requirements, and the types, sizes, and quantities of spaces needed to support operations.

The programmer organizes and classifies information using the Information Index. The project team can assimilate large amounts of information when it is pertinent, meaningful, and well organized. The programmer applies professional judgment to determine what is relevant to the current phase and the appropriate level of detail. To avoid information overload, the team removes trivial input, sets aside irrelevant material, and retains information that may be useful in another phase. Detailed data may be analyzed and summarized, for example, in a conference-room supply-and-demand study or food-service capacity analysis—while the supporting data is retained as backup information or in a governed database.

3.2.6 Information Display and Validation

The project manager requires the programming team to validate collected information before the architect uses it for schematic design. The team checks source authority, completeness, currency, lineage, units, definitions, duplicates, outliers, and conflicts and records the disposition of material exceptions. During interviews, user work sessions, and focus groups, the team displays key information for review and comment through accessible digital or physical methods. Participants identify errors, omissions, relationships, and sensitive information that require restricted handling. AI-assisted transcription, extraction, summarization, or semantic search may accelerate documentation, but a named reviewer compares every material output with the source, corrects errors, records unresolved uncertainty, and approves the result before the team relies on it. For larger public or departmental meetings, the project manager scales the displays and provides accessible mechanisms for structured feedback.

3.2.7 Programming is a Participatory Process

Programming is a participatory process in which stakeholders contribute experience, knowledge, and perspectives on how the facility should perform. Specialists may supplement that input with research, benchmarking, and comparative analysis. The programmer should distinguish valid project-specific requirements from individual preferences that do not support broader organizational goals. Compare requests with evidence from comparable facilities and the project’s goals, operations, and constraints rather than treating prevailing practice as automatically correct. This approach reduces the risk of requirements that become obsolete when a user group changes.

The project manager and programmer should develop a stakeholder-participation plan. Begin with interviews with executives and organizational leaders to establish goals and identify the issues and concerns the process should address. Then interview the departments directly involved in the new facilities to understand their needs and concerns. The programming team may also hold cross-organizational focus groups on topics such as workplace concepts and standards, facility services, and amenities.

3.2.8 False Harmony—Agreement by Default

Shared understanding should not be inferred from apparent agreement. A group may endorse a course of action that its members privately oppose because each mistakenly assumes the others support it. This communication failure is known as the Abilene paradox. It differs from an informed compromise: participants go along with assumed preferences rather than openly compare their own. False harmony describes the broader risk of treating silence or unexamined assent as genuine agreement; it need not indicate the Abilene paradox or be confined to a particular organizational structure.

In strategic planning and architectural programming, this risk arises when stakeholders are asked to align project goals and requirements before their meanings and operational consequences have been examined. Pressure to reach a unified vision can leave concerns unrecorded. Facilitators should distinguish individual preferences, shared interpretations, acceptance of trade-offs, and formal authorization rather assume them all as consensus.

Apparent Agreement on Space Programs and Project Goals: During visioning workshops, stakeholders may endorse open-plan arrangements, space-reduction targets, or shared amenities without stating reservations or confirming how these choices would affect their work. An expression of support is not a validated requirement. If assent is recorded as a confirmed requirement without examining assumptions and consequences, unresolved needs may emerge during schematic design or construction documentation as change requests, scope changes, or objections. Record qualifications and distinguish candidate requirements from validated and approved requirements.

Unreported Exceptions and Incomplete Evidence: Effective information processing depends on operational users and specialists, making workflow constraints and exceptions visible. Issues should be addressed where the relevant information exists and escalate when they exceed delegated authority.  When concerns remain unexpressed or unrecorded, assessments may omit constraints that conflict with the emerging project vision. The resulting program or business case can overstate feasibility or understate uncertainty. Capture contrary evidence and unresolved issues for specialist review and, where necessary, an authorized decision.

Mistaking Silence for Shared Meaning: Equivocality concerns multiple plausible interpretations of information. Silence or passive assent does not establish that participants interpret a requirement in the same way. Unclear meaning and unexpressed disagreement may coexist, but they are not the same problem.  A term such as “flexible” may appear agreed while participants hold different expectations about what a space must accommodate. Translate abstract goals into operational definitions, scenarios, and testable criteria, then confirm the interpretation and record remaining differences before treating the requirement as validated.

To reduce the risk of false agreement, programmers should invite differing views, test interpretations, and make choices explicit. The following practices support evidence-based requirements development.

Complement abstract discussion with spatial options, simulations, or operational scenarios. Ask participants to explain effects on workflows, constraints, and success criteria. These enactment activities make assumptions visible without treating a preliminary option as an approved design.

Use anonymous surveys where anonymity can be maintained, confidential individual feedback where follow-up is needed and facilitated small-group discussions to explore concerns. Breakout sessions are not anonymous. Explain access and confidentiality limits, and preserve substantive findings without unnecessary personal attribution.

Present an interpretation or proposed requirement, gather responses, and revise it considering that feedback. Record what changed, the supporting rationale, and unresolved differences rather than finalize requirements in a single meeting. Retain the evidence and review history in the decision-support system, and route remaining trade-offs to the appropriate authority.

3.2.9 Organize the Process for Decision Making

Programming requires timely, sound decisions. The project manager and programmer define the steps needed to approve the program under the project sponsor’s guidance. The team seeks stakeholder consensus on requirements and ideas where practical. When groups disagree or requested information remains unavailable, the project manager documents and escalates the issue to the project sponsor. The sponsor decides within delegated authority or refers the matter to the steering committee. The steering committee reviews scope, schedule, budget, risk, and cross-functional impacts and resolves issues within its authority. Both the sponsor and the steering committee report matters requiring higher authority to the chief executive officer or administrator. Programs with significant financial, organizational, risk, or community impacts may also require board or municipal approval.

3.2.10 Communication

Effective programming depends on clear communication with multiple audiences. The programming team coordinates with the enterprise’s communications and public-relations functions. The project sponsor should announce the initiative, explain that it is in the programming stage, describe why stakeholder participation matters, and identify how participants will contribute. A kickoff meeting can introduce the project, process, roles, and expected inputs. The project manager then schedules leadership, department, user-group, and facility-service interviews and workshops. Programmers should facilitate and document meetings, manage conflicts constructively, and provide participants with a useful and respectful experience. Throughout the process, the project manager briefs the sponsor on progress, unresolved issues, and required course corrections. The programming team should also be prepared to brief steering committees, senior executives, boards, public authorities, and community audiences when appropriate.

3.2.11 Process Steps – Establish Goals

Establishing goals is the first step in the architectural programming process. A program is more than a list of spaces and required areas; it must also describe what stakeholders want to accomplish and explain why those outcomes matter. Goals document the enterprise’s aspirations for the project and provide direction for planning, building design or workplace solution.

For the programmer, goals also guide subsequent inquiry and fact-finding. A comprehensive set of goals addresses four categories: function, form, economy, and time.

Functional goals address:

  • ·       Why is the project being undertaken?
  • ·       What are the priorities among the functions to be provided?
  • ·       What capacity must the facility provide?
  • ·       What human values should the facility promote for its users?
  • ·       Must people or property be protected to an extent that establishes major form-givers?
  • ·       If functional efficiency is a stated goal, how should the facility’s performance be measured?

Form goals address:

  • ·       What image should the facility project?
  • ·       How should the facility respond to its physical and contextual environment?
  • ·       What is the institution’s land-use policy?
  • ·       What level of quality should the facility achieve?
  • ·       What balance between the quantity of space and the desired level of quality does the institution expect?

Economy goals address:

  • ·       What funding or budget constraints apply to the project?
  • ·       Does the sponsor expect a return on investment?
  • ·       What are the sponsor’s economic priorities?
  • ·       Is the priority initial cost, operating cost, or life-cycle cost?

Time goals address:

  • ·       When should the project be completed?
  • ·       What historical considerations could affect the project?
  • ·       What foreseeable future conditions might require the design to adapt to change?

Some stakeholder goals can be addressed through architectural programming, while others fall outside the scope of the built environment. These goals can be classified into three types:

  • ·       Practical goals: These goals can be implemented through programmatic concepts.
  • ·       Aspirational goals: These goals are too general to guide programming or design decisions directly, although they can provide          useful inspiration for the participants in the process.
  • ·       Nonprogrammable goals: These goals cannot be achieved through a planning or design solution. They may instead represent public relations, operational, or broader social objectives that fall outside the project’s built-environment scope.

Stakeholders bring different perspectives and interests to a project. At the outset of the process, participants should therefore develop a shared understanding of the direction being undertaken and agree on a common set of project goals. The programmer accomplishes this through review meetings with project participants. Before presenting the goals for review and approval, the programmer edits them into a succinct, practical, and relevant set that supports the project’s strategic intent. The project manager reviews the set, the project sponsor approves them.

3.2.12 Discover Concepts

Programmatic concepts express how stakeholders intend to accomplish project goals through abstract performance requirements, without prescribing physical design. They describe how a building should support its users and perform over time. Design concepts, in contrast, are concrete physical solutions to architectural problems. This distinction establishes the qualitative relationship between goals and concepts: goals provide the desired outcomes, and programmatic concepts express stakeholder ideas for achieving them. Based on analysis of many architectural programs, the Problem Seeking method identifies 24 concepts that recur across project types, including housing, hospitals, schools, shopping centers, and factories. The programmer adapts the relevant general concepts into project-specific requirements. Not all 24 apply to every project; use the matrix to identify those that do.

Concept

What It Defines

Key Programming Question

Typical Requirement

Character

The image the organization wants to convey.

What should occupants and the public understand about the organization?

Communicate identity through arrival, public areas, materials, and visible operations.

Priority

The relative importance of functions and requirements.

Which functions require the greatest visibility, access, space, quality, or investment?

Allocate location, area, quality, and resources according to operational importance.

Hierarchy

How the facility expresses authority and organizational roles.

Where should space, access, visibility, or finish distinguish roles or remain consistent?

Define role-based differences without creating unnecessary inequity.

Service Grouping

The distribution of building systems and support services.

Which services should be centralized or decentralized, and why?

Centralize for efficiency and control; decentralize for responsiveness, resilience, or local support.

Activity Grouping

How activities and functions should be organized.

Which activities should be integrated, separated, or arranged in sequence?

Group compatible work; separate functions where privacy, security, noise, contamination, or disruption requires it.

People Grouping

How individuals and teams should be organized.

Should people be grouped by workflow, organization, shared purpose, or another relationship?

Organize people at the scale that supports identity, communication, supervision, privacy, and effective work.

Density

The space provided per person, group, activity, or planning unit.

What occupancy range supports the work safely and effectively?

Set minimum, target, and maximum density or capacity ranges for each major use.

Home Base

Territory assigned to individuals or groups.

Who needs assigned space, storage, personalization, or an identifiable address?

Define where assigned workpoints, team neighborhoods, lockers, storage, or shared settings are required.

Neighbors

The organization’s relationship with surrounding communities and uses.

Which neighboring uses require independence, cooperation, shared resources, buffers, or controls?

Define interfaces, shared facilities, setbacks, buffers, access agreements, and community responsibilities.

Communication

How people and groups exchange information.

Who must communicate, how often, by what method, and at what distance?

Provide face-to-face and digital settings, technology, and proximity according to interaction needs.

Relationships

Desired affinities among people, activities, departments, and spaces.

Which functions must be adjacent, nearby, accessible, separated, or remotely connected?

Record critical, desirable, accessible, and undesirable adjacencies and the reason for each.

Accessibility

How people, goods, and services enter, use, and leave the site or building.

Who requires access, where should entry occur, and what controls or accommodations are needed?

Define public, staff, service, secure, and accessible entries, routes, controls, and wayfinding.

Tolerance

The acceptable variation between minimum and maximum requirements.

Which spaces require a precise fit, and which should accommodate variation?

Set acceptable ranges for area, capacity, equipment, environmental conditions, and future change.

Flow

The movement of people, vehicles, materials, products, services, and information.

Which movements should be direct, separated, mixed, controlled, automated, or sequential?

Define circulation networks, process sequences, separation requirements, transfer points, and orientation cues.

Flexibility

The capacity to accommodate growth, new uses, or changing operations.

Which spaces, systems, utilities, or equipment must expand, convert, or support multiple functions?

Identify requirements for expansibility, convertibility, versatility, modularity, and future connections.

Safety

Protection from illness, injury, and life-safety hazards.

Which hazards and code provisions will materially affect planning or building form?

Define life-safety, egress, accessibility, hazardous-process, emergency-response, and protective requirements.

Security

Protection of people, property, operations, and information.

Where do security levels change, and how should the facility deter, detect, delay, and respond?

Define security zones, access control, visitor management, surveillance, separation, CPTED, and continuity requirements.

Energy Conservation

Efficient energy use through planning, envelope, systems, and operations.

Which passive and active strategies will reduce demand while supporting performance?

Set targets for energy use, envelope performance, zoning, controls, electrification, metering, and renewable readiness.

Environmental Controls

Conditions for human comfort and specialized activities.

What temperature, humidity, ventilation, light, sound, air-quality, weather conditions apply?

Set measurable environmental criteria and identify spaces requiring specialized control.

Phasing

How the project reaches its intended capacity over time.

What must occur first, what can follow later, and how will each phase remain operational?

Define initial and future phases, enabling work, temporary conditions, decision triggers, and continuity requirements.

Cost Control

How the project balances scope, quality, time, risk, and cost.

Which requirements protect lifecycle value, and which can become alternates or future phases?

Set budget limits, escalation and contingency assumptions, alternates, checkpoints, and first-cost versus operating-cost criteria.

Use the matrix as a heuristic tool, not as a checklist that forces every concept into every project. Select only the concepts that materially affect the design problem, combine related concepts when they produce one requirement, and document the resulting performance statements in the Program of Requirements (POR).

3.2.13 Testing Goals and Concepts

The programmer tests goals and concepts for integrity, usefulness, and relevance to the design problem. Here, integrity means a clear relationship between a desired outcome and a programmatic concept capable of implementing it: goals define what owners and stakeholders want to achieve and why, while concepts identify how they intend to achieve it. Practical goals require supporting concepts. A goal with no implementable programmatic concept should be reconsidered within the architectural program. Aspirational goals may be broadly accepted but remain too general to guide programming decisions directly. Goals and concepts must also concern matters the planning or design solution can address, rather than social or other issues that cannot be resolved through architecture. The project manager confirms that the resulting requirements remain aligned with the charter and business case.

Before presenting the program to the project sponsor or steering committee, the programmer edits the collected ideas and retains only those that meet the criteria for integrity, usefulness, and relevance.

3.2.14 Functional Relationships

Functional relationships address the arrangement and proximity of functions. The programmer may express these functions as organizational departments, sets of activities, or lists of spaces. The programmer ranks proximity as:

  • ·       Critical (Adjacent)
  • ·       Desirable (Same floor)
  • ·       Accessible (Same building)
  • ·       Undesirable (negative adjacency)

One task of programming is the collection and analysis of the enterprise’s organizational structure to analyze the work processes and functional relationships among the units. This analysis determines the required proximity among user groups. The following concepts describe common functional-relationship requirements:

  • ·       Flow: The movement of people, material, products, or information from location to location.
  • ·       Proximity: The shortest practical distance among groups needed to support communication, interaction, and access.

The first step of the analysis is to confirm the relationship requirements and test the requirement statements for meaningfulness with the user organization. Each organization is unique and may have specific or idiosyncratic terms to describe how they work. Collect adjacency requirements through questionnaires, interviews, or both. Use an interaction matrix to summarize and analyze the required interactions among functions. Then represent those interrelationships using a bubble diagram. The thickness of the connecting line represents the strength of interaction between the functions.

An interaction matrix documenting the proximity requirements among departments.

A bubble diagram graphically illustrates the proximity and separation requirements among departments.

In addition to horizontal functional relationships, it is often useful to illustrate vertical relationships among functions. In this example, the program identifies certain levels as hub floors that house decentralized shared services, such as food service and training. Visitor-accessible central services, including the main lobby, reception area, and client meeting area, are located near the transfer floor. The 63rd level houses central functions that require secure access and are not open to unescorted visitors, including the boardroom, central cafeteria, and assembly hall.

3.2.15 Collect and Analyze Facts

Facts are verified information about the project, its context, and the enterprise. They provide the evidence needed to analyze current conditions, forecast needs, establish requirements, and evaluate alternatives.

Programming requires systematic collection, integration, validation, organization, analysis, stewardship, and controlled reuse of qualitative and quantitative information. The project manager treats the information architecture as part of the program: the team identifies the decisions to support, selects authoritative systems of record, maps shared identifiers and definitions, and establishes a governed common data environment for project records. Contemporary practice combines internal enterprise systems, authoritative external sources, field observations, connected built-environment data, interoperable building and geospatial models, and software-assisted analysis. The following guidelines support an efficient, secure, traceable, and reliable process:

  • ·       Define each decision to be supported, then collect only the data needed to establish requirements, test assumptions, compare alternatives, and manage risk.
  • ·       Create a data-management plan that identifies owners, definitions, units, formats, access rights, retention requirements, update frequency, and quality criteria.
  • ·       Connect approved internal sources—such as human-resources, finance, real estate, facilities, maintenance, space-management, scheduling, security, and building-automation systems—through governed exports, application programming interfaces, or a common data environment.
  • ·       Use authoritative external sources for demographics, climate, hazards, codes, zoning, market conditions, benchmarks, costs, transportation, utilities, and environmental conditions.
  • ·       Supplement existing records with interviews, questionnaires, workshops, observations, occupancy studies, sensor data, site surveys, photogrammetry, geographic information systems, and building information models when appropriate.
  • ·       Standardize names, classifications, locations, time periods, and measurement units so datasets can be compared and combined across systems.
  • ·       Record source, author, collection date, geographic and organizational scope, assumptions, transformations, confidence, and version for every material fact.
  • ·       Use software to detect duplicates, missing values, outliers, conflicts, and stale records; resolve significant exceptions with the responsible subject-matter expert.
  • ·       Use artificial intelligence to accelerate classification, extraction, summarization, semantic search, forecasting, scenario generation, and anomaly detection—not to replace professional judgment or stakeholder decisions.
  • ·       Require human review of AI-assisted outputs, verify material claims against their original sources, test results for accuracy and bias, and document prompts, models, dates, assumptions, and approvals when AI affects a project decision.
  • ·       Protect personal, confidential, security-sensitive, and proprietary information through data minimization, role-based access, approved storage, cybersecurity controls, and applicable legal and contractual requirements.

Use a structured information request and data inventory to collect available documents, datasets, models, system reports, and access instructions for the enterprise and project. Identify the system of record, data owner, format, date range, refresh cycle, sensitivity, and permitted use for each source.  The information request includes:

  • ·       Enterprise mission, strategic plans, policies, organization, stakeholders, users, and service-delivery model
  • ·       Portfolio, site, facility, lease, space, asset, equipment, maintenance, utility, sustainability, security, security assessments, and occupancy records
  • ·       Headcount, workforce plans, schedules, work patterns, transactions, demand, workload, operational performance, and future scenarios
  • ·       Existing drawings, surveys, specifications, building information models, geographic information system layers, digital twins, photographs, point clouds, and building commissioning records
  • ·       Budgets, cost histories, schedules, procurement constraints, risk registers, standards, owner requirements, and approval criteria

3.2.16 Managing Collected Information

The Information Index is a living data catalog and checklist of potential facts, sources, owners, systems, and collection methods. Use it to plan research, map each fact to the decision it supports, identify gaps, assess source authority and data quality, manage permissions, track validation status, and preserve a traceable record of findings. Where practical, link the index to the project’s common data environment, document-management system, building information model, geographic information system, or analytics platform.

The project team uses a shared semantic layer—controlled vocabulary, classification, units, locations, asset types, and stable identifiers—to connect documents and data across human-resources, finance, portfolio, GIS, BIM, IWMS, CMMS, scheduling, cost, procurement, and building systems. The team validates required model and asset information through machine-readable rules where practical and resolves exceptions before publishing an information package. When an open exchange standard can meet the use case, the team prefers it to a proprietary-only handoff and tests the exchange in the receiving software before approval.

The project manager applies least-privilege, role-based access to information resources; requires approved identities and devices; encrypts sensitive information in transit and at rest; logs access and material changes; separates public, internal, confidential, personal, security-sensitive, and controlled information; and defines incident-response and recovery procedures. The team minimizes personal data, aggregates or anonymizes occupancy and location data where feasible, and completes privacy, cybersecurity, legal, records-management, and contractual reviews before connecting systems or using external AI and analytics services.

3.2.17 Factual Information Checklist

Built-environment information should remain connected across a consistent hierarchy: portfolio, land parcel, site, facility, building, floor, room or space, and fixed or movable asset. Each level requires an appropriate unit of measurement, identifier, updating frequency, and degree of detail tied to the decision being supported.

Planning, design, and workplace requirements vary by process, scale, time horizon, and unit of measurement. Treat each level of analysis as an entity in a connected hierarchy: land parcels form sites; sites support facilities; facilities may include buildings; buildings contain floors; floors contain rooms and spaces; and those spaces contain fixed and movable assets. Use consistent identifiers to connect records across portfolio, geographic information system, building information model, digital-twin, facility-management, and enterprise platforms. Match the level of detail and update frequency to the entity being studied and to the decision the information must support. Avoid false precision: where evidence is incomplete, state assumptions, uncertainty, and confidence explicitly.

Functional Facts

  • ·       Demand, workload, transactions, and service levels — Enterprise systems, operational databases, approved data warehouses, and process-mining tools
  • ·       Headcount, roles, schedules, work patterns, and forecasts — Human-resources and workforce-planning systems, validated questionnaires, and interviews
  • ·       Occupancy and utilization — Reservation and access-control records, privacy-preserving sensors, observations, and space-management platforms
  • ·       Area requirements and space adequacy — Owner standards, benchmark datasets, facility inventories, measured drawings, building information models, and utilization analytics
  • ·       User characteristics, needs, and experience — Interviews, workshops, surveys, accessibility reviews, and approved research
  • ·       Movement, interaction, and behavioral patterns — Observations, journey mapping, network analysis, simulations, and anonymized location data where permitted
  • ·       Criticality and value of loss — Business-impact analyses, continuity plans, insurance records, risk registers, and security assessments

Form Facts

  • ·       Site, boundaries, topography, utilities, access, and surroundings — Surveys, geographic information systems, utility records, aerial imagery, point clouds, and field verification
  • ·       Geotechnical, hydrologic, ecological, climate, and hazard conditions — Site investigations and authoritative scientific, environmental, and governmental datasets
  • ·       Land use and development controls — Adopted zoning ordinances, land-development codes, planning-agency records, and confirmed interpretations
  • ·       Regulatory requirements — Adopted building, fire, accessibility, energy, environmental, zoning, and other applicable codes and standards
  • ·       Existing conditions and asset configuration — Field surveys, record documents, building information models, photogrammetry, laser scanning, inspections, and facility-management systems
  • ·       Building performance and environmental quality — Building-automation systems, meters, commissioning records, indoor-environmental sensors, and post-occupancy evaluations
  • ·       Security, resilience, and continuity — Threat and vulnerability assessments, climate-risk tools, emergency plans, and stakeholder workshops

Economic Facts

  • ·       Capital-cost parameters and escalation — Current cost databases, quantity takeoffs, market intelligence, recent comparable projects, and estimator review
  • ·       Funding limits and cash flow — Approved budgets, finance systems, funding agreements, and client decisions
  • ·       Operating, maintenance, replacement, and life-cycle costs — Utility bills, computerized maintenance-management systems, asset registers, energy models, and life-cycle cost analysis
  • ·       Market, demographic, and economic conditions — Authoritative government data, real-estate research, industry reports, and validated forecasts
  • ·       Energy sources, tariffs, demand charges, incentives, and emissions factors — Utility providers, regulators, energy models, and approved public datasets
  • ·       Sustainability and certification requirements — Owner goals, applicable policies, carbon accounting methods, and rating systems such as LEED
  • ·       Scenario and sensitivity analysis — Parametric cost models, Monte Carlo or other risk models, and AI-assisted forecasting with documented assumptions and expert validation

Time Facts

  • ·       Required occupancy, milestones, approvals, and constraints — Client decisions, governance records, regulatory calendars, and integrated schedules
  • ·       Project delivery and procurement strategy — Owner requirements, procurement policies, legal guidance, market capacity, and construction-industry standards
  • ·       Activity and process durations — Historical project records, operational logs, observations, subject-matter estimates, and schedule-risk analysis
  • ·       Phasing, swing space, shutdowns, and move sequencing — Operational constraints, facility data, stakeholder workshops, and four-dimensional model simulations
  • ·       Growth, demographic, demand, and technology change — Approved forecasts, scenario planning, trend analysis, and externally validated datasets
  • ·       Schedule performance and escalation risk — Integrated project-management systems, market reports, risk registers, and probabilistic analysis
  • ·       Data currency — Source dates, refresh cycles, version histories, and triggers for revalidation as the project evolves

3.2.18 Sustainability and Energy Consumption

An enterprise may have specific goals and policies regarding sustainability and energy consumption programs that require design and construction compliance. Translate major sustainability frameworks—such as LEED v5, WELL v2, and Living Building Challenge—into programming metrics requires specific considerations:

Programming Phase

Green and Wellness Action Item

Standard Reference

Site and Massing

Establish max floor depth for natural light; orient footprint for solar/wind efficiency.

LEED Daylight / WELL Light [cite: 1.2.1]

Space Allocation

Reserve space for biophilic amenities, quiet rooms, mothers' rooms, and central stairs [cite: 1.2.1].

WELL Mind / Movement / Equity

Adjacency and Layout

Group spaces by acoustic tolerance and thermal load to optimize HVAC/acoustics.

LEED IEQ / WELL Sound and Thermal

Room Data Sheets

Require MERV 13+ filtration, low-VOC finishes, and sit-stand options.

WELL Air and Materials [cite: 1.2.1]

Building Systems

Space allocations for all-electric equipment, water reuse, and BESS storage.

LEED Decarbonization v5

Analyzing major energy standards and codes and translating the implications for programming metrics and performance considerations requires specific considerations.

Geographic Region

Primary Reference Frameworks

Architectural Programming Focus

Europe (EU)

ISO 52000, EN 16798, EPBD (Energy Performance of Buildings Directive)

High envelope performance, thermal bridge mitigation, district energy hookups, mixed-mode ventilation [cite: 1.1.4].

Asia-Pacific (APAC)

Green Mark (Singapore), CASBEE (Japan), ISO 50001

High-density HVAC zoning, humidity control, integrated solar shading, on-site energy storage.

Americas

ASHRAE 90.1-2022, IECC, Title 24 (US) / local municipal codes

Electrification, heat pump mechanical footprints, sub-metering, renewable energy expansion space [cite: 1.1.3].


3.2.19 Determine Needs

The needs analysis quantifies the project’s functional scope and tests its feasibility against the other considerations: form constraints, economic targets, and schedule implications. The method varies with the scale of the project—site, building, or workplace—and uses either U.S. customary or metric units.

Site

At the site scale, the analysis may support campus plans, land-use plans, or municipal planning. A population or demand forecast establishes the required planning capacity, expressed in measures such as people, housing units, or student enrollment. The analysis then quantifies the required land area in acres or hectares. The program may distribute this area among land uses and calculate gross building area, site facilities, parking, assumed floor levels, and building footprints. The land area required for buildings can be estimated by dividing the total building footprint by the allowable or target ground-area coverage ratio (GAC). The selected GAC should also preserve adequate area for circulation, utilities, stormwater management, landscape, open space, and other site-development features.

The needs analysis tests whether the required land area can be accommodated within the available site area, subject to zoning, easements, covenants, environmental constraints, and existing conditions. If it cannot, the team revises the capacity assumptions, land-use distribution, density, building configuration, or GAC target. The planner and cost estimator then estimate land-development costs, including roads, utilities, grading, stormwater systems, landscape, open space, and amenities. The team compares the estimate with the authorized budget and reconciles scope, quality, and cost as needed. It also develops a phased implementation and construction schedule. For revenue-generating projects, financial feasibility may include a return-on-investment analysis that incorporates site cost and the target rate of return established in the strategic plan; other projects may use different value or affordability criteria.

Building

At the building scale, the analysis may address a new standalone building, a building complex, an owner-developed facility, or a build-to-suit project. Capacity measures vary by building type: offices may use occupants, seats or work points; manufacturing facilities, production units; hospitals, beds, treatment spaces, or patient volumes; parking structures, vehicles; and auditoriums, seats. The programmer selects measures appropriate to the facility and its operations. Building scope is expressed as gross floor area in gross square feet (GSF) or gross square meters (GSM). The programmer first determines the net assignable or usable areas required for each function. For an office headquarters, these may include workspaces, departmental support areas, specialty spaces, floor services, lobbies, food service, conference facilities, employee amenities, fitness areas, and facilities and IT operations. The programmer develops requirements from workplace standards, planning guidelines, operational data, and consultation with users and internal service providers. The programmer may organize the space list by department or summarize it by space type. The programmer then estimates gross floor area by applying a net-to-gross or building-efficiency factor appropriate to the organization’s measurement convention. This factor accounts for circulation, building services, toilets, janitor closets, walls, partitions, structure, and other non-assignable areas.

The analysis then tests whether the required gross floor area can be accommodated within the site envelope and applicable zoning, code, covenant, height, setback, parking, and coverage constraints. If it cannot, the team revises the program, configuration, density, or efficiency assumptions and records the resulting trade-offs. The project manager and cost estimator prepare a total project cost estimate. The cost estimator commonly estimates construction cost from gross area and appropriate unit-cost benchmarks and adjusts the estimate for building type, location, quality, market conditions, and project complexity. The budget should also address site development, fixed and movable equipment, technology, acquisition or demolition, professional services, permits, owner administrative costs, escalation, and contingency. Contingency should reflect the project’s stage, uncertainty, and risk rather than serve as an unexplained allowance. If the estimate exceeds the target budget, the team reconciles scope, quality, cost, and risk with the project sponsor. The project manager and scheduler also develop a preliminary schedule that reflects approvals, design, procurement, construction, commissioning, and occupancy. If the required occupancy date is not achievable, the team evaluates phasing, acceleration, scope adjustments, or a revised date and presents the implications for decision.

Concurrently, the IT and audiovisual (AV) manager develops requirements, a preliminary scope of work, budget, and schedule consistent with the program. The organization should decide whether these costs are included in the total project budget or managed as a coordinated separate budget. During programming, the team may prepare procurement documents and market-engagement plans for network, AV, low-voltage, printing, and related services. Solicitation, selection, negotiation, and award should occur only when authorized and at a point that supports design coordination, long-lead procurement, and the occupancy schedule.

Workplace

At the workplace scale, programming addresses interior space in a leased facility or the renovation of an existing building, often for office uses. The analysis follows the same principles as building programming but focuses on the usable area required, expressed in usable square feet (USF) or usable square meters (USM). The programmer derives usable areas from the net functional area by applying a planning or layout-efficiency factor that accounts for internal circulation and layout inefficiencies caused by the floor-plate configuration. The programmer should define the factor clearly because organizations and measurement standards may use different conventions. Workplace programming is typically participatory and draws on occupant profiles, work processes, attendance and utilization data, workplace standards, and input from user groups. Planning is also shifting from fixed ratios—such as assigned-seat profiles, uniform sharing ratios, and fixed area-per-seat benchmarks—toward evidence-based approaches that reflect attendance patterns, team activities, role profiles, and regional variation.

After establishing the required usable area, the team tests it against the usable area available under the lease or confirmed by field measurement. Because leases commonly state rentable areas, the programmer should apply the measurement standard specified in the lease—such as the applicable BOMA standard—to determine the relationship between rentable and usable areas. The method varies by property type, measurement standard, and whether a floor is occupied by one tenant or multiple tenants. A qualified professional should verify the available area rather than rely solely on marketing or owner-provided data.

If the requirement exceeds the available area, the team revises the functional program, workplace strategy, layout assumptions, or premises under consideration. The project manager, IT project manager, and cost estimator then estimate fit-out or renovation costs and compare them with relevant local benchmarks. The analysis should consider both capital expenditure (CAPEX) and operating expenditure (OPEX), including rent and lease obligations where relevant. If projected costs exceed the authorized budget, the project sponsor decides whether to increase funding, reduce scope, change quality or phasing assumptions, or reconsider the premises. The team also updates the project delivery schedule and tests it against the required occupancy date, including design, approvals, procurement, construction, commissioning, technology deployment, move planning, and operational readiness. The project manager should present any mismatch and its implications to the project sponsor for decision.

3.2.20 State the Problem

Problem statements synthesize the preceding programming work into clear, concise descriptions of the essential problems the design must address. They establish premises for design and provide criteria the owner and design team can use to evaluate proposed solutions.  The project manager assigns responsibility for drafting and confirming the problem statements according to who prepares the program of requirements and the scope established in the owner–architect agreement.

Under AIA Document B101–2017, the standard owner–architect agreement for building design and construction contract administration, the owner provides information about the project’s objectives, schedule, constraints, criteria, and budget. The architect consults with the owner to confirm the project requirements and the scope of services. Because contractual duties vary by agreement and amendment, the project team should verify the requirements of the executed contract rather than rely on a generic summary.

The owner may prepare the program with in-house staff or retain a programming consultant. When programming is performed by others, the architect reviews the information furnished by the owner, identifies apparent inconsistencies or missing information, considers applicable laws, codes, and regulations, and works with the owner to reach a shared understanding of the project requirements. Any need for additional information, specialist advice, or expanded services should be documented promptly and addressed through the project’s contractual procedures.

If the owner has not prepared an adequate program, the architect may recommend programming as a supplemental or additional service. The parties should define the scope, deliverables, schedule, responsibilities, and compensation in the agreement or an appropriate scope-of-services exhibit. The architect may provide the service with qualified internal staff or retain a programming consultant under a properly coordinated consultant agreement.

When the owner or its programming consultant prepares the program of requirements, the program should include a preliminary set of problem statements. After the architecture and engineering team is selected, the owner’s project manager should brief the design team on the program, its supporting evidence, and unresolved issues. The owner and design team may then refine the statements to reflect validated changes or newly available information. The approved program serves as a project baseline rather than an immutable document; departures from it should be evaluated, authorized, and recorded through a formal change-control process.

When the architecture and engineering firm prepares the program of requirements, the programmer presents it to the owner and other designated stakeholders for review and approval. After approval, the programmer briefs the design team on the program’s content, assumptions, evidence, priorities, and constraints. The programmer and design team then confirm or refine the problem statements as the basis for design, with participation by the owner’s representatives when appropriate. The parties responsible for project decisions should accept the final statements.

Problem statements describe required performance and critical conditions; they do not prescribe architectural form or a preferred solution. A complete set should address the programming consideration function, form, economy, and time—without forcing an arbitrary count. Depending on the project, the statements may cover operations and user needs, context and site conditions, quality and budget, schedule and phasing, risk, resilience, adaptability, and other factors that materially affect design.

Abstraction—the ability to distill complex information to its essential meaning—is a core programming skill. The programmer filters the collected facts, goals, concepts, and needs to identify the few conditions that will have the greatest influence on design. Important qualifications, conflicts, and constraints must remain visible; simplification should clarify the problem without concealing material information.

The programmer should express one major issue in each statement, using direct, measurable language where measurement is appropriate. Collectively, the statements should represent the whole problem, including significant interactions, conflicts, assumptions, and constraints, while remaining brief enough to guide design decisions. Well-composed statements establish design premises and later support evaluation of the proposed solution.

At the transition from programming to design, the problem statements identify the critical conditions the design must address and define the intended direction of performance. They do not determine a single answer. Instead, they provide a common basis for generating and comparing alternatives, recognizing that the preferred solution will balance competing criteria and project constraints.

The project team can also convert problem statements into evaluation criteria. The project team may assign priorities or weights, define an appropriate rating scale, document the supporting evidence, and score each design alternative consistently. This approach is especially useful when several stakeholder groups share decision-making authority because it makes trade-offs explicit, creates a traceable record of the evaluation, and provides a reasoned basis for the recommended solution. The project team should use the scoring process to support—not replace—professional judgment and owner approval.

3.3 Align Delivery and Procurement with Project Objectives

The project manager and procurement manager develop the delivery and sourcing strategy and submit it to the project sponsor. The steering committee reviews the strategy’s alignment with project objectives, risk, schedule, and governance. The project sponsor approves matters within delegated authority and seeks chief executive officer or administrator approval when required. The project manager aligns contract responsibilities, external service requirements, selection procedures, and procurement timing with the project’s objectives and requirements. Approval of the strategy does not authorize contract award or later-phase work.

  • ·       Delivery method: Compare design-bid-build, design-build, construction manager at risk, and integrated project delivery against scope definition, technical complexity, schedule, affordability, risk allocation, owner participation, and applicable procurement requirements. Recommend the structure that best supports the project objectives.
  • ·       Scope of services: Define service requirements and responsibility boundaries for external consultants, architects, engineers, and specialty vendors.
  • ·       RFQs and RFPs: Prepare targeted requests for qualifications (RFQs) and requests for proposals (RFPs) to attract qualified project partners.
  • ·       Consultant selection: Evaluate project partners transparently against published qualifications and technical criteria, and pricing criteria where permitted. Document the selection rationale, obtain award approval, and confirm responsibilities before onboarding.

3.3.1 Project Delivery Methods

Select the project delivery method during project definition to align contractual responsibilities, risk allocation, collaboration, and procurement timing with the owner’s objectives. The method influences schedule and cost outcomes but does not guarantee them; performance also depends on scope clarity, team capability, contract terms, and execution.

Delivery methods differ in contractual relationships, timing, owner involvement, and risk allocation. Design-Bid-Build separates design and construction sequentially; design-build places both under one design-builder; construction manager at risk retains separate design and construction contracts while adding early construction input; and integrated project delivery aligns key participants through early collaboration and shared governance or incentives.

The following comparison covers four delivery methods: design-bid-build (DBB), design-build (DB), construction manager at risk (CMAR), and integrated project delivery (IPD). Each offers different responsibilities and trade-offs; no method is best for every project.

Design-Bid-Build (DBB)

Design-Bid-Build is generally sequential: the owner contracts separately with the architect or design team to prepare construction documents, then solicits contractor bids and awards a separate construction contract. Why Consider It:

  • ·       Price competition: Contractors price a common set of completed construction documents. A lump-sum award establishes the initial contract price, but changes, unforeseen conditions, and other contractual adjustments can affect the final cost.
  • ·       Separate design and construction responsibilities: The owner retains a direct relationship with the architect, whose construction-phase services are defined by the agreement. Contract administration and review support design intent and quality; they do not guarantee the contractor’s performance or create an unrestricted fiduciary role.
  • ·       Familiar procurement framework: Design-bid-build is widely understood and can support competitive public-sector bidding. Confirm that the proposed solicitation and award procedures comply with the requirements applicable to the owner and project.

When to Consider It:

  • ·       When price competition on fully completed documents is the primary decision driver.
  • ·       When time-to-market is not constrained, and there is ample time for sequential design followed by competitive bidding.
  • ·       When the project scope is conventional, highly predictable, and unlikely to require major mid-stream alterations.

Design-Build (DB)

In the traditional Design-Bid-Build model, the owner contracts separately with an architect and a contractor. In contrast, Design-Build unifies architectural/engineering design and construction under a single contract with a single entity (the Design-Builder). Why Consider It:

  • ·       Schedule overlap: Authorized early construction packages, such as foundations or core and shell, may begin before later design packages are complete. This can shorten the overall schedule, but requires coordinated scope, approvals, and management of changes between packages.
  • ·       Single contractual responsibility: The owner contracts with one design-builder for design and construction, simplifying coordination and accountability. The agreement determines the responsibilities, remedies, and risks retained by each party; a single contract does not eliminate disputes.
  • ·       Pricing approach: Design-build may use a fixed price or guaranteed maximum price (GMP), with timing dependent on the procurement approach and scope maturity. Progressive design-build develops scope and price collaboratively after team selection. Review allowances, exclusions, contingencies, and change provisions before treating a price as a limit on owner exposure.

When to Consider It:

  • ·       When speed-to-market is the absolute highest priority (e.g., rapid commercial expansion, highly competitive market windows).
  • ·       When the owner can define functional and performance requirements and review the design at agreed milestones, while assigning design-construction coordination to the design-builder.
  • ·       When the organization has a low tolerance for schedule overruns and prefers transferring design-construction coordination risk to a single entity.

Construction Manager at Risk (CMAR)

Under CMAR, the owner retains separate design and construction contracts and engages the construction manager early to provide preconstruction services, often during predesign or schematic design. The construction manager later assumes construction responsibility. A guaranteed maximum price (GMP) is commonly negotiated at an agreed level of design development; its scope, assumptions, allowances, exclusions, and change provisions determine the protection it provides. Why Consider It:

  • ·       Early constructability and cost input: The construction manager advises on material availability, labor costs, constructability, and value engineering during design. This can identify problems earlier and reduce redesign, rather than guarantee its prevention.
  • ·       Cost transparency: CMAR commonly uses cost-of-the-work-plus-fee pricing with GMP. Define access to subcontractor bids, cost records, contingencies, and any shared-savings provisions in the agreement; transparency depends on those provisions and their administration.
  • ·       Flexibility: It retains the traditional separation of design and construction contracts while introducing collaborative benefits.

When to Consider It:

  • ·       When the project is complex, technically challenging, or involves tight site constraints where early contractor insight is vital.
  • ·       When the owner needs continuing cost modeling and budget management during design rather than waiting for a lump sum bid after design is complete.
  • ·       When the organization values a collaborative relationship with the builder but wants an independent architect looking out for their design interests.

Integrated Project Delivery (IPD)

IPD integrates the owner, design team, and construction team through early collaboration and shared project goals. A multiparty agreement can establish shared governance and risk-and-reward arrangements, but IPD principles can also be applied through other contractual structures. Define each participant’s responsibilities, compensation, and risk allocation in the chosen agreements. Why Consider It:

  • ·       Aligned incentives and joint problem-solving: Shared goals and contractual incentives can encourage participants to resolve problems together and reduce duplication, waste, and disputes. They do not eliminate change orders, disagreements, or litigation.
  • ·       Coordinated innovation: Building Information Modeling (BIM) and team co-location can support concurrent evaluation of design and construction options. Their value depends on agreed information procedures and effective participation.
  • ·       Performance alignment: Establish shared sustainability, schedule, and budget targets and track achievement against them. IPD supports coordinated management of these objectives but does not guarantee superior results or the highest performance scores.

When to Consider It:

  • ·       For complex or highly technical facilities, such as advanced R&D laboratories, high-tech manufacturing plants, or healthcare environments, where early integration can help manage interdependent requirements and delivery risks.
  • ·       When the enterprise owner has a mature organizational culture capable of true collaborative governance and shared decision-making.
  • ·       When innovation, lifecycle efficiency, and waste reduction justify a collaborative risk-and-reward structure rather than a traditional fixed-bid approach.

Delivery Method Matrix

Delivery Method

Primary Advantage

Primary Risk to Owner

Best Suited For

Design-Bid-Build (DBB)

Competitive pricing on a common design and separate design and construction contracts.

Sequential design and bidding can extend the schedule; design gaps and changes can increase cost and disputes.

Traditional, non-urgent projects with fully defined scopes and strict competitive bidding requirements (common in public sector).

Design-Build (DB)

Potential schedule overlap and one contractual point of responsibility for design and construction.

Less direct owner control over evolving design details.

Fast-track projects, commercial spaces, standardized expansions.

Construction Manager at Risk (CMAR)

Early cost control, constructability input, and open-book transparency.

Incomplete scope, allowances, exclusions, and GMP adjustments can leave residual cost risk with the owner.

Complex buildings, urban constraints, phased capital projects.

Integrated Project Delivery (IPD)

Early collaboration and aligned risk-and-reward arrangements that can reduce waste.

Requires sustained owner participation, shared decision-making, and suitable contractual and risk arrangements.

Highly complex technical facilities, advanced labs, major corporate campuses.

After evaluating the delivery options, the project team, procurement manager, and executive sponsor select the method that best supports the enterprise’s objectives, subject to applicable approvals. The procurement manager then organizes the authorized sourcing and procurement activities.

3.3.2 Procurement Process

Procurement defines how the owner obtains external goods, professional services, and construction services. The project manager and procurement manager establish the sourcing strategy, responsibilities, selection criteria, and required approvals. The project sponsor approves solicitation and award within delegated authority; the sponsor seeks chief executive officer or administrator approval when thresholds require it. The project team proceeds only within those authorized limits. Contract administration and post-project review occur during design and construction but are summarized here so the owner can plan responsibilities, information requirements, and later approvals.

The procurement lifecycle moves from requirements definition and sourcing strategy through solicitation, evaluation and selection, contract negotiation and award, and contract administration and post-project review. Each transition requires applicable approval, and authorization at one stage does not automatically authorize later work. The stages below describe the broader procurement lifecycle. Plan their sequence during predesign, and distinguish activities authorized now from those requiring later approvals.

3.3.3 Requirement Definition and Sourcing Strategy

The project team, in coordination with procurement and legal departments, defines what needs to be procured (e.g., OPM services, architectural design, general contracting, or technology packages). The team aligns sourcing with the approved delivery method, define service scopes and responsibility boundaries, establishes selection criteria and budget limits, and confirms applicable procurement procedures and award authority.

3.3.4 Solicitation (RFQs and RFPs)

The enterprise goes to market by issuing formal procurement documents to invite qualified vendors and firms:

  • ·       Request for Qualifications (RFQ): Used primarily in the early stages to evaluate firms based on their experience, past performance, technical expertise, and financial stability, resulting in a short-list of qualified candidates.
  • ·       Request for proposals (RFP): Invite technical approaches, methodologies, staffing plans, and commercial proposals appropriate to the authorized selection procedure. An RFP may follow an RFQ shortlist, but the sequence and use of pricing depend on the procurement method and applicable requirements.

3.3.5 Evaluation and Selection

A cross-functional committee evaluates submissions against published criteria, such as technical competence, comparable project experience, ability to collaborate, and cost where permitted. Apply the approved selection procedure consistently and document the rationale. The committee conducts interviews or presentations with top-ranked candidates, performing reference checks, and selecting the optimal partner or contractor.

3.3.6 Contract Negotiation and Award

Legal, procurement, and project leadership negotiate the specific terms of the contract (e.g., indemnification, insurance, schedule milestones, fee structures, and warranty terms). The team coordinates contract documents, using appropriate AIA agreements or enterprise contracts where suitable. They confirm approved scope, funding, and delegated authority before award. Contract execution authorizes only the specified work; it does not automatically authorize construction or other subsequent phases.

3.3.7 Contract Administration and Post-Project Review

During predesign, the project team presents the delivery strategy to the project sponsor for review and approval and aligns capital expenditure (CAPEX), service scopes, and award authority with the approved business case and project baseline. Where early contractor or integrated-team input is needed, the team plans and obtains authorization for preconstruction services in time to inform feasibility, constructability, and cost modeling. A clear procurement strategy helps manage qualification, cost, coordination, and contractual risks; it does not guarantee their elimination. During project execution, the procurement and project management teams oversee vendor performance, manage change orders, process payment applications, and ensure contractual compliance. After completion, they conduct lessons-learned evaluations and feed historical cost and performance data back into enterprise systems.

3.3.8 Project Readiness Review

The Project Readiness Review tests validated planning inputs; design-ready requirements; reconciled scope, budget, and schedule; measurable success criteria; aligned delivery and procurement; visible risks and dependencies; digital information and AI readiness; and documented authorization and handoff. For each condition, the project manager identifies whether the evidence is satisfied, conditional, unresolved, or not ready, and assigns an accountable owner and next action to every gap. Phase success depends on the quality and alignment of the decisions that enable design, not simply on completion of activities. Use the following checklist to demonstrate readiness to proceed.

  • ·       Validated planning inputs: The project manager reviews headcount forecasts, hybrid work assumptions, and functional, technical, and operational needs with the responsible business units; the project manager documents assumptions and unresolved gaps.
  • ·       Design-ready requirements: The program of requirements defines space needs, standards, performance criteria, and scope boundaries clearly enough to guide design without prematurely prescribing design solutions.
  • ·       Reconciled scope, budget, and schedule: Preliminary CAPEX and OPEX models and a realistic schedule support the proposed scope; the project manager resolves material trade-offs and critical dependencies or explicitly identifies them for decision.
  • ·       Measurable success criteria: Stakeholders agree on qualitative and quantitative targets, how each will be assessed, and who will verify achievement during subsequent phases.
  • ·       Aligned delivery and procurement: The delivery method, external scopes of services, and sourcing approach support project objectives, risk tolerance, and schedule; responsibility boundaries are clear.
  • ·       Visible risks and dependencies: Material uncertainties and cross-functional dependencies have named responsible parties and defined next actions; the project manager surfaces issues that could prevent design readiness before authorization.
  • ·       Digital information and AI readiness: The project manager confirms that the team has defined authoritative sources, data ownership, common identifiers, quality and refresh rules, access controls, interoperability requirements, approved AI uses, human-review responsibilities, cybersecurity and privacy controls, and the information needed for design, procurement, commissioning, and operations. The team resolves material data quality and exchange failures or records them as conditions of authorization.
  • ·       The steering committee reviews the consistent project charter, program of requirements, and updated business case at the Project Readiness Review; the project manager preserves the decision to proceed, any conditions, and responsibility for outstanding actions in the decision record.

3.3.9 Review and Approval

The project manager concludes the Project Definition Phase by assembling the deliverables for the Project Readiness Review. The steering committee reviews alignment, the project sponsor recommends an authorization decision, and the chief executive officer or administrator decides when organizational authority requires that level of approval. These deliverables establish the basis for authorization to proceed to design:

  • 1.      Project charter: Document executive authorization through the project mandate, sponsorship, goals, and authorized resource allocations.
  • 2.      Program of requirements (POR): Document the space list, functional, technical, and performance requirements, and scope boundaries that define the design problem. Cross-reference the reconciled budget and schedule baseline and measurable success criteria. State what the project must achieve without unnecessarily prescribing how it must be designed.
  • 3.      Information-management and digital-delivery plan: Define the common data environment, authoritative sources, information requirements, data dictionary, identifiers, model and document exchanges, validation rules, cyber and privacy controls, approved AI uses, audit evidence, and handover to the asset information environment. Assign an owner and acceptance criterion for every required information deliverable.
  • 4.      Approved project delivery strategy: The project sponsor has approved the delivery strategy recommended by the project team and procurement manager, including the selected delivery method, sourcing approach, responsibility boundaries, procurement timing, and required decision gates.
  • 5.      Updated business case: The project team presents the rationale for proceeding in relation to business priorities, defined requirements, scope, budget, schedule, and delivery strategy to the project sponsor for approval.

Decision Gate

Primary Question

Action Required

Project Readiness Review

Are the project requirements, scope, budget, schedule, and stakeholder alignment established for design?

Review the requirements, feasibility, scope, budget, schedule, risks, and stakeholder alignment. Record whether design is authorized, authorized with conditions, deferred, or not authorized, together with outstanding actions and accountable parties.

Prepared by Steven Parshall, with the use of AI agents. © Copyright of the Strategic Predesign Association

Feedback on this section

Click on POST to share your thoughts, ideas, comments, and constructive critiques about this section. Tell us what is unclear, what could be improved, and what additional topics we should address.

© 2026 Strategic Predesign Association

Domain: pred-int.org

Powered by Wild Apricot Membership Software