Professional learning guide

Integrated Change Control Guide

Evaluate proposed changes across scope, schedule, cost, quality, resources, risk, procurement, benefits, and stakeholders before authorized decisions.

Core concepts

Build the mental model first

Change request
A documented proposal to modify a deliverable, plan, baseline, document, or controlled item.
Change authority
The person or body authorized by governance to approve, reject, defer, or request more analysis.
Configuration control
Identification and controlled management of product and document characteristics.
Impact analysis
Assessment of direct, indirect, cumulative, transition, contractual, and benefit effects.

Formula reference

Calculate—and understand what direction means

MeasureFormulaInterpretation
Change approval rateApproved requests ÷ decided requests × 100Governance trend, not a target by itself.
Average change cycle timeΣ decision elapsed time ÷ requests decidedHighlights decision-process delay.
Cumulative impactΣ approved change cost or duration impactShows aggregate baseline movement.

Worked reasoning

Executive requests an urgent deadline reduction

01

Situation

The requested date requires overlapping design and build plus expedited supplier work.

02

Manager’s approach

Document the objective, assess compression options and risk, identify cost and quality effects, present alternatives, obtain authorization, and update all affected plans.

03

Takeaway

Senior sponsorship does not eliminate integrated analysis; it clarifies who may decide after impacts are known.

PMP lens

What to remember in scenario questions

  • Analyze before asking the change authority to decide.
  • Only approved changes update controlled baselines.
  • Corrective and preventive actions can be change requests.
  • Update documents and communicate the decision after approval or rejection.

Common doubts

Questions learners ask

Can the project manager approve changes?

Only within the authority and thresholds defined by the change-management approach.

Is an issue fix always a change?

It becomes a formal change when it modifies controlled scope, plans, baselines, or configuration.

Should rejected changes be deleted?

No. Retain the decision and rationale according to governance and record-management rules.

Practice tools

Apply governance & decisions concepts

View all related tools