IS5540 Chap.3 Governance, Charters and Change Control
Governance, Charters and Change Control
Make authority visible
This chapter links the project charter to the detailed management plan and then traces a change from request through logging, impact analysis, decision, implementation and re-baselining. Governance is treated as an evidence path rather than a list of committees.
The critical distinction is between permission to request, responsibility for analysis and authority to accept consequences.
Use the charter as an authority boundary
The charter states why the project exists, the high-level result, major constraints and assumptions, the sponsor and the authority granted to the project manager. It does not replace the detailed management plan.
Its value is that later analysis can be compared with an authorised purpose rather than an informal preference.
A charter should make escalation possible: if a request exceeds the project's objective, funding or delegated authority, the project manager can identify the mismatch and route it to the sponsor instead of silently absorbing it.
Turn governance roles into decisions
A governance chart becomes useful when each role is connected to a decision, input and retained record.
A sponsor may approve the charter or resolve a strategic exception. A project manager may coordinate analysis and operate within delegated tolerances. A change control body may decide changes crossing a defined threshold. Functional managers may commit scarce people. Customers or acceptance owners judge specified results. Avoid assigning several roles the same verb without a boundary.
If everyone approves, a reader cannot tell whose decision changes the baseline.
Preserve the complete change path
A request should be recorded before implementation, described clearly and analysed for impact on scope, schedule, cost, quality, resources, risk, stakeholders and intended value. The decision may be approval, rejection or deferral.
Every outcome deserves a record because rejected requests explain why the current baseline remains valid, while deferred requests protect a possible benefit without pretending the present project can absorb it.
Approved change then requires communication, implementation, verification and controlled updates to affected baselines and plans.
Separate analysis from advocacy
An influential requester can have a legitimate strategic reason and still lack authority to bypass control. The analysis should state that reason fairly, then compare approval, rejection and deferral.
Include the do-nothing consequence, implementation cost, timing, new risks and effects on existing commitments. This makes the paper decision-ready rather than a one-sided justification. The project manager protects the request by making its value visible and protects the project by exposing its consequences.
Check configuration consistency
Once a change is approved, related artefacts must tell the same story.
A new deliverable can affect the scope statement, WBS, dictionary, schedule, budget, quality criteria, risks, communication and acceptance plan. Updating only a task board creates a hidden baseline. Close the loop by naming the changed documents, their version or approval state and the person who verifies implementation.
Re-baselining is not erasing history; the former reference and the authorised reason for change remain part of the audit trail.
What this chapter covers
- 01
Governance and strategic alignment
- 02
Charter authority
- 03
Sponsor and manager roles
- 04
Change request logging
- 05
Impact analysis
- 06
Change control decisions
- 07
Re-baselining and communication
Worked example · free
Repair a sponsor request
- 2Record the request.
- 3Analyse linked impacts.
- 3Route, decide and update.
Key terms
- Project Charter
- The document that authorises a project and states its high-level purpose, roles and boundaries.
- Governance
- The arrangement through which project direction, control and strategic alignment are exercised.
- Change Request
- A recorded proposal to alter an approved project reference.
- Impact Analysis
- Assessment of how a proposed change affects scope, schedule, cost, resources and risk.
- Change Control Board
- The named body that approves or rejects analysed change requests within its authority.
- Re-baselining
- Updating an approved reference after an authorised change decision.
Governance, Charters and Change Control FAQ
Can a sponsor bypass change control?
A sponsor may hold significant authority, but the request still needs a record and impact analysis so the consequence is visible. The applicable governance design determines who makes the decision and which baselines require authorised updates.
Why keep rejected requests in the register?
A rejected request preserves the issue, evidence and reason for the decision. This prevents repeated analysis, shows that the baseline was actively defended and allows later reviewers to understand the history rather than seeing only accepted changes.
What is the charter's role after initiation?
The charter remains the anchor for purpose, high-level boundaries and authority. Change analysis should explain whether a request supports the authorised reason for the project and what delivery consequences must be accepted to pursue it.
Exam move
Draw one change path with five boxes: request, log, analyse, decide and implement. Add the actor and retained evidence at each box, then test whether a rejected request and an approved request both leave a complete history.
Working through Governance, Charters and Change Control in IS5540? Sia is AskSia’s AI Project Management tutor — ask any IS5540 Governance, Charters and Change Control question and get a clear, step-by-step explanation grounded in how IS5540 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.