EPM programmes rarely fail loudly. They drift. The status stays green, the workstreams keep reporting progress, and then, somewhere around testing or cutover, the gap between what was reported and what is real becomes impossible to hide. By then the cost of correction is a multiple of what it would have been three months earlier.
The uncomfortable truth is that more governance of the usual kind rarely catches this. Another steering committee, another RAG report, another risk log does not help if the information feeding them is already optimistic. What changes the picture is an independent view: someone on your side of the table whose job is to tell you what is actually happening, not to defend a plan.
Why green status reports hide red risk
Status usually flows up from the people delivering the work. That is not dishonesty, it is human. Delivery teams are close to the detail, invested in the plan, and inclined to believe a slipping date can be recovered. Add a delivery partner whose commercial position depends on the programme looking healthy, and optimism becomes structural.
The other quiet killer is misalignment. Finance and technology sign up to the same plan while meaning different things by it, so a requirement that reads as agreed is still contested, and the disagreement only surfaces when the build makes it concrete.
What independent assurance actually looks at
Assurance is not a second project manager. It is a focused, evidence-based read of the things that most threaten the outcome:
- Whether the business outcome and scope have stayed intact, or quietly eroded
- Whether the architecture and design decisions still support the requirement
- The real state of data, integration, testing and operational readiness, not the planned state
- Plan, resourcing, dependencies and governance, tested against reality
- Commercial assumptions and change exposure
- Who owns each decision, and whether sponsors still have confidence
The point is to work client-side, independently of the implementation supplier. An implementer assuring its own programme is marking its own homework.
Three moments when it pays to bring in an independent view
Assurance is most valuable before a problem is obvious, not after.
At the start. Before build begins, an independent check of scope, design and plan catches the assumptions that would otherwise surface expensively later.
Mid-flight, when confidence dips. If something feels wrong but the reports say green, a focused health check finds the few issues that matter and puts them in front of sponsors with evidence.
When control has been lost. A stalled or failing programme needs an honest reset: the true status agreed, priorities re-set, and a recovery plan sponsors can actually act on.
Assurance that leads to action, not more theatre
Done badly, assurance is a fat report nobody reads. Done well, it is short and pointed: the handful of issues that most threaten the outcome, the evidence for each, and an accountable action against every one. Sponsors should be able to read it and decide, not commission another review.
Whether it runs as a one-off health check or as continuous oversight alongside the delivery partner, the value is the same: material risks made visible early enough to do something about them, from someone with no reason to tell you anything other than the truth. See how our EPM assurance and rescue work, or bring us the specific worry and we will tell you whether it is a real risk.
Before approving the next programme milestone
| Question | Evidence to ask for |
|---|---|
| Is the status green because the work is on track, or because no one has tested it lately? | Evidence behind the RAG rating, not just the rating itself. |
| Has the business outcome and scope stayed intact? | A comparison of today's scope against what was originally approved. |
| Is the reported progress real, or planned? | The actual state of data, integration, testing and operational readiness. |
| Do finance and technology mean the same thing by “agreed”? | Requirements confirmed by both sides, not assumed to be shared. |
| Who is assuring the programme? | An independent view, not the implementer marking its own homework. |
| If something feels wrong, can you name it with evidence? | A short, pointed health check rather than another status meeting. |
An answer you cannot evidence is a risk to resolve now, while correction is still cheap.