Change Management in Projects: Formal Process vs Informal Agreement

Scope creep kills projects. So does a change process so bureaucratic that genuine, value-adding changes are blocked for weeks. Effective change management sits in the space between — structured enough to protect the project's integrity, flexible enough to accommodate legitimate evolution.

The Options

Informal Change Agreement

Changes are handled through verbal agreement or email confirmation between project manager and sponsor, without a formal change control process. This is fast and pragmatic for small, low-risk changes in trusted relationships. The risk is that the cumulative effect of many small informal changes erodes the baseline, distorts effort tracking and creates disputes about what was actually agreed.

Formal Change Control Process

Every change to scope, schedule or budget is documented through a defined process: a change request is raised, assessed for impact, approved or rejected through an appropriate authority, and the baseline is updated. Formal change control is mandatory in most public sector, defence and large commercial contracts. It provides an audit trail, protects contractual positions and makes the cost of change visible to decision-makers.

Tiered Change Control

A pragmatic middle ground: simple, low-impact changes are handled with a lightweight process (a one-page change note, approval by the PM); significant changes require full impact assessment and sponsor or board approval; changes beyond a defined threshold trigger a formal replan. This approach matches the overhead of the process to the significance of the change.

Why It Matters in Practice

Change is inevitable in projects. The question is whether it is managed or absorbed informally. Organisations that have implemented tiered change control typically find that it does not slow down genuine necessary changes, but it does make the cost of change visible — which naturally reduces the volume of discretionary scope additions that accumulate in poorly controlled projects.

For contract delivery, change management is also a commercial protection mechanism. Uncontrolled change without contract variation can result in contractors absorbing costs they are not obligated to carry.

In the Simulation

In SPPIN Sim, your change management approach affects your scope stability score and your cost performance index. Informal agreement keeps your process overhead low but exposes you to significant score penalties when scope change events compound without a documented baseline to reference. Formal change control adds overhead but protects your cost and schedule performance metrics across the run.