Project Change Control: Process, Change Requests and Approval

A seemingly simple project request — “Can we just add this feature?” — may be the point at which change control becomes essential. Scope, schedule and budget may already be agreed, yet even a modest addition can alter dependencies, shift milestones, consume specialist resources, increase cost or introduce new risk. 

Change control in project management does not exist to prevent those changes. It ensures that a proposed change is clearly defined, its wider consequences are assessed, and the right authority approves it before the project commits time, money or resources. This discipline helps teams adapt without quietly losing control of what was originally approved.

This guide from LOTC focuses on project change control rather than organisational change management concerned with workforce adoption and behavioural transition.

Change control in project management is the governance process used when a proposed change could alter something the project has already approved or committed to. It turns a request into a controlled decision rather than allowing it to become work by default.

The process follows:

proposed change → documented request → impact assessment → authorised decision → implementation and update. It may apply to:

• scope or requirements;

• schedule or milestones;
• budget or resources;
• technical solutions;
• contractual commitments; or

• significant assumptions and constraints.

A requested change is not an approved change. A stakeholder may raise a need, but the baseline should remain unchanged until the request has been assessed and authorised. 

Project change control provides a structured basis for assessing, approving or rejecting change requests before approved changes are incorporated into project baselines.

Not every adjustment needs a formal request. If the project manager acts within delegated authority and agreed tolerances, routine decisions can remain part of day-to-day management. Formal change control becomes necessary when a change exceeds those boundaries or affects an approved commitment.

A strong change control process in project management turns a proposed change into an evidence-based decision before the project commits to it. The sequence is clear: define the request, assess its impact, route it to the right authority, record the decision, then implement what has been approved.

1. Capture and Define the Change Request

Document exactly what should change, who requested it, why it is needed, which approved deliverable, requirement or baseline is affected, and whether urgency matters. “The customer wants an additional reporting feature” is not enough; the request should state what differs from the approved requirement.

2. Assess the Integrated Impact Before Approval

Evaluate the change across the project, not only where it first appears. Integrated change control asks what the proposal does to:

• scope, requirements and the Work Breakdown Structure (WBS);

• dependencies, milestones and the Critical Path Method (CPM) schedule;
• cost, resources and procurement;

• risk, quality, contracts and expected benefits.

A small feature may require a supplier, extend procurement lead time, delay a critical-path activity, increase cost and introduce implementation risk.

3. Route the Request to the Right Decision Authority

Send the request to whoever has authority to decide. A project manager may approve changes within delegated tolerances; larger changes may require the sponsor, customer, contractual authority or a change control board.

Authority thresholds should be known before a difficult change arrives. The Project Charter may establish initial decision authority, while governance arrangements define how material changes are escalated.

A CCB is not mandatory for every project. On larger or more complex projects, it provides a formal forum to approve, reject, defer or request further analysis.

4. Record the Decision and Its Rationale

Record more than “approved” or “rejected”. A decision may be approved with conditions, deferred, or returned for further analysis. Capture the rationale too. Without it, the change log loses governance value when stakeholders later ask why a request was not accepted.

5. Update the Baseline, Implement and Close the Change

Approval is not the final step. Update the affected baselines, plans and project documents as required, communicate the decision, assign ownership, implement the approved change, verify completion and close the record.

If an approved change is implemented without updating the affected baseline, the team may end up measuring performance against a version of the project that no longer exists.

Read also: Project Planning: Process, Benefits & Best Practices

Use this change request template to turn a proposed change into a structured input for assessment and decision-making. It can be adapted as a project change request template, change control template or formal record within your existing governance system.

Copy this change request form template into Word, Excel, Google Docs or your organisation’s project-management system and adapt the fields to your governance requirements.

Completing the form does not authorise the change. The template provides evidence for assessment and creates a decision record; authority still rests with the person or body defined by the project’s change control arrangements.

Consider a CRM implementation whose approved charter states that active customer records will be migrated before the Q4 go-live. A stakeholder then raises a project change request to include five years of archived customer records within the same deadline.

The completed change request form example might look like this:

This illustrates the purpose of the change request process: not to favour approval, but to expose trade-offs before commitment.

Good change control is not designed to approve change requests. It is designed to make the consequences of a decision visible before the organisation commits to them.

Understanding change management in project management starts with separating control of the project from adoption of the change it delivers. They may interact, but they answer different questions.

For example, adding a new integration to a CRM implementation requires project change control; preparing employees to use that integration effectively is organisational change management.

The Project Management Institute (PMI) describes organisational change management as a structured approach to moving individuals, groups and organisations from a current state towards a desired future state. In practice, it complements rather than replaces the project controls used to govern changes to scope, schedule, cost and other approved commitments.

Poor project change control usually fails at one of two extremes: teams either bypass governance or make it so cumbersome that people work around it.

Common mistakes include:

• implementing a request before formal approval;

• accepting material verbal changes without documenting them;
• assessing scope while ignoring schedule, cost, resources or risk;
• escalating every minor operational adjustment to the change control board;
• giving the project manager accountability without clear decision authority;
• treating approval as the final step instead of updating baselines, communicating the decision and closing the record;
• removing rejected or deferred requests from the change log; and

• using change control to block legitimate change rather than evaluate it objectively.

The aim is control without unnecessary bureaucracy.

If the team cannot show what changed, why it changed, what impact was assessed, who authorised it and which baseline now applies, the change has not been fully controlled.

Effective change control does not make a project resistant to change. It gives decision-makers the information, discipline and authority needed to accept worthwhile changes without losing control of the project already approved.

London Optimum Training & Consultancy’s Comprehensive Guide to Project Management develops that capability across the wider project lifecycle, including the project charter, WBS, planning, cost and schedule control, EVM, and managing project changes and issues.

For professionals building formal project-management knowledge, the Certified Associate in Project Management (CAPM) course covers Project Integration Management, including monitoring and controlling project work and performing integrated change control.

If you are deciding which training route best fits your role, team or current project responsibilities, speak with London Optimum Training & Consultancy on WhatsApp.