A project can look busy, well-attended and broadly on track right up until the point it is not. Status reports stay green because teams are working hard, not because the plan remains credible. A project delivery health review cuts through that false comfort. It tests whether the work can still deliver its intended outcome, within the constraints the organisation has actually approved.
For executives, the value is not another report. It is a clear view of what is true, what is at risk, what decisions cannot wait and what it will take to restore control. That matters whether the project is a core platform replacement, regulatory uplift, construction program, customer transformation or new operating model.
What a project delivery health review is designed to find
A delivery health review is an independent, evidence-based assessment of a project or program's ability to achieve its objectives. It examines the practical conditions required for delivery: scope, schedule, budget, governance, resourcing, risks, dependencies, vendor performance and stakeholder alignment.
The word “independent” matters. Project teams can become too close to the work to see warning signs clearly. Sponsors may receive filtered information. Leaders can also inherit a program with decisions already made and assumptions rarely challenged. A well-run review creates enough distance to test the story against the evidence.
It should not be treated as an audit designed to assign blame. The purpose is to establish a credible baseline and give leaders a path forward. Sometimes that path is a targeted reset. Sometimes it is stronger governance, a revised sequence of work or a sharper decision on scope. In more serious cases, it may mean pausing activity before further money and goodwill are spent on the wrong plan.
The warning signs that justify a review
Most organisations do not need a health review for every piece of work. A capable project manager, engaged sponsor and proportionate governance can keep a straightforward initiative on course. A review becomes valuable when the signals are mixed, confidence has dropped, or the consequences of getting it wrong are significant.
Common triggers include a project that has missed more than one key milestone, a budget that is being consumed faster than delivery is progressing, or a team that cannot explain the critical path in plain language. Other signs are more political: competing executive views on the outcome, frequent scope changes without a clear approval trail, or a steering committee making decisions too late to influence delivery.
In regulated sectors, the trigger can be an approaching compliance date with no reliable evidence of readiness. In digital transformation, it may be a build that appears complete while data, integration, security, operating model and adoption work remain unresolved. In construction or social infrastructure, the pressure often sits in interfaces between contractors, approvals, procurement and site conditions.
None of these signs automatically mean the project has failed. They do mean leaders should stop relying on optimism and establish the facts.
What a credible review examines
A useful project delivery health review goes beyond a RAG status and a risk register. It follows the chain from strategic intent to day-to-day execution, looking for gaps between what has been promised and what the organisation is genuinely positioned to deliver.
The case for the work
The review starts with the outcome. Is there a current, agreed definition of success? Are the benefits measurable, owned and still relevant? Projects often retain their original business case even after market conditions, regulatory expectations or organisational priorities have changed. If the destination is unclear, no amount of schedule discipline will solve the problem.
The scope must then be tested against the available time, funding, people and decision-making capacity. A scope that is technically possible may still be commercially unrealistic. The right answer may be to stage delivery, protect the minimum viable outcome or remove lower-value work. That is not failure. It is disciplined prioritisation.
The plan and the critical path
A plan is credible when it reflects real dependencies, accountable owners, decision dates and capacity constraints. It is not credible simply because it contains hundreds of tasks.
Reviewers should test whether the critical path is understood and actively managed. They should ask whether estimates are based on evidence, whether contingency is realistic, and whether the team has accounted for activities that are routinely underestimated, such as data remediation, testing, procurement, approvals, change impacts and operational readiness.
The distinction matters. A project may be “on track” against an outdated baseline while already being unable to meet the date the business needs. A health review puts those two truths in the same room.
Governance and decision quality
Weak governance is rarely about the absence of meetings. More often, it is about the wrong people meeting without the information or authority needed to make timely decisions.
A review examines whether the sponsor is active, whether accountabilities are clear, and whether escalations reach the right level early enough. It also checks whether the steering committee is resolving material issues or merely receiving updates. If decisions on scope, risk acceptance, funding or priorities sit unresolved for weeks, the project team will fill the vacuum with assumptions.
Good governance gives the team direction and protection. It does not create a second project around the project.
Delivery capability and capacity
Projects fail when critical roles are nominally assigned but not meaningfully available. Subject matter experts get pulled back into business-as-usual work. Leaders approve a plan without releasing the people required to execute it. One capable individual becomes the bottleneck for every decision, artefact or technical sign-off.
A review looks at whether the delivery structure matches the complexity of the work. It assesses capacity as well as capability, because highly experienced people still cannot do the work of three roles indefinitely. It also tests whether responsibilities across internal teams, delivery partners and suppliers are clear at the hand-offs, where problems tend to accumulate.
Risk, issues and dependencies
Risk registers can create an illusion of control when they list everything but drive nothing. The review should identify the few risks that could materially affect outcomes, then test whether mitigation actions have owners, dates, funding and executive support.
Dependencies deserve the same scrutiny. A project can be well managed within its own boundaries and still fail because another initiative, vendor decision, policy change or operational team is not ready. Mapping those dependencies makes hidden exposure visible. It also gives sponsors a basis for making enterprise-level trade-offs rather than asking individual teams to absorb impossible commitments.
How to run the review without creating more disruption
The best reviews are focused and fast enough to influence the work while there is still room to act. They combine document review with direct conversations across the project team, sponsor group, operational leaders, technical specialists and key suppliers. The aim is not to interview everyone. It is to hear enough perspectives to distinguish isolated frustration from a systemic problem.
Evidence should include the approved business case, current plan, financial position, risk and issue logs, governance papers, key decisions, dependency maps and readiness materials. Interviews then test whether these documents describe lived reality. If the schedule says a dependency is complete but the owner says they have not started, the review has found something that deserves attention.
A strong output is concise, specific and prioritised. It should identify what is working, the material gaps, the consequence of inaction and practical recommendations with clear owners. A 70-page report that no one acts on is not a recovery plan.
For complex or troubled work, an embedded senior delivery lead can turn recommendations into action. This is where a review has real value: not just diagnosing the problem, but resetting the plan, establishing decision discipline and maintaining momentum through the difficult weeks that follow.
What leaders should expect after the review
The first outcome may be uncomfortable. A credible review can confirm that a committed date is not achievable, that the scope exceeds available capacity, or that an assumed benefit has no accountable owner. Senior leaders need to create room for that truth. Punishing bad news only ensures it arrives later and costs more.
The next step is a decision-led recovery plan. It should set out the baseline position, immediate controls, priority decisions, revised milestones and governance rhythm. It should also be clear about what will not be done. Recovery plans fail when every original commitment remains untouched and the team is simply asked to work harder.
JJPH sees this regularly in recovery work: the strongest turnarounds begin when leaders replace vague reassurance with a small number of clear choices. Protect the outcome that matters. Put accountable people around the table. Resolve dependencies early. Then measure progress against evidence, not sentiment.
A project delivery health review is not a sign that leadership has lost control. Used early, it is how leadership demonstrates control: by asking for an honest picture, making the necessary calls and giving the delivery team a plan they can genuinely execute.
Melvin Phan
Founder & CEO
