7.3 Why Activities Are Re-Planned After a Review

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

7.3 Why Activities Are Re-Planned After a Review

Key Takeaways Explain This Topic AI

A review that never changes the plan is a reporting ritual rather than a control; re-planning is how review findings take effect.

Triggers include emerging estimate accuracy, materialised risks, moved dependencies, approved change, resource shifts, benefit forecast changes, and assurance findings.

Re-planning within tolerance is delivery management; re-planning that breaches a baseline requires change control and the correct approval authority.

The approved baseline must stay visible so cumulative variance can be seen rather than reset each reporting period.

Re-plan the whole picture — dates, resources, cost, dependencies, and benefits together — or the revised plan will fail at the next review.

Last updated: August 2026

Outcome 6d is a single line — understand why activities may be re-planned after a review — and it is the outcome that turns reviewing from a reporting ritual into a control. A review that never changes anything is not governance; it is minutes.

Why Activities May Be Re-Planned After a Review

Re-planning after a review is not a sign that the project "failed the meeting." It is often correct control. Activities are re-planned when review evidence shows the current plan is no longer a reliable route to objectives.

Common triggers:

• Review finding Why re-planning follows
• Schedule or cost forecast exceeds tolerance Baselines, resource loading, or sequence must change
• Critical risk materialises or rises Contingent actions, buffers, or alternative approaches are needed
• Scope or priority change approved Work packages, backlog order, and dependencies must be rewritten
• Quality/acceptance shortfalls Rework, extra testing, or design change enters the plan
• Business case weakened Descope, resequence benefits-critical work, or prepare stop options
• Gate conditions imposed Conditional go requires new activities before full next-stage entry
• Dependency failure (supplier, regulator, BAU) Interface dates and critical path change
• Benefits review shows low adoption Transition, training, process, or product fix work is added

Re-planning should update the integrated picture — schedule, resources, cost, risk, quality, and benefits — not only one Gantt bar. After re-plan, communicate the new baseline or iteration plan and reset reporting against it so the next review measures the right thing.

Scenario A — decision gate

A local authority digital project reaches a deployment gate. Progress is 90% of planned build, but user acceptance testing shows high defect density, the cost forecast is +14% against a 10% tolerance, and the benefits case assumed contact-centre savings that operations no longer endorse. The board should not treat "nearly finished" as automatic go. Appropriate actions: require a re-plan focused on defect clearance and a benefits revalidation with operations; approve only a conditional next step; or pause further spend until viability is restored. Communicating that decision to suppliers and the team prevents further work on unstable features.

Scenario B — benefits review

Six months after handover of a warehouse management system, throughput benefits are half the business-case figure because night-shift staff were never trained on the exception process. A benefits review identifies the gap, assigns operational owners, and feeds corrective actions. The project may already be closed, but the organisation still re-plans BAU activities — and may raise a small follow-on change — because reviews protect outcomes, not just project administration.

Scenario C — audit

An internal audit finds that supplier variations above the project manager’s financial authority were approved informally by email. Findings escalate to the sponsor. Delivery continues, but the plan now includes retrospective change control, contract regularisation, and a control check before the next gate. The audit did not replace the project manager; it forced governance back into the plan.

Answer Pattern for Long-Response Questions

When a PMQ scenario mentions a review:

Name the review type (gate, benefits review, audit, or routine management review) and its purpose.

State the information/data decision makers need.

State the decision options (continue, conditional continue, re-plan, stop).

Explain who must be informed and what actions they own.

If the plan is no longer valid, explain why re-planning is required and what integrates into the new plan.

That chain matches LO6: reviews assess status and viability; reporting supports outcomes; data enables decisions; communication makes decisions real; re-planning restores a credible path to success.

Re-planning is a consequence of reviewing, not an admission of failure

State this explicitly in written answers, because the instinctive framing — "we had to re-plan, so something went wrong" — misses the syllabus point. Reviews exist to surface new information. If new information never changed the plan, collecting it would be pointless.

Legitimate re-planning triggers a review can surface:

• Trigger found at review Typical re-planning response
• Estimates proved optimistic as detail emerged Re-estimate remaining work; reforecast dates and cost
• A risk has materialised into an issue Insert response activities; consume contingency; reforecast
• A dependency moved outside the project's control Resequence; add float; escalate the interface
• Scope changed through approved change control Rebaseline affected activities and resources
• Resource availability changed Re-level or re-smooth; renegotiate priority through governance
• Benefits forecast shifted Re-prioritise scope towards the benefit that still holds, or escalate viability
• Assurance found a control gap Add assurance, testing, or documentation activities
• Re-plan properly, or not at all

Poor re-planning is worse than none, because it destroys the ability to measure anything. Three disciplines matter:

Change the plan through the right authority. Re-planning inside tolerance is delivery management; re-planning that breaches a baseline needs change control and, beyond delegated limits, sponsor or board approval.

Keep the old baseline visible. If the plan is silently overwritten every month, nobody can see cumulative slippage — each report looks like a fresh start. Retain the approved baseline and report variance against it.

Re-plan the whole picture. Moving a date without re-checking resources, cost, dependencies, and benefits produces a plan that is internally inconsistent and fails at the next review.

For a five-mark answer: name the trigger the review surfaced, the re-planning action, the authority needed, and the effect on the baseline and the business case.