A change control board (CCB) is the group that reviews proposed changes to a project's agreed baseline and decides whether each one is approved, rejected or deferred. Its job is to make sure only beneficial or necessary changes get in, and that everyone knows the cost in scope, schedule and budget before they do. This guide covers who sits on a CCB, how the process runs from request to record, how it differs from a change advisory board, and how to run a light version when you are the freelance project manager and the team is small.
TL;DR
- A CCB is the approval authority for change requests. It reviews each request and its impact on risk, scope, cost and schedule, then approves, rejects or defers it.
- The core process is four moves: submit the request, analyze the impact, decide, then implement and update the baseline and the change log.
- Typical members are the project manager, sponsor, a technical lead, a finance representative and a client or user representative. Smaller projects often need no formal board at all.
- A CCB handles changes inside a project. A change advisory board covers changes to live services, including emergencies.
- Agile teams rarely keep a standing CCB, but a lightweight one can remain for changes that touch contracts, regulations or release commitments.
Table of Contents
- What a change control board is
- Why projects need one
- Who sits on a change control board
- The change control process, step by step
- A simple change request log you can copy
- What the board does not do
- Change control board vs. change advisory board
- Does Agile have a change control board?
- Running change control as a freelance PM
- Perspective
- Build your change process with the Club
- FAQ
- Sources
What a change control board is
Every project starts with a baseline: the approved scope, schedule and budget. Change control is the process through which all requests to change that approved baseline are captured, evaluated and then approved, rejected or deferred. The change control board is the group that makes the call.
A state agency's change management template puts it plainly: the CCB is the approval authority for all proposed change requests on the project. Its purpose is to review each request, determine the effect on project risk, scope, cost and schedule, and approve or deny it.
The board is a tool, not a requirement. A university project management textbook notes that not every change control system has a board. The system is designed around the size and complexity of the project, organizational policies, the business field and contract requirements. A two-person website build and a multi-vendor infrastructure program need very different machinery.
You will also see the same body called a change review board. Whatever the name, the purpose does not move: protect the baseline from uncontrolled change while still letting valuable change through.

Why projects need one
Uncontrolled change is how projects quietly grow. Each small request sounds reasonable, nobody prices it, and three months later the budget and deadline no longer match the work. The UK government's project delivery guidance says the purpose of change control is to ensure only beneficial or necessary changes to a baseline are implemented, and that every change request should go through an impact assessment before approval.
A CCB gives you three practical things:
- One door. Every change enters through the same form, so nothing is agreed in a hallway or a chat thread.
- A price tag. The cost, time and risk of each change is written down before anyone says yes.
- A record. When someone asks six weeks later why the launch moved, the log answers the question.
For independent consultants this matters even more. You usually have no PMO behind you, and the person asking for "one small addition" is often the person paying your invoice. A defined change process turns an awkward conversation into a routine one. If scope creep is your main worry, our scope creep control guide with templates goes deeper on the front end of this process.
Who sits on a change control board
Membership follows the decision, not the org chart. One practitioner guide lists these common roles:
| Role | What they bring |
|---|---|
| Project manager | Prepares and submits change requests, provides impact analysis |
| Project sponsor | Final approval authority for significant changes |
| Technical lead | Assesses technical feasibility and risk |
| Finance or commercial representative | Evaluates cost implications and return on investment |
| Stakeholder or client representative | Speaks for the end user |
These roles come from a practitioner guide to implementing a CCB. Another project management source adds that boards are a group from the project team that meets regularly and includes representatives of the relevant functional areas plus the project manager, with experts, customers and sponsors also likely included.
Who chairs it
On larger work, the UK government guidance describes a dedicated change control manager or support office manager who oversees changes on behalf of the project manager. They may work through a dedicated change control board, usually a sub-board reporting to the main project board. Either that manager or the project manager may chair it.
Keep it small
The more people on the board, the slower the decisions. Pick the fewest people who can speak for budget, delivery and the customer's interests. A professional standard from the Royal Institution of Chartered Surveyors says a committee or board should be appointed, especially on larger projects, and should meet at regular intervals to assess, manage and record the changes in that period. Regular, short meetings beat ad hoc emergencies.
Contracts can also decide who has the final word. The same standard notes that under an NEC contract the final decision sits with the Project Manager, and under a JCT contract with the Contract Administrator. Read your contract before you assume the board outranks it.
The change control process, step by step
Different organizations number the steps differently, but the sequence is stable. A state template describes five stages: request submission, CCB review, change control plan development, implementation and monitoring, and results assessment. A simpler four-part version, from a project management practitioner, runs submission, impact analysis, decision and implementation. Here is a working version that combines them.

