Carpadium

Project Health Check vs Project Assurance: What’s the Difference?

Written by Andrew McDonald, Founder & Principal at Carpadium· Published 24 September 2026

Both provide independent confidence—but they solve different governance problems.

A Project Health Check provides a point-in-time assessment of project health and delivery confidence.

Project Assurance provides independent oversight across the project lifecycle, helping executives understand whether risks, decisions and delivery conditions remain appropriately controlled over time.

The right approach depends on the decision being made, the level of uncertainty and how long independent oversight is required.

Executive guide | Project Assurance

THE SHORT ANSWER

The main difference is point-in-time assessment versus continuing confidence.

PROJECT HEALTH CHECK

A structured, independent assessment of the project’s current health, risks and delivery confidence at a particular point in time.

Best when executives need to answer:

“What is the real delivery position today?”

Typical characteristics

  • point-in-time
  • focused review period
  • evidence-based assessment
  • findings and recommendations
  • useful before major decisions or when concerns emerge

PROJECT ASSURANCE

Independent oversight conducted at defined points throughout the project lifecycle to provide continuing confidence in delivery.

Best when executives need to answer:

“Are we continuing to manage this project in a way that supports successful delivery?”

Typical characteristics

  • ongoing or periodic
  • lifecycle-based
  • risk-driven
  • independent challenge
  • continuing visibility for executives and governance bodies

“A Health Check establishes confidence at a point in time. Project Assurance helps maintain confidence over time.”

SIDE-BY-SIDE

Health Checks and Project Assurance differ primarily in purpose, timing and continuity.

Purpose

Project Health Check

Establish current project health

Project Assurance

Provide continuing independent confidence

Timing

Project Health Check

Point-in-time

Project Assurance

Across defined lifecycle points

Trigger

Project Health Check

Decision, milestone, concern or uncertainty

Project Assurance

Planned governance and assurance approach

Scope

Project Health Check

Broad or targeted

Project Assurance

Risk-based and adjusted throughout delivery

Duration

Project Health Check

Short, focused review

Project Assurance

Periodic or ongoing

Primary question

Project Health Check

“What is the real position?”

Project Assurance

“Can we continue to have confidence in delivery?”

Outputs

Project Health Check

Findings, assessment and recommended actions

Project Assurance

Assurance observations, actions, escalation and continuing insight

Best suited to

Project Health Check

Important decisions or emerging concerns

Project Assurance

Major, complex or high-risk projects requiring continuing oversight

POINT-IN-TIME CONFIDENCE

When is a Project Health Check appropriate?

A Health Check is appropriate when executives need an independent view of the project at a particular moment.

It does not require the project to be failing or reporting Red.

01

Before a major funding or governance decision

02

When milestones repeatedly move

03

When cost or resource pressure increases

04

Before implementation or go-live

05

When stakeholder confidence declines

06

Following significant change or disruption

Executive question

“Do we have sufficient independent evidence to make the next important project decision with confidence?”

EXPLORE WHEN TO CONDUCT A PROJECT HEALTH CHECK

CONTINUING CONFIDENCE

When is ongoing Project Assurance appropriate?

Some projects carry sufficient complexity, investment, organisational impact or delivery risk that executives require independent confidence throughout the lifecycle rather than at a single point.

01

INITIATE

Focus

  • Business case
  • Governance
  • Delivery approach
  • Scope clarity
02

PLAN

Focus

  • Schedule credibility
  • Resources
  • Commercial arrangements
  • Dependencies
03

DELIVER

Focus

  • Progress
  • Cost
  • Risk
  • Quality
  • Delivery confidence
04

IMPLEMENT

Focus

  • Readiness
  • Testing
  • Data
  • Transition
  • Go-live risk
05

REALISE

Focus

  • Adoption
  • Benefits
  • Operational performance
  • Outstanding risk

Project Assurance should not duplicate project management or governance. Its purpose is to provide independent evidence and challenge so decision-makers can determine whether the delivery position remains credible.

ASSURANCE IS NOT GOVERNANCE

