By Olivia Richards, Research & Improvement Analyst, Hedyn

Across the sector, we talk a lot about vulnerability – but too often, we treat it as a label rather than a lens. A flag on a system. A note on a record. Something that sits alongside services, rather than shaping them.

We’re continuously faced with the question: are our services designed for the people who use them, or for the systems that deliver them?

Designing vulnerability data with purpose

Data integrity and data quality are core to robust insight; so, in completely redesigning how we recorded resident vulnerabilities, we recognise the need to move away from static vulnerability flags and towards a system that:

  1. Captures vulnerabilities consistently.
  2. Links them directly to reasonable adjustments.
  3. Creates visibility across services.
  4. Recognises that vulnerabilities are dynamic, so they’ll inevitably change over time.

But even with this, services need to be designed for the flexibility of vulnerabilities.

Embedding vulnerability across the service journey

The real value of vulnerability data is realised when it’s applied consistently across end-to-end services. From first contact through to resolution, vulnerability insight should inform:

  1. How and when residents are communicated with.
  2. Which channels are used.
  3. Where flexibility is built into process.
  4. How colleagues and front-line are empowered to respond.

We need to completely shift our thinking from ‘what vulnerabilities do residents have?’ to ‘how are residents who need an adjusted approach experiencing our services?’.

In a sector facing increasing demand and complexity, using data to identify and respond to vulnerability isn’t about prediction or categorisation – it’s about designing services that work and designing services around real human behaviour, especially when residents need it most.