Taking Back Control of the NHS Estate

11 Sept

Why In-House Facilities Teams Need Sovereign Data

Key takeaways

Asset histories often live inside a contractor's own system, not the Trust's
The same loss of control can happen at the software layer if a vendor's ownership changes
Most CAFM platforms were originally built for contractors managing multiple clients, not for the Trust that owns the estate
Contractor-scoped permissions let contractors work efficiently without ever holding the underlying database
Full, self-service data export is the real test of ownership
Sovereign data is a structural design choice, not a promise made after the fact

Here's a question worth sitting with for a minute. If your Trust changed one of its maintenance contractors tomorrow, would you keep the full history of your assets, the condition surveys, the certificates, the job records, or would a meaningful part of it leave with the contractor?

Want to empower your estate team with sovereign data? Download our free e-book to discover what you can achieve.

Download free guide

Why this happens more often than it should

For a lot of Trusts, asset histories and job data genuinely do live inside the contractor's own system rather than the Trust's. It works perfectly well until the relationship changes, or until someone needs an answer faster than a third party can provide one. And it isn't only a contractor issue. The same loss of control can happen one layer up, at the software itself. If a CAFM or IWMS platform's ownership changes, some Trusts have found themselves required to migrate onto a different underlying system, on a timeline that isn't theirs, with less certainty over how much control they'll retain once that migration is finished. If any part of that sounds familiar, it's a reasonable moment to ask harder questions about who actually controls your estate's data today.

Why it's a design choice, not an accident

A Trust that can say with confidence "this is what's high risk, this is what's significant, and here's the survey evidence behind both" is in a fundamentally different negotiating position than one working from a register that hasn't been walked in eighteen months. It's not just about winning more capital. It's about being able to defend a prioritisation decision at board level. Below questions are key to evaluate your current situation:

What genuine ownership requires, technically

Contractors and internal teams working in the same system under permissions scoped to what they actually need, rather than each holding a separate copy of the data
A full, self-service export of raw asset and compliance data, available to the Trust at any time, without needing a vendor's cooperation to release it
Compliance evidence that's portable in a usable format, not something that only makes sense inside one specific system

The test isn't what a contract promises about data ownership. It's whether your team could actually walk away with a complete, usable copy of its own data tomorrow, without asking permission.

What ownership looks like once you actually test it

This is the founding principle behind how Invida is built from grounds up. Contractors work inside the platform under permissions scoped to their own tasks, never holding the underlying database themselves. Instead, Trust's estates team retains full, exportable ownership of the asset and compliance record as a structural fact of the system, allowing them to take full control of their data long after a vendor contract comes to an end or a service provider is no longer the preferred contractor.