A strong project assurance framework provides confidence that projects are delivering what they should, while applying the right level of scrutiny for their complexity and risk. The key is proportionality. Too little assurance creates blind spots. Too much creates bureaucracy. The goal is to design a framework that strengthens decision-making without overwhelming delivery teams.
Why Do Organisations Struggle to Get Project Assurance Right?
Many organisations do not lack assurance. They lack calibration.
Some projects are lightly reviewed until issues escalate. Others are subjected to the same governance structure regardless of scale or complexity.
The issue is rarely whether assurance exists. It is whether the level is appropriate.
As Marisa Silva explains:
“If assurance is not improving confidence and decision-making, then it is simply creating paperwork.”
The challenge is not whether to assure. It is how much.
What Should a Project Assurance Framework Actually Do?
A project assurance framework should provide structured confidence that projects and programmes will achieve their intended outcomes.
According to the Association for Project Management, assurance supports beneficial change by strengthening oversight and accountability.
If you would like a deeper dive into the core foundations behind effective assurance, we explore the six essential project assurance principles in more detail here.
A well-designed framework should:
- Clarify who provides assurance
- Define when reviews occur
- Differentiate between review types
- Scale scrutiny according to risk
- Ensure findings lead to action
It should not treat every initiative identically.
Watch video: Project Assurance: What It Is and Why It Matters
Presented by Marisa Silva and Emma Arnaz-Pemberton
How Do You Design or Reset a Project Assurance Framework?
Avoid launching assurance across the entire portfolio at once. A project assurance framework is most effective when it is introduced thoughtfully and proportionately.
If you are wondering where to begin in practical terms, this short video outlines the key first steps:
Once you have clarity on your starting point, a sensible rollout typically includes:
- Starting with engagement and clarifying the purpose
- Co-creating expectations with delivery leads and sponsors
- Piloting the framework on a representative project
- Gathering feedback and refining proportionality
- Scaling gradually across the portfolio
| Tier | Characteristics | Assurance Intensity |
|---|---|---|
| Tier 1 | High risk, complex, strategic | Full gateway lifecycle plus regular health checks |
| Tier 2 | Moderate risk | Core gateway reviews plus targeted checks |
| Tier 3 | Low risk | Essential stage gates only |
This allows governance to scale proportionately.
When Should Gateway Reviews Be Used?
Gateway reviews are structured decision points in the lifecycle.
They are appropriate when:
- Significant investment decisions are required
- Risk exposure increases
- Major stage transitions occur
Typical gateway stages include:
- Strategic assessment
- Business case approval
- Delivery readiness
- Investment approval
- Operational readiness
- Benefits realisation
For Tier 1 initiatives, a full sequence is often appropriate. For Tier 3 projects, fewer gates may be justified.
The framework should define this clearly.
What Is the Role of Project Health Checks?
Health checks assess the health of delivery during a stage.
They typically review:
- Governance effectiveness
- Sponsor engagement
- Risk management maturity
- Delivery trajectory
For high-risk programmes, quarterly health checks can provide early warning signals.
For lower-risk initiatives, phase-based reviews may be sufficient.
As Marisa Silva says:
“Often the real risks are not in the documents. Health checks create space for conversations that would not otherwise happen.”
Health checks should strengthen transparency, not create defensiveness.
Should Project Assurance Always Be Risk-Based?
Yes.
A project assurance framework should allocate attention according to risk exposure.
Risk profiles evolve. A low-risk project can become high-risk following scope changes or supplier shifts.
It is also worth recognising that assurance must adapt to different delivery environments. In Agile and hybrid settings, evidence looks different, but oversight remains essential. We explore this in more detail in our article on assurance and Agile projects.
Tiering and assurance intensity should therefore be revisited at key gateway transitions.
Assurance is not static.
Why Does Culture Matter in Project Assurance?
No framework succeeds without cultural alignment.
Warning signs include:
- Leaders rewarding only green reporting
- Reviews treated as pass or fail tests
- Findings ignored or delayed
In such environments, increasing assurance volume will not improve outcomes.
As Emma Arnaz-Pemberton puts it:
“Assurance should feel like a critical friend. If teams prepare defensively for reviews, something in the framework needs adjusting.”
Confidence depends on psychological safety.
Watch video: Building a Culture of Project Assurance – Why It’s Not Just a Checkbox
Presented by Marisa Silva – Senior Project Consultant at Wellingtone
How Do You Design or Reset a Project Assurance Framework?
Avoid launching assurance across the entire portfolio at once.
Instead:
- Start with engagement and clarify purpose
- Co-create expectations with delivery leads
- Pilot the framework on a representative project
- Gather feedback
- Refine proportionality before scaling
This approach builds credibility and prevents resistance.
How Do You Know If the Level Is Right?
A well-calibrated framework produces:
- Early risk visibility
- Informed sponsor decisions
- Clear accountability
- Reduced bureaucracy on low-risk work
- Meaningful follow-up on findings
If you are looking for more practical guidance on applying assurance effectively within your organisation, this guide on how to apply good project assurance expands on the operational side.
If assurance strengthens confidence without slowing delivery unnecessarily, the level is right.
Strengthen Your Assurance Skills
Wellingtone’s APM Endorsed Assurance Practitioner course equips PMOs and delivery leaders with the practical tools to apply integrated, risk-based assurance confidently and proportionately.
Download the brochure to explore the course structure, outcomes and upcoming dates.
