The Single Central Record is the most important compliance document in education recruitment. It’s the first thing auditors ask for. It’s the document that determines whether a school can evidence its safeguarding obligations.
And for most agencies, it’s a spreadsheet.
The spreadsheet problem
Spreadsheets are flexible. That’s their strength and their weakness. They don’t enforce data integrity. They don’t flag when a DBS check has expired. They don’t tell you that a reference was received but never reviewed.
They record what someone typed. Not what actually happened.
What auditors actually look for
Auditors don’t just want to see that a check was done. They want to see when it was done, by whom, what the outcome was, and whether it was done before the candidate was placed.
A spreadsheet can’t answer those questions reliably. A system can.
The shift from record-keeping to compliance execution
The SCR shouldn’t be something you maintain. It should be something your system produces — as a by-product of actually running compliance.
When checks are executed automatically, every action is logged. Every document is timestamped. Every decision is recorded with a clear audit trail.
The SCR becomes an output, not an input. That’s the difference between record-keeping and compliance infrastructure.