7.1 Reviews, Decision Gates, Benefits Reviews and Audits
Key Takeaways
- 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.
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.
At a decision gate, the build is almost complete but the cost forecast exceeds tolerance and expected benefits have fallen. What is the most appropriate governance focus of the review?
Which statement best distinguishes a benefits review from an independent project audit?
What most clearly distinguishes a decision gate from a routine progress meeting?