Scope and Change Order Management

Defining scope around project outcomes and maturing it through revisions, a robust and well-timed change order process (including agile handling and the use of technology), evaluating changes against core outcomes, and the scope evaluation and management tools (value engineering, cost-benefit analysis).

5 minutes 5 Questions

In the PMI Construction Professional (PMI-CP) framework, Scope and Change Order Management covers how construction teams define, control, and adjust the work required to deliver a project, while protecting cost, schedule, quality, and contractual relationships. Scope management starts with clearly …

Concepts covered
Change Order Schedule and Cost ImpactsEvaluating Changes Against Core OutcomesTiming the Change Process in the LifecycleBenefits and Downfalls of Change TechnologyPricing and Negotiating Change OrdersScope Maturity and the Project Definition Rating IndexScope Statement and Basis of DesignScope Evaluation and Gap AnalysisScope Freeze and Design FreezeValue EngineeringStakeholder Alignment on ScopeChange Order Documentation and ApprovalDesigning a Robust Change Order ProcessOutcome-Based Scope DefinitionTechnology for Scope and Change ManagementScope Revisions and Scope MaturityWork Breakdown Structure for Built Environment ProjectsConstructability ReviewsScope Creep PreventionProject Mission and Business ObjectivesScope Verification and AcceptancePivoting Scope with Scope Management ToolsAgile and Rapid Change HandlingOwner-Directed Versus Contractor-Initiated ChangesCost-Benefit Analysis for Scope Decisions
Test mode:
Start practice test

PMI-CP - Scope and Change Order Management Example Questions

Test your knowledge of Scope and Change Order Management

Question 1

In a work breakdown structure for a built environment project, what does the code of accounts provide?

Correct Answer: Unique hierarchical identifiers for each WBS element so cost, time and responsibility data roll up consistently

The code of accounts is a numbering system that gives every WBS element a unique hierarchical identifier. Because the codes follow the WBS structure, cost, schedule and responsibility data can be collected at any level and roll up consistently to the summary level.
Mapping elements to trade or specification sections describes a classification system such as MasterFormat or UniFormat, not the WBS coding itself. Activity numbering and logic links belong to the schedule network, which is built from work packages rather than defined by the code of accounts. The code of accounts covers all WBS elements, not just control accounts, and its purpose is not limited to earned value reporting.
Key concept: WBS code of accounts as the hierarchical identification and roll-up structure.

Question 2

On a lump-sum contract, the roofing subcontractor prefers a membrane system its crews already know. The contractor proposes that system in place of the specified product at no change to the contract sum. The change clause lets the owner accept or reject contractor-initiated substitutions. Which consideration should govern the owner's project manager's recommendation on the proposal?

Correct Answer: Whether the substitute meets the specified performance, warranty and life-cycle outcomes

The owner's project manager should judge a contractor-initiated substitution by whether it delivers the specified performance, warranty and life-cycle value, because the owner keeps the roof long after the contractor's convenience stops mattering.
Schedule recovery is not the stated purpose of this substitution and does not prove the product is equivalent. An unchanged lump sum is already offered, so cost neutrality alone cannot justify accepting a different product. Shifting defect risk to an insurer does not secure the quality, warranty coverage or service life the owner specified.
Key concept: evaluating substitutions for equivalence against the owner's specified outcomes and life-cycle value.

Question 3

During Front End Planning for a school renovation, the owner's operations team assumes that loose furniture and classroom IT equipment are part of the project. The design team's draft scope statement does not mention either item, and the finance group has budgeted only for building works. The project manager wants to prevent a scope dispute later. Which action BEST achieves this?

Correct Answer: Clarify inclusions and exclusions in the scope statement and confirm them with each group

Explicitly stating what is included and excluded in the scope statement, then getting each stakeholder group to confirm it, aligns the operations, design and finance expectations before the baseline is set. That removes the ambiguity that causes later disputes.
Carrying furniture and IT as provisional sums assumes they are in scope without the owner agreeing to it, and it still leaves the budget gap unresolved. Deferring the decision until design development lets the misalignment persist and grow. Logging the items as a risk covered by contingency treats a known definition gap as an uncertainty, which misuses contingency.
Key concept: defining scope boundaries (inclusions and exclusions) and gaining stakeholder agreement during Front End Planning.

More Scope and Change Order Management questions
372 questions (total)
Practice 100 questions
One session at a time, always new questions