Prevention is back in the conversation across social care. It sits in the Care Act 2014, where section 2 places a duty on local authorities to prevent, reduce or delay needs for care and support. It runs through Regulation 12, which asks providers to assess the risks to people’s health and safety and do all that is reasonably practicable to mitigate them. Most care leaders would say they already believe in it.

Belief is rarely the problem. Prevention fails in practice because the way most services are organised makes an early observation harder to capture than a late crisis.

Why crises are easier to record than concerns

A fall, a medication error or a safeguarding incident has a clear route. There is a form, a named person to tell, a timescale and a follow-up. Everyone knows what to do.

A small change does not. A person who is eating a little less, seems more withdrawn than last week or is taking longer to get ready in the morning rarely fits a category. The care worker who notices it may not be sure it is worth mentioning. If mentioning it means finding the right form, logging in to a separate screen or phoning the office at a busy time, the observation often stays in their head. By the time the pattern is obvious, it has usually become the incident.

That is not a failure of care. It is a failure of design.

The chain that prevention depends on

Prevention works as a chain: someone observes, someone records, someone acts. Each link has its own conditions.

  • Observe: staff need enough time with the person to notice change. Visit or shift patterns built with no slack squeeze out the moments where noticing happens.
  • Record: logging a concern needs to be as easy as the observation itself. A free-text note or a simple “something has changed” option in the care record is often more useful than a detailed form nobody completes.
  • Act: someone has to read what is logged, look for patterns and decide what happens next. If recorded concerns never lead to a response, staff quickly learn that raising them is pointless.

Break any one link and the others stop mattering.

Permission matters as much as process

The weakest link is often permission. Staff need to know that raising a small concern is expected, not a nuisance, and that they will not be asked to justify it before anyone listens. That comes from how managers respond the first few times far more than from any policy.

A useful habit is to make low-level concerns a standing item in handovers, supervisions and team meetings. Not “any incidents?” but “what have you noticed?” The question shapes what people pay attention to.

Making it routine

Treating prevention as an operational discipline means building it into rotas, records and management routines rather than relying on individual goodwill. It means checking regularly whether early concerns are being logged at all, and what happened after they were.

Here is a challenge for this week. Pick one person you support and look back through the last month of their records. Can you find an early observation that was logged, and evidence of what someone did about it? If you cannot, which link in the chain broke?