Reporting on the estate is not the same as planning it

Estate data has never been better presented. The harder question is what a Trust is supposed to do after the report lands.

There has been real progress in how estate data gets presented. Condition, cost, carbon, utilisation and backlog can now be pulled into a single view, updated continuously, and put in front of a Board in a format that looks nothing like the spreadsheets of ten years ago.

That progress is worth having. It has also created a question that gets asked less often than it should. Once the report is on the table, what happens next?

What the “so what” actually involves

A dashboard can tell you that backlog maintenance sits at a certain figure and has grown for three years running. Useful, and worth knowing.  However, it does not tell you:

  • which six schemes go into next year’s programme;
  • what the risk position looks like if the seventh is deferred again;
  • how to phase the work around clinical activity;
  • or which parts of it would hold up if a regulator challenged them.

Between the output and the decision sits a layer of interpretation. Somebody has to weigh options that are not directly comparable, form a view, sequence it, cost it, and then defend it in a room where estates is competing with clinical priorities for the same money.

That layer has never really had a name, and it rarely has an owner. In most Trusts it ends up with whoever is preparing the paper before the deadline.

The responses that follow and why neither is enough on its own

When this gets recognised, the instinct is often to build analytical capability inside the estates team. Hire or train people who can work with the data properly. There is logic to it and there are Trusts doing it well. But estates is competing for data skills with every other part of the NHS and with every employer outside it. And for a role that is hard to define and even harder still to retain. Expecting experienced estates professionals to become analysts on top of compliance, capital and operational responsibility is a great deal to ask.

The other instinct is to assume the platform will close the gap. It will not, at least not by itself. Software can do a lot of the analytical heavy lifting, but it cannot decide what a Trust should do. That depends on:

  • clinical strategy
  • local pressures
  • risk appetite
  • what the organisation actually has the capacity to deliver this year

None of that lives in the estate data.

The useful question is not whether software can replace judgement. It is how much interpretation the output still requires before anyone can act on it. A view of condition and cost is description. A comparison of three investment options against the same baseline, showing what each does to backlog, running cost, carbon and space over time, is much closer to a decision.

That is what OPAL’s Scenario and Option Modelling module is for. It works from the baseline held in Operational Performance, so options are tested against one agreed version of the estate rather than assembled from separate extracts the night before. What comes out is not a picture of where things stand. It is a set of options with their consequences attached, which lowers the analytical burden considerably without pretending to remove the need for judgement.

The part that was always going to need people

What remains is choosing between options that sit close together. Knowing which of them a Board will actually approve. Sequencing work so it can be delivered alongside clinical activity. Anticipating the question a Non-Executive Director will ask, and having the evidence ready before it is asked.

This is where a consultancy either earns its place or does not. Most either advise or deliver, but we do both, and the advice is better for it. Our recommendations are shaped by having run the schemes and managed the estates rather than handed over at the point the analysis ends. We would rather give a Trust a recommendation we are prepared to be accountable for than a report that describes the situation accurately and stops there.

Time to reframe the training question

None of this means development has no place. It means the question is worth putting differently. Rather than asking how to turn estates professionals into data professionals, ask how much analytical work an estates team should have to do at all.

Some of it belongs in the platform. Some of it is worth bringing in for the two or three months a year when a capital case is being built. What is left is estates knowledge, operational context, and an understanding of how buildings and clinical services interact, which is already in the team and considerably harder to recruit than data skills. If there is a capability worth deliberately developing, it is knowing which question to put to the data and recognising when an answer is strong enough to act on.

Presenting estate data well took the sector a decade and it was a genuine achievement. The next gain will not come from presenting it better but from closing the distance between the output and the decision. This will be achieved partly through tools that produce something closer to a decision in the first place, and partly through judgement applied by people who have made these calls before and stayed around long enough to see how they turned out.

If you have a capital case being prepared this year, we are happy to look at what your current outputs would support and what would need to sit around them.

Get in touch today

About Natasha Richardson