1. Submit the request
The requester describes the change and why it is needed. Using the state template's sequence, the requester describes the change, assesses its impact, completes the form, updates the log, reviews it with the project manager and submits it to the board.
A useful request form has:
- a unique ID and date
- who is asking and why
- what changes (scope, deliverable, date, budget, resources)
- the business reason or the problem it fixes
- urgency
2. Analyze the impact
The project team analyzes cost, schedule impact and resource requirements before the board sees it. This is where most weak change processes fail: the board is asked to decide with no numbers. Write down the effect on scope, time, money, quality and risk, and list at least one alternative, including doing nothing.
The RICS standard adds that a competent person who can review the safety, reliability, performance, cost and timescale implications should be appointed, and that each proposed change should be looked at by at least one other key member or designated representative from each project department.
3. Decide
The board reviews the request, the analysis and the options, then approves, rejects, modifies or defers. Deferral is a legitimate answer: the idea is good but belongs in a later phase or needs more analysis.
How do you judge a request? Most boards work through a short set of questions:
- Is the change necessary (a legal need, a defect, a business-critical gap) or just nice to have?
- What does it cost in money, time and risk, and who pays?
- What happens to the rest of the plan, including dependencies and other deliverables?
- Can it wait for a later release or phase?
- Does the benefit outweigh the cost?
A time limit helps. One large grid operator's procedure sets specific timing: 3 business days for a form completeness check and 7 business days for board review. Your project probably needs faster, but the principle holds: promise a turnaround and keep it.
4. Communicate and record the decision
After the decision, update the change register with the status and notify the change owner, relevant team members and stakeholders. According to the UK government guidance, if the change is approved, update the relevant configuration items such as baselines, documentation and deliverables.
Two habits keep the record trustworthy:
- Record the reason with the decision. A short reason in the decision record keeps everyone aligned and stops the same debate from reopening.
- Log rejected requests too. The log is the register of every request and what happened to it, and a column for the date the baseline was updated shows whether the process is real.
A Canadian provincial guideline recommends treating the log as a living document, reviewed weekly by the project manager and service provider, and monthly by the sponsor. That cadence fits neatly into your normal status meeting rather than adding another calendar invite.
5. Implement and monitor
Approved changes become work: the schedule, budget and scope documents are updated, and the team executes against the new baseline. Check afterward that the change delivered what the request promised.
A simple change request log you can copy
| ID | Date | Requester | Change | Impact (scope / time / cost / risk) | Decision | Reason | Baseline updated |
|---|---|---|---|---|---|---|---|
| CR-001 | Approved / Rejected / Deferred |
One row per request, never deleted. Share it with the client so both sides see the same history.
What the board does not do
A CCB is not a second project team. One experienced practitioner observes that when the project team and sponsor have already approved a change, there are few reasons for the CCB to block it. She describes the board's role as assessing, approving, scheduling and keeping records. In other words, a good board validates and sequences decisions rather than reopening them.
Change control board vs. change advisory board
The two names get mixed up, and the difference is mostly scope. A change control board primarily handles changes within a projects, while a change advisory board covers changes across the service lifecycle, including emergency changes, according to one comparison. Think of the CCB as the gatekeeper for a project's baseline, and the change advisory board as the group that assesses changes to live IT services and operations.
If you manage a project that changes a live system, you may deal with both: the CCB approves the scope change, and the advisory board approves the release window.
Does Agile have a change control board?
Usually not a standing one. A glossary on governance notes that formal standing CCBs are rare in pure Agile environments because change is welcomed. In Scrum, the Product Owner can adjust the backlog at any time, and the team adapts in Sprint Planning.
The same source adds a caveat worth remembering. A lightweight CCB may remain inside a larger predictive governance structure for changes affecting fixed-price contracts, regulatory compliance or interfaces with other teams. If a change would breach a release commitment or a contractual milestone, an organization often steps in with a governance review that looks very much like a CCB meeting.
Practical Agile version:
- Let the Product Owner reprioritize freely inside the sprint and release commitments.
- Define a short list of triggers that escalate a change: contract value, regulatory impact, a milestone date, a dependency on another team.
- Hold escalations in an existing meeting rather than creating a new board.
For how these decisions sit inside a wider structure, see our guide to project governance.
Running change control as a freelance PM
Most freelancers will never convene a formal board, and they do not need to. Scale the idea down:
- Put it in the contract. State that changes to agreed scope go through a written request, with an estimate of the effect on time and fees.
- Name the approver. Usually it is one client sponsor. Make sure that person has the authority to say yes to spend.
- Use one form and one log. The table above is enough.
- Answer within a set time. Two business days is a promise most solo PMs can keep.
- Update the plan the same day. A decision that does not reach the baseline did not happen.
- Agree how updates travel. A clear communication cadence means approved changes reach everyone affected without a flurry of messages.
The point is saying yes without losing the project: price the change, get a decision, record it.
Perspective
Most freelance PMs we meet learned change control inside a large organization, where a board existed and someone else ran it. Then they go independent and discover that the discipline matters more, not less, because nobody else is protecting the baseline.
Our view is that a change process is part of how you sell your work. When a client sees a clear request form, a priced impact and a logged decision, they see a professional who can be trusted with their budget. That is the standard we encourage inside the Club: curated roles, courses, templates and a community of other independent PMs who have faced the same awkward scope conversation and can tell you how they handled it.
If you are moving from corporate to freelance, build your change log template before your first engagement, not after your first dispute.
Ashanti
Build your change process with the Club
If you are setting up change control for your own client work, you do not have to start from a blank page. The Freelance PM Club is a membership platform for freelance project managers and consultants, with curated job listings, expert-led courses, a library of templates and tools, career coaching and a networking community.

