Getting a DBS check done for a new cleaner is the easy part. You send them the link, they complete it, the certificate comes back a few weeks later, and it goes in a folder, physical or digital, next to their contract. Job done, or so it looks. The actual hard part starts two, three years later, when that certificate is quietly ageing in the same folder while nobody is watching the calendar, and a client asks to see current vetting for everyone on their site.
A DBS check from three years ago isn’t vetting at that point, it’s a screenshot of vetting, a record of a decision that was correct once and has said nothing about that person since. Most cleaning companies that get caught out here aren’t cutting corners on purpose. They simply never built a system for tracking renewal dates across a growing staff roster, because when there were six cleaners it was easy enough to remember, and at sixty it isn’t.
Why the renewal date matters more than the original check
A DBS certificate is a snapshot at the point it was issued. It doesn’t update itself, and unless a cleaner was actively subscribed to the DBS Update Service from day one, there’s no ongoing feed telling you or the client whether anything has changed since. Commercial clients increasingly build a renewal window straight into the contract, often three years, sometimes annually for higher-risk sites, and expect you to be tracking it without being chased. The same procurement teams asking about DBS status before they’ll sign a contract in the first place are the ones who’ll ask again eighteen months later, and a company that can only answer the first question has only solved half the problem.
Where renewal tracking actually breaks down
It rarely fails because nobody cares. It fails because the process depends on someone remembering, months in advance, to check a spreadsheet column that nobody else looks at, for a growing list of names with different start dates and different renewal cycles. Add staff turnover, a few maternity leaves, and a couple of people moving between sites with different client requirements, and the spreadsheet stops being reliable roughly the same moment it stops being small enough to eyeball in one sitting.