A Change-Control Process You Can Run This Week
Most projects do not blow their budget on one dramatic decision. They bleed out through a hundred small "can you just" requests that nobody logged. A change-control process is the seam that keeps scope, schedule, and budget honest — but only if it is light enough that the team uses it instead of routing around it. With work spread across remote and hybrid teams, where a quick desk-side "sure, I'll add that" is invisible to everyone else, a written process matters more than it did when everyone shared a floor. Here is a checklist you can stand up this week.
Before you accept a single change
Agree what the baseline is. You cannot control change against a scope, schedule, and budget that were never signed off. Lock the baseline first, in writing.
Define what counts as a change. Clarifying an existing requirement is not a change; adding a new capability is. Write the line down so it is not re-argued every time.
Name one owner. Someone — usually the project manager — owns the log and the decision routing. Diffused responsibility means changes slip in unrecorded.
Decide who approves what. Set a threshold: small changes the PM can approve, larger ones go to a sponsor or change board. Match the ceremony to the stakes.
The five-step loop for each request
Log it. Every request gets a number, a requester, a date, and a one-line description — before any work starts. A request that is not logged cannot be controlled.
Assess the impact. State the effect on scope, schedule, cost, quality, and risk. "Two extra days and one more reviewer" is a real assessment; "shouldn't be a big deal" is not.
Route to the right approver. Send it to whoever your threshold names. Record who decided and when, so the trail survives a staffing change.
Decide and communicate. Approve, reject, or defer — and tell everyone affected, including the people who were counting on the original plan.
Update the baseline. An approved change that never updates the schedule and budget guarantees you will be measured against a plan you already abandoned.
Keep it honest
The process fails in predictable ways. Verbal approvals that never reach the log; an emergency change rushed through without an impact note; a backlog of "deferred" items that quietly becomes a second, unmanaged scope. Review the open log in your weekly check-in, force every change through the same door no matter how small, and treat the baseline as something you revise deliberately, not something that erodes by accident. A change-control process is not bureaucracy for its own sake — it is how you can say yes to the right changes with your eyes open, and no to the rest with a reason on record.
If you want a change process that fits your project rather than fighting it, XNM's program & project delivery advisory can help you set one up and make it stick.