11.3 Project Reviews, Decision Gates, and Audits
Key Takeaways
- Project reviews provide structured governance checkpoints to evaluate progress, confirm strategic alignment, maintain business case viability, and capture organizational learning.
- Decision Gates (Stage Gates) occur at phase boundaries where the Sponsor and Governance Board evaluate deliverable completion and business case viability to authorize proceeding, reworking, or terminating.
- Post-Project Reviews (PPR) take place at project closeout to assess project management success (time, cost, scope, quality), evaluate team performance, and compile the final lessons learned.
- Benefits Reviews are conducted during operational use—often months or years post-handover—to measure actual realized business benefits against the original Business Case projections.
- Project Audits are objective, independent evaluations conducted by internal or external auditors to verify compliance with organizational policies, statutory regulations, contract terms, and quality standards.
11.3 Project Reviews, Decision Gates, and Audits
Definition (APM BoK7 glossary): A decision gate is a point in the life cycle between phases that is used to review and confirm viability of the work in line with the business case. Alternatively called stage gates or gates.
Assessment criterion 8.6 asks you to state the purpose of four things: decision gates, post-project reviews, benefit reviews and project audits. BoK7 (2.2.2) states that reviews in advance of decision gates ask four questions: what has been achieved? what is required for the next stage? what are the key decisions to be made? is the business case still viable, i.e. can the desired benefits be achieved for an acceptable level of cost and risk? It adds that in a linear life cycle decision gates are event-driven, at the end of a phase of work, whereas in an iterative life cycle they are time-bound — and that in all cases "the sponsor and the wider governance board is accountable for the decision to continue the work".
A project review, more broadly, is a formal, structured evaluation of a project’s progress, performance, alignment and viability at key points throughout its life cycle.
No project can succeed if managed as an unmonitored trajectory from initial chartering to final closeout. Robust project governance demands systematic checkpoints where decision-makers assess progress, evaluate health, confirm strategic alignment, maintain business case justification, and capture valuable organizational knowledge.
Within the APM Body of Knowledge 7th Edition (BoK7) and the APM Project Fundamentals Qualification syllabus (Learning Outcome 8, Assessment Criterion 8.6), candidates are expected to understand the distinct purpose, timing, leadership, and outputs of four formal project review types:
- Decision Gates (Stage Gates / Phase Gates)
- Post-Project Reviews (PPR / Closeout Reviews)
- Benefits Reviews (Benefits Realization Reviews)
- Project Audits
1. Decision Gates (Stage Gates / Phase Gates)
Core Purpose: To evaluate whether a project has satisfied the exit criteria of its current phase and whether the Business Case remains viable to justify authorizing commitment to the next phase.
In a linear or hybrid project life cycle, work is partitioned into discrete sequential phases (e.g., Concept, Definition, Deployment, and Transition). A Decision Gate—often termed a Stage Gate, Phase Gate, or Tollgate—is a formal governance checkpoint situated directly at the boundary between two lifecycle phases.
+-----------------------------------------------------------------------------------------+
| DECISION GATES ACROSS THE LIFE CYCLE |
+-----------------------------------------------------------------------------------------+
| [CONCEPT] ===> [GATE 1] ===> [DEFINITION] ===> [GATE 2] ===> [DEPLOYMENT] |
| (Idea & (Approve (Detailed PMP (Approve (Execution |
| Viability) Business Case) & Design) Delivery Plan) & Build) |
+-----------------------------------------------------------------------------------------+
Who Leads and Participates?
- Led By: The Project Sponsor (or the Project Steering Committee / Governance Board). The Sponsor chairs the review because they are the ultimate owner of the Business Case and the capital investment.
- Key Participants: The Project Manager (who presents actual progress, deliverable completion evidence, and the forward plan for the subsequent phase), the PMO lead, key technical specialists, and senior functional representatives.
Gate Evaluation Criteria
At a Decision Gate, the governance board examines three critical dimensions:
- Phase Deliverable Completion: Have all mandatory deliverables and acceptance criteria for the concluding phase been verified and signed off?
- Baseline Performance & Risk: Is the project tracking acceptably against approved time, cost, and scope baselines, and are emerging risks manageable?
- Continued Business Case Viability: Does the underlying commercial justification still stand? Have market shifts, technological advancements, or regulatory changes invalidated the investment?
The Four Possible Gate Decisions
A Decision Gate is not a ceremonial rubber-stamping meeting; it is a critical decision-making event that must result in one of four formal determinations:
- Go: Unconditional approval to commit resources, authorize expenditure, and commence work on the subsequent phase.
- Go with Conditions: BoK7 notes that "all gates are intended to be go–no-go decision points, although in some cases a provisional or conditional ‘go’ will be given based on a set of conditions that need to be fulfilled within a set time frame."
- Hold / Rework: Authorization is temporarily paused. The project team is directed to re-evaluate options, revise designs, or redo incomplete deliverables before reconvening for a repeat gate review.
- Terminate (Stop): The project is formally halted and closed prematurely.
[!IMPORTANT] Within the APM framework, terminating an unviable project at a decision gate is viewed as an exemplary demonstration of mature project governance, not as a failure. Cancelling a project whose business case has collapsed prevents organizations from throwing good money after bad.
2. Post-Project Reviews (PPR / Closeout Reviews)
Core Purpose: To evaluate project management success, capture lessons learned, evaluate team and supplier performance, and formally document project closure.
A Post-Project Review (PPR)—also known as an End-of-Project Review or Project Closeout Review—takes place at the very end of the project life cycle, inside the Transition phase and immediately following the handover and acceptance of project deliverables by operational end users.
Who Leads and Participates?
- Led By: The Project Manager (working closely with the Project Sponsor).
- Key Participants: The core project delivery team, user representatives, operational support staff, key external contractors, and PMO representatives.
Core Objectives of the Post-Project Review
- Assessing Project Management Success: The review compares actual project delivery performance against the approved baselines in the Project Management Plan:
- Time: Was the project delivered on schedule?
- Cost: Did delivery complete within the authorized financial baseline?
- Scope & Quality: Were all agreed deliverables produced to the required specifications and acceptance criteria?
- Identifying Lessons Learned: The team conducts a candid, blameless evaluation of what worked well, what failed, what unexpected risks materialized, and what practices should be institutionalized or avoided on future projects.
- Evaluating Team and Supplier Performance: Formal feedback is documented regarding contractor performance, commercial vendor reliability, and internal team contributions.
- Authorizing Administrative Closure: Confirming that project accounts are reconciled, contracts are closed, documentation is archived, and project resources are released back to functional departments or new projects.
Primary Output: The Project Closeout Report
The findings of the PPR are synthesized into the Project Closeout Report (or End of Project Report) and deposited into the organization's central PMO knowledge repository, ensuring that lessons learned directly enhance corporate delivery capability.
3. Benefits Reviews (Benefits Realization Reviews)
Core Purpose: To evaluate project/investment success by measuring actual realized business benefits against the forecasts set out in the original Business Case.
A project is undertaken to deliver capabilities that enable business change, which in turn generates beneficial outcomes for the sponsoring organization. However, benefits are rarely realized instantaneously upon project handover. New systems take months to embed, operational efficiencies take time to mature, and revenue streams ramp up over financial quarters.
A Benefits Review is conducted during the Operations phase of the extended project life cycle—typically 6, 12, or 24 months after the project team has disbanded and the deliverables have been in active operational use.
Who Leads and Participates?
- Led By: The Project Sponsor and designated Business Change Managers (BCMs) or operational asset owners.
- Key Participants: Operational managers, finance teams, and executive stakeholders.
- Crucial Distinction: The Project Manager and project delivery team are typically not present, as they have long since been disbanded and redeployed to other projects.
Core Questions Answered During a Benefits Review:
- Are the planned financial benefits (e.g., cost savings, increased profitability, revenue growth) being realized as projected in the Business Case?
- Are non-financial benefits (e.g., enhanced safety, improved regulatory compliance, carbon reduction, higher customer satisfaction) being achieved?
- Have unintended negative consequences or dis-benefits emerged that require operational mitigation?
- Are ongoing operational processes optimized to continue extracting maximum value from the asset?
Primary Output: The Benefits Realization Report
The review produces a formal Benefits Realization Report detailing actual versus forecasted value realization, which is submitted to corporate executive governance.
4. Project Audits
Core Purpose: To provide independent, objective assurance that the project complies with organizational governance, statutory regulations, contract terms, and quality management standards.
A Project Audit is an independent, objective evaluation of any aspect of a project. BoK7 calls audit "an important tool to provide assurance" and states the governing principle: "the auditor is independent of the area being audited." The auditee is the person responsible for responding to audit findings, and follow-up audits to confirm suitable action has been taken are typical before the audit is closed out. Unlike Decision Gates and Post-Project Reviews—which are managed internally by the project leadership—audits are conducted by parties strictly external to and independent of the immediate project management team.
Who Leads and Conducts Audits?
- Conducted By: Internal corporate audit departments, external regulatory bodies, independent quality certifiers (e.g., ISO auditors), or third-party forensic accounting specialists.
- Timing: Audits may be scheduled at predetermined points (e.g., bi-annually) or triggered on an ad-hoc basis in response to project distress, major budget anomalies, whistleblowing reports, or safety incidents.
Focus of Project Audits:
- Governance and Process Compliance: Verifying whether the project is adhering to organizational project management frameworks, approved change control protocols, and quality standards.
- Financial and Commercial Integrity: Scrutinizing procurement procedures, supplier contract administration, accounting records, and payment approvals for financial rectitude and fraud prevention.
- Regulatory and Statutory Compliance: Ensuring full conformity with external legislation, environmental protections, data security laws (e.g., GDPR), and occupational health and safety standards.
Primary Output: The Formal Project Audit Report
The audit produces an official Audit Report containing specific findings, non-conformance notices, risk assessments, and mandatory corrective action recommendations that the Project Manager and Sponsor are obligated to implement.
Master Comparison: The Four APM Project Review Types
The following table summarizes and contrasts the four primary project review types defined in APM BoK7:
| Review Type | Timing in Life Cycle | Primary Purpose | Led By / Core Participants | Key Question Answered | Primary Output Document |
|---|---|---|---|---|---|
| Decision Gate (Stage Gate) | At formal phase boundaries between project lifecycle stages. | To confirm phase completion and validate business case viability before authorizing next phase funding. | Led by: Project Sponsor.<br/>Participants: Project Manager, Steering Board, PMO. | "Does the business case remain viable, and are we justified in starting the next phase?" | Gate Review Record & Authorization to Proceed. |
| Post-Project Review (PPR) | At project closure, immediately following handover to operations. | To evaluate project management performance against baselines and capture lessons learned. | Led by: Project Manager.<br/>Participants: Project Team, Sponsor, Users, Contractors. | "Did we deliver the agreed scope on time, to budget, and to standard, and what can we learn?" | Project Closeout Report & Lessons Learned Log. |
| Benefits Review | Post-handover during operational use (6, 12, 24+ months after closeout). | To evaluate investment success by measuring actual realized benefits against business case forecasts. | Led by: Project Sponsor & Business Change Managers.<br/>(Project team is disbanded). | "Has the investment delivered the promised strategic value, ROI, and operational benefits?" | Benefits Realization Report. |
| Project Audit | Scheduled or ad-hoc at any point throughout the project life cycle. | To provide independent assurance of compliance with policies, standards, legislation, and contracts. | Led by: Independent Internal or External Auditors.<br/>Participants: Project Manager, PMO. | "Is the project operating in full compliance with mandatory governance, laws, and standards?" | Formal Project Audit Report & Corrective Action Plan. |
Project Management Success vs. Project Investment Success
To synthesize the governance value of project reviews, the APM draws a vital conceptual distinction between project management success and project investment success:
- Project Management Success: Assessed during the Post-Project Review. It evaluates the efficiency and effectiveness of the project delivery process itself—measuring whether the project manager delivered the agreed scope on time, within the approved budget, and to the agreed quality criteria.
- Project Investment Success: Assessed during Benefits Reviews. It evaluates the long-term effectiveness of the investment—measuring whether the asset actually created value, generated expected returns, and solved the underlying business problem.
[!NOTE] A project can be an exemplary project management success (delivered on time, under budget, to specification) but ultimately a project investment failure (market demand collapsed, competitors rendered the product obsolete, or operational costs outstripped revenues). Conversely, a project can suffer severe cost overruns and delays (project management failure) yet ultimately become a legendary project investment success (such as the Sydney Opera House or the Thames Barrier, which became invaluable commercial and social assets).
What is the primary governance purpose of a Decision Gate (Stage Gate) in a project life cycle?
When is a Benefits Realization Review typically conducted, and who is responsible for leading it?
Which statement correctly captures the operational distinction between a Post-Project Review and a Project Audit?