Change Control Board: Membership, Remit and Cadence
A change control board is the standing group that decides change requests against a baseline. It typically includes delivery, business, technical and commercial representation, meets on a short cadence, and works from assessed requests. Its remit is bounded: it decides changes within the project's envelope and refers anything beyond that to the steering committee.
Who sits on it and what they bring
| Seat | What they assess |
|---|---|
| Chair | Usually the project or programme manager. Runs the queue, holds the threshold |
| Business representative | Whether the change is needed, and what it is worth to the receiving function |
| Technical lead or architect | Feasibility, effect on design integrity, technical debt being accepted |
| Test lead | Retest scope and whether the change fits the remaining test window |
| Commercial or finance | Cost, contract implications, whether the vendor change is chargeable |
| Operations or service owner | Run-cost and supportability once the change is live |
How it is used
The board exists because change decisions are frequent and a monthly steering committee is too slow for them. A typical cadence is weekly, or twice weekly during a build phase. Requests arrive already assessed; the board decides rather than analyses, and a request without an impact assessment is deferred rather than debated.
Its authority is bounded by threshold. Below the line it decides; above it — a committed date moving, the budget envelope breached, contracted scope altered — it recommends and the steering committee decides. Where that line sits is a governance design choice, covered in programme governance, and where the board recommends rather than decides, the item lands in the pack described in the steering committee report guide.
The board's output is a decision on each request with a date, an approver and any conditions. Kept on the request itself, as in the change request log, the record stays with the impact assessment that justified it. Where decisions need presenting alongside the dependencies they unblock, the decision log and dependency matrix covers the same ground for a governance audience.
In a release or cutover context the same body often takes a second role: approving what enters the release, and enforcing the change freeze in the window before go-live. Where that applies, the freeze scope and the emergency exception path both need writing down before the window opens.
Where it goes wrong
- Meeting as workshop. Requests arrive unassessed and the board spends an hour estimating. The queue grows and delivery waits.
- No threshold. Trivial changes consume the agenda while a material one is approved in the last four minutes.
- Quorum by seniority. Where every seat needs a senior attendee, the board cancels for diary reasons and becomes a bottleneck.
- Approving without run-cost. No operations seat means changes that are cheap to build and expensive to support get approved routinely.
- Emergency path becomes the normal path. An expedited route with no post-hoc review turns into the default under schedule pressure.
- No record of what was rejected. Where only approvals are logged, the same request returns from a different requester and is assessed from scratch.
- Decisions not fed back to the plan. Approved changes that never reach the schedule and the budget forecast produce a plan nobody believes.
Related terms
Change request — the item the board decides. Steering committee — where changes above threshold go. Change freeze — the period before go-live in which the board's remit narrows sharply. Baseline — the approved position each request is measured against. Go/no-go — the decision the freeze protects.
Questions
Is a change control board the same as a steering committee?
No. The change control board decides scope changes within a threshold and meets frequently. The steering committee holds investment authority, meets on a longer cycle, and decides changes above the threshold.
How often should a change control board meet?
Weekly is common, moving to twice weekly during build and test where request volume is high. The cadence should be short enough that waiting for the board does not stall delivery.
Does a small project need a change control board?
Usually not. On a small project the project manager and sponsor can decide changes directly. A standing board earns its place when request volume or the number of functions affected makes ad hoc decisions unreliable.
What is an emergency change?
A change that cannot wait for the next board, normally to resolve a live incident. It is approved by a named authority and reviewed retrospectively at the next session, so the route stays exceptional.