Mastering Change Requests
Unmanaged scope creep is the death knell of project baselines. Discover how a structured change request framework controls scope, safeguards budgets, and keeps stakeholders aligned.
- The Anatomy of a Change Request
- A Real-World Scenario Analysed
- The Lifecycle of Change
- Quick Reference
§1 The Anatomy of a Change Request
A robust Change Request (CR) is more than a permission slip; it is a comprehensive impact analysis designed to protect the integrity of the project baseline.
Whether a project is traditional, agile, or hybrid, change is inevitable. A formalised process ensures that changes are evaluated against the triple constraint: scope, cost, and schedule. The standard KEVOS® Change Request template is structured into four critical domains to facilitate objective decision-making by the Change Control Board (CCB) or project sponsor.
| Domain | Key Elements | Purpose |
|---|---|---|
| Categorisation | Scope, Quality, Requirements, Cost, Schedule, Documents | Immediately flags which foundational baselines the proposed change will disrupt. |
| Justification | Detailed description and business rationale | Ensures the change aligns with the strategic objectives of the project, filtering out arbitrary additions. |
| Impact Analysis | Quantified changes to Cost, Schedule, and Quality | Forces the requestor and PM to calculate exact financial and temporal impacts before seeking approval. |
| Disposition | Approve, Defer, Reject, and Authorising Signatures | Provides a clear, auditable trail of governance and final authorisation. |
§2 A Real-World Scenario Analysed
To understand the mechanics of a CR, we examine a completed request (CR-007) for the "Mary's Consulting - New Company Website" project.
Mid-flight through the website build, the CEO and project sponsor (Mary) requested the addition of a comprehensive "Press / Media" section to capitalise on recent Fortune 500 client wins. While strategically sound, adding roughly 15 content items and two new page templates introduces immediate scope creep.
Impact Quantification (CR-007)
The project manager (Andrew) did not simply estimate "a few extra days." Instead, the impact was rigorously quantified in the CR document:
- Cost Increase: $3,800 in total. This was calculated exactly: Bob (Tech Lead) at 24 hours × $72/hr ($1,728) plus Christine (Content) at 30 hours × $50/hr ($1,500), alongside a $572 contingency buffer.
- Funding Source: Drawn directly from the existing $15,000 project contingency reserve, reducing it to $11,200.
- Schedule Impact: An addition of 8 working days. Work package 1.4.3 was extended by 5 days, and A014 by 3 days.
The Outcome: Because the CR clearly demonstrated that the schedule expansion merely reduced total schedule slack (from 7 days down to 2 days) without jeopardising the critical path or the 24 November 2026 go-live date, the sponsor could confidently approve it. The Risk Register was subsequently updated to reflect the diminished schedule float.
↑ Contents§3 The Lifecycle of Change
A template is only as effective as the process governing it. A disciplined change control lifecycle ensures nothing is implemented until it is fully understood and authorised.
- Initiate: The requestor submits the CR outlining the description and core business justification.
- Assess: The Project Manager and technical leads analyse the ripple effects across the Work Breakdown Structure (WBS), cost baseline, and schedule slack.
- Review: The CCB or Sponsor reviews the quantified impact against project objectives to render a disposition (Approve, Defer, Reject).
- Execute: If approved, project documents—including the Requirements Traceability Matrix (RTM) and Risk Register—are updated, and the new baseline is communicated to the team.
§4 Quick Reference
Quantify Relentlessly
Never accept ambiguous impacts like "a minor delay." Calculate the exact hours, resource costs, and contingency drawdowns required to execute the change.
Monitor Schedule Slack
Assess how a change affects the critical path. A change that consumes float may not push the final delivery date, but it inherently increases overall project risk.
Update Baselines
An approved CR is only half the job. Immediately update the WBS, schedule, cost baseline, and requirements documentation to reflect the new reality.
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Mastering Project Change Requests. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to convert the subject into a governed decision, owned work, usable evidence and a reviewable outcome. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Use Mastering Project Change Requests as a decision instrument rather than an administrative form. The subject terms—change, requests, real-world, scope, creep—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.
Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.
A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.
Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.
Step-by-step operating method
- Clarify the decision. Name the outcome, sponsor, affected stakeholders and decision that this work must enable.
- Set boundaries. Record scope, assumptions, constraints, dependencies, tolerances and escalation conditions.
- Plan the evidence. Define deliverables, measures, owners, due dates and acceptance criteria before execution.
- Control delivery. Compare actual performance with the baseline, assess changes and manage risks and issues explicitly.
- Close the loop. Confirm acceptance, transfer ownership, capture lessons and track benefits beyond handover.
Completion and governance protocol
Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.
| Information type | Minimum useful content | Review test |
|---|---|---|
| Outcome | Observable change and intended recipient | Not merely a deliverable or activity |
| Measure | Definition, baseline, target, frequency and source | Two reviewers would calculate it the same way |
| Ownership | One accountable role plus contributors and approver | Authority matches responsibility |
| Uncertainty | Assumption, risk or issue with response and trigger | Status reflects current reality |
| Control | Version, approval, review date and change rule | Current baseline is identifiable |
Common failure modes and recovery actions
1. Watch for
Producing a document with no named decision or accountable owner.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Mixing risks, current issues, assumptions and actions in one unstructured list.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Measuring activity or output while leaving the intended outcome undefined.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Accepting changes without evaluating effects on value, scope, schedule, cost and risk.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Closing the project at delivery even though benefit ownership has not transferred.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- Which decision or commitment does this artefact support?
- Who owns each action, risk, acceptance and post-project benefit?
- What is the baseline and what variance triggers escalation?
- Where is the evidence that the result was accepted and transferred?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying Mastering Project Change Requests?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about change would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- PMI Standards and Publications — Project Management Institute. Used for project, program, portfolio and organisational project management. Accessed 2026-08-13.
- ISO 31000 family — Risk management — International Organization for Standardization. Used for principles and guidance for enterprise risk management. Accessed 2026-08-13.