How often should a project health check be conducted?
Written by Andrew McDonald, Founder & Principal at Carpadium· Published 24 September 2026
There is no universal timetable. The right cadence depends on project risk, complexity, lifecycle stage and the decisions ahead.
A Project Health Check can be a single point-in-time assessment or part of a recurring cycle of independent review. For major or high-risk programs, periodic health checks help executives maintain confidence as delivery conditions change.
The question is not simply whether to conduct a health check, but how often independent review adds value without creating unnecessary overhead.
Executive guide | Project Health
ONE-OFF OR REPEATED
A project health check can be a single assessment or a recurring cycle.
A one-off Project Health Check provides a point-in-time view of delivery health. It is often commissioned before a major decision, at a stage gate, or when concerns emerge and executives want an independent view of the current position.
For major, complex or high-risk programs, a single assessment may not be enough. Delivery conditions change throughout the lifecycle — schedules move, costs shift, dependencies evolve and readiness becomes clearer. Recurring health checks provide periodic independent confidence as those conditions change.
The right choice depends on the investment, the risk, the decisions approaching and the assurance the organisation requires. Not every project needs repeated review. Many are best served by a focused point-in-time assessment at the moment that matters most.
If you are still deciding whether a health check is warranted at all, see our guide on when a project health check should be conducted.
“Frequency should follow the risk and the decisions — not a fixed calendar that treats every project the same.”
WHAT DRIVES FREQUENCY
How often a health check should occur depends on risk, complexity and stage.
There is no universal schedule for independent review. The appropriate cadence is shaped by the nature of the investment and the assurance the organisation needs.
PROJECT SCALE & INVESTMENT
Larger investments generally warrant more frequent independent review.
DELIVERY COMPLEXITY
Multiple workstreams, technologies, vendors and dependencies increase the case for recurring review.
RISK PROFILE
A higher material risk profile supports a denser review cadence.
LIFECYCLE STAGE
High-risk phases such as implementation and go-live may warrant closer review than stable delivery.
UPCOMING DECISIONS
Major milestones, stage gates and funding decisions influence when reviews add most value.
ASSURANCE REQUIREMENTS
Governance forums, regulators or Boards may require a defined cadence of independent review.
Cadence should be proportionate to delivery risk, complexity, stage and organisational assurance requirements.
WHY CADENCE MATTERS
More frequent review preserves management options.
The value of independent review changes as delivery confidence evolves. Periodic health checks help identify emerging issues while management still has options available — before contingency is exhausted, commitments are locked in or recovery options narrow.
Intervention options narrow as confidence deteriorates
PROJECT PULSE
Rapid independent perspective on a focused concern.
PROJECT HEALTH CHECK
Evidence-based assessment of overall project health and delivery confidence.
PROJECT RECOVERY
Stabilisation, reprioritisation and replanning where confidence has materially deteriorated.
“The earlier uncertainty is tested, the more options executives usually retain.”
PLANNED VS TRIGGERED REVIEWS
Health checks can be scheduled — or triggered by emerging concerns.
Recurring review cadence usually combines two patterns: reviews scheduled at predetermined points, and reviews triggered when delivery conditions warrant closer examination.
SCHEDULED REVIEWS
Planned at predetermined points in the project lifecycle to provide regular independent confidence.
- major decision approaching
- stage gate or milestone
- phase transition
- periodic program oversight
- leadership change
- regular cadence for high-risk programs
Objective
Maintain ongoing confidence and protect future options.
TRIGGERED REVIEWS
Initiated because evidence or stakeholder confidence suggests closer examination is required.
- milestones materially missed
- cost significantly increasing
- dependencies failing
- governance unable to resolve issues
- readiness concerns
- confidence declining
Objective
Establish the true position and determine intervention required.
“A health check does not require a project to be failing. Uncertainty itself can justify seeking independent evidence.”
CADENCE ACROSS THE LIFECYCLE
Review points should follow the project lifecycle.
Rather than a fixed interval, recurring health checks are usually aligned to the stages and decision points of the project. Each stage carries different risks and warrants a different focus.
INITIATION / MOBILISATION
Test business case, delivery strategy, governance and mobilisation.
MAJOR DELIVERY GATE
Test progress, forecasts, dependencies and readiness for the next phase.
PRE-IMPLEMENTATION
Test technical readiness, business readiness, transition and go-live risk.
POST-IMPLEMENTATION
Test stabilisation, residual risk, benefits and BAU transition.
Health checks should complement — not replace — effective governance and ongoing management assurance.
ADJUSTING REVIEW FREQUENCY
When to increase — or reduce — review frequency.
Cadence is not set once and forgotten. As a project moves through delivery, the appropriate frequency of independent review should change with the risk and the decisions ahead.
INCREASE FREQUENCY WHEN
- delivery risk is rising
- confidence in forecasts is declining
- major milestones or stage gates are approaching
- significant change or disruption has occurred
- contingency is being consumed faster than planned
- stakeholder confidence no longer aligns with reporting
REDUCE FREQUENCY WHEN
- delivery is stable and on plan
- material risk is well controlled
- confidence is high and supported by evidence
- the project is in a low-risk lifecycle phase
- few significant decisions remain
“Cadence should be proportionate to delivery risk, complexity, stage and organisational assurance requirements.”
CHOOSING THE INTERVENTION
Not every delivery concern requires a recovery program.
PROJECT PULSE
For a focused delivery question requiring rapid independent attention.
EXPLORE PROJECT PULSEPROJECT HEALTH CHECK
For testing overall delivery confidence, risks and credibility of the current plan.
EXPLORE PROJECT HEALTH CHECKSPROJECT RECOVERY
Where confidence has materially deteriorated and stabilisation or replanning is required.
EXPLORE PROJECT RECOVERYWHAT EACH REVIEW EXAMINES
Every health check should test the evidence behind the reported position.
Whether a health check is one-off or recurring, each review examines the same nine Project Health dimensions. The depth of review in each area can shift with the lifecycle stage and the questions executives need answered.
GOVERNANCE
Are decisions being made at the right level, speed and accountability?
SCHEDULE & DELIVERY
Is the plan achievable with credible assumptions and dependencies?
FINANCIALS
Are forecasts, contingency and financial risks realistic?
RISKS & ISSUES
Are material risks and issues understood, owned and actively managed?
PEOPLE & CAPABILITY
Are leadership, resources and capability sufficient for delivery?
TECHNOLOGY
Are architecture, platforms and technical delivery sound?
VENDORS
Are vendor performance, commercial arrangements and accountability clear?
BUSINESS READINESS
Will the organisation be ready to adopt, operate and realise value?
BENEFITS
Do intended outcomes remain realistic, measurable and on track?
A strong health check connects these dimensions rather than assessing them in isolation. The objective is to understand the overall delivery position.
RECURRING CHECKS
Recurring health checks support ongoing delivery confidence.
For major or high-risk programs, a series of health checks across the lifecycle gives executives a consistent independent view of how delivery confidence and material risks change over time.
Recurring checks do not duplicate the PMO or replace governance. They provide periodic independent confidence at the points where decisions are made and where risk is most likely to materialise.
For transformations requiring continuous independent oversight rather than periodic review, ongoing project and program assurance may be more appropriate than repeated health checks.
“The value of recurring review is not the number of reports. It is the continuity of independent confidence across the decisions that matter.”
COMMON QUESTIONS
How often should a project health check be conducted — FAQs
There is no universal schedule. Frequency should be proportionate to project risk, complexity, lifecycle stage and the decisions approaching. Major, high-risk programs may warrant periodic reviews, while smaller or lower-risk projects may only need a single point-in-time assessment before an important decision.
Either can be appropriate. A one-off health check provides a point-in-time view before a major decision or when concerns emerge. Repeated checks provide ongoing confidence for major or high-risk programs where delivery conditions change over time. The right approach depends on the investment, risk and governance requirements.
Project scale, complexity, risk profile, lifecycle stage, upcoming milestones or stage gates, and the organisation’s assurance requirements all influence how often a health check should occur. Higher risk and complexity generally warrant more frequent review.
Different stages carry different risks. Initiation and mobilisation, major delivery gates, pre-implementation and post-implementation each warrant a different focus. Review cadence can be denser during high-risk phases and lighter when delivery is stable.
Frequency may be increased when delivery risk is rising, confidence is declining, major milestones or stage gates are approaching, or significant changes have occurred. The objective is to preserve management options by identifying emerging issues earlier.
Where delivery is stable, risk is well controlled and confidence is high, less frequent review may be appropriate. Assurance should be proportionate — not every project requires ongoing review.
No. Recurring health checks complement effective governance and management assurance. They provide periodic independent confidence rather than continuous oversight. For major transformations requiring ongoing independent oversight, project assurance may be more appropriate than repeated health checks.
WRITTEN BY
Andrew McDonald
Founder & Principal, Carpadium
Andrew leads and delivers Carpadium’s independent project and program assurance, health check and recovery engagements, working directly with executives, sponsors and governance forums across the Australian market.
INDEPENDENT PROJECT & PROGRAM HEALTH CHECKS
Need greater confidence in what your project is really telling you?
Independent perspective. Senior-level judgement. Evidence before opinion.
Carpadium provides independent Project and Program Health Checks for complex Australian organisations, helping executives understand the true delivery position before critical decisions are made.