8 Techniques
Practical Methods, Tools, Templates, Deliverables to do the Work
Introduction 1.0 Methodology: Problem Seeking to Strategic Predesign 1.1 Shared Method of Inquiry 1.2 Broader Scope and Process Structure 1.3 Working Methods and Decision Outputs 1.4 Enabling Role of AI | 2.0 Techniques 2.1 Strategic Planning and Business Case 2.1.1 Tools, Templates and Deliverables 2.2 Real Estate Evaluation and Selection 2.2.1 Tools, Templates and Deliverables 2.3 Project Definition and Program of Requirements (POR) 2.3.1 Tools, Templates and Deliverables 2.4 Change Management and Adoption Readiness 2.4.1 Tools, Templates and Deliverables |
Techniques are repeatable methods for doing work. Activities perform the work. Tools and templates apply the methods and record results. Deliverables record findings, recommendations, and decisions. Choose the methods to use that fit the scope and level of effort of the project. Use them iteratively throughout the process: strategy guides property and project requirements, while feasibility findings may require earlier assumptions or choices of an earlier phase to be reconsidered.
Each phase produces controlled records that preserve evidence and explain the basis for a decision. Strategic Planning produces the strategic plan, portfolio priorities, and initial business case. Real Estate produces selection criteria, property search and appraisal findings, due diligence by specialists, transaction recommendation and authorization record, and a handoff package. Project Definition produces the charter and governance arrangements, program of requirements (POR), scope, budget, and schedule baseline, and delivery and procurement plan. Maintain one traceable business case across all three phases, updating it at gates and after material changes. The final readiness package includes the updated business case, review report, decision record, and, if there is authorization to proceed, handoff documents.
Change management supports project delivery, especially during programming and design. The change manager helps stakeholders explain their concerns and understand proposed changes, keeps the project team informed of misunderstandings or objections, and prepares people for the new work environment. Programmers lead requirements work. The project manager coordinates decisions, issues, actions, and formal change control; the change manager contributes to those existing records rather than maintaining a parallel system. Communications work with the change manager and project manager to issue approved project messages.
The strategic planner leads Strategic Planning, the portfolio asset manager leads Real Estate, and the project manager leads Project Definition. The strategic planner coordinates the initial business case; the portfolio asset manager coordinates property-stage inputs; the project manager coordinates the updated case and gate submission during Project Definition, retaining strategic-planner review of strategic continuity. Financial analysis is an explicit specialist workstream, while Finance, Legal, Procurement, IT, and information-security functions have assigned mandatory controls. Until a project manager is appointed, the sponsor names the phase coordinator and recordkeeper. For every material record, retain an identifier, named owner, date, version, sources, units, assumptions, limitations, review status, unresolved conditions, approval links, and change history. Following the organization’s policies, the information systems manager controls the use of data sources, software and AI applications; content owners and specialists are responsible for evidence, the work performed, and the validation of sources and deliverables.
Problem Seeking and Strategic Predesign share a central principle: understand and define the problem before committing to a solution. Problem Seeking provides a systematic method of architectural programming. Strategic Predesign builds on that method within a broader framework that connects organizational priorities with decisions about facilities, location, and project requirements. It extends the scope of inquiry and the methods used to support decisions while retaining the discipline of problem definition.
Problem Seeking organizes inquiry into five steps: Establish Goals, Collect and Analyze Facts, Uncover and Test Concepts, Determine Needs, and State the Problem. Each step examines four considerations: Function, Form, Economy, and Time. Together, these steps and considerations help the team translate client goals and evidence into a clear statement of the architectural problem and the requirements a design must meet.
Strategic Predesign carries this discipline into the decisions that precede and frame a project. Both approaches use inquiry and analysis to clarify goals, test assumptions, identify strategies and programmatic concepts, and establish requirements. Strategic Predesign connects that work to the organization’s purpose, the evaluation of alternatives, and the authority to proceed. The comparison is therefore between a method of inquiry and a broader framework for applying that inquiry to organizational and facilities decisions.
In its architectural application, Problem Seeking defines the problem the design of a proposed building or group of buildings must address. Strategic Predesign begins with the organization and considers how facilities decisions can support its mission and operations. Its strategic planning phase examines organizational direction, portfolio priorities, change, alternative futures, and business cases. Its real estate phase develops location strategy and site criteria, evaluates market options, and conducts technical due diligence. Its project definition phase translates the preceding decisions and evidence into a project charter and procurement strategy in addition to developing the facility requirements for approval before design authorization.
The five steps of Problem Seeking and the three phases of Strategic Predesign describe different levels of work. The five steps structure inquiry; the three phases organize the broader decision process. They are not matching sequences. Inquiry can recur within and across phases as the team tests alternatives, identifies missing information, and responds to changing evidence or conditions.
The Strategic Predesign framework applies activities, procedures, and techniques. Activities are the repeatable work participants undertake. Procedures explain how to carry out, coordinate, and review that work. Techniques are the practical methods, tools, and templates used to produce reviewable outputs. This framework explains continuity between the two approaches: the core logic of inquiry can remain stable while work practices and tools expand to address a wider scope of application. Technology enables how the team gathers and analyzes information; it does not remove the need to define the problem or exercise judgment.
Problem Seeking leads to a statement of the architectural problem and its requirements. Strategic Predesign places project definition within a wider decision framework involving organizational roles, accountability, governance, and supporting resources. It concludes with a documented Project Readiness Review and, when design is authorized, a controlled handoff to design. The review supports the authorization decision; it does not mean that authorization has already been granted. Review and approval record decisions based on the evidence available at that time. When material evidence or conditions change, the team updates the affected analysis and business case and reassesses the relevant decisions.
Common methodology provides a useful basis for applying artificial intelligence. AI can support the work of inquiry, but it is not a substitute for the method or the people responsible for decisions. These features of Problem Seeking offer opportunities for AI support within Strategic Predesign: systematic inquiry, experience-based judgment, and pattern recognition. In each application.
Systematic inquiry: The architectural information index organizes considerations and procedures relevant to defining a problem. It guides inquiry. The standard index provides a general framework that is adapted to the project. AI can help prepare a tailored index from the standard framework using preliminary background information, such as the project charter, briefings and relevant source material. Applications may include workplace planning, urban or campus planning, specific building types, engineering processes, or business operations. The team should review proposed additions and omissions for relevance and completeness.
Experience-based judgment: Architectural programmers using Problem Seeking apply heuristics—practical rules of thumb based on experience—to decide which information to analyze and which questions to ask. They test these judgments against project evidence. Machine-learning models learn patterns from training data; a language model can also use source material supplied or retrieved for a task without learning from it through retraining. Neither capability is equivalent to professional experience. A programmer can use AI to draft project-specific questions, suggest follow-up inquiries, and identify gaps in available information. The programmer then checks the questions for relevance and unsupported assumptions before using them.
Pattern recognition: Architectural programmers use analysis cards, wall displays, and content analysis to examine program information for relationships, recurring themes, and conflicts. These findings help define the problem and the requirements a solution must meet. AI can assist by grouping related information, highlighting possible patterns, and flagging potentially conflicting statements for review. A repeated theme is not necessarily a priority, and an apparent conflict may reflect different stakeholder needs or contexts rather than an error. The team should trace proposed findings to their sources and interpret them in the organizational and project context.
Visualization: Architectural programmers use graphic techniques to organize information and present it for review and evaluation. Traditional methods include wall displays of analysis cards and flip charts. Digital displays and collaborative whiteboards, such as Miro, extend this approach by giving project teams a shared workspace. These visual formats help owners, users, programmers, and design teams examine relationships, compare alternatives, and understand the implications of program requirements.
These techniques are also useful in Strategic Predesign. AI can help prepare visual material, such as diagrams based on text, graphs based on spreadsheet data, and dashboards based on database information. Digital displays and collaborative whiteboards provide ways to present and explore information. Virtual reality could offer an additional way to explore large information displays, although practical applications for this purpose still need to be developed and tested.
Techniques are repeatable methods for doing work required to produce a result or output. They use tools and templates to produce reviewable records or presentable decision packages. For the following techniques, the narrative states its purpose, timing, coordinators, contributors, and controls. Deliverables may be sections of a combined report rather than separate publications.
Each group of techniques is followed by its corresponding tools, templates, and deliverables table. The tables identify the tools, templates, deliverables, conventional methods, and AI-assisted methods used to do the work. Conventional methods and AI applications provide options to consider. Choose methods that fit the project scale and complexity. Use meeting transcription and photography with the required permissions and privacy safeguards.
1. Existing Condition Assessment by Location: Establish a dated, reliable baseline of existing asset conditions by location. The portfolio asset manager coordinates asset classifications, ownership and lease commitments, condition, usable capacity, utilization, service performance, and costs. HR and business owners validate workforce and activity forecasts; operations, IT, security, and qualified specialists validate their inputs and constraints. The data analyst reconciles space inventory, area definitions, units, periods, sources, coverage, and confidence, distinguishing observed occupancy from future demand. The financial analyst reconciles cost inputs with Finance and Legal, and the information systems manager maintains the database of files and records.
2. Executive Vision and Strategy: The head of real estate meets periodically with the chief executive and annually with business-unit or administrative leaders to understand business direction, real estate expectations, and workplace needs. When portfolio performance needs to change, the head of real estate appoints a strategic planner to lead an initiative and coordinates any initiatives running at the same time. The strategic planner interviews senior executives and, where useful, holds vision sessions with key stakeholders. The planner records the vision, goals, strategies, and direction the initiative must achieve. This record provides the basis for strategic planning.
3. SWOT Analysis, Competitive Forces Analysis, and Portfolio Analysis Prioritization: Connect business objectives to credible facilities and portfolio responses through complementary analyses. During strategic alignment and portfolio reviews, the strategic planner leads an evidence-based assessment of internal strengths and weaknesses and external opportunities and threats. Use competitive-forces analysis where relevant to business strategy, not as a substitute for property analysis. The portfolio asset manager compares responses for strategic appropriateness, dependencies, resources, timing, and risk, drawing on advisors and stakeholders. Refresh findings when business direction, demand, technology, or market conditions change. Executives authorize portfolio priorities; SWOT findings alone neither rank investments nor approve them.
4. Gap Analysis: Compare current capacity and performance with validated future needs using matching definitions, locations, units, and periods. After baseline and demand review, the strategic planner coordinates the comparison with the portfolio asset manager and planners; the data analyst checks comparability, while HR, operations, IT, and stakeholders validate forecasts and service assumptions. Identify shortages, surplus, unsuitable assets, performance gaps, and timing conflicts. Investigate causes and business consequences, then test operational change, reuse, consolidation, and other feasible responses before assuming additional space or a transaction is needed. Reassess when supply, demand, or assumptions change.
5. Scenario Planning: Test strategic options against coherent, plausible future conditions before major commitments. The strategic planner establishes the problem boundaries and works with portfolio, HR, workplace, IT, operations, and business stakeholders to develop explicit demand, work-pattern, technology, resource, and timing assumptions. The data analyst compares the same options and objectives across scenarios; the financial analyst tests financial consequences, and Finance reviews fiscal assumptions. Identify robust choices, contingencies, and monitoring or reassessment triggers, retaining controlled model versions. Revisit pivotal uncertainties as evidence changes. Scenarios explore alternatives; they are not predictions or probabilities unless supported by evidence.
6. Options Appraisal and Business-Case Development: Develop a traceable comparison of credible ways to meet a defined business need. Establish measurable objectives, screen a long list, and compare business as usual with feasible operational, reuse, and property alternatives using consistent demand assumptions and horizons. Assess strategic fit, costs, quantitative and qualitative benefits, risks, affordability, commercial feasibility, and delivery capability; disclose exclusions and trade-offs. The strategic planner leads the initial case, the portfolio asset manager integrates property appraisal, and the project manager coordinates Project Definition updates with strategic-planner review. Estimators, schedulers, financial and data analysts, Finance, Legal, and Procurement validate their assigned inputs. Maintain one living case across phases and revalidate it at gates or material changes. The sponsor endorses the recommendation within delegation; the designated authority authorizes stated commitments. Scores and financial measures support judgment, not automatic approval.
7. Risk Assessment and Sensitivity Analysis: Assess uncertain events separately from gaps in data, forecasts, and models, and test their effects on affordability, feasibility, timing, and option rankings. The phase lead coordinates specialists and assigns risk owners, responses, and residual exposure. The data analyst checks evidence and ranges; the financial analyst leads financial tests with estimators and Finance, while schedulers test timing. Use single-variable sensitivity and combined scenarios to examine material interactions and thresholds that change the preferred option. Record model validation, assumptions, limitations, and reassessment triggers; avoid double-counting risk, contingency, and estimation bias. Repeat when evidence changes and escalate residual exposure beyond delegated limits.
8. Lifecycle Value and Master-Schedule Analysis: Compare whole-life consequences and logic-linked timing before commitments. Estimators prepare scoped capital, occupancy and operating, renewal, transition, and end-of-life cost inputs with operations, IT, technical specialists, and real estate advisors. The financial analyst prepares comparable cashflow and value models, documenting horizons, currency, price date, inflation, residual values, discounting where used, funding assumptions, exclusions, and uncertainty. Finance validates conventions and affordability; the data analyst checks consistency. Schedulers link approvals, lease dates, enabling work, procurement, delivery, activation, and handoff milestones and test delays and dependencies. The phase lead integrates findings into the business case; the project manager controls the project baseline once appointed. Update material changes. Model acceptance neither authorizes funding nor guarantees completion.
9. Strategic Plan: Translate business objectives and validated evidence into a coordinated facilities strategy before the strategic phase decision. The strategic planner synthesizes stakeholder research, baselines, forecasts, gaps, scenarios, and appraisal, retaining alternatives and decision rationale. Portfolio, workplace, HR, IT, operations, security, and technical contributors validate relevant inputs; estimators, schedulers, and Finance Review Resource Assumptions. State preferred direction, measurable outcomes, planning horizon, initiative owners, resources, dependencies, implementation sequence, review dates, and reassessment triggers. Revise when objectives or material assumptions change. The sponsor endorses the plan, and the designated authority accepts direction within its powers; this does not itself authorize individual projects or transactions.
10. Portfolio Priorities: Prioritize and sequence facilities initiatives within business and resource constraints. The portfolio asset manager compares strategic outcomes, mandatory needs, asset suitability and condition, utilization, value, reuse and expansion or contraction options, dependencies, funding, delivery capacity, timing, and risk. The strategic planner checks alignment and relevant advisors, service owners, estimators, schedulers, and analysts validate evidence. Make scoring criteria and trade-offs transparent, test ranking sensitivity, and avoid double-counting shared benefits. Assign owners and review triggers, updating priorities when material conditions change. Executives authorize priorities and allocations; ranking does not itself authorize a budget, transaction, or project.
11. Initial Business Case: Document whether proceeding to the next stage is justified and state the precise decision requested, commitment limits, and conditions. During Strategic Planning, the strategic planner consolidates the need, objectives, baseline, alternatives, preferred direction, value, affordability, commercial and delivery feasibility, risks, sensitivity, and roadmap. Domain owners and specialists validate inputs; estimators and schedulers provide cost and timing bases, financial analysts prepare models, data analysts check comparisons, and Finance validates conventions and funding assumptions. Identify benefits owners, measures, uncertainty, and further investigations. The sponsor endorses the recommendation and owns intended outcomes; the designated authority authorizes only stated commitments. Maintain the same business case through Real Estate and Project Definition, updating it at gates and after material changes.
12. Decision Briefings: Brief the designated authority on a specific decision before gate or commitment reviews; refresh the briefing if evidence changes. The named recommender, normally the phase lead, presents the problem, evidence, alternatives, criteria, trade-offs, financial implications, risks, dissent, conditions, and requested decision. The strategic planner checks business-case alignment and specialists confirm their contributions; Communications supports clear presentation and distribution. Obtain sponsor endorsement where required, distinguishing consultation and technical concurrence from authorization. Retain the reviewed briefing and its links to controlled evidence and the actual decision.
13. Decision, Action, and Issues Tracking: Maintain distinct records of actual decisions, assigned actions, and unresolved issues throughout predesign. The phase lead checks decision wording against authorization evidence and records rationale, limits, conditions, and any departure from the recommendation, including residual risks and reassessment duties. Named actors accept actions and deadlines; specialists confirm technical closure. Keep evidence, escalation routes, and closure criteria current, and transfer custody and open responsibilities at handoff. The information systems manager retains controlled versions and Communications distributes approved direction. Notes or proposed actions are not authorization.
14. AI-Assisted Work Governance: Control each approved AI task through human accountability, permitted data, source checks, and documented review. Use Govern, Guide, Guard as this chapter’s shorthand, not a claim of external-framework compliance. Govern: the sponsor or delegated authority approves purpose and accountability; the information systems manager controls authorized tools. Guide: phase leads set boundaries, evidence requirements, and reviewers; analysts and specialists validate outputs against sources and checked calculations. Guard: information systems, IT, security, Legal, and HR apply access, privacy, protection, logging, incident, and escalation controls. Reassess changes in tools, data, permissions, or consequences. Generated material is not verified evidence, and AI cannot authorize commitments; responsible humans validate each contribution and the integrated result.
15. Evidence Management and Integrated Decision Support: Maintain reliable, connected evidence from initiation through handoff. The strategic planner sponsors the information operating model, and the project manager coordinates its acceptance during Project Definition. The information systems manager maintains repositories, integrations, metadata, permissions, version status, retention, and audit trails; IT, security, Legal, and HR validate applicable protection and records controls. The data analyst checks definitions, provenance, coverage, and analytical treatment; source owners and specialists validate meaning and content, and financial analysts preserve model assumptions and review evidence. Phase leads link sources to requirements, analyses, recommendations, and decisions. Acceptance of the information environment does not confer technical approval or commitment authority.
|
Technique |
Descriptions |
Tool, Template, Deliverable |
Conventional Methods |
AI Applications |
|
1. Existing Condition Assessment by Location |
Establish current property conditions, capacity, use, costs, and commitments by location, and compare them with checked workforce and activity forecasts. |
Tool: Asset, lease, and workforce databases; baseline reconciliation workbook. Template: Asset/capacity inventory; demand forecast; data dictionary and source/assumption register. Deliverable: Reviewed baseline and forecast register with confidence, limitations, and named data owners. |
Analysis: spreadsheet; maps; drawing / modeling software; digital twins. |
Organize: Extract dated asset, lease, workforce, capacity, utilization, and cost inputs. Draft inventories, data dictionaries, and source registers. |
|
2. Executive Vision and Strategy |
Understand executive vision, goals, and strategy, and record the direction for the strategic planning initiative. |
Tool: Question sets for executive interviews and vision sessions. Interview and meeting calendar invitation. Agenda. Template: Question response categories form. Vision session agenda. Deliverable: Strategic Initiative Vision and Strategy Report. |
Collaboration: calendar; meeting scheduler; email; video conference system; display monitor; whiteboard; digital canvas. |
Prepare: Draft executive interview questions, vision-session agendas, invitations, and presentation materials. |
|
3. SWOT Analysis, Competitive Forces Analysis, and Portfolio Analysis Prioritization |
Assess business strengths, weaknesses, opportunities, threats, and relevant competitive forces to inform portfolio options and priorities. |
Tool: Strategy-analysis worksheets and portfolio comparison workbook. Template: SWOT/context matrix; competitive-forces worksheet where applicable; portfolio-options and evaluation matrix. Deliverable: Reviewed strategic diagnosis and portfolio-options assessment linked to priorities and business cases. |
Analysis: spreadsheet; web site. |
Organize: Summarize research and classify evidence into strengths, weaknesses, opportunities, threats, and relevant competitive forces. |
|
4. Gap Analysis |
Compare current capacity and performance with future needs, identify gaps, and test feasible responses before assuming more space is needed. |
Tool: Capacity and demand workbook and gap-analysis worksheet. Current state: Validated capacity, utilization, condition, service performance, and constraints by location. Future state: Business-validated demand and performance requirements using matching units and planning horizons. Gaps: Shortages, surplus capacity, unsuitable space, or timing conflicts; record causes, consequences, and uncertainty. Template: Current-state/future-state matrix with sources, assumptions, gap, response options, and owner. Deliverable: Reviewed gap findings and response options supporting planning decisions. |
Analysis: spreadsheet; drawing / modeling software; digital twins. |
Organize: Align current capacity and performance with future demand by location, definition, unit, and period. |
|
5. Scenario Planning |
Test the same options against plausible future conditions to identify resilient choices, backup plans, and reasons to reassess. |
Tool: Scenario-planning workshop aids and linked demand/capacity models. Template: Scenario matrix; assumptions register; option-performance and trigger table. Deliverable: Documented scenarios, comparative findings, contingencies, and monitoring triggers. |
Analysis: spreadsheet; scheduling software; drawing / modeling software; digital twins. |
Prepare: Draft scenario narratives and assumption registers covering demand, work patterns, technology, resources, and timing. |
|
6. Options Appraisal and Business-Case Development |
Compare feasible ways to meet the business need and explain the preferred option, its value, risks, affordability, and approval needs. |
Tool: Options-appraisal workbook; financial model; structured review workshop. Template: Options matrix, assumptions register, and business-case outline covering strategic, value, commercial, financial, and delivery considerations. Deliverable: Traceable appraisal and recommended course, with conditions and required approvals, maintained in one living business case. |
Analysis: spreadsheet; scheduling software. |
Organize: Compile objectives, business-as-usual and alternative options, evidence, assumptions, and appraisal criteria. |
|
7. Risk Assessment and Sensitivity Analysis |
Identify risks and test how changes in key assumptions affect costs, timing, feasibility, and the preferred option. |
Tool: Risk register; sensitivity workbook; financial and schedule models. Template: Risk/response register; assumptions-quality log; sensitivity and switching-threshold table. Deliverable: Reviewed risk exposure, response actions and owners, sensitivity findings, and reassessment triggers. |
Analysis: spreadsheet; scheduling software. |
Prepare: Extract risks and uncertain assumptions from project evidence. Draft risk questions, response options, owner fields, and sensitivity-test tables. |
|
8. Lifecycle Value and Master-Schedule Analysis |
Compare costs and value over the same lifecycle and link them to a schedule of approvals, commitments, delivery, and transition. |
Tool: Controlled cash-flow workbook and logic-linked master-schedule model. Template: Lifecycle model with financial conventions; milestone/dependency and assumptions register. Deliverable: Reviewed lifecycle-value comparison and master schedule with cost/timing sensitivities and unresolved conditions. |
Analysis: spreadsheet; scheduling software; digital twins. |
Organize: Extract lifecycle cost inputs, financial conventions, milestones, and dependencies. Draft assumptions and source registers. |
|
9. Strategic Plan |
Combine business objectives and reviewed evidence into a facilities strategy with outcomes, owners, resources, timing, and review points. |
Tool: Strategic-planning workshop and controlled synthesis/roadmap workbook. Template: Strategic plan outline with objective–initiative–measure links, assumptions, owners, milestones, and review triggers. Deliverable: Reviewed strategic facilities plan, sponsor endorsement, and separate authorized-direction record. |
Analysis: spreadsheet; scheduling software. |
Assemble: Combine objectives, stakeholder findings, baselines, forecasts, gaps, scenarios, and appraisal results. |
|
10. Portfolio Priorities |
Prioritize and sequence initiatives against business needs, value, resources, dependencies, and risk. Priority is not budget approval. |
Tool: Portfolio prioritization workbook and dependency/resource planning model. Template: Priority register and roadmap with criteria, evidence, dependencies, costs, benefits, owners, timing, and status. Deliverable: Reviewed portfolio priorities and sequencing recommendation; separate authorized priorities and allocations record. |
Analysis: spreadsheet; scheduling software. |
Organize: Compile initiatives, criteria, evidence, costs, benefits, dependencies, resource limits, owners, and timing. |
|
11. Initial Business Case |
Explain whether moving to the next stage is justified, what decision is requested, and what conditions or further investigations remain. |
Tool: Business-case document and linked appraisal/financial workbooks. Template: Executive summary and case outline with evidence links, assumptions, options, benefits/measures, conditions, and decision request. Deliverable: Initial business case with review/endorsement status and separate authorization record; versioned updates at gates and material changes. |
Analysis: spreadsheet; scheduling software. |
Assemble: Compile the business need, objectives, baseline, options, appraisal, risks, affordability, and delivery roadmap. |
|
12. Decision Briefings |
Explain the evidence, options, trade-offs, concerns, and specific decision requested from the authorized decision-maker. |
Tool: Brief the designated decision authority. Template: Decision paper and presentation outline. Deliverable: Reviewed decision briefing. |
Collaboration: calendar; meeting scheduler; email; video conference system; display monitor. |
Prepare: Draft decision papers, agendas, presentations, and evidence summaries for the designated authority. |
|
13. Decision, Action, and Issues Tracking |
Record actual decisions, assigned actions, deadlines, unresolved issues, and evidence of completion. |
Tool: Track decisions and follow-up. Template: Decision, action, and issues-register fields. Deliverable: Controlled logs and closure records. |
Analysis: spreadsheet. |
Capture: Extract decisions, proposed actions, and unresolved issues from notes and authorization records, keeping their status distinct. |
|
14. AI-Assisted Work Governance |
Define permitted AI tasks and data, responsible reviewers, validation checks, and routes for handling problems. |
Tool: Track approved AI use and review. Template: AI-use register fields. Deliverable: Reviewed AI-task and incident records. |
Analysis: spreadsheet. |
Prepare: Draft AI-use register fields and task-review checklists from the chapter’s Govern, Guide, Guard arrangements. |
16. Selection-Criteria Development and Objectives Brief: Establish one controlled Objectives and Selection Criteria Brief before market search or candidate scoring. The portfolio asset manager coordinates advisors, planners, workplace consultants, and stakeholders to translate authorized strategy, validated demand, timing, and resources into mandatory eligibility thresholds and measurable preferences. Include talent availability and cost, workforce and customer or supply-chain access, continuity, flexibility, sustainability, and facility requirements where relevant. HR, operations, IT, security, and qualified specialists validate requirements; estimators, schedulers, financial analysts, Finance, and data analysts check resource limits, affordability, and measurement scales. Define evidence requirements, scoring scales, and weights before evaluating properties. Obtain sponsor endorsement and approval by the named criteria authority within delegation; revise through controlled review when requirements change.
17. Weighted Scoring: Compare eligible properties transparently after mandatory screening and approval of criteria, performance scales, and weights. The portfolio asset manager coordinates advisors and specialists; the data analyst checks calculations, uncertainty, double counting, and ranking sensitivity. Relate weights to defined performance ranges and assess candidates consistently against dated evidence, retaining rejection reasons and decision rationale. Distinguish a simple scorecard from a developed multicriteria value model. Financial analysts and Finance validate financial comparisons. Repeat after material evidence or authorized criteria changes. A high preference score cannot override a mandatory requirement or authorize a property commitment.
18. Market Survey, Site Visits, and Comparative Assessment: Build and maintain a longlist and shortlist against approved search criteria. Real estate advisors lead market enquiries and visits under the portfolio asset manager; users, planners, operations, IT, security, and qualified specialists assess functional and technical fit. Use common questions and dated sources to confirm availability, quoted terms, measured area basis, location access, and operating constraints. Record observations, source representations, exclusions, and investigations still needed; independently verify material claims before commitment. Refresh the comparison when availability, terms, criteria, or evidence change and link findings to test fits and due diligence.
19. Site and Space Planning Test Fits: Test preliminary accommodation of required quantities, functional relationships, and operational interfaces against checked site and building drawings with explicit area definitions. A qualified planner or architect prepares layouts during property feasibility or Project Definition, before commitment or POR acceptance. Users, operations, IT, security, engineers, and relevant specialists review circulation, support space, access, service, and technical constraints. Record drawing versions, assumptions, exclusions, exceptions, and further checks; repeat when requirements or constraints change. A test fit indicates potential accommodation, not completed design, comprehensive code compliance, or a substitute for due diligence.
20. Due Diligence Coordination and Specialist Reports: Coordinate scoped investigations to reduce material property and feasibility uncertainty before commitment. The portfolio asset manager agrees specialist appointments, competence, access, methods, and limitations with advisors, Legal, architects, engineers, and other qualified reviewers. Investigate condition, capacity, building fabric and services, safety/fire, accessibility, environmental and hazardous-material issues, sustainability, zoning, geotechnical, infrastructure, and legal/title matters as applicable. Each specialist owns their methods, findings, limitations, and reports. Record deficiencies, consequences, remediation, cost responsibility, further investigations, and urgent actions; estimators and schedulers assess implications, and service owners validate operational effects. Track action owners and closure evidence, escalating unresolved risks to the sponsor and authority. Supplement investigations when circumstances change; limited scope is not comprehensive assurance.
21. Search and Options Appraisal Report: Integrate property findings into a reviewable shortlist or selection recommendation. Under the portfolio asset manager, advisors assemble market and commercial evidence, planners prepare test fits, specialists provide due diligence, and estimators and schedulers assess cost and timing. Compare credible stay/renew, reconfigure, relocate, lease, purchase, and other feasible alternatives, including eligibility, scores, feasibility, workforce/location impacts, and uncertainty. Financial analysts prepare total occupancy and lifecycle comparisons on common areas, horizon, and financial assumptions with Finance review; data analysts check scores and sensitivities. Disclose exclusions and unresolved conditions, link to the business case, and submit for sponsor endorsement and designated-authority decision. Refresh material changes; quoted rent alone is not a comparable cost basis.
22. Transaction Recommendation and Authorization Record: Present a specific proposed property commitment before binding execution and preserve the authority’s decision separately. The portfolio asset manager integrates appraisal, due diligence, the updated business case, funding, timing, and negotiated heads of terms or term sheet. Advisors confirm commercial terms; Legal reviews binding effects, obligations, authority, and conditions. For leases, examine term, renewal/break rights, rent/review, incentives, outgoings, repair, permitted use, fit-out, assignment/subletting, and insurance as applicable. Financial analysts reconcile obligations, Finance provides required funding concurrence, and Procurement checks process conditions. The sponsor endorses; the designated commitment authority authorizes, conditions, defers, or declines. Record rationale, limits, accepted risks, actions, and execution authority. Reassess material changes; only authorized signatories execute binding documents.
23. Executed Contract or Lease Record, Where Applicable: After authorized execution, preserve the signed agreement, attachments, amendments, notices, and authorization links in a controlled repository. Legal confirms the operative document set and interpretation; advisors prepare the abstraction and commercial schedules. The portfolio asset manager coordinates a legally reviewed obligations and critical-date schedule with project and lease-administration owners, covering rent changes, renewal/break notices, payments, guarantees, repair, fit-out, and other relevant duties. Verify source clauses and notice dates before reliance and assign action owners. The information systems manager protects records and valid updates. Summaries support coordination but neither amend nor replace executed documents or legal advice.
24. Transaction Readiness and Real Estate Handoff: Review property readiness before binding or irreversible commitment, then transfer the authorized direction at Real Estate phase exit. The portfolio asset manager integrates appraisal, due diligence, requirements, the living business case, funding, timing, and terms. Advisors and Legal validate commercial and binding conditions; financial analysts, Finance, and Procurement confirm assigned financial and process controls. The sponsor endorses the recommendation, and the designated authority decides within its powers. Keep commitment approval, execution, and phase-transition approval separate. Transfer controlled objectives, demand assumptions, alternatives and rationale, specialist findings, cost/timing ranges, terms, decisions, executed documents where applicable, and open risks/actions. The receiving project manager and domain or lease-administration owners acknowledge receipt, responsibilities, conditions, deadlines, and reassessment triggers. Legal confirms binding interpretations and the strategic planner confirms case continuity. Revisit material mismatches found during Project Definition.
|
Technique |
Descriptions |
Tool, Template, Deliverable |
Conventional Methods |
AI Applications |
|
16. Selection-Criteria Development and Objectives Brief |
Define mandatory property requirements and measurable preferences before the search, based on business needs, demand, timing, and resources. |
Tool: Translate approved requirements into eligibility tests and a location/property comparison matrix. Template: Search brief; criteria register with source, threshold, evidence, scale, weight, owner, and approval fields. Deliverable: Endorsed and approved Objectives and Selection Criteria Brief linked to validated requirements. |
Analysis: spreadsheet; maps; web site. |
Organize: Extract property requirements, demand, timing, resource limits, and aggregate workforce and location inputs. Separate mandatory thresholds from preferences. |
|
17. Weighted Scoring |
Compare eligible properties using approved criteria, scoring scales, and weights; test uncertainty and explain the results. |
Tool: Calculate criterion scores and test changes in weights, assumptions, and evidence. Template: Property scorecard with eligibility, definitions, evidence links, weights, scores, uncertainty, and sensitivity fields. Deliverable: Reviewed comparison and sensitivity results supporting—not determining—the shortlist or selection decision. |
Analysis: spreadsheet. |
Check: Compare scorecards with approved eligibility tests, criteria, scales, weights, and dated evidence. Flag missing inputs and duplicate criteria. |
|
18. Market Survey, Site Visits, and Comparative Assessment |
Find and visit candidate properties, compare them with search criteria, and separate verified findings from claims needing investigation. |
Tool: Maintain the candidate register; research markets, map locations, and conduct consistent site visits. Template: Property register; market enquiry or proposal request; visit checklist; source and commercial-terms fields. Deliverable: Dated market survey and comparative findings linked to criteria, test fits, and due diligence. |
Analysis: web site; maps; spreadsheet. |
Organize: Extract listing and proposal data into candidate registers, retaining dates, sources, quoted terms, area definitions, and availability status. |
|
19. Site and Space Planning Test Fits |
Test whether required space and activities could fit the site or building, and record constraints, assumptions, and further checks. |
Tool: Professionally prepare and review preliminary site/space layouts and accommodation comparisons. Template: Area schedule; drawing/version register; fit-summary and constraint/exception checklist. Deliverable: Qualified preliminary site/space test fits and findings linked to requirements and due diligence. |
Analysis: maps; spreadsheet; drawing / modeling software. |
Organize: Compile required quantities, relationships, drawing versions, area definitions, and site or building constraints. |
|
20. Due Diligence Coordination and Specialist Reports |
Coordinate specialist property investigations and record findings, limitations, consequences, remedies, and unresolved risks. |
Tool: Coordinate the data, facility and specialist investigations; track findings, risk significance, action owners, and closure evidence. Template: Scope-of-services checklist; document request list; specialist-report structure; issues/findings and closure registers. Deliverable: Specialist-owned reports with evidence, methods, limitations, cost/timing implications, and a coordinated unresolved-risk/action register. |
Analysis: spreadsheet; maps; drawing / modeling software; digital twins. |
Prepare: Draft document requests, investigation-scope checklists, coordination schedules, and report indexes. |
|
21. Search and Options Appraisal Report |
Combine property, cost, timing, and specialist findings into a comparison of feasible alternatives and a selection recommendation. |
Tool: Integrate the candidate register, checked scorecards, financial models, and schedule scenarios. Template: Options-appraisal report; occupancy-cost model; assumptions and sensitivity register; business-case crosswalk. Deliverable: Reviewed Search and Options Appraisal Report with alternatives, exclusions, recommendation, and business-case links. |
Analysis: spreadsheet; maps; scheduling software; drawing / modeling software. |
Assemble: Combine candidate records, scorecards, test fits, specialist findings, occupancy-cost models, and schedule scenarios. |
|
22. Recommend Transaction and Authorization Record |
Recommend a specific property commitment and record its terms, obligations, conditions, and separate authorization. |
Tool: Reconcile commercial terms with appraisal, legal review, financial concurrence, and delegated authority. Template: Transaction memorandum; heads-of-terms checklist; conditions register; separate authorization fields. Deliverable: Sponsor-endorsed recommendation and the actual authority’s separate decision, limits, conditions, accepted risks, and execution authority. |
Analysis: spreadsheet. |
Analyze: Compare term-sheet versions and extract changed commercial terms, obligations, conditions, and financial implications. Link them to appraisal and due-diligence findings. |
|
23. Executed Contract or Lease Record, Where Applicable |
Preserve signed agreements and related records and prepare a legally reviewed summary of obligations and critical dates. |
Tool: Maintain the protected executed-document repository and assign obligation and critical-date owners. Template: Executed-document register; lease/contract abstraction; obligations and critical-date schedule with source-clause references. Deliverable: Controlled signed-document set and reviewed abstraction/obligations schedule transferred to project and lease-administration owners. |
Analysis: spreadsheet. |
Organize: Index signed agreements, attachments, amendments, and notices. Flag missing documents and conflicting versions. |
|
24. Transaction Readiness and Real Estate Handoff |
Check readiness for a property commitment and transfer approved direction, evidence, conditions, and open responsibilities to the receiving team. |
Tool: Check readiness conditions and coordinate indexed transfer, briefings, receipt, and responsibility acceptance. Template: Readiness checklist; legal-reviewed terms/obligations schedule; package index; receiving-owner and open-actions register. Deliverable: Separately identifiable authorization/phase-transition records and acknowledged Real Estate Handoff Package, with qualifications and unresolved responsibilities. |
Analysis: spreadsheet; scheduling software. |
Assemble: Compile the readiness evidence, requirements, property findings, terms, business case, cost and timing inputs, and separate approval records. |
25. Decision-Role and Responsibility Mapping: Separate decision accountability from responsibility for preparing, reviewing, accepting, and executing work. At governance setup and significant decisions, the project manager and sponsor map RAPID roles: Recommend integrates evidence and proposes a course; Agree provides required concurrence on defined mandatory constraints; Perform executes the authorized decision; Input supplies evidence and expertise; Decide makes the decision within actual authority. Identify one recommender and one Decide role per decision, with documented procedures where authority rests with a board or committee. Use Agree sparingly, record delegation limits and escalation, and maintain separate deliverable responsibilities. Update organizational changes; role mapping cannot create or override legal powers.
26. Project Charter and Governance Arrangements: Formally authorize the project through the appropriate initiator, sponsor, or designated authority within actual delegation. Prepare the charter when the project is constituted, no later than Project Definition entry, and revise material mandate or organizational changes. The project manager coordinates sponsor and contributor review of the business need, measurable objectives, high-level requirements, scope/exclusions, stakeholders, assumptions, constraints, initial risks, budget/schedule parameters, and resource authority. Confirm appointments, phase leads, specialist scopes, deliverable owners, decision roles, reporting, gates, and escalation, with Legal and control-function review. Record sign-off and business-case links. Charter authorization is separate from later capital, procurement, and design decisions and does not create powers beyond delegation.
27. Architectural, Site or Workplace Programming: Research and define the design problem through architectural, site, or workplace programming appropriate to the project. Before POR acceptance, the programming lead coordinates goals, facts, functional concepts, needs, and problem statements across function, form, economy, and time. Users and workplace consultants validate activities and work patterns; HR, operations, IT, and security define service needs; qualified architects, engineers, and facility-type specialists validate technical assumptions. Reconcile demand, occupancy, equipment, space quantities and area definitions, site constraints, accessibility, safety, sustainability, maintainability, budget, and timing with the project manager. Retain validated findings and uncertainties, using the Functional Relationship Analysis and Standards and Performance-Criteria Review tasks. Revise changed needs or constraints. Programming concepts establish relationships and performance, not a predetermined design.
28. Functional Relationship Analysis: Define proximity, separation, access, and support relationships after workflows are understood and before POR acceptance. The programming lead and stakeholders map movement, shared services, interfaces, and relationship strength with explicit scales and operational rationale. Workplace and facility-type specialists validate assumptions; operations, IT, security, architects, and engineers review relevant access, separation, servicing, and technical interfaces. Record conflicts, dependencies, evidence, and requirement links and update changed activities or operating arrangements.
29. Standards and Performance-Criteria Review: Identify applicable obligations and measurable owner-selected performance targets during property feasibility and programming. The project manager appoints a coordinating architect or engineer; qualified specialists interpret requirements within their disciplines, with operations, HR, IT, security, Legal, and facility-type input. Record source editions, applicability, assumptions, conflicts, and interpretation owners, distinguishing mandatory obligations from optional targets. Assign later verification methods, stages, and owners and link requirements to the POR. Reassess changes in site, jurisdiction, intended use, or standards. Predesign review is not a permit, authority approval, or final design-compliance determination.
30. Stakeholder Mapping: Identify affected groups, functions, interests, representation, information needs, expertise, resources, and authority at initiation and phase gates. The strategic planner coordinates the initial map with the sponsor; portfolio and project leads to update it in their phases, supported by workplace consultants and Communications. Include distributed users, HR, IT, security, operations, specialists, resource owners, and decision authorities. Maintain an organization chart with hierarchical identifiers and a participant/contact register but distinguish reporting relationships from project decision rights. Confirm consultation, engagement, and escalation arrangements; update changed scope, sponsorship, services, or populations. Participation does not confer approval authority.
31. Interviews: Executive, End User, Support Services, Project Team: Use structured interviews to clarify and corroborate goals, strategy, concepts, workflows, constraints, and facility needs or performance criteria. Before requirements and options reviews, the strategic planner coordinates decision questions and workplace consultants or planners conduct executive, end-user, support-service, and project-team interviews. Schedule a calendar and agenda, using a consistent core with role-specific follow-ups. Distinguish facts from preferences, corroborate material claims against records and forecasts, and document sources, permissions, confidentiality limits, actions, and unresolved issues. Return notes for review and correction through a documented follow-up; confirmation of notes does not approve requirements. Repeat conflicting or changed assumptions.
32. User Surveys: departmental requirements questionnaire, and workplace satisfaction and assessment survey: Collect departmental requirements and workplace satisfaction or assessment evidence through distinct instruments where appropriate. A named workplace consultant or planner designs the questionnaire and survey with HR and the data analyst; Communications supports distribution. Define recipients and population, pilot questions, choose accessible distribution methods, record dates, versions, response coverage, and potential nonresponse bias. Analyze and report departmental and workplace findings separately, aggregating under agreed privacy controls. Corroborate material patterns through interviews, observations, and other evidence; reported preferences are not automatically validated requirements. Use during baseline and requirements review and repeat material changes or coverage gaps.
33. Observation and Activity Mapping: Observe workflows and space use to inform capacity and functional requirements. Workplace consultants and planners agree definitions, sampling, notation, and privacy safeguards with HR, security, and operations; the data analyst documents time periods, locations, denominators, and coverage limits. Record activities through consistent checklists and maps, with permitted photographs or image analysis where appropriate. Distinguish observed occupancy, defined utilization, and available capacity, reconciling observations with schedules and stakeholder explanations. Report activity profiles and workplace patterns rather than individual performance. Repeat unrepresentative or changed operating conditions; a short sample is not a complete demand forecast.
34. Facilitated Requirements Work Sessions: individual managers, departments, focus groups: Reconcile requirements and test assumptions through individual-manager, departmental, and focus-group work sessions. Before requirements or options reviews, the phase lead appoints a workplace consultant or planner to facilitate and circulates analyzed evidence and decision boundaries. Stakeholders, HR, IT, security, operations, and specialists examine survey findings, ideas, criteria, priorities, and trade-offs using suitable meeting aids. Record evidence, agreement, dissent, issues, actions, and reviewed notes linked to requirements. Distinguish preferences from justified needs and escalate unresolved conflicts to the sponsor or authority. Repeat after material changes; discussion or apparent agreement is not approval.
35. Collect and Analyze Facts: The programming lead uses the information index to identify facts about function, form, economy, and time that the project needs. Users and service owners provide operational information; qualified specialists provide site and technical findings. Estimators, financial analysts, and schedulers provide cost and timing inputs. The programming lead organizes and checks the information, records sources and uncertainties, and prepares the Facts section of the POR as the basis for needs analysis.
36. Needs Analysis: The programming lead summarizes performance requirements and calculates space needs from checked capacity forecasts and space-type standards. Estimators prepare cost inputs, specialists assess site or building capacity, and schedulers prepare the delivery schedule. The programming lead works with the project manager to reconcile the proposed scope with budget, property, and timing constraints. The result is the Needs section of the POR; changes requiring approval follow project change control.
37. Frame Problem and Success Criteria: Define the problem, boundaries, uncertainty, and success criteria before selecting a solution. At initiation or phase entry, the strategic planner translates the mandate and baseline evidence into statements of current conditions and required direction with the sponsor. Stakeholders and specialists validate causes, needs, constraints, dependencies, and measurable outcomes. Record sources, assumptions, measures, decision authority, timing, and appraisal links. The sponsor endorses prioritized criteria within delegation; executives resolve enterprise commitments or conflicts beyond it. Revisit changed evidence or boundaries.
38. Requirements Prioritization: Prioritize justified requirements during consolidation and baseline reviews, distinguishing mandatory obligations and essential needs from enhancements. The programming lead coordinates stakeholders, service owners, and technical specialists; estimators and schedulers assess resource and timing effects. Record sources, priority definitions, rationale, acceptance measures, dependencies, conflicts, owners, and approval links. Refer trade-offs to the project manager and sponsor and reassess changed resources, evidence, or obligations. A preference ranking cannot waive mandatory requirements; exceptions require qualified review and applicable authorization.
39. Requirements Validation and Traceability: Validate requirements and retain traceable links to evidence, success criteria, acceptance measures, and later verification. The programming lead maintains the record; stakeholders and service owners confirm intended needs, and qualified specialists validate domain requirements. The project manager checks interfaces and unresolved conflicts. Record identifiers, sources, owners, dates, units, confidence, dependencies, status, and approval links, assigning planned verification methods, stages, and owners. Revalidate changed sources, requirements, or scope through POR and readiness reviews. Predesign validation establishes a credible requirement, not proof that the later design or completed facility complies.
40. Issue Program of Requirements (POR): Issue one coordinated POR defining the accepted design problem and conditions the project must meet. The programming lead consolidates validated demand, space schedules and area basis, functional relationships, equipment, priorities, and spatial, technical, operational, and performance requirements. Users, service owners, workplace consultants, and qualified specialists validate their contributions; the project manager reconciles site, resources, and interfaces with estimators and schedulers. Include sources, success and acceptance measures, later verification duties, assumptions, qualifications, conflicts, and approval status. Submit for sponsor endorsement and designated-owner approval, then issue the controlled version with receiving-team responsibilities. Revise through authorized review and change control. The POR is not completed design or proof of compliance.
41. Scope, Budget, Site, and Schedule Reconciliation and Baseline: Reconcile requirements, property constraints, scope, resources, and timing into a controlled baseline supporting readiness and design authorization. The programming lead provides validated quantities; portfolio advisors and technical specialists confirm site constraints and feasibility. Estimators own their methods, price bases, ranges, contingencies, exclusions, and qualifications; schedulers own logic, dependencies, and timing assumptions. Service owners supply activation and operational inputs. The project manager integrates scope, budget, schedule, funding, procurement, approvals, and risks, exposing trade-offs for sponsor endorsement and designated-authority approval. Finance validates funding and conventions; financial analysts check cash flows and affordability; data analysts check quantities and units; information systems retains controlled versions. Reassess material changes through authorized change control. Estimates are not budget authorization and schedules are not guarantees; reconciliation is the method and the accepted baseline is its output.
42. Adaptation and Change Control: Adapt planning to changed evidence without losing approved baselines or accountability. The phase lead coordinates assessments; the project manager controls the project baseline once appointed. Programmers and specialists evaluate requirement effects, estimators and schedulers assess cost and timing, financial and data analysts update affected models, and Legal reviews commitments. The strategic planner revalidates the case; HR and Communications assess engagement and adoption effects. Record the reason, baseline version, impacts, owner, trigger, authority, decision, and linked revisions. The sponsor resolves trade-offs within delegation and escalates further commitments. Retain original records and the authorized change trail; people-side change management does not replace formal baseline approval.
43. Updated Business Case: Revalidate the same living business case at gates and material changes. During Project Definition, the project manager integrates the POR, baselines, delivery strategy, risks, and property findings, with strategic-planner review of continuing alignment. Estimators and schedulers validate cost and timing; financial analysts update cash flows, affordability, and sensitivities; data analysts check evidence and comparisons; Finance, Legal, and Procurement provide assigned controls. Record changed assumptions, options, feasibility, roadmap, monitoring owners, version comparisons, and custody transfers. The sponsor confirms intended outcomes and endorses submission; the designated authority records commitments separately. Do not create an unrelated replacement case.
44. Project Readiness Review: Assess whether the integrated predesign package supports entry to design at Project Definition completion. The project manager coordinates review of the plan, charter, validated POR, delivery strategy, updated business case, reconciled baselines, property conditions, risks, evidence, and success criteria. Strategic, portfolio, programming, technical, cost, schedule, financial, data, and information-management reviewers validate assigned contributions; Finance and other control or service functions confirm mandatory conditions. Review change-management engagement, communication, feedback resolution, and transition readiness without claiming complete adoption. Identify gaps, qualifications, actions, owners, deadlines, closure authority, and restrictions on starting work. The sponsor endorses the gate recommendation; the designated owner authority decides separately. Repeat required revisions or material changes.
45. Project Readiness Review Report: Document the Project Readiness Review findings and recommendation, not authorization itself. The project manager records the coordinated domain reviews described above, including controlled versions, evidence, reviewers, consistency checks, qualifications, unresolved conditions, and change management readiness. Specialists retain responsibility for their findings and the sponsor endorses the integrated recommendation. State whether the package supports design authorization, what further work is required, and who must close each condition by when. Link the report to the separate owner decision and handoff package; revise after required analysis or material changes.
46. Delivery and Procurement-Options Assessment: Compare feasible delivery and service-procurement approaches before strategy approval or commitments. The project manager coordinates Procurement, Legal, designers, estimators, schedulers, and relevant specialists to assess complexity, requirements maturity, owner capacity, design control, market capability, timing, cost, interfaces, and risk allocation. Distinguish delivery method, provider selection, and contract/payment form. Consider design–bid–build, design–build, and construction manager at risk where appropriate; construction-management adviser is a management service, not CM at risk. Record criteria, owner-capacity and interface assessments, assumptions, exclusions, and trade-offs. Procurement checks sourcing rules and Legal checks contractual duties. The sponsor endorses; the designated authority approves strategy and awards separately. Revisit material changes.
47. Delivery and Procurement Strategy: Translate the accepted options assessment into a coordinated delivery and procurement strategy. The project manager works with Procurement, Legal, technical specialists, estimators, and schedulers to define package and service scopes, interfaces, existing appointments, remaining sourcing, selection criteria, qualification/proposal requirements, pricing and contract assumptions, milestones, risk responsibilities, and implementation owners. Procurement confirms sourcing requirements and Legal reviews duties and risk allocation. Record sponsor endorsement, strategy approval, award authority, and execution requirements separately, updating material scope, risk, timing, or market changes. No delivery method is universally best; contractual terms determine responsibilities and risk allocation.
48. Post-Decision Monitoring and Learning Arrangements: Plan how changing conditions and eventual outcomes will be monitored against the approved case. Before authorization and handoff, the sponsor assigns benefits and measure owners in portfolio, operations, HR, IT, or other relevant functions. The strategic planner links measures to objectives; the data analyst checks definitions, baselines, and sources; financial analysts and Finance validate financial measures. The project manager integrates checkpoints, thresholds, reassessment triggers, corrective-action authority, and receiving responsibilities; Communications supports reporting and information systems maintains longitudinal records. Revise changed measures or accountability. Predesign establishes future evaluation duties, not evidence of realized benefits.
49. Final Decision Record: Record the actual owner decision on entry to design immediately after readiness review. The designated owner authority or expressly delegated approver decides; the project manager confirms and preserves wording against the submitted recommendation and controlled evidence. State authorization, conditions, modification, deferral, return for analysis, or refusal, with rationale, departures, accepted risks, funding limits, commitments, owners, deadlines, closure authority, checkpoints, and dissent. The sponsor ensures obligations and escalations are understood, Communications distributes approved direction, and Legal reviews material authority or commitment interpretations. Retain subsequent authorized changes without erasing the original decision. Recordkeeping confers no decision authority.
50. Authorized Handoff Package to Design Team: Transfer accepted requirements, evidence, and the authorization basis to the design team after approval and subject to its conditions. The project manager assembles the charter, POR, living business case, decision, delivery strategy, baselines, standards, property terms, risks, and open actions. Programming, strategic, and portfolio leads explain requirements and constraints; receiving architects, engineers, and specialists acknowledge versions, qualifications, and later verification duties. Service owners confirm interfaces and monitoring responsibilities. Transfer change-management plans, feedback resolution, and transition readiness with named receiving owners and briefings. Record receipt, exclusions, unresolved conditions, and change/escalation routes. Receipt neither proves compliance nor permits conditions to be disregarded.
|
Technique |
Descriptions |
Tool, Template, Deliverable |
Conventional Methods |
AI Applications |
|
25. Decision-Role and Responsibility Mapping |
Assign decision roles and responsibilities, delegation limits, and escalation routes; distinguish these from project authorization in the charter. |
Tool: Design and Construction Playbook, RAPID matrix, project team calendar, contact directory, and Shared documents folder. Project briefing presentation. Template: RAPID matrix; Shared documents protocols. Deliverable: Decision-role-responsibility assignments. Project briefing presentation. |
Analysis: spreadsheet; scheduling software. |
Analyze: Summarize the Real Estate handoff and identify decisions, roles, delegation limits, and escalation routes. Flag missing or conflicting assignments. |
|
26. Project Charter and Governance Arrangements |
Prepare and authorize the project charter, confirming the mandate, appointments, responsibilities, and governance arrangements. |
Tool: Project charter and governance checklist. Template: Charter format. Deliverable: Authorized project charter and confirmed governance arrangements. |
Collaboration: email. |
Analyze: Extract the mandate, objectives, scope, constraints, stakeholders, risks, resources, and decision roles from background records. Identify gaps and inconsistencies. |
|
27. Architectural, Site or Workplace Programming |
Review the Real Estate handoff to begin defining the design problem. Organize programming work, information requests, team responsibilities, milestones, and communication and document procedures. |
Tool: Programming Playbook. Workplan. Information requests checklist. Contact directory, shared document storage. Project calendar. Template: Information requests: communication and document protocols. Deliverable: Project team directory, Information requests and issue tracking system, project schedule. |
Analysis: spreadsheet; scheduling software; drawing / modeling software; digital twins. |
Organize: Summarize the handoff, draft the programming workplan and kick-off agenda, and compile contacts, milestones, and document procedures. |
|
28. Functional Relationship Analysis |
Define which activities need proximity, separation, access, or shared support. |
Tool: Relationship matrix and workflow maps. Template: Relationship scales, rationale, interfaces, conflicts, and requirement links. Deliverable: Reviewed functional relationships linked to the POR. |
Analysis: spreadsheet; maps; drawing / modeling software. |
Analyze: Extract workflows, movement, shared services, access needs, and separation requirements. Identify conflicting relationships and missing interfaces. |
|
29. Standards and Performance-Criteria Review |
Identify applicable obligations and measurable performance targets, with later verification duties. |
Tool: Standards register and performance-criteria checklist. Template: Source edition, applicability, interpretation owner, requirement, and verification fields. Deliverable: Reviewed standards and performance criteria linked to the POR. |
Analysis: web site; spreadsheet; drawing / modeling software. |
Organize: Extract cited standards, editions, obligations, and performance targets from source documents. Draft the standards register and compare versions. |
|
30. Stakeholder Mapping |
Identify affected groups, their interests and roles, and their reporting relationships; distinguish these from project decision rights. |
Tool: Organization Chart. Map interests and authority. Template: Participants register matrix and contact information. Deliverable: Reviewed organization chart, stakeholder map and engagement matrix. |
Analysis: spreadsheet. |
Organize: Compile participants, groups, functions, reporting relationships, contacts, and project roles from source records. Identify missing representation and duplicate entries. |
|
31. Interviews: Executive, End User, Support Services, Project Team |
Use interviews to clarify and check goals, work processes, constraints, and facility needs or performance criteria. |
Tool: Question sets for each interview type. Interview calendar and meeting invitation. Template: Question-response form and follow-up request to review and correct interview notes. Deliverable: Reviewed interview notes and goals for the POR; note confirmation is not requirements approval. |
Collaboration: calendar; meeting scheduler; email; video conference system. |
Prepare: Draft role-specific questions, interview agendas, invitations, and follow-up requests. |
|
32. User Surveys: departmental requirements questionnaire, and workplace satisfaction and assessment survey |
Collect departmental requirements and workplace satisfaction evidence through distinct questionnaires or surveys. |
Tool: Departmental questionnaire. Workplace satisfaction survey Template: Use forms application to prepare digital questionnaire and survey. Email cover letter template for each Deliverable: Departmental requirements report, and analysis of survey responses. |
Analysis: spreadsheet; web site. |
Prepare: Draft separate departmental questionnaires and workplace surveys, cover messages, and response-tracking formats. Flag unclear or repeated questions. |
|
33. Observation and Activity Mapping |
Observe work and space use to inform capacity and functional requirements, recording the limits of the sample. |
Tool: Record sampled activities. Activity mapping, observational notes and photography. Template: Observation checklist, map layout and notation coding system. Deliverable: User profiles and workplace utilization report. |
Analysis: maps; spreadsheet; drawing / modeling software; digital twins. |
Prepare: Draft observation checklists, activity codes, sampling logs, and map labels. |
|
34. Facilitated Requirements Work Sessions: individual managers, departments, focus groups |
Review requirements, priorities, and trade-offs with managers, departments, and focus groups; record agreement, disagreement, and unresolved issues. |
Tool: Meeting agenda, visual documentation and presentation of information received and analyzed. Facilitate requirements review and discussion. Template: Workshop agenda and recording and analysis methods and forms. Deliverable: Work session meeting notes. Concepts section of the program of requirements. |
Analysis: spreadsheet. |
Prepare: Draft agendas, evidence summaries, slides, note-card text, and discussion questions for managers, departments, and focus groups. |
|
35. Collect and Analyze Facts |
Collect and check facts about function, form, economy, and time to support needs analysis and the Facts section of the POR. |
Tool: Function: Operational and workforce systems, surveys, interviews, observations, and utilization analytics establish demand, user needs, space requirements, and business risks. Form: Surveys, mapping tools, building models, inspections, sensors, and authoritative codes establish site conditions, asset configuration, performance, and regulatory requirements. Economic: Budgets, cost databases, financial records, energy models, and risk analyses establish funding, capital and life-cycle costs, and economic uncertainty. Time: Integrated schedules, historical records, simulations, forecasts, and version histories establish milestones, durations, phasing, change, and data currency. Template: Formats for questionnaires, inventories, cost analyses, schedules, risk registers, and source tracking. Deliverable: The Facts section of the program of requirements (POR). |
Analysis: spreadsheet; web site; maps; scheduling software; drawing / modeling software; digital twins. |
Organize: Extract and classify source information under function, form, economy, and time. Build inventories and source indexes and identify missing or outdated information. |
|
36. Needs Analysis |
Calculate space needs and reconcile performance requirements and scope with cost, property capacity, and timing constraints. |
Tool: Checked capacity forecast, space-type guidelines, space calculator, cost-estimating workbook, and delivery schedule. Template: space lists formats: site, building, interiors. Deliverable: Needs section of the program of requirements. |
Analysis: spreadsheet; maps; scheduling software; drawing / modeling software; digital twins. |
Prepare: Organize capacity forecasts, space standards, quantities, cost inputs, property limits, and schedule assumptions. Draft space-list and feasibility-workbook formats. |
|
37. Frame Problem and Success Criteria |
Define the problem, boundaries, uncertainties, and success criteria before developing solutions. |
Tool: Analysis of quantitative and qualitative background information. Template: Problem statement format (condition & direction) Deliverable: Endorsed problem statements and evaluation criteria section of the POR. |
Collaboration: whiteboard; digital canvas; flip charts; note cards; post its; wall displays. |
Analyze: Synthesize goals, facts, concepts, and needs into statements of current conditions and required direction. Flag solution assumptions that obscure the underlying problem. |
|
38. Requirements Prioritization |
Separate mandatory and essential requirements from enhancements and record trade-offs. |
Tool: Requirements register and priority matrix. Template: Priority definitions, rationale, dependencies, resource effects, owners, and approval links. Deliverable: Reviewed requirement priorities and trade-offs for authorized decisions. |
Analysis: spreadsheet. |
Organize: Classify requirements using the established priority definitions. Link priorities to sources, obligations, dependencies, and acceptance measures. |
|
39. Requirements Validation and Traceability |
Check requirements and link them to evidence, acceptance measures, and later verification. |
Tool: Requirements register and evidence crosswalk. Template: Requirement ID, source, owner, status, acceptance measure, and verification fields. Deliverable: Validated requirements with traceable evidence and verification duties. |
Analysis: spreadsheet. |
Analyze: Check requirement wording for ambiguity, duplication, contradictions, missing units, and unclear acceptance measures. Flag gaps in sources, ownership, and status. |
|
40. Issue Program of Requirements (POR) |
Issue the coordinated POR, including goals, facts, concepts, needs, and the design problem, for review and approval. |
Tool: Standard document format. Template: POR document template. Transmittal template. Deliverable: POR document for review and approval. |
Analysis: spreadsheet; drawing / modeling software. |
Assemble: Compile goals, facts, concepts, needs, space schedules, relationships, technical criteria, and approval records into the POR. |
|
41. Scope, Budget, Site, and Schedule Reconciliation and Baseline |
Reconcile requirements, property constraints, costs, and timing into a baseline for approval. |
Tool: Space schedules, cost and schedule models, and baseline register. Template: Scope, cost basis, constraints, assumptions, risks, funding, and approval fields. Deliverable: Reconciled scope, budget, and schedule baseline with review and approval status. |
Analysis: spreadsheet; scheduling software; drawing / modeling software. |
Analyze: Compare space schedules, property limits, costs, funding, schedule dependencies, procurement, and risks. Flag inconsistent scope, units, assumptions, or versions. |
|
42. Adaptation and Change Control |
Assess changes to evidence or requirements and retain the original baseline and approval trail. |
Tool: Change register and impact-assessment worksheets. Template: Reason, baseline version, impacts, owner, authority, decision, and linked revision fields. Deliverable: Reviewed change assessments and authorized revisions. |
Analysis: spreadsheet; scheduling software. |
Analyze: Compare versions and identify changed requirements, assumptions, commitments, and affected records. Draft cost, timing, risk, and stakeholder-impact questions. |
|
43. Updated Business Case |
Update the same business case with current requirements, baselines, property findings, and delivery plans. |
Tool: Living business-case document and linked financial models. Template: Changed assumptions, options, costs, risks, version comparison, and review fields. Deliverable: Updated business case for sponsor endorsement and the separate commitment decision. |
Analysis: spreadsheet; scheduling software. |
Analyze: Compare the current case with changed demand, scope, property, cost, schedule, benefits, and risk inputs. Flag missing evidence and inconsistent assumptions. |
|
44. Project Readiness Review |
Check whether the coordinated predesign package supports entry to design and identify conditions. |
Tool: Readiness checklist and controlled project package. Template: Evidence, reviewer, condition, action, owner, deadline, and closure-authority fields. Deliverable: Reviewed readiness findings and gate recommendation. |
Analysis: spreadsheet; scheduling software. |
Prepare: Draft the readiness checklist and assemble evidence against each review criterion. |
|
45. Project Readiness Review Report |
Record readiness findings, qualifications, and the recommendation separately from authorization. |
Tool: Reviewed readiness checklist and evidence index. Template: Package versions, reviewers, findings, restrictions, actions, owners, and decision-link fields. Deliverable: Readiness review report linked to the owner decision and handoff package. |
Analysis: spreadsheet. |
Assemble: Compile the review purpose, criteria, evidence, participants, findings, dissent, qualifications, and unresolved conditions. |
|
46. Delivery and Procurement-Options Assessment |
Compare feasible delivery and procurement approaches against project needs, owner capacity, timing, cost, and risk. Keep delivery method, provider selection, and contract or payment form distinct in the comparison. |
Tool: Comparison matrix covering delivery-option features and project delivery considerations. Template: Options matrix; owner-capability assessment; risk allocation matrix; service-scope and selection-criteria outline. Deliverable: Delivery options assessment and recommendation report. |
Analysis: spreadsheet; web site; scheduling software. |
Organize: Compile delivery and procurement alternatives, package boundaries, interfaces, constraints, and evaluation criteria. |
|
47. Delivery and Procurement Strategy |
Document the selected delivery approach, service packages, procurement steps, responsibilities, milestones, and separate approvals. |
Tool: Service packages, selection processes, and procurement milestones. Template: Delivery/procurement strategy; package/service-scope matrix; selection/evaluation criteria; procurement schedule; approval and award register. Deliverable: Approved delivery and procurement strategy with implementation responsibilities, awards/contracts. |
Analysis: spreadsheet; scheduling software. |
Prepare: Draft the strategy package, sourcing sequence, procurement schedule, package descriptions, and interface responsibilities. |
|
48. Post-Decision Monitoring and Learning Arrangements |
Plan how future outcomes will be measured, who will monitor them, and when reassessment or corrective action is required. |
Tool: Monitor approved measures. Template: Monitoring-plan and indicator fields. Deliverable: Monitoring plan with named owners. |
Analysis: spreadsheet; scheduling software; digital twins. |
Prepare: Draft the monitoring plan with measure definitions, baseline values, sources, owners, checkpoints, thresholds, and reporting formats from project records. |
|
49. Final Decision Record |
Record the actual decision on entry to design, including conditions, reasons, limits, and responsibilities. |
Tool: Decision Tracking System. Template: Decision-record. Deliverable: Controlled decision record. |
Analysis: spreadsheet. |
Capture: Extract the actual decision, authority, date, rationale, commitment limits, conditions, and departures from the recommendation from the authorization record. |
|
50. Authorized Handoff Package to Design Team |
Transfer accepted requirements, project records, approval conditions, and open responsibilities to the design team. |
Tool: Email attachment or file storage device. Template: Transmittal document and acceptance-register format. Deliverable: Authorized design-team handoff package. |
Analysis: scheduling software; drawing / modeling software. |
Assemble: Compile the authorized POR, baselines, business case, decision record, delivery strategy, and supporting evidence into an indexed package. |
51. Change Management Plan: The change manager develops and maintains a plan to address the social and psychological effects of the project on affected groups. Working with HR, Communications, and the project manager, the change manager identifies concerns, sponsor and manager support, consultation, communication, preparation, resources, risks, and readiness checks. The project sponsor appoints the change manager, authorizes the plan, and provides funding within delegated authority. The plan supports programming and project delivery; programmers lead requirements work, and the project manager coordinates project records and formal change control.
52. Shared-Meaning Workshops: The change manager supports programming workshops with HR and Communications to help affected groups understand why change is proposed, what has been decided, and what they can influence. Participants discuss effects on work, roles, policies, services, and space, including other changes and their ability to cope. The change manager records differing interpretations and concerns in existing project records and brings them to the project team. Programmers assess any implications for requirements.
53. Testing Apparent Agreement: Before a course of action is chosen or announced, the change manager checks whether stakeholders understand it and raises their practical concerns with the project manager. The change manager adds questions to existing interviews, workshops, or short feedback checks and arranges separate sessions only to address gaps. HR confirms privacy limits. The change manager includes groups whose views are often missed, records support, disagreement, responses, and unresolved barriers in existing project records, and explains outcomes to participants. Silence is not agreement; participation does not guarantee consensus or grant a veto.
54. Communication Plan: Communications develops the communication plan with the change manager and project manager, using the project calendar. The plan identifies what each group needs to know, who will explain it, when, and through which accessible methods. Sponsors explain the business reasons; managers explain personal and local effects; the project manager explains delivery. Communications prepares speakers and messages, while the change manager supports discussion and checks understanding. Messages distinguish proposals from decisions and follow the required approval and privacy reviews.
|
Technique |
Descriptions |
Tool, Template, Deliverable |
Conventional Methods |
AI Applications |
|
51. Change Management Plan |
Plan how to support affected groups through the change, including communication, preparation, resources, risks, and readiness. |
Tool: Change-impact checklist and project records. Template: Plan outline covering affected groups, concerns, activities, owners, resources, risks, and readiness checks. Deliverable: Authorized change-management plan with assigned responsibilities and funding. |
Analysis: spreadsheet; scheduling software. |
Organize: Summarize affected groups, concerns, support needs, and project milestones from stakeholder feedback and project records. |
|
52. Shared-Meaning Workshops |
Help participants understand the proposed change and discuss its effects during programming workshops. |
Tool: Programming workshop agenda and discussion questions. Template: Notes recording interpretations, concerns, and links to existing project issues or requirements. Deliverable: Reviewed workshop notes and concerns for project-team follow-up. |
Collaboration: flip charts; note cards; post its; wall displays; whiteboard; digital canvas; video conference system; display monitor. |
Prepare: Draft workshop questions and briefing materials explaining proposed changes, recorded decisions, and matters participants can influence. |
|
53. Testing Apparent Agreement |
Check understanding and practical concerns before choosing or announcing a course of action. |
Tool: Questions added to existing interviews, workshops, or short feedback checks. Template: Question set and feedback notes showing groups included, privacy limits, responses, and unresolved concerns. Deliverable: Reviewed understanding and concerns, recorded in existing project records. |
Analysis: spreadsheet. |
Prepare: Draft understanding checks and practical-concern questions for existing interviews, workshops, and feedback forms. |
|
54. Communication Plan |
Plan what each group needs to know, who will explain it, when, and how; distinguish proposals from decisions. |
Tool: Project calendar, approved messages, and audience checklist. Template: Audience, message, speaker, method, timing, approval, and response-owner fields. Deliverable: Coordinated communication plan, approved messages, and speaker briefings. |
Analysis: scheduling software. |
Prepare: Draft the audience–message–speaker schedule using project milestones and recorded decisions. Match messages to business reasons, delivery information, and local effects. |
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.
Go to Explore the Practice |