DBS renewals: the compliance task most homes get wrong

Almost every home has a process for checking DBS status when someone is hired. Far fewer have a reliable process for catching renewals three, four homes and a dozen staff changes later, when the person who set up the original spreadsheet has moved on — the practical version of this problem, and how to fix it, is covered in tracking DBS and training renewals.

The pattern that causes real problems is quiet drift: a renewal date sitting in a spreadsheet nobody opens unless someone remembers to, until it's flagged in an inspection or, worse, after someone's already been working for weeks on an expired check.

Training expiry follows the same shape, just with more moving parts — safeguarding refreshers, first aid, medication administration, each on its own cycle, for every member of staff, across however many homes an organisation runs.

The fix isn't more diligence from already-stretched managers. It's removing the dependency on someone remembering to check a spreadsheet, and instead surfacing what's expiring — and who it affects — automatically, before it becomes a gap rather than after.

A realistic scenario

Picture a small provider running two homes with around fifteen staff between them. The DBS spreadsheet was set up carefully by a deputy manager who's since moved to a different role. The current manager knows it exists, glances at it occasionally, but has never been the one who built the habit of checking it weekly. Six months pass. Nobody notices a renewal quietly slipping past its date until it surfaces — sometimes at a routine audit, sometimes worse, at inspection. Nothing about this scenario involves anyone being careless in any single moment; it's a slow accumulation of a process that depended on one person's personal discipline outliving their time in the role.

Why this specific compliance task is so prone to drift

DBS renewals are unusual among compliance tasks because they're infrequent per person — typically once every few years — which makes them easy to deprioritise relative to weekly or monthly tasks that stay top of mind through repetition. A task that only comes around once every few years per staff member is exactly the kind of thing that falls through the cracks of institutional memory, especially across staff turnover in the manager role itself, which is common enough in this sector to be a real, ongoing risk rather than a hypothetical one.

What the update service can and can't do for you

Some staff will be subscribed to the DBS update service, which allows an existing check to be kept current through online status checks rather than requiring a fresh application each time. Where that's the case it changes the mechanics of renewal, but not the underlying discipline required — someone still needs to actually run the status check at the right interval and record that it was done, rather than assuming a subscription alone means nothing further is needed. It's worth confirming, for each staff member, whether they're on the update service or not, because the two groups need slightly different renewal processes and it's easy to accidentally apply the wrong one.

It's worth reviewing this list itself periodically too — who's on the update service can change over time as individual staff opt in or out, and a tracker that assumes the split is fixed once and never revisited will eventually apply the wrong process to someone without anyone noticing until a check is actually due.

Finally, it's worth treating a clean run of on-time renewals as something to actively notice and reinforce, not just a non-event. A quiet acknowledgement that the tracker has caught everything for another quarter, however small, helps keep the underlying discipline visible as a genuine achievement rather than an invisible task that only gets attention when something goes wrong.

That reframing matters more than it sounds — a task that only ever gets attention when it fails will always feel thankless, and thankless tasks are exactly the ones that eventually get deprioritised under pressure, however important they genuinely are.

Get the underlying system right once, keep it visible, and DBS renewals stop being the recurring source of anxiety they are for so many homes, and become instead one of the more genuinely boring, well-controlled parts of the compliance calendar — which is exactly where it belongs.

It's a small, unglamorous fix for what's genuinely one of the more consequential compliance risks a home carries, and that gap between how mundane the fix is and how serious the risk it addresses is exactly why it's worth taking seriously rather than leaving to chance.

Most homes that get this wrong aren't careless — they simply never built the underlying system properly in the first place, and that's a genuinely fixable gap, not a character flaw in how the home is run.

What good practice actually looks like

• –A tracker that's owned by the role, not the individual — so it survives a change of manager without anyone having to rebuild it from scratch
• –A standing, calendared check rather than an ad hoc glance whenever someone remembers
• –Renewals flagged well in advance — 60 to 90 days — so there's genuine time to act, not a scramble against an expiry that's already close
• –A named backup who also has visibility, so the whole process doesn't depend on a single person