Plans on the subscriptions page are Job Board Access at $5 per month, Freelancer Pro at $10 per month and Freelancer Elite at $20 per month. If you would rather talk through your move into independent work, career coaching is available through the Club.
FAQ
What is the purpose of a change control board?
Its purpose is to review proposed changes to a project's baseline and decide whether to approve, reject or defer them. It weighs each change's effect on risk, scope, cost and schedule first. That keeps the project from absorbing changes nobody has priced.
Who should be on a change control board?
Usually the project manager, the sponsor, a technical lead, a finance or commercial representative and someone speaking for the client or end user. Keep it as small as the project allows so decisions stay quick. On small projects, one approver and the project manager can be enough.
How is a CCB different from a change advisory board?
A CCB decides on changes inside a project's baseline. A change advisory board looks at changes to live services across their lifecycle, including emergencies. Large IT projects can involve both.
Does Agile use a change control board?
Standalone, standing boards are uncommon in Agile because the Product Owner reprioritizes the backlog continuously. A light governance review can still apply when a change touches a fixed-price contract, a regulation or a release commitment. Define those triggers up front.
Do I need a CCB on every project?
No. The change control system should fit the size and complexity of the project, organizational policy and contract requirements, and some systems have no board at all. What every project needs is a clear way to request, assess, decide and record changes.
Sources
- APM: What is change control?
- UK Government Project Delivery: Chapter 22, Change control
- Connecticut DSS Change Management Plan Template
- CSU Ohio Pressbooks: Change Control Process
- PL Projects: How to Implement a Change Control Board
- ProjectManager: Change Control Board Roles, Responsibilities & Processes
- RICS: Change control and management
- TSO Change Control Procedure
- The Stoic PM: Change Control
- Plane: What is change control in project management?
- Portfolio Hub: Change Control Process
- Nova Scotia Integrated Change Control Guideline
- ProjectManagement.com: The role of the CCB
- Change Control Board vs. Change Advisory Board
- BVOP: What Is a Change Control Board?