Project Assurance provides evidence to governance—it does not replace it.

PROJECT MANAGEMENT

Runs the project.

Focus

  • Planning
  • Delivery
  • Resources
  • Issues
  • Reporting

PROJECT GOVERNANCE

Directs and makes decisions.

Focus

  • Accountability
  • Decisions
  • Escalation
  • Investment
  • Risk acceptance

PROJECT ASSURANCE

Provides independent confidence.

Focus

  • Evidence
  • Challenge
  • Delivery credibility
  • Emerging risk
  • Decision confidence

“Management owns delivery. Governance owns decisions. Assurance provides independent confidence in the evidence supporting those decisions.”

CHOOSING THE RIGHT INTERVENTION

Use the smallest intervention that provides sufficient confidence.

PROJECT PULSE

Use when

There is a focused question or emerging concern.

Purpose

Rapid independent perspective around a specific delivery issue.

PROJECT HEALTH CHECK

Use when

There is broader uncertainty about overall project health.

Purpose

Establish the actual delivery position.

PROJECT ASSURANCE

Use when

Independent confidence is required throughout delivery.

Purpose

Provide continuing evidence and challenge across the lifecycle.

PROJECT RECOVERY

Use when

Delivery confidence has materially deteriorated.

Purpose

Stabilise, replan and restore delivery confidence.

Assurance continuum

PROJECT PULSE
PROJECT HEALTH CHECK
PROJECT ASSURANCE
PROJECT RECOVERY

These services do not need to be used sequentially. The appropriate intervention depends on the decision, uncertainty and delivery risk.

“The appropriate intervention depends on the decision, uncertainty and delivery risk—not simply the project’s RAG status.”

COMPLEMENTARY APPROACHES

A Health Check can form part of a broader Project Assurance approach.

Project Health Checks and Project Assurance are not mutually exclusive.

A major transformation may establish an assurance framework across its lifecycle while commissioning deeper Health Checks at particularly important decision points.

Example assurance timeline

BUSINESS CASE
Assurance review
FUNDING APPROVAL
Health Check
DELIVERY
Periodic assurance
PRE GO-LIVE
Health Check
IMPLEMENTATION
Readiness assurance
BENEFITS
Post-implementation assurance

“The level of assurance should change as the project’s risk profile and executive decisions change.”

EXECUTIVE DECISION GUIDE

Five questions can help determine the right assurance approach.

1

Do we need confidence around one specific question?

If yes, consider a Project Pulse.

2

Do we need to understand the project's overall health now?

If yes, consider a Project Health Check.

3

Will executives need independent confidence repeatedly throughout delivery?

If yes, consider ongoing Project Assurance.

4

Has delivery confidence materially deteriorated?

If yes, a recovery intervention may be required.

5

Is an irreversible or high-consequence decision approaching?

Consider whether additional independent evidence is required before making the commitment.

Assurance should be proportionate to the scale of the decision, the uncertainty surrounding delivery and the consequences of being wrong.

COMMON QUESTIONS

Project Health Check vs Project Assurance FAQs

Yes. A Project Health Check is a point-in-time assurance activity. Broader Project Assurance typically involves independent review at multiple points throughout the project lifecycle.

Not necessarily. The level of assurance should be proportionate to project complexity, investment, risk, organisational impact and the decisions executives need to make.

Yes, provided accountability for the assurance assessment remains independent of the people responsible for delivery. Assurance can engage closely with the project while maintaining independent judgement.

Yes. Formal project status is only one source of evidence. Assurance can be particularly valuable before major commitments even where the project continues to report Green.

There is no universal frequency. Reviews should align with project risk, major decision points, lifecycle transitions and material changes in delivery conditions.

Executives should receive a concise, evidence-based view of delivery confidence, material risks, significant assumptions, required actions and issues requiring governance attention.

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 CONFIDENCE

Need greater confidence in a major project?

Independent perspective. Senior-level judgement. Evidence before opinion.

Carpadium provides independent Project Health Checks and Project Assurance designed to give executives clear, evidence-based insight into project health, delivery risk and the decisions requiring attention.