Project Health Check
What is a Project Health Check?
A project health check is an independent, structured review of whether a project is on track to deliver its goals. It recommends specific actions to fix any problems it finds.
Updated November 2026 · 2 min read
What a health check looks at
A health check goes beyond the project's own status reports. A reviewer, usually from a PMO, internal audit or an outside firm, looks at evidence across several areas and talks to the people involved. The aim is to find problems early, while there is still time to correct them.
| Area | Typical questions |
| Business case | Is the case still valid? Are benefits still expected? |
| Scope and requirements | Is scope stable and controlled? Do the sponsor and the business agree on what is being built? |
| Schedule and budget | Is the plan realistic? How do actuals compare with the baseline? |
| Governance | Are decisions being made at the right level and in time? |
| Risks and issues | Are risks identified, owned and acted on? |
| Team and resources | Are the right people available? Is morale a concern? |
| Sponsorship and buy-in | Are sponsors engaged? Are the people affected ready for the change? |
| Delivery and quality | Is work meeting acceptance criteria? Is testing adequate? |
When to run one
- At set points, such as before a major go/no-go decision or a stage-gate review
- When warning signs appear: repeated slippage, a project stuck on amber, key people leaving
- On a regular cycle for large or high-risk programs, often every quarter
- When a new sponsor or project manager takes over
How a health check runs
- Agree the scope, questions and timeline with the sponsor
- Review documents: plans, the RAID log, reports, budgets and the business case
- Interview the sponsor, project manager, team members and the people most affected
- Rate each area, often using a RAG scale or maturity score
- Present findings and a short list of prioritized recommendations
- Agree actions and owners, and follow up on progress
An example
A bank's PMO runs a two-week health check on a core-systems migration that has reported green for six months. Interviews reveal that data-quality problems have been discussed in workstream meetings but never reached the steering committee. The schedule assumes two rounds of data testing; the evidence suggests four will be needed. The check rates the project red on schedule and amber on governance, and recommends replanning testing, adding a data-quality lead and changing reporting so that workstream risks are escalated. The sponsor accepts all three, and the go-live moves by six weeks rather than failing later.
Keeping health checks useful
Independence matters: reviewers should not report to the project manager. Keep the tone supportive, framing the review as help rather than an audit, so people speak openly. Focus recommendations on a few changes that matter most. And follow up; a report that changes nothing is wasted effort. Health check results can also feed portfolio risk management and a PMO maturity model assessment.
Frequently asked questions
Who performs a project health check?
Someone independent of the project team, such as a PMO analyst, an experienced project manager from another area, internal audit or an external consultant. Independence matters because project teams can become too close to their own work to see problems clearly, and people often speak more openly to a neutral reviewer.
How long does a project health check take?
For most projects, one to three weeks, including document review, interviews and a findings presentation. Light-touch checks for smaller projects can be done in a few days. Large, complex programs may need a longer review or a series of reviews by workstream. The time required grows with the number of people and teams involved.
What is the difference between a health check and a project audit?
A health check is usually forward-looking and supportive, aiming to help a project succeed by finding and fixing problems. A project audit is more formal and focuses on compliance with policies, controls and contracts, often after the fact. Health checks lead to recommendations; audits often lead to formal findings that must be addressed.
Related terms
Go/No-Go Decision
A formal checkpoint to decide whether a project goes ahead.
Stage-Gate Process
Work divided into stages, with go or stop decisions at each gate.
RAID Log
One place to track a project's risks, assumptions, issues and dependencies.
Steering Committee
Senior stakeholders who set direction and make the big calls on major work.