Ask a care provider how staff competency is tracked, and you will usually hear one of three answers. There is a spreadsheet. There is a shared folder. Or, most commonly, there is Sandra.
Sandra goes by many names, but every service has one. The administrator or deputy who just knows where everything is. Which folder holds the moving and handling sign-offs. Which version of the matrix is current. Why there are two files for the same staff member and which one to trust. Sandra is brilliant, and Sandra is a single point of failure.
Systems that work until they don’t
Here is the uncomfortable truth about spreadsheet-and-folder compliance. It genuinely works, most of the time. Day to day, records get kept, questions get answered, and the service runs. That everyday adequacy is exactly what makes the fragility invisible.
The failure modes only appear under stress, and they arrive together.
Sandra leaves, or goes on long-term sick, and it turns out the filing system was a mental model, not a system. An inspection lands with 48 hours’ notice, and assembling evidence for thirty staff across four storage locations becomes a two-day emergency. A safeguarding inquiry needs proof that a specific staff member was assessed as competent on a specific date, and the spreadsheet, edited by six people over three years, cannot say who changed what or when.
None of these is exotic events. Staff turnover, inspections and safeguarding processes are the normal weather of social care. Building compliance on tools that fail in normal weather is the definition of fragility.
Why spreadsheets specifically struggle
The spreadsheet deserves a fair hearing, because it is flexible, free and familiar. Its weaknesses are structural, though, and no amount of care fixes them.
It has no memory. Overwrite a cell and the previous truth is gone, which is fatal for evidence. It has no controls. Anyone with access can edit anything, and versions multiply. It has no awareness. It cannot tell you an assessment expired last Tuesday, because it does not know what Tuesday is. And it has no view. It shows rows, not the answer to the question a manager actually holds. Who needs attention this week, across every role and every site.
Every one of those gaps gets bridged, daily, by human effort. Usually Sandra’s.
What operational resilience looks like
Fixing this is not about abandoning what works. It is about moving three properties into the system itself, so they stop depending on individual heroics.
Permanence. Records of assessments and sign-offs should be tamper-evident and dated, so evidence from two years ago is still evidence today.
Visibility. One live view of the whole workforce, showing who is compliant, who is overdue and where the gaps sit, available to any authorised manager in minutes.
Continuity. The system should survive any single person leaving. If the knowledge walks out of the door with an individual, it was never organisational knowledge at all.
A fair test for your own setup
Try this thought experiment. If your most knowledgeable administrator won the lottery on Friday, how would Monday go? If the honest answer involves a long and painful reconstruction, the service is running on borrowed resilience. Centralised, real-time workforce records are sometimes sold as a luxury for large groups. They are closer to basic infrastructure, like a fire alarm. You do not buy one because today is likely to go wrong. You buy one because someday it eventually will.