6 Activities
What Participants Do
Introduction 1.0 Activity Types 2.0 Phase-Based Activity Framework 2.1 Strategic Planning Phase 2.2 Real Estate Phase 2.3 Project Definition Phase | 3.0 Cross-Phase Controls & Participation Methods 4.0 Activity Descriptions by Phase 4.1 Strategic Planning Phase 4.2 Real Estate Phase 4.3 Project Definition Phase |
Introduction
Strategic planners, portfolio asset managers, program managers, and architectural programmers lead activities that support the intended process outcomes. With support from the project sponsor, they select activities and allocate resources appropriate to the initiative’s scope and the complexity of the built environment. They adapt these activities as conditions change and use a process checklist to verify that the required tasks are complete. Guided by established process principles, they use tools and techniques to organize and manage the work, assemble and manage data, analyze information, communicate with constituents, and produce deliverables. The resulting information and deliverables are incorporated into a decision-support system that supports a coordinated process, reliable data access, and informed decisions.
This chapter organizes strategic predesign activities by Strategic Planning, Real Estate, and Project Definition, matching the Process chapter. The eight activity types below classify the work across these phases; they are not sequential steps. Section 2.0 identifies the phase-based activity framework, Section 3.0 describes continuing controls and participation methods, and Section 4.0 retains illustrated activity descriptions grouped by phase. Activities overlap and may recur as assumptions, requirements, and options change.
|
Type of Routine Activity |
Purpose |
Activities |
|
1. Strategic alignment and goal setting |
Establish organizational direction, project purpose, success criteria, and planning assumptions. |
Executive interviews; leadership goal setting for project definition. |
|
2. Information gathering and needs assessment |
Understand workflows, growth expectations, user needs, service requirements, and location priorities. |
Business unit interviews and needs reviews; stakeholder requirements; service manager interviews; surveys and individual follow-ups. |
|
3. Collaborative analysis and requirements development |
Reconcile competing needs, test assumptions, and consolidate requirements into a shared basis for planning and design. |
Collaborative strategy development; stakeholder review workshops; real estate requirements; Program of Requirements (POR). |
|
4. Site and building evaluation |
Assess physical options, identify constraints, and determine what further investigation is needed. |
Candidate site visits; leased-space visits; specialist due diligence on building systems. |
|
5. Options appraisal and business-case development |
Compare alternatives using consistent criteria and explain the recommended investment direction. |
Facility strategy recommendations; real estate option comparisons; business-case development and review. |
|
6. Communication and consultation |
Explain evidence, recommendations, and trade-offs; gather feedback and confirm understanding. |
Stakeholder meetings and presentations; public authority presentations; in-person and videoconference meetings. |
|
7. Governance, review, and authorization |
Track issues, clarify decision authority, and record approvals, deferrals, conditions, and next steps. |
Project sponsor reviews, steering committee meetings; board briefings; executive leadership presentations. |
|
8. Transaction and implementation preparation |
Translate documented needs and due diligence findings into practical commitments. |
Lease negotiations addressing price, contract terms and conditions, modifications, responsibilities, and unresolved requirements and constraints. |
Use this framework with the Process chapter’s work breakdown structure. Scale the activities to the assignment and identify conditional work explicitly. Describe each activity using a consistent sequence: purpose, accountable lead, inputs, work performed, output, review or approval, and subsequent use. An interview or workshop is a method; a business case or Program of Requirements is an output; neither replaces the underlying analytical work or authorization decision.
Establish strategic direction: The strategic planner confirms the mandate, reviews strategic context, facilitates executive vision and business-unit inquiry, and translates priorities into facilities implications.
Establish the evidence baseline: The strategic planner and data owners define authoritative sources, validation, access, refresh, and controlled AI review responsibilities before relying on analysis.
Forecast demand and diagnose the portfolio: Planning, finance, operational, and facilities participants determine demand ranges, capacity, condition, utilization, occupant experience, obligations, and the bounded demand–supply gap.
Develop and evaluate scenarios: The team compares distinct alternatives and a credible baseline using common assumptions, criteria, multiyear CAPEX, rent and OPEX models, and sensitivity testing.
Prepare and review the business case: The strategic planner integrates strategic fit, alternatives, value, risks, implementation requirements, and the decision request.
Authorize direction and transfer the baseline: The sponsor or higher authority records next-phase scope, conditions, unresolved actions, and whether to advance to Real Estate or directly to Project Definition.
Conditional work: Combined-portfolio integration planning addresses merger or acquisition requirements when applicable.
Confirm strategy and approve selection criteria: The portfolio and asset manager translates approved direction into preliminary requirements, mandatory thresholds, weighted preferences, evidence requirements, and an approved evaluation method.
Survey and screen the market: The real estate advisor identifies candidates, documents screening and exclusion reasons, develops the shortlist, arranges visits, and maintains credible fallback options.
Coordinate specialist due diligence: Qualified specialists investigate legal, environmental, title, survey, entitlement, building, utilities, technology, accessibility, and other material constraints. The portfolio and asset manager integrates findings and assigns unresolved risks.
Test spatial and financial feasibility: The team develops preliminary test fits or site-opportunity studies and compares lifecycle costs, occupancy timing, transition requirements, and flexibility under common assumptions.
Update the business case and negotiate: The portfolio and asset manager presents the preferred alternative and obtains negotiation authority before developing commercial and delivery terms with advisors and legal counsel.
Authorize and execute commitments separately: The authorized decision-maker accepts the required evidence and residual risks; the authorized signatory executes only the approved documents and limits.
Transfer the accepted baseline: The portfolio and asset manager hands objectives, requirements, feasibility findings, financial and schedule ranges, terms, decisions, and open actions to the project manager.
Conditional work: Relocation, temporary accommodation, decommissioning, continuity planning, and public communication are included when the initiative requires them.
Mobilize the project and approve the charter: The sponsor assigns project and IT managers; the project manager confirms the entry baseline, governance, authority, scope boundaries, resources, and participation plan.
Define and procure specialist services: The project manager coordinates specialist scopes with procurement and legal participants, obtains applicable solicitation and award approvals, and mobilizes providers under executed agreements.
Establish information responsibilities: The project and information managers define the common data environment, source ownership, identifiers, revisions, validation, access, exchanges, and information-delivery requirements.
Develop and validate requirements: The programming team establishes goals, collects and validates facts, analyzes workflows and adjacencies, tests programmatic concepts, and quantifies capacity, space, and technical performance requirements.
Reconcile feasibility and project baselines: The project manager coordinates cost and schedule analysis and resolves or escalates mismatches among scope, quality, budget, schedule, property fit, and risk.
Prepare and approve the POR: The programmer synthesizes requirements and concise problem statements; designated owner reviewers validate the supporting evidence and approve the requirements baseline.
Develop delivery and procurement strategy: The project manager and procurement manager compare methods, define responsibility boundaries, and plan packages, selection procedures, timing, and separate authorization gates.
Conduct readiness review and handoff: The project manager assembles the reconciled business case and readiness package, the steering committee reviews alignment, and the authorized owner records the decision and conditions. When authorized, the project manager publishes the controlled baseline and briefs the receiving design team.
Conditional work: Master planning, prototype development, and pilots are included where needed to test site-scale requirements or repeatable concepts.
Information and evidence: Maintain authoritative sources, validation status, assumptions, versions, access controls, human review of material AI outputs, and reproducible decision evidence.
Risk, issues, and decisions: Keep current registers with accountable owners, resolution requirements, escalation paths, authorization limits, and recorded conditions.
Requirements and change control: Retain approved baselines and evaluate, authorize, and record departures that affect objectives, scope, quality, cost, schedule, or feasibility.
Communication and participation: Select interviews, surveys, workshops, presentations, and in-person or videoconference participation to suit the audience and inquiry. Record qualifications and unresolved disagreement; do not treat silence as validation or approval.
Review and handoff: Confirm outputs, acceptance criteria, receiving-party responsibilities, outstanding actions, and the specific work authorized at each transition.=
4.0 Activity Descriptions by Phase
|
4.1 Strategic Planning Phase |
|
Business Unit Leader Needs Review |
Business unit leaders review space needs, anticipated team growth, location priorities, and operational requirements. The review distinguishes current needs from future assumptions and coordinates unit-level requirements across the organization, identifying overlaps and competing demands. |
|
|
Collaborative Strategy Development |
Leaders, planners, and end users develop strategies from a shared evidence base. They test assumptions, reconcile competing needs, and document trade-offs and decisions. This collaboration creates a coordinated set of requirements and a clear rationale for the proposed direction. |
|
|
Recommending Facility Strategies |
Options to expand, optimize, transform, or contract the real estate footprint are compared against common criteria. The assessment considers cost, risk, space utilization, and capital needs. Documented assumptions and trade-offs explain why the recommended facility strategy best supports organizational goals. |
|
|
Board of Directors Briefing |
The board briefing presents the project’s purpose, strategic priorities, expected outcomes, and recommended direction. It summarizes investment implications and principal risks, identifies the decision requested, and separates matters submitted for approval from information provided for oversight. |
|
|
Business Case Development and Review |
The business case combines the strategic rationale, investment summary, expected benefits, and risks. It compares the recommendation with alternatives and explains the assumptions behind cost and benefit estimates. Review confirms the rationale for proceeding and identifies uncertainties requiring resolution before approval. |
|
|
Occupant Surveys and Individual Follow-ups |
The portfolio asset manager coordinates individual input through one-on-one follow-ups, including with people working at home. Findings supplement leadership interviews and identify needs that group discussions may miss, helping connect workplace requirements with portfolio planning. |
|
4.2 Real Estate Phase |
|
|
Requirements for people, processes, technology, place, and capital are translated into comparable real estate options. Each option is tested against the same goals and requirements. The comparison documents advantages, constraints, and trade-offs, providing a clear basis for selecting a direction. |
|
|
Site Visit |
The portfolio asset manager, real estate advisor, and key stakeholders visit candidate sites and assess them against documented site-selection criteria. They record observations, constraints, and unanswered questions. Findings support comparison of the sites and identify further due diligence needed before selection. |
|
|
Stakeholder Presentation |
Stakeholders review the recommendation alongside project objectives, option scores, and decision criteria. The presentation explains the evidence and trade-offs, checks understanding, and records feedback and unresolved concerns for consideration before the proposed direction is finalized. |
|
|
Lease Space Visit |
Existing or prospective leased space is reviewed for fit with documented requirements, flexibility, and anticipated modification costs. The visit identifies spatial constraints and questions about building suitability. Findings guide feasibility investigations; the visit alone does not establish technical adequacy. |
|
|
Due Diligence on the Building Systems Performance |
Qualified specialists assess relevant building systems against intended use and performance requirements. The agreed scope combines site observations, available records, and testing where needed. Findings document condition, capacity, deficiencies, and assessment limits, identifying further investigations and potential upgrade needs rather than assuming adequacy from a walkthrough. |
|
|
Lease Negotiations |
Predesign and due diligence findings give the negotiation team a documented basis for evaluating lease terms. They clarify space needs, required modifications, and unresolved constraints. The team uses these findings to address project requirements and responsibilities in the proposed lease, with appropriate legal review. |
|
|
Public Authority Presentations |
The project sponsor will present to public authorities like city councils to explain the project’s purpose, supporting evidence, options, and recommendations. It makes the trade-offs understandable for community discussion and council consideration, clearly distinguishing public feedback from any formal decision or authorization requested. |
|
4.3 Project Definition Phase |
|
|
Leadership defines the goals the project must serve and the outcomes that will indicate success. These goals provide the basis for project definition and evaluation criteria, allowing requirements, site findings, and proposed options to be tested against a shared purpose. |
|
|
Business Unit Interviews |
Leaders from research and development (R&D), sales, operations, and finance explain their workflows and opportunities for improvement. Interviews identify the activities and relationships that space must support, translating operational insights into future requirements rather than simply reproducing existing arrangements. |
|
|
Stakeholder Requirements |
People who use the workplace daily describe their activities, practical needs, and constraints. Their input is reviewed against organizational goals to distinguish preferences from justified project requirements. The resulting record makes user needs explicit and provides a basis for resolving competing priorities. |
|
|
Service Manager Interviews |
Human resources (HR), information technology (IT), security, and food service managers define their services’ operational and support requirements. These needs are coordinated with user and business unit requirements so the building can support both daily work and the services needed to operate it. |
|
|
Participation Method: Videoconference Meetings |
Videoconference meetings gather input from distributed teams and multi-site organizations using consistent questions and documentation. Findings are combined with in-person interviews to identify shared and location-specific needs, ensuring that remote participation contributes to the same requirements review. |
|
|
Stakeholder Review Workshop |
Stakeholders review the evidence, confirm evaluation criteria, and weigh trade-offs among options. The workshop tests the proposed direction against agreed needs and documents areas of agreement, outstanding concerns, and issues requiring escalation. Its recommendation supports subsequent review and approval. |
|
|
Steering Committee Meeting |
The steering committee reviews progress, decisions, and open issues within its assigned authority. A shared record captures decisions, responsible parties, and next steps. Matters requiring higher-level approval are identified for escalation, maintaining continuity and accountability between meetings. |
|
|
Presenting the Program of Requirements (POR) for Approval |
The architectural programmer presents the Program of Requirements (POR) for review and approval. It consolidates leadership goals, functional needs, space quantities and relationships, performance targets, experience-based user input, and project drivers. It provides a brief for the A/E design team that aligns the scope with budget and schedule constraints, defining what the project must achieve without prescribing its design solution. |
|
|
Executive Leadership Presentation |
The executive presentation summarizes the recommended direction, supporting rationale, financial implications, and next steps. It identifies the decision requested and any outstanding conditions. The decision record documents what leadership approves, defers, or returns for further work, distinguishing the recommendation from the authorized direction. |
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.
Go to Explore the Practice |