Study guide
7.1 Reviews, Decision Gates, Benefits Reviews and Audits
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.1 Reviews, Decision Gates, Benefits Reviews and Audits
Key Takeaways Explain This Topic AI
Reviews gather information to assess the status of a project and the ongoing viability of the work.
Decision gates authorise continuation, change, or stopping before further major commitment; they are decision events, not status meetings.
Benefits reviews test whether expected outcomes are appearing and remain achievable, and often continue after project closure.
Audits provide independent examination of compliance with process, policy, and contractual or regulatory requirements.
Reviews throughout the life cycle catch problems while correction is still affordable; a single end-of-project review only records what happened.
Last updated: August 2026
What Reviews Mean on the APM PMQ
In the APM Project Management Qualification , reviews are ways of gathering information to assess the status of a project and the ongoing viability of the work . A review is not a status chat for its own sake. It is a controlled pause that asks: Where are we? Are we still justified? What should we decide next?
Reviews sit close to governance. Sponsors, boards/steering groups, and project managers use review evidence to release funding, approve the next stage or increment, change scope, re-plan, escalate risk, or stop the project. Weak answers on the PMQ list meeting names. Strong answers link review type → information needed → decision → communication → re-plan if required .
Exam frame: Review = assessment of status and viability. Status alone ("tasks are late") is incomplete if nobody re-tests whether the investment is still worthwhile.
Benefits of Reviews Throughout the Life Cycle
Reviews create value at every stage, not only at the end. Used well, they:
Protect progressive commitment — major money, contracts, and operational disruption are released only when evidence supports the next step.
Re-test the business case — costs, benefits, risks, and strategic fit can change; reviews force an honest update.
Surface problems early — schedule slip, quality shortfalls, stakeholder resistance, and dependency failure are cheaper to fix when found early.
Improve decision quality — boards decide on facts, options, and forecasts rather than optimism or silence.
Create an audit trail — decisions, assumptions, and actions are recorded for accountability and later lessons.
Align stakeholders — users, suppliers, sponsors, and delivery teams hear the same status and the same agreed actions.
Enable controlled stop/go — stopping a weak project is a successful governance outcome if it prevents waste.
In a linear life cycle, formal phase-end or stage-gate reviews dominate. In an iterative life cycle, frequent increment or sprint reviews still assess progress and viability, even if the ceremony is lighter and more frequent. Hybrid work uses both: gates for capital/compliance packages and frequent product reviews for evolving components.
Types of Review: Decision Gates, Benefits Reviews, and Audits
The syllabus expects you to understand reviews including decision gates, benefits reviews, and audits . These are not interchangeable labels.
Review type Primary question Typical timing Who is central Typical decision
Decision gate (stage gate) Are we ready and justified to commit to the next phase/stage of work? Phase boundaries in linear work; major investment points in hybrid Sponsor and project board/steering group, with PM evidence pack Go, no-go, conditional go, re-scope, re-plan, or stop
Benefits review Are planned benefits being realised (or still likely), and is value still on track? After transition into BAU; also checkpoints in the extended life cycle Sponsor / benefits owner, with operational owners and PM/programme input Sustain benefits actions, adjust operations, re-baseline benefits, or change/stop related work
Audit Is the project complying with required processes, standards, controls, and governance? Planned or triggered points; often independent of the delivery team Internal/external auditors or independent reviewers Findings, non-conformances, corrective actions, and escalation if controls fail
Decision gates
Decision gates (also called stage gates) are formal control points, especially in linear life cycles. The project manager prepares evidence: progress against objectives, updated forecasts, risk and issue position, quality and readiness, and an updated view of the business case. The sponsor and board decide whether further investment is justified.
Benefits of decision gates include senior involvement at the right moments, progressive funding, forced reconfirmation of viability, and a clear place to stop or redirect before the next expensive phase. A gate is a decision event, not a progress celebration. If the case is weak, "no-go" is a valid outcome.
Benefits reviews
Benefits reviews focus on whether the change is delivering (or still expected to deliver) the intended business value , not only whether products were built. Many benefits appear only after outputs are adopted in business-as-usual, so benefits reviews often sit in the extended life cycle after handover. The sponsor or benefits owner remains accountable; operational managers usually own day-to-day realisation actions.
A project can hit time, cost, and specification targets and still fail a benefits review if users do not adopt the change, volumes are lower than assumed, or operating costs erase the case. That distinction is highly examinable.
Audits
Audits provide a structured, often independent check that required processes and controls are being followed — for example change control, financial authority, safety, information security, procurement, or configuration management. Audits may be internal (organisational audit function) or external (regulator, funder, certification body).
Distinguish carefully:
Aspect Management review (e.g. gate or progress review) Independent audit
Purpose Assess status/viability and decide next action Test compliance, control effectiveness, and evidence quality
Ownership Project governance (sponsor, board, PM) Audit/assurance function with defined mandate
Independence Delivery leadership is usually central Deliberately independent of those who manage day-to-day work
Output Go/no-go, re-plan, escalate, approve change Findings, non-conformances, recommendations, residual risk
Focus Outcomes, forecasts, and investment decisions Whether required processes and standards are actually operating
A gate can use audit findings as evidence, but a gate is not automatically an audit. Conflating the two is a common PMQ trap.