When a project fails, the post-mortem usually points to the end. Missed deadline. Budget overrun. Scope creep. Stakeholder dissatisfaction.
But the failure rarely starts there. It starts at the beginning, when nobody asked a simple question: if something goes wrong, who needs to know, and how do they find out?
That question is an escalation path. And without one, risks sit with the wrong people, decisions get made too late, and by the time leadership is aware there is a problem, the project is already in recovery mode.
What an escalation path actually is
An escalation path is not a org chart. It is not a RACI. It is the defined route a risk, issue, or decision takes when it cannot be resolved at the level where it was identified.
It answers three things: who owns this, who do they tell if they cannot resolve it, and how quickly does that need to happen.
Without those three things documented and understood, escalation becomes political. People protect their patch. Risks get downgraded to avoid uncomfortable conversations. Issues sit in a log that nobody reads.
The signs it is missing
You are in a project where escalation is broken if any of these sound familiar:
Risks are raised in the weekly call but the same risks appear the following week with no change in status. Issues are logged but ownership changes depending on who is in the room. Senior stakeholders say they were not aware of a problem that has been in the RAID log for six weeks. Decisions that should take days take weeks because nobody is sure who has the authority to make them.
These are not people problems. They are governance problems. The structure does not support good decision making so good decision making does not happen.
What good looks like
A functioning escalation path is documented before the project starts. It is part of the governance framework, not an afterthought. It defines escalation thresholds, the point at which something moves from operational to senior leadership visibility. It is tested early so people understand it before they need it under pressure.
It does not have to be complicated. A one page escalation matrix with clear ownership and timescales is enough to transform how a programme handles risk.
The governance fix
If you are inheriting a programme that is already in flight and you suspect escalation is broken, the fastest diagnostic is to pull the RAID log and look at issue age. Anything that has been open for more than two weeks without a status change or owner update is a signal. Anything that has been escalated and then gone quiet is a red flag.
Fix the path first. Everything else follows.