7 Procedures
Questions that Guide Inquiry
Introduction Common Procedures 2.1 Problem Framing and Decision Criteria 2.1.1 Define the Problem or Opportunity 2.1.2 Establish the Existing-Situation Baseline 2.1.3 Define Decision Scope 2.1.4 Define and Prioritize Success Criteria 2.1.5 Connect Work to Decisions 2.2 Participation, Decision Rights, and Coordination 2.2.1 Identify and Engage Stakeholders 2.2.2 Assign Roles and Decision Rights 2.2.3 Facilitate Alignment and Resolve Disagreement 2.2.4 Coordinate Specialist Contributions 2.2.5 Orchestrate Shared Work and Distributed Contributions 2.3 Evidence, Analysis, and Information Governance 2.3.1 Define Information Needs 2.3.2 Analyze and Synthesize Findings 2.3.3 Examine Relevant Planning Considerations 2.3.4 Validate Evidence Quality 2.3.5 Document Assumptions and Limitations 2.3.6 Apply AI Governance: Govern, Guide, Guard 2.3.7 Maintain Integrated Decision Support 2.4 Risk Assessment and Response 2.4.1 Identify and Assess Risks and Uncertainties 2.4.2 Define Risk Responses 2.5 Alternatives, Feasibility, and Business Case 2.5.1 Develop Credible Alternatives 2.5.2 Compare Alternatives Against Decision Criteria 2.5.3 Test Scenarios and Sensitivity 2.5.4 Evaluate Lifecycle Value 2.5.5 Maintain the Master Schedule 2.5.6 Test Affordability and Implementation Feasibility 2.5.7 Maintain the Business Case as a Living Decision Instrument 2.6 Authorization, Change Control, and Learning 2.6.1 Establish Adaptation and Change Control 2.6.2 Assess Decision Readiness 2.6.3 Document Authorization Conditions 2.6.4 Preserve the Decision Record 2.6.5 Record Executive Departures from Recommendations 2.6.6 Assign Post-Decision Review and Learning | Strategic Planning Phase 2.7 Organizational Direction and Portfolio Priorities 2.7.1 Translate Organizational Strategy into Facility Needs 2.7.2 Conduct the Executive Vision Session 2.7.3 Assess Strategic Context and Competitive Forces 2.7.4 Develop Strategic Facilities Responses 2.7.5 Set Portfolio Priorities 2.7.6 Plan for Portfolio Change 2.8 Portfolio Diagnosis, Scenarios, and Sponsor Review 2.8.1 Diagnose Portfolio Needs and Frame the Problem 2.8.2 Establish the Portfolio Scenario Baseline 2.8.3 Compare Portfolio Scenarios and Recommend a Strategy 2.8.4 Review the Strategic Budget and Obtain Sponsor Direction 2.8.5 Prepare the Strategic Planning Business Case Real Estate Phase 2.9 Search, Alternatives, and Due Diligence 2.9.1 Define Real Estate Objectives and Search Criteria 2.9.2 Survey the Market 2.9.3 Conduct Technical, Environmental, and Legal Due Diligence 2.9.4 Compare Real Estate Alternatives and Lifecycle Value 2.10 Transaction Authorization and Phase Handoff 2.10.1 Assess Transaction Readiness 2.10.2 Review Real Estate Phase Readiness 2.10.3 Handoff to Project Definition Project Definition Phase 2.11 Governance, Planning Inputs, and Requirements 2.11.1 Establish Project Governance and Charter 2.11.2 Apply the Programming Method and Develop Requirements 2.11.3 Validate Project Information and Traceability 2.11.4 Identify Applicable Standards, Sustainability, and Resilience Requirements 2.11.5 Test Needs and State Design Problems 2.12 Scope, Delivery Strategy, and Design Authorization 2.12.1 Reconcile the Scope, Budget, and Schedule Baseline 2.12.2 Define Delivery and Procurement Strategy 2.12.3 Review Project Definition Readiness 2.12.4 Conduct the Project Readiness Review 2.12.5 Submit the Project for Authorization to Proceed |
Introduction Procedures provide protocols and questions that guide the strategic predesign process. Use these procedures as a heuristic to trigger questions, test evidence, and identify further inquiry in the context of the initiative or project at hand. Apply them throughout strategic planning, real estate, and project definition, adapting the depth of inquiry to the built environment, material uncertainty, and proposed commitment. Review relevant procedures at the beginning of strategic predesign and each phase, at major decision gates, and whenever material conditions change. For each procedure, record the supporting evidence, the responsible party, review status, unresolved questions, and required follow-up. Issues are unanswered questions. Make unresolved issues visible to the appropriate reviewer or decision authority and seek resolution. Common procedures apply to all three phases: framing; participation and coordination; evidence and information governance; risk; alternatives and business case; and authorization, change control, and learning. The next group of procedures apply to a specific phase: strategic planning, real estate, and project definition. The phase-specific groups supplement rather than replace the common procedures. Each procedure states the work to execute and the questions to review. Common Procedures 2.1 Problem Framing and Decision Criteria2.1.1 Define the problem or opportunity. Develop a problem statement using leadership vision, stakeholder goals and reasoning, and qualitative and quantitative evidence of conditions, demand, capacity, costs, benefits, risks, and performance requirements. What problem or opportunity does the evidence establish? Which findings provide criteria for evaluating potential solutions, and what remains uncertain? 2.1.2 Establish the existing situation baseline. Document current conditions, performance gaps, root causes, constraints, prior decisions, and relevant commitments. Does the baseline explain the current situation and distinguish underlying causes from symptoms? Which conditions or commitments constrain further inquiry? 2.1.3 Define decision scope. State the decision’s purpose, boundaries, timing, authority, dependencies, and possible outcomes. What decision is required, who may authorize it, and what is outside its scope? Which dependencies must be resolved before a commitment can be made? 2.1.4 Define and prioritize success criteria. Establish measurable strategic, operational, financial, functional, schedule, risk, and stakeholder outcomes. How will success be evaluated in this initiative or project? Are competing outcomes and their relative priorities explicit? 2.1.5 Connect work to decisions. Link each study, meeting, analysis, and deliverable to the information needed for a defined decision or gate. What decision-relevant question will this work answer? Does the proposed work reduce uncertainty or support evaluation rather than produce information without defined use? 2.2 Participation, Decision Rights, and Coordination2.2.1 Identify and engage stakeholders. Identify affected stakeholders, end users, implementers, resource owners, subject-matter experts, and decision authorities; engage them in the relevant inquiry and review. Whose needs, knowledge, resources, or authority affect the decision? What perspectives or implementation concerns are missing? 2.2.2 Assign roles and decision rights. Specify who provides input, recommends, validates, approves, and implements, and how disagreements are resolved. Do participants understand their responsibilities and the limits of their authority? Are recommendation, validation, and authorization clearly distinguished? 2.2.3 Facilitate alignment and resolve disagreement. Make assumptions, criteria, trade-offs, and stakeholder positions explicit; test genuine commitment; document unresolved disagreements and escalate them to the appropriate decision authority. What is agreed, what remains contested, and why? Does apparent agreement reflect a shared understanding of the proposed commitment? 2.2.4 Coordinate specialist contributions. Engage internal and external service providers at the appropriate time; define scopes, interfaces, deliverables, and responsibility for coordination. Which specialist contributions are needed for the current inquiry? Are gaps, overlaps, and dependencies between their assignments understood? 2.2.5 Orchestrate shared work and distributed contributions. Establish roles, decision rights, shared methods, standards, interfaces, tools, and feedback loops. Consider arbitrage, aggregation, rewiring, and reassembly when governing repetitive AI-assisted tasks, combining shared capabilities, connecting the information chain, and validating distributed contributions. How will these approaches produce coherent decision-support information? Where are coordination or validation gaps, and how do the AI controls in Group 2.3 apply? 2.3 Evidence, Analysis, and Information Governance2.3.1 Define information needs. Identify the qualitative and quantitative questions needed to reduce uncertainty and evaluate alternatives. What information would materially affect the decision? Which unanswered questions require further inquiry? 2.3.2 Analyze and synthesize findings. Analyze the problem as understandable parts and identify the choices the owner must make. Synthesize evidence, constraints, priorities, alternatives, and evaluation criteria into a coherent course of action. What does the analysis reveal about the available choices? Does the synthesis preserve material conflicts and uncertainty rather than conceal them? 2.3.3 Examine relevant planning considerations. Examine function, form, economy, and time alongside relevant political, regulatory, organizational, technological, operational, environmental, and cultural factors. Which considerations are material to this built environment and decision? How do their interactions affect the problem, alternatives, or evaluation criteria? 2.3.4 Validate evidence quality. Review sources for currency, relevance, authority, completeness, validation, and traceability. Is the evidence sufficient for the proposed commitment? Which sources or findings require corroboration, updating, or qualification? 2.3.5 Document assumptions and limitations. Distinguish facts from assumptions, estimates, interpretations, preferences, and AI-generated content. Document material gaps, conflicts, biases, and limitations. Which conclusions depend on unvalidated assumptions? How could these limitations change the evaluation or recommendation? 2.3.6 Apply AI governance: Govern, Guide, Guard. Under Govern, establish strategy, accountable owners, risk classification, authorization, monitoring, and compliance oversight. Under Guide, define approved and prohibited uses, data protection, documentation, procurement expectations, human review, and training. Under Guard, restrict authority, access, and autonomy through testing, verification, logging, security, escalation, and mandatory human intervention for consequential decisions. Which controls apply to the proposed use and its consequences? What evidence demonstrates that the controls operate as intended, and what requires human intervention or further review? 2.3.7 Maintain integrated decision support. Connect definitions, sources, processes, systems, responsibilities, dependencies, analyses, and prior decisions within a reliable, controlled information framework. Can reviewers trace a recommendation back to its evidence and assumptions? Where could missing connections, inconsistent definitions, or uncontrolled information affect the decision? 2.4 Risk Assessment and Response2.4.1 Identify and assess risks and uncertainties. Identify material risks, constraints, dependencies, unknowns, external trends, and second- or third-order effects; assess them and assign responsibility for monitoring or response. What could change the initiative’s outcomes or feasibility? Which uncertainties need investigation before the next commitment? 2.4.2 Define risk responses. Specify whether each material risk is to be avoided, reduced, transferred, accepted, or addressed through contingency planning or staged commitment. Why is the proposed response appropriate to the risk and decision context? What residual exposure, contingency, or acceptance requires review by the appropriate authority? 2.5 Alternatives, Feasibility, and Business Case2.5.1 Develop credible alternatives. Develop multiple feasible courses of action at a comparable level of detail. Include the status quo and, where appropriate, deferral, process change, improvement, leasing, sharing, capital investment, or a combined strategy. Do the alternatives address the defined problem without assuming a building solution? Are meaningful noncapital or staged responses represented? 2.5.2 Compare alternatives against decision criteria. Use explicit, weighted or prioritized criteria and appropriate scenario, sensitivity, cost, benefit, risk, schedule, and implementation analyses. Are assumptions and levels of detail comparable? What explains differences in performance, and how do the criteria support or challenge the emerging recommendation? 2.5.3 Test scenarios and sensitivity. Test alternatives as demand, cost, timing, assumptions, and external conditions change. Make trade-offs, dependencies, future options, and contingencies explicit. Under what conditions does the preferred alternative change? Which findings support a traceable recommendation, and which require further inquiry? 2.5.4 Evaluate lifecycle value. Consider acquisition or construction, activation, operation, maintenance, adaptation, renewal, and eventual disposition consequences as inputs to predesign decisions. Evaluate affordability, resilience, and avoidable lock-in. Does the comparison account for consequences over a common planning horizon? Which commitments limit future options or shift costs and risks to later phases? 2.5.5 Maintain the master schedule. Connect properties, initiatives, decision events, funding cycles, dependencies, useful lives, and anticipated consequences in a regularly reviewed master schedule. Are commitments and decision gates coordinated with resource availability and capacity timing? Which changes in one initiative affect others? 2.5.6 Test affordability and implementation feasibility. Assess funding, staffing, schedule, technology, procurement, regulatory approvals, organizational capacity, and change readiness. Are these resources and conditions sufficient for the proposed alternative? What must be resolved, staged, or qualified before implementation is considered feasible? 2.5.7 Maintain the business case as a living decision instrument. Explain the problem or opportunity, feasible alternatives including the status quo, total costs, projected financial, operational, and strategic benefits, major risks and their management, and why the recommended course is best now. Establish feasibility, timing, and alignment with enterprise objectives. Preserve the evaluation and recommendation separately from the authorized decision record. Revalidate the case at major decision gates and when evidence or conditions materially change. Does the case support the current recommendation and proposed commitment? Which findings, conditions, or unresolved issues require revision or further inquiry? 2.6 Authorization, Change Control, and Learning2.6.1 Establish adaptation and change control. Define review intervals, monitored indicators, acceptable ranges, change thresholds, impact-assessment requirements, and escalation responsibilities. What changes would invalidate assumptions or require reconsideration? Who assesses their consequences and brings them to the appropriate decision authority? 2.6.2 Assess decision readiness. Present unresolved issues and assess whether evidence is sufficient to proceed, proceed with conditions, revise, defer, conduct further inquiry, or stop. Is the evidence proportionate to the proposed commitment? Which unresolved matters prevent a sound decision or require explicit conditions? 2.6.3 Document authorization conditions. Record approval conditions, funding limits, contingencies, delegated authorities, required follow-up actions, and the next decision gate. What is authorized, by whom, and within which limits? Are conditions and follow-up responsibilities explicit rather than inferred from completion of a procedure? 2.6.4 Preserve the decision record. Distinguish the planning team’s recommendation from the ultimately authorized decision. Preserve supporting evidence, assumptions, alternatives, criteria, rationale, dissenting views, approvals, qualifications, conditions, commitments, and responsible parties. Can a later reviewer reconstruct what was recommended, what was authorized, and why? Are departures or qualifications visible? 2.6.5 Record executive departures from recommendations. When leadership overrides a recommendation, preserve the original analytical record and state the basis for departure. Name the accountable executive and document accepted risks, safeguards, monitoring indicators, reassessment checkpoints, and escalation thresholds. Is the departure and its accountability explicit? What conditions would require reassessment or escalation? 2.6.6 Assign post-decision review and learning. Assign responsibility for scanning changed conditions, comparing actual costs, benefits, risks, timing, and performance with the approved business case, and taking corrective action. Specify how reviews will record whether earlier decisions remain sound, why adaptations were made, and lessons for future decisions. Who will conduct the reviews, using which indicators and checkpoints? Establish these responsibilities during predesign; do not treat this chapter as an assessment of later design, construction, or facility operations. 2.7 Organizational Direction and Portfolio Priorities2.7.1 Translate organizational strategy into facility needs. Clarify mission, vision, goals, strategies, implementation requirements, and measures of success. Derive facilities need from organizational priorities rather than a predetermined solution. What organizational outcomes must the built environment support? Which needs require facilities responses, and which could be addressed otherwise? 2.7.2 Conduct the executive vision session. Engage executives, critical stakeholders, and the implementation team to establish a shared desired state, align goals and objectives, and explore possibilities without premature selection. Record unresolved issues and follow-up responsibilities. Is the desired end state clear and shared? Which differences or unanswered questions inform subsequent inquiry? 2.7.3 Assess strategic context and competitive forces. Assess organizational strengths, weaknesses, and changes affecting demand, resources, or priorities. Where relevant, evaluate new entrants, customer and supplier bargaining power, substitute products or services, and rivalry among existing providers. Distinguish organizational needs from assumptions about buildings or space. Which external or internal forces materially affect this organization? How do they change the need, timing, or range of credible responses? 2.7.4 Develop strategic facilities responses. Evaluate synergy, differentiation, focus, skills, and technology as potential responses to identified organizational needs. For each response, state the strategic focus, facilities implications, and need addressed. Treat specific interventions as alternatives to test rather than predetermined design or implementation commitments. How does each response address an evidenced need? What must be tested before it becomes a recommendation? 2.7.5 Set portfolio priorities. Assess business-unit strategic positions and resource priorities; connect the appropriate mix of people, technology, space, and place to organizational strategy. Which needs deserve priority and why? Does the portfolio response reflect organizational priorities rather than isolated property preferences? 2.7.6 Plan for portfolio change. Define each business unit’s expansion, optimization, or contraction response, accounting for sudden and gradual change, capacity timing, resource availability, reuse opportunities, and market constraints on releasing surplus facilities. Can the response accommodate different rates or directions of change? Which resource or market constraints limit adjustment? Strategic Planning Phase 2.8 Portfolio Diagnosis, Scenarios, and Sponsor Review2.8.1 Diagnose portfolio needs and frame the problem. Compare long-range financial, workforce, and sector-specific demand forecasts with asset capacity, utilization, suitability, infrastructure, and lease constraints. Incorporate occupant surveys and business-unit interviews into the gap analysis. Establish a bounded problem statement before recommending alternatives. Where do needs and available capacity diverge? Which findings or assumptions require validation before scenarios are developed? 2.8.2 Establish the portfolio scenario baseline. Use an analysis of strengths, weaknesses, opportunities, and threats (SWOT) to establish the existing-situation baseline within defined problem boundaries. Does the baseline provide a consistent basis for comparing scenarios? Which strengths, constraints, opportunities, or threats materially affect the comparison? 2.8.3 Compare portfolio scenarios and recommend a strategy. Within the problem boundaries and against the baseline, compare alternative real estate strategies, building prototypes, hybrid work models, and operational responses under different future conditions. Use explicit criteria for workplace experience and culture, location, project delivery, financial implications, risks, space efficiency, timing, and change management. Translate findings into an evidence-based recommendation for executive review, sponsorship, and subsequent implementation where authorized. Which scenario best addresses the need under the tested conditions? What trade-offs, conditions, and uncertainties must accompany the recommendation? 2.8.4 Review the strategic budget and obtain sponsor direction. Compare capital expenditure (CAPEX), rent and lease obligations, operating expenditure (OPEX), total cost of occupancy, and cash-flow implications consistently across alternatives. Present findings, trade-offs, risks, and investment criteria to sponsors; document approval for the appropriate next phase. What direction and limits have sponsors authorized? Does the record distinguish phase approval from transaction authorization and the final Project Readiness Review? 2.8.5 Prepare the strategic planning business case. Apply Group 2.5 to prepare an executive summary, problem or opportunity statement, strategic alignment, alternatives analysis, financial assessment and return on investment, risk analysis and mitigation, and implementation roadmap. State recommendation conditions and unresolved issues. Maintain the case through real estate and project definition. Does the case support sponsor review and the next phase’s inquiry? Which elements need refinement as evidence develops? Real Estate Phase 2.9 Search, Alternatives, and Due Diligence2.9.1 Define real estate objectives and search criteria. Translate organizational priorities into measurable real estate objectives and requirements brief. Validate demand using utilization evidence, operational requirements, and growth scenarios. Distinguish essential location constraints from preferences and agree evaluation weights before reviewing properties. What needs must a property or occupancy strategy satisfy? Which criteria are essential, and which assumptions about demand require further testing? 2.9.2 Survey the market. Assess credible properties consistently for functional fit, location, availability, occupancy timing, and commercial terms. Which properties warrant further investigation against the agreed criteria? Where are market information or availability assumptions incomplete? 2.9.3 Conduct technical, environmental, and legal due diligence. Engage qualified specialists to test zoning, environmental and legal constraints, entitlements, building systems, accessibility, infrastructure, and preliminary feasibility. Assign material risks and unresolved issues for resolution. What constraints could prevent or qualify the proposed use or commitment? Which findings require specialist confirmation or further project definition? 2.9.4 Compare real estate alternatives and lifecycle value. Compare relocation, renovation, existing-space optimization, flexible occupancy, and a no-project baseline where credible using common demand assumptions, criteria, and planning horizons. Update the business case for CAPEX, OPEX, lease commitments, fit-out, relocation, disruption, contingencies, end-of-term obligations, qualitative benefits, and sensitivity to changing conditions. Which alternative offers the strongest fit and lifecycle value? What assumptions, obligations, or uncertainties could change that conclusion? 2.10 Transaction Authorization and Phase Handoff2.10.1 Assess transaction readiness. Have qualified legal and real estate advisers review proposed commercial terms, their binding effect, flexibility provisions, delivery responsibilities, access, and occupancy timing. Before an irreversible commitment, obtain authorized executive acceptance of feasibility, affordability, schedule, material risks, and conditions requiring further project definition. What obligations would the transaction create? Is the evidence sufficient for that commitment, and what specific authorization or conditions remain outstanding? 2.10.2 Review real estate phase readiness. Review outcome-led objectives, validated demand, early stakeholder integration, credible alternatives, evidence proportionate to commitment, lifecycle value and deliverability, practical flexibility, explicit decision authority and criteria, and iterative feasibility testing. Document residual risks and conditions for acceptance by the appropriate executives. Is there an authorized basis for handoff to project definition? Does readiness extend beyond transaction completion alone? 2.10.3 Handoff to project definition. Transfer authorized direction, the business case and decision record, objectives, success criteria, requirements and demand assumptions, alternatives and rationale, feasibility findings, cost and schedule ranges, commercial terms, and assigned outstanding actions. Require reconsideration of the real estate decision if project definition reveals a material mismatch. Can the receiving team trace the direction and its conditions? Which findings would trigger a return to the real estate decision authority? Project Definition 2.11 Governance, Planning Inputs, and Requirements2.11.1 Establish project governance and charter. Define the mandate, executive sponsorship, goals, resource allocations, roles, escalation paths, reporting intervals, and decision gates. Assign RAPID responsibilities—Recommend, Agree, Perform, Input, and Decide—with coordinated participation from real estate, human resources (HR), information technology (IT), finance, legal advisers, and workplace operations. Are the project’s purpose, authority, and responsibilities clear? Which interfaces or unresolved governance matters could impede definition or authorization? 2.11.2 Apply the programming method and develop requirements. Complete the five programming steps—establish goals, collect and analyze facts, test and evaluate concepts, determine needs, and state the problem—across function, form, economy, and time. Translate validated business-unit needs into spatial, technical, operational, and performance requirements, measurable success criteria, and clear scope boundaries without prematurely prescribing design solutions. Are requirements traceable to validated needs? Which conflicts or assumptions require further inquiry before the program of requirements can support design? 2.11.3 Validate project information and traceability. Apply Group 2.3 by tying each material fact to a decision, authoritative source, owner, date, unit, assumption, confidence level, and validation status. Maintain consistent definitions across enterprise, portfolio, site, building, floor, room, and asset records. Apply access, retention, privacy, cybersecurity, and human review controls to AI-assisted analysis. Can the requirements and analyses be traced and reconciled across these records? Which information or control gaps affect confidence in the project definition? 2.11.4 Identify applicable standards, sustainability, and resilience requirements. Identify workplace standards, accessibility requirements, building-system criteria, indoor environmental quality targets, energy and carbon goals, material-health criteria, water and resilience requirements, and regional codes at the appropriate level of detail. Coordinate measurable, locally applicable requirements with the program, site constraints, budget, and operating model. Which requirements apply to this project and location, and what evidence or specialist review is needed to demonstrate compliance? Identification or procedural completion alone does not establish compliance. 2.11.5 Test needs and state design problems. Test site, building, and workplace capacity requirements against physical constraints, applicable measurement standards, available area, budget, schedule, and operational readiness. State the critical performance conditions, conflicts, assumptions, constraints, and evaluation criteria that design must address. Are the needs achievable within the identified constraints? Which unresolved conflicts must be addressed before design is authorized? 2.12 Scope, Delivery Strategy, and Design Authorization2.12.1 Reconcile the scope, budget, and schedule baseline. Reconcile defined requirements with preliminary CAPEX and OPEX models, financial constraints, and realistic schedules through move-in and operational readiness. Make critical dependencies, material trade-offs, outstanding risks, and responsibility for resolution explicit. Are scope, cost, and timing mutually consistent? What must change or be resolved before the baseline can support authorization? 2.12.2 Define delivery and procurement strategy. Compare delivery methods against scope maturity, complexity, schedule, owner participation, risk allocation, and applicable procurement requirements. Define external service scopes, selection criteria, requests for qualifications (RFQs) and requests for proposals (RFPs) where appropriate, contract responsibilities, pricing assumptions, and award authority. Distinguish authorized predesign services from later design, construction, and contract administration. Does the strategy fit the project’s requirements and constraints? Which procurement or authority conditions must be resolved before later services or awards are authorized? 2.12.3 Review project definition readiness. Review shared business purpose, clear decision authority, validated planning inputs, design-ready requirements, reconciled scope, budget, and schedule, measurable success criteria, aligned delivery and procurement, and visible risks and dependencies. Confirm the basis for documented authorization and handoff; assign verification responsibilities and actions for unresolved issues before the Project Readiness Review. What evidence supports readiness for the gate? Which gaps require further definition, explicit conditions, or deferral? 2.12.4 Conduct the Project Readiness Review. Before design authorization, review the project charter, program of requirements, approved project delivery strategy, updated business case, scope, budget, schedule, risks, success criteria, and stakeholder alignment for consistency and acceptance by the appropriate authorities. Does the evidence support the specific authorization requested? 2.12.5 Submit the Project for Authorization to Proceed. Record whether the project is authorized, authorized with conditions, modified, deferred, returned for further analysis, or not authorized; state outstanding actions, accountable parties, and required follow-up. What conditions and limits govern any handoff for design? Prepared by Steven Parsahall, 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 |