Change Management in Project Management: Plan, Process, Change Control, and Examples

Change Management vs Change Control in Project Management

Change management is broader than change control. Change management addresses how change is prepared for, governed, implemented, communicated, and adopted, while change control focuses specifically on evaluating and deciding proposed changes to an approved project baseline.

This distinction is important because the terms are frequently treated as interchangeable. Change control in project management is a controlled decision process, whereas change management may also address stakeholder readiness, communication, training, transition, resistance, and adoption.

For this reason, good project governance needs both disciplines. A project may approve the technically correct change through change control but still experience poor results if affected stakeholders do not understand or adopt it.

Change Management vs Project Management

Project management organizes the work required to achieve defined project objectives, while change management focuses on introducing and supporting change so that the intended transition can be implemented effectively. They overlap when a project creates changes that affect processes, technology, roles, behaviors, or established ways of working.

The two disciplines therefore complement each other rather than compete. Project management can deliver the new system, process, facility, or service, while change management helps affected stakeholders transition to the new way of operating.

What Is a Change Request in Project Management?

A change request in project management is a documented proposal to modify an approved or planned aspect of a project. Depending on the project’s governance arrangements, a request may concern requirements, deliverables, scope, schedule, budget, quality expectations, resources, contracts, technical specifications, corrective action, or another controlled project element.

A change request should provide enough information for an informed decision. It commonly identifies the requested change, the reason for it, the expected benefit or necessity, the affected project components, the requesting stakeholder, and any initial assumptions or constraints.

Example of a Project Change Request

Suppose Northbridge Analytics is developing a financial reporting platform. Halfway through the project, the client requests an additional real-time reporting dashboard.

1. The client submits a formal request explaining the new reporting requirement.
2. The project team estimates that the additional work will require three more weeks and approximately £18,000 of additional development and testing expenditure.
3. The team identifies technical integration risks and evaluates whether existing resources can complete the additional work.
4. The authorized decision-makers review the expected business value against the additional cost, schedule impact, and risk.
5. If approved, the project manager updates the affected plans and controlled baselines before implementation begins.

The request therefore becomes a controlled project decision rather than an informal instruction that unexpectedly increases work.

What Is Change Control in Project Management?

Change control is the formal process used to capture, assess, decide, track, and implement proposed modifications to controlled project elements. Its purpose is to ensure that significant changes are not introduced simply because somebody requests them.

A disciplined change control process protects the project from uncontrolled modifications while still allowing justified changes. It is particularly important when a change affects approved project scope and requirements management, contractual obligations, budget, deadlines, or major deliverables.

In baseline-driven environments, this coordinated evaluation may also be described as integrated change control. The principle is important because a scope adjustment rarely exists in isolation. It can affect schedule, cost, resources, risks, quality expectations, procurement, and stakeholder commitments.

What Is a Change Control Board?

A change control board, commonly abbreviated as CCB, is a formally authorized group that reviews specified categories of change requests and decides whether they should be approved, rejected, deferred, or escalated.

The board may include the project sponsor, customer representatives, project manager, technical specialists, financial representatives, operational stakeholders, or other people with appropriate authority and expertise. Its composition depends on project size, complexity, risk, contractual conditions, and governance requirements.

Importantly, not every project requires a separate CCB, and not every change must be approved by one. The project’s governance arrangements should define who has authority at different decision thresholds. A project manager may approve minor changes within delegated tolerances, while significant changes may require a sponsor, steering committee, client, or CCB decision.

Who Approves Changes in a Project?

Changes should be approved by the person or governance body given the appropriate authority in the project’s change management arrangements. Approval authority should be established before major requests arise so that project decisions remain consistent and accountable.

• The project manager may approve changes that fall within explicitly delegated limits.
• The project sponsor may authorize changes that materially affect project objectives, funding, or business commitments.
• A Change Control Board may evaluate changes requiring cross-functional or formal governance review.
• A client or project owner may need to approve changes affecting contractual requirements or accepted deliverables.
• A steering committee or senior governance body may decide changes that exceed established project tolerances.

Clear authority prevents uncertainty and ensures that the people accepting the consequences of a change also have the mandate to authorize it.

What Is a Project Change Management Plan?

