22 March 2026 · updated 28 August 2026 · 4 min read
UK organisations — across the public sector, NHS, construction, financial services, and beyond — spend billions each year on projects that overrun, underdeliver, or fail altogether.
NISTA — the National Infrastructure and Service Transformation Authority, which took over the Infrastructure and Projects Authority’s role in 2025 — publishes an annual report on the Government Major Projects Portfolio. In the 2025–26 report, covering 189 projects worth £924.2bn over their whole life, 34 were rated Red and 109 Amber: 143 of 189, or 76%. NISTA’s own definition of Amber is that delivery “appears feasible but significant issues exist, requiring management attention”. Only 29 projects were rated Green. The picture in the private sector is no different, and it is less visible because nobody publishes it.
The tools exist. The methodologies exist. The governance frameworks exist. And yet the failure rates persist. The question worth asking is whether the tools are solving the right problem.
Most project monitoring software in the UK market — whether a standalone tool or part of a larger enterprise platform — does the same fundamental thing: it provides a structured way to record and display information that human beings input.
Status reports. RAG ratings. Milestone trackers. Risk registers. These are all input-dependent systems. Their accuracy is only as good as the information that people choose to provide — and people under project pressure have strong incentives to present their projects optimistically.
This is not a technology problem. It is a structural one. When the same person responsible for project delivery is also responsible for reporting on that project delivery, the signals you receive are inevitably filtered.
What most UK organisations actually need from project monitoring software is not a better way to record what people tell them. It is a way to understand what is actually happening — independently of what people choose to report.
That means monitoring signals that do not require human input. It means pattern recognition that draws on how projects actually behave, not just the data in the system. And it means telling the right people at the right level of the organisation what to do — in plain language, calibrated to their sector and their context.
For UK public sector organisations in particular, the stakes are high. Project failure is not just a commercial risk — it is a public accountability risk. Scrutiny committees, audit bodies, and Ministers ask hard questions when projects fail. The organisations that can demonstrate independent, continuous monitoring of project health are in a fundamentally stronger governance position than those that rely on self-reported status.
Slayt is built with the language, failure patterns, governance pressures and stakeholder dynamics of the UK public sector in mind — and where that is concrete, it is concrete rather than claimed. A Treasury Green Book five-case business case is a document type for central government projects. CQC notification and registration are prompts on social care and private healthcare projects, not fields somebody has to remember to add. Procurement regimes — the Procurement Act 2023, and PCR 2015 where it still governs contracts that started under it — are covered by our advisory practice rather than by the platform, and we would rather say so than imply otherwise.
Whether you are a local authority running a housing programme, an NHS trust managing a digital transformation, a construction company delivering infrastructure, or a financial services firm managing regulatory change — the fundamentals of project delivery intelligence are the same.
Signals. Patterns. Action. Before the problem becomes a crisis.
14-day trial. Full platform. Card required — no charge until day 15.