Study guide
5.2 The Business Case as Baseline and Reviewing Change
APM Project Management Qualification PMQ
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Exam Format & Question Types 1.3 How to Study for APM PMQ
2 Life Cycles
2.1 Linear Life Cycles and Why Work Is Phased 2.2 Iterative and Hybrid Life Cycles 2.3 Project Life Cycles and Extended Life Cycles 2.4 Choosing a Life Cycle: Context, Culture, Strengths and Limitations
3 Governance Arrangements
3.1 Functional, Matrix and Projectised Structures 3.2 Governance Frameworks, Policies and Delegated Responsibility 3.3 Life-Cycle Impact on Governance and Limits of Financial Authority 3.4 Project Roles and Responsibilities 3.5 Project Manager and Project Sponsor Through the Life Cycle 3.6 Linking Projects to Organisational Objectives
4 Sustainability
4.1 Sustainability Responsibilities, Principles and Impact 4.2 Monitoring and Reporting Sustainability Measures
5 Business Case
5.1 Business Case Fundamentals and Analysis Tools 5.2 The Business Case as Baseline and Reviewing Change
6 Procurement
6.1 Procurement Strategy: Purpose and Contents 6.2 Supplier Selection and Negotiation 6.3 Features of Different Contractual Relationships 6.4 Supplier Reimbursement Methods
7 Reviews & Assurance
7.1 Reviews, Decision Gates, Benefits Reviews and Audits 7.2 What Gets Reported and Informing Decisions 7.3 Why Activities Are Re-Planned After a Review 7.4 Project Assurance
8 Transition & Benefits Management
8.1 Transition Requirements and Business-as-Usual Readiness 8.2 Knowledge Transfer and Agreeing the Transition Plan 8.3 Benefits Management: Identification to Realisation 8.4 Aligning and Communicating Benefits
9 Stakeholder Engagement & Communication
9.1 Stakeholder Analysis, Influence and Engagement 9.2 The Communication Management Plan and Its Benefits 9.3 Managing Stakeholder Expectations 9.4 Communication Methods and Tailoring the Message 9.5 Factors That Help and Hinder Communication
10 Conflict Resolution
10.1 Sources and Impacts of Conflict 10.2 Addressing Conflict and the Thomas-Kilmann Model
11 Leadership
11.1 Leadership, Motivation and Team Performance 11.2 Changing Leadership Styles for the Situation 11.3 Coaching, Mentoring and Emotional Intelligence
12 Team Management
12.1 Team Development Stages and Models 12.2 Characteristics and Benefits of Effective Teams 12.3 Leading Virtual and Hybrid Teams
13 Diversity & Inclusion
13.1 Diversity Characteristics and the Equality Act 13.2 Incorporating Diversity and Diverse Thinking 13.3 Conscious and Unconscious Bias and Fair Treatment
14 Ethics, Compliance & Professionalism
14.1 Continuing Professional Development and Competence 14.2 Sources of Specialist Advice and Standards 14.3 The Legal and Regulatory Landscape
15 Requirements & Solutions
15.1 Establishing Scope Through Requirements Management 15.2 Managing Scope Through Configuration Management 15.3 Solutions Development and Prioritisation
16 Quality Management
16.1 Quality Planning, Indicators and the Business Case 16.2 Quality Control and Success Criteria
17 Integrated Planning
17.1 The Integrated Project Management Plan: Format and Contents 17.2 Why an Integrated Plan Matters
18 Schedule Management
18.1 Defining Scope and Breakdown Structures 18.2 Dependencies and What Drives the Schedule 18.3 Re-Estimating and Schedule Optimisation
19 Resource Management
19.1 Determining Resource Requirements and Availability 19.2 Organisational Breakdown Structure and RACI 19.3 Categorising and Allocating Resources 19.4 Resource Smoothing and Resource Levelling
20 Budgeting & Cost Control
20.1 Creating a Budget and Cost Types 20.2 Earned Value and Cost Forecasting 20.3 Monitoring and Reporting Financial Performance 20.4 Closing Down Project Finances
21 Risk & Issue Management
21.1 Benefits of Risk and Issue Management and Contingency Planning 21.2 The Risk and Issue Management Processes 21.3 Proactive and Reactive Risk Responses 21.4 Governance in Risk and Issue Management
22 Change Control
22.1 The Change Control Process and Its Stages 22.2 What a Change Request Must Capture 22.3 Assessing Options and the Impact of a Change 22.4 Recommending Decisions and Updating Plans
5.2 The Business Case as Baseline and Reviewing Change
Key Takeaways Explain This Topic AI
The approved business case forms a baseline for the project: a reference for viability, benefits expectations, and investment decisions.
The business case baseline tracks investment worth; the scope, schedule, and cost baselines in the project management plan track delivery.
Material changes in cost, benefits, risk, strategy, or external environment require review of the business case so governance can continue, change, or stop the project.
Reviewing well means re-forecasting benefits, costs, risks, assumptions, and strategic fit together rather than one metric in isolation.
Stopping a project whose case no longer holds is value-protecting governance, not a failure.
Last updated: August 2026
Outcome 4b joins two ideas that the syllabus deliberately places together: understand the importance of regularly reviewing the impact of any changes in a project to the business case , and know that the business case forms the baseline for the project . The pairing is the point. A baseline that is never re-tested is just an old document; a review with nothing to compare against is just an opinion.
The Business Case as Baseline
The syllabus states that the business case forms the baseline for the project . In control language, a baseline is an approved reference against which performance and continued viability are judged.
What that means in practice:
Approved version control — once authorised, the case (or the version at a gate) is the reference for expected benefits, investment envelope, key assumptions, and risk appetite relevant to justification.
Alignment of plans — scope, schedule, cost, and benefits plans should be consistent with the approved case; material drift must be explained.
Change impact lens — proposed changes are assessed not only for delivery impact but for impact on the justification (benefits, costs, risks, strategic fit).
Decision anchor — continue/stop/change decisions refer back to whether the baseline case still holds or needs formal revision.
The business case baseline is related to, but not identical with, the performance measurement baselines for scope, schedule, and cost in the project management plan. Those track delivery; the business case baseline tracks investment worth . Both require controlled change when materially amended.
Regularly Reviewing the Impact of Changes
Learning outcome (b) requires understanding the importance of regularly reviewing the impact of changes on the business case. Context never stays frozen: costs inflate, strategy shifts, regulations change, benefits forecasts move, and delivery risk materialises.
When to review
Trigger Example Governance question
Stage / decision gates End of definition before major spend Is the preferred option still justified?
Material cost forecast change +15% capital Do benefits still outweigh costs and risks?
Benefits forecast change Adoption rates below plan Is the minimum viable benefit still achievable?
Strategic change New corporate priority or merger Does the project still fit objectives?
External shock (PESTLE/VUCA) New regulation, market collapse Are assumptions still valid?
Major scope change request Significant new feature Does added cost buy enough benefit?
Risk materialisation Critical supplier failure Is residual case still acceptable?
Scheduled periodic review Quarterly investment review Any slow drift that needs correction?
How to review well
Re-forecast the whole picture — update benefits, costs, risks, assumptions, and strategic fit together, not one metric in isolation.
Compare against the baseline case — state variance and drivers clearly.
Generate options — continue as planned, re-scope, re-sequence, add funding, pause, or stop.
Recommend with evidence to the sponsor/board within the scheme of delegation.
If approved, re-baseline the business case so future reporting remains meaningful.
Continue, change, or stop
Decision When it is appropriate Notes
Continue Benefits, costs, and risks still justify investment within appetite Confirm tolerances and any minor updates
Change Case salvageable with re-scope, extra funding, or different option Use change control; update baseline case
Stop Case no longer viable or strategically aligned Stopping can be value-protecting, not failure of governance
Critical exam scenario: a project is still within cost tolerance but forecast benefits have fallen below the minimum threshold in the business case. Correct action is to escalate for a viability decision — not to continue silently because the budget is "green." Benefits are central to justification.
Counter-scenario: costs rise by 15%, but a new strategic objective means benefits may be higher than originally estimated. The business case should be updated and reviewed with the revised whole picture; neither ignore the cost rise nor treat higher potential benefits as automatic approval without governance.
Roles in ongoing review
Role Contribution to business-case review
Project manager Maintains forecasts; assesses change impacts; prepares options and recommendations; reports honestly
Sponsor Owns continued justification; chairs or drives continue/change/stop decisions; escalates to corporate level if needed
- Steering group / board Approves major revisions, further investment, or termination within remit
- Users / benefit owners Validate whether outcomes and benefits remain realistic
- Assurance / finance Challenge estimates, affordability, and evidence quality
- Worked Scenario: Keeping the Case Alive
A regional hospital approves a business case for a patient portal. Baseline case: £2.1m cost, benefits in reduced call-centre load and improved access, go-live in 14 months, key assumption that 40% of patients will register in year one.
Mid-delivery, three changes hit:
Economic (PESTLE): specialist developer rates rise; cost forecast +12%.
Social: patient trust survey shows lower willingness to share data online than assumed.
Technological / VUCA: a national digital standard is announced that may force redesign (uncertainty and complexity).
Weak response: keep building to the original scope and hope benefits appear.
Strong PMQ response:
Update cost forecast and benefits forecast (registration rate sensitivity).
Refresh risk and assumptions (standards dependency).
Use SWOT: strength = clinical sponsorship; weakness = scarce UX capacity; opportunity = national funding for standards compliance; threat = delayed interoperability.
Present options to the board: (A) continue with extra funding and stronger adoption campaign; (B) re-scope to a thinner MVP aligned to the emerging standard; (C) pause until the standard is confirmed.
Board decides Option B, re-baselines the business case, and adjusts benefits and cost envelopes.
The business case remains the baseline for justification ; delivery baselines for scope and schedule are updated through change control to stay consistent with that revised case.
Common Exam Traps
Business case is only for start-up. It justifies initiation and continuation; review through the life cycle.
PM owns the business case. The PM maintains evidence; the sponsor owns justification.
PESTLE/SWOT/VUCA replace the case. They inform it; they are not the investment decision itself.
Baseline means never change. Baseline means controlled reference; material change triggers formal review and re-approval.
Green budget = automatic continue. Benefits and strategic fit can fail while cost remains inside tolerance.
Stopping is always failure. Stopping a non-viable project protects organisational value.
Answer Pattern for Long-Response Questions
State the purpose of the business case (justify initiation/investment/continuation via benefits, costs, risks).
Apply the relevant tool (PESTLE, SWOT, or VUCA) to the scenario facts.
Explain baseline role and what has changed against it.
Recommend continue / change / stop with who decides (sponsor/board) and what must be re-baselined.
That chain matches LO4 (a) and (b) and mirrors how APM PMQ awards marks for applied justification and control, not template memorisation alone.