Most capital projects don't fail on a single day. They drift — quietly at first, then all at once — until a gate review, a budget report or a handover date forces the truth into the open. By then, the fix costs far more than it would have a few months earlier.
Independent reviewers see the same early indicators recur across healthcare, science, pharma and data centre programmes. None of them are dramatic on their own. Together, they're a reliable early-warning system — and every one of them is visible well before a project is formally "in trouble."
No commissioning strategy, this late
If a programme is within a few months of handover and commissioning is still being treated as an operational afterthought rather than a planned workstream with its own governance, the handover date is already at risk — even if nobody has said so yet.
Governance that was never really set up
Programmes that move straight into delivery without a robust Project Execution Plan, a clear decision framework, or an honest gap analysis at setup tend to carry that weakness for the rest of the programme's life.
Meetings about position, not progress
When contractual friction starts shaping how people behave in meetings — when the conversation is about protecting a position rather than solving a problem — the relationship has become adversarial, and delivery usually suffers next.
The same issues, meeting after meeting
Recurring open items that never quite get closed are a symptom of weak decision-making cadence, not bad luck. If nobody owns closing an issue, it doesn't close.
Visible fatigue in the client team
Team resilience and working relationships erode quietly under sustained pressure. By the time it's visible to a sponsor or board, it has usually been building for months.
Gate packs that describe intentions, not evidence
A readiness review should be able to distinguish between "we plan to have this ready" and "this is ready" — if a gate pack leans heavily on the former, the gate is being passed on hope.
No single accountable voice
When decisions get diffused across too many stakeholders and no one person is independently checking the whole picture, small inconsistencies between workstreams go unnoticed until they collide.
Employer's Requirements drifting from delivery
What's actually being built starts to diverge from what was specified — often for good reasons in isolation, but without anyone checking the cumulative effect against the original requirements.
Bids and business cases that haven't been red-teamed
A bid or investment case that has only ever been reviewed by the people who wrote it rarely survives first contact with genuine scrutiny — and that scrutiny is far cheaper before submission than after.
Nobody wants to be the one who raises it
The clearest warning sign of all: when everyone privately senses the programme is off track, but no one internally has the independence — or the standing — to say so plainly.
Only 15% of the UK government's major projects were rated Green for delivery confidence in March 2026; most sat at Amber, with significant issues that are still resolvable if addressed promptly. Catching them early is the differentiator. (NISTA Major Projects Annual Report 2025–26)
What to do if you recognise more than two or three of these
None of these signs mean a project is doomed. Every one of them is recoverable — we've personally taken programmes from this exact position back to a controlled, structured footing, as set out in our case studies. What matters is getting an honest, independent read before the warning signs turn into missed gates, budget overruns, or disputes.
That's the entire premise of a Project Failure Prevention Review or a Gateway Readiness Review — a fixed-scope, fast, independent look at exactly where a programme stands, with a clear board-ready view of what to do next.