A project change management plan explains how proposed project changes will be submitted, evaluated, authorized, communicated, implemented, tracked, and closed. It establishes a predictable decision process before the project team faces competing requests or urgent pressure to alter agreed work.

The level of detail should be appropriate to the project. A small internal initiative may use a simple procedure and change log, while a complex contractual or regulated project may require detailed approval thresholds, configuration controls, audit records, and formal governance meetings.

Key Components of a Change Management Plan

• Roles and responsibilities: The plan should identify who may raise change requests, who performs impact analysis, who makes decisions, and who implements approved changes.
• Change categories and thresholds: The plan should define which changes require formal review and which can be managed within delegated authority.
• Change request format: A standardized request should capture the proposed change, reason, expected value, affected areas, requester, urgency, and supporting information.
• Impact assessment criteria: Reviewers should examine scope, schedule, cost, quality, resources, risks, dependencies, contracts, benefits, and stakeholder implications where relevant.
• Approval process: The plan should explain whether decisions are made by the project manager, sponsor, CCB, client, or another governance authority.
• Change log: All formal requests and their status should be recorded so that the project retains a reliable decision history.
• Baseline and document updates: The plan should specify which project documents are updated after approval and who controls the revised versions.
• Communication arrangements: Relevant stakeholders should know what was decided, why it was decided, and what actions or responsibilities follow.
• Implementation and closure: Approved changes should be tracked until implementation is verified and the request can be formally closed.

The plan should also coordinate with project cost planning and control when financial baselines are affected and with risk management in project management practices when a proposed change creates, removes, or modifies project risks.

Change Management Process in Project Management

The change management process in project management moves a proposed change from identification through documented evaluation, authorization, implementation, monitoring, and closure. The exact procedure varies between projects, but a disciplined process makes decisions traceable and prevents unauthorized changes from entering project work.

1. Identify the Proposed Change

The process starts when a stakeholder, project team member, customer, supplier, manager, or project control activity identifies a need for change. The need may arise from a new requirement, risk response, defect, regulatory requirement, technical discovery, resource constraint, or changed business priority.

2. Document the Change Request

The proposed change should be formally recorded. The request explains what is changing, why the change is needed, who requested it, its urgency, and what project areas may be affected.

Documentation prevents important decisions from being based only on informal conversations, messages, or undocumented instructions.

3. Assess the Impact of the Change

Impact assessment determines what the project would gain, lose, spend, delay, expose, or need to reorganize if the proposed change were accepted. The depth of the assessment should match the significance of the request.

• Scope: The project team determines which requirements, deliverables, activities, or acceptance criteria would change.
• Schedule: The team evaluates whether additional work changes activity durations, dependencies, milestones, or the completion date.
• Cost: The assessment estimates additional expenditure, savings, funding requirements, and effects on the cost baseline.
• Resources: Reviewers determine whether additional people, equipment, expertise, suppliers, or materials will be required.
• Quality: The team evaluates whether specifications, testing, acceptance criteria, or quality expectations need to change.
• Risk: The assessment considers new threats and opportunities as well as changes to existing risks.
• Stakeholders: Reviewers identify who will be affected and whether expectations, responsibilities, training, or acceptance may change.
• Dependencies and contracts: The team checks whether the proposed change affects suppliers, interfaces, approvals, procurement commitments, or external obligations.

This analysis should connect naturally with stakeholder management in project management because a technically small change can still create significant effects for customers, users, sponsors, suppliers, or operational teams.

4. Approve, Reject, Defer, or Escalate the Change

The authorized decision-maker reviews the change request and impact assessment. The proposed change can then be approved, rejected, deferred until more information is available, or escalated when the decision exceeds the authority of the current governance level.

A good decision considers not only whether the proposed change is desirable, but whether its expected value justifies its total impact on project objectives and commitments.

5. Update Project Plans and Baselines

Approval alone does not complete the control process. Relevant plans, schedules, budgets, requirements, registers, technical documents, contracts, responsibilities, and baselines should be updated before the team treats the revised position as authorized.

An approved change should become part of the controlled project plan, not remain a separate decision that the project documentation fails to reflect.

6. Implement and Communicate the Approved Change

The team implements the authorized work according to the revised plan. Stakeholders should receive information appropriate to their roles, particularly when the change affects responsibilities, deadlines, processes, interfaces, expected outputs, or ways of working.

Effective project communication management – planning and information flow is therefore an important part of implementation. Explaining why a change has been approved can be just as important as explaining what has changed.

7. Monitor, Verify, and Close the Change

The project manager monitors implementation to confirm that the approved change has produced the intended result and that unexpected consequences are identified. Actual cost, schedule, quality, risk, and stakeholder effects should be compared with the assumptions used during approval where appropriate.

Once implementation has been verified, records can be updated and the change formally closed. This history provides useful evidence for audits, lessons learned, future estimates, and later project decisions.

Project Change Management Examples

Project change management examples show how a request moves from an idea or requirement to an evaluated and authorized project decision. The following scenarios demonstrate the same control logic in two different industries.

Example 1: Software Project Change Management Process

Northbridge Analytics is developing an accounting platform for a commercial client. After development has started, the client asks for a new real-time financial reporting dashboard.

1. The client submits a documented change request explaining the reporting requirement and expected business benefit.
2. The project team determines that the dashboard requires additional development, data integration, security testing, and user acceptance testing.
3. The impact analysis estimates an additional £18,000 cost, three weeks of work, and a moderate integration risk.
4. The authorized change board compares the expected benefit with the additional cost, schedule impact, and technical risk.
5. The request is approved because the client accepts the revised budget and delivery date.
6. The project manager updates the requirements, schedule, budget, risk information, responsibilities, and affected project baselines.
7. The team develops and tests the dashboard while the project manager monitors the approved change until completion.

The formal process allows the client to obtain additional value without allowing the new requirement to become uncontrolled scope expansion.

Example 2: Construction Project Change Control

Greenfield Civic Authority is renovating a public administration building. After exterior materials have been ordered, the project owner requests a different exterior finish.

1. The project manager records the requested finish change and documents the owner’s reason for requesting it.
2. The construction team determines that some ordered materials can no longer be used and replacement materials will cost approximately £6,500.
3. The schedule analysis identifies a possible four-day delay because the revised material has a longer delivery lead time.
4. The team reviews contractual, supplier, quality, cost, and schedule implications before presenting the request for approval.
5. The owner accepts the additional cost and revised milestone, so the authorized change is approved.
6. The project manager updates the relevant specifications, procurement information, budget, schedule, and contractor instructions.
7. The approved finish is implemented and monitored during subsequent construction work.

Change control converts a seemingly simple design preference into a documented decision that accounts for its wider project consequences.

Managing Project Change Without Creating Scope Creep

Project teams prevent scope creep by separating authorized project change from informal additions to project work. A useful idea is not automatically an approved requirement. Proposed work should enter the agreed control process whenever it exceeds established authority or alters a controlled project commitment.

This is especially important because scope changes can influence time and cost simultaneously. Understanding how project scope is defined and controlled helps teams recognize when a requested adjustment changes the agreed work rather than merely clarifying it.

Practical control depends on several habits: document requests early, evaluate the full impact before promising delivery, apply agreed authority thresholds, update plans only after authorization, communicate decisions clearly, and keep a traceable change log.

Professional Learning for Effective Project Change Management

Professional project management education helps practitioners understand change as part of a wider governance system involving integration, scope, cost, risk, stakeholders, communication, and decision authority.

Professionals who want structured project management training can explore the practical CPM certification with PMP training and exam prep. Managers seeking broader business and leadership development may consider an online MBA in Project Management for advanced managerial roles.

Experienced professionals who want to develop advanced research capability in project, program, portfolio, governance, or organizational change topics can also review the doctoral PhD in project management by research.

Final Words on Change Management in Project Management

Effective project change management allows a project to adapt without surrendering control. The project manager should ensure that significant changes are documented, assessed for their wider impact, reviewed by the appropriate authority, reflected in project plans, communicated to affected stakeholders, and monitored after implementation.

Communication remains particularly important. Stakeholders usually need more than notification that something has changed. They need to understand why the decision was made, what consequences it creates, and what actions are expected from them.

For this reason, the strongest change processes combine disciplined governance with clear human communication. Projects can then respond to legitimate new requirements while protecting objectives, resources, accountability, and stakeholder confidence.