Capability
Integrated Change Control
Route scope, time, and money changes through one control record so the baseline is only updated when change is approved.
C02 — The problem
The technical problem
Projects lose control when instructed work is absorbed into the programme without a decision, or when the cost file is updated while the schedule is not — or the reverse.
Integrated Change Control is the project-controls capability: one register of proposed, instructed, and approved change, with time and money consequences visible before the baseline is rewritten. It is not the same assignment as contractual variation administration, which sits under Contract Management.
C03 — Engagement
When this capability is needed
-
01
Baseline about to be locked
The change path is not defined.
-
02
Scope drift
Field instructions are changing the works without a control-account trail.
-
03
Split records
Cost has a change log and the programme does not, or vice versa.
-
04
Steering / owner review
Leadership needs to see what is approved versus what is still variance.
C04 — Scope / method
How the work is approached
Design and run the control path for change: identification, impact on time and cost, approval status, and baseline update. Commercial notices and variation instruments remain Contract Management. Claims packages remain Claims & Disputes.
-
01
Define change classes
Scope, sequence, quantities, and interfaces that must enter the register.
-
02
Log proposed and instructed change
Status, origin, and affected control accounts.
-
03
Assess time and cost impact
Enough to decide, not a full claim narrative.
-
04
Hold the baseline
Approved change updates it; unapproved change remains variance.
-
05
Report the change position
What moved, what is pending, what the forecast still excludes.
C05 — Outputs
Typical deliverables
| Output | What it contains |
|---|---|
| Change control procedure | How change enters, is assessed, and updates the baseline. |
| Integrated change register | Status, time, and cost against control accounts. |
| Impact summaries | Decision-ready notes for pending items. |
| Baseline update record | What was incorporated, when, and on whose approval. |
C06 — Decision value
What this work is used to decide
Whether to approve, reject, or defer a change, and whether the current baseline still represents the authorised works. It does not determine contractual entitlement.
C08 — Project environments
Relevant project environments
C09 — Who we support
Who commonly needs this capability
C10 — Boundaries
Important distinctions
This is control of the project baseline. It is not legal advice, variation certification, or a substitute for the contract administrator’s notices.
C11 — Next step
Discuss your project
If this is the technical problem you are facing, talk to Value Construction about the work, the records required, and what you would receive. Outcomes are not guaranteed.