The single central record is one of the first things Ofsted or ISI will ask to see as part of their inspection. If your inspection is due tomorrow, this is a terrible moment to discover that a supply teacher who covered three days in October has no DBS date against her name. An incomplete SCR can raise safeguarding concerns during inspection if a school cannot demonstrate that the required checks have been completed and recorded appropriately.The record itself isn’t complicated. Keeping it complete, current and evidenced across every starter, leaver and supply booking, while running a school, is where things come unstuck. This guide walks through SCR compliance in practical, tutorial fashion. What the record is, who belongs on it, how to maintain single central record accuracy through the year, and how to be inspection ready every day rather than the night before.
What Is a Single Central Record?
A single central record is defined as the statutory register of pre employment and vetting checks for everyone working in a school or college. It’s a statutory requirement under Keeping Children Safe in Education (KCSIE), which is reissued each September, and it applies to every school in England, from maintained schools and academies to free schools, independent schools and colleges. All schools and colleges covered by KCSIE must maintain an SCR, although some recording requirements vary depending on the type of institution.
The golden rule: The SCR should be kept as a live document, with required pre-employment checks recorded before a person starts work, except where legislation or KCSIE explicitly permits otherwise. |
Getting Set Up: Single Central Record Step by Step
Start by working out exactly who belongs on the record. In our experience the gaps are rarely teachers, whose checks are drilled into every school’s routine. The people most often missed sit around the edges of the workforce, like the trustee appointed at a summer meeting, the sports coach who comes in on Thursdays, or the agency cover booked in a hurry on a Monday morning. Under KCSIE 2025, your record must cover:
All staff, including teacher trainees on salaried routes and supply staff employed directly by the school.
Agency and third party supply staff, even if they work a single day.
Members of the proprietor body, including academy trust members and trustees, and governors where checks apply.
Volunteers in regulated activity, and contractors who work regularly or unsupervised with pupils.
Then the data. Paragraph 274 of KCSIE 2025 sets out who must appear, and for each person the record must show which checks were carried out, the date each check was completed, and who verified it. Depending on the role, that means:
Check | Who needs it? | What should be recorded? |
|---|---|---|
Identity | Everyone included on the SCR | Date the check was completed and the name or initials of the person who verified it |
Enhanced DBS check (with children’s barred list check where required) | Individuals undertaking regulated activity where a barred list check is legally required. | Date the certificate was seen (or check completed) and the name or initials of the verifier |
Right to work | All staff | Date the check was completed and the name or initials of the verifier |
Prohibition from teaching | Qualified teachers and others who require the check | Date the check was completed and the name or initials of the verifier |
Section 128 direction | Individuals in relevant management roles in academies, independent schools and free schools | Date the check was completed and the name or initials of the verifier |
Overseas checks | Individuals who have lived or worked abroad where further checks are appropriate under KCSIE. | Details of the overseas checks completed, the date, and the name or initials of the verifier |
Professional qualifications | Staff in roles where specific qualifications are legally or contractually required (for example, QTS) | Date qualifications were verified and the name or initials of the verifier |
Missing dates or incomplete entries may prevent a school from demonstrating that required checks were completed appropriately during inspection. It feels harsh the first time you see it, because the school has usually done the check and simply not recorded who verified it or when. But that’s the point of the record. A drawer of documents isn’t compliance; a complete, verified row is.
How to Maintain Single Central Record Accuracy All Year
Setting the record up is a project. Keeping it accurate is a habit, and it’s the half schools struggle with. The pattern we see most often is a beautifully built September spreadsheet that’s quietly wrong by February half term. Nobody did anything careless. A cell got nudged, a tab was saved over, a version went round by email until no one knew which copy was real. The record drifts, and it drifts silently. Here’s the maintenance routine that actually holds. Treat it as the SCR compliance tutorial you hand over whenever the record changes owners:
Hold the record in one live system, connected to your staff records, so changes flow through once rather than being rekeyed.
Trigger vetting checks at the point of hire. DBS applications, right to work checks and references should be prompted by the onboarding workflow itself, never retrofitted after someone has started.
Set expiry alerts for anything time limited, so renewals are prompted before a check lapses rather than discovered after.
Restrict edit permissions to named, authorised staff, with an audit trail of every change.
Audit monthly, not annually. A named person cross checks the record against your HR system each month, so gaps become routine fixes instead of inspection findings.
Responsibility, Agency Staff and Retention
Who is responsible for the single central record?
Accountability sits at the top. Under KCSIE, the governing body or proprietor is responsible for ensuring the school meets its safer recruitment duties, with the headteacher and HR team running the record day to day. The designated safeguarding lead is a key user of the record, but the legal duty doesn’t rest with them, and both Ofsted’s school inspection toolkit and the ISI’s framework mean inspectors will ask leaders, not just administrators, how they assure themselves it’s accurate.
What about agency and supply staff?
For agency and third-party staff, the agency is responsible for carrying out the required pre-employment checks. Schools should obtain written confirmation that these checks have been completed and verify the individual’s identity when they arrive on site.
How long should records be kept?
Schools should follow their records management policy when deciding whether former staff remain on the live SCR or are archived, ensuring historical recruitment records are retained appropriately.
Single Central Record FAQs
Do academies and independent schools need a single central record?
Yes. The requirement applies to every school in England, including academies, free schools and independent schools, and to colleges. There are no exemptions, and both Ofsted and ISI will ask for the record at the start of an inspection.
Can the single central record be kept electronically?
Yes. KCSIE confirms the record can be held electronically or on paper, provided it is immediately accessible and clearly presented when requested. In practice an electronic record connected to your HR system is the only format that stays accurate as staff come and go.
Who checks the single central record during an inspection?
Inspectors will normally request and review the SCR during an inspection and may ask school leaders how they assure themselves it remains accurate. Many schools carry out monthly internal audits as good practice to help ensure the SCR remains accurate throughout the year.
Inspection Ready Every Day, Not Just Inspection Week
School office teams aren’t short of diligence. They’re short of hours, and the SCR is exactly the kind of always on obligation that shouldn’t depend on one person’s spreadsheet discipline or survive on goodwill through a staffing change. Whatever you record it in, the test is the same: could someone else pick it up tomorrow and prove every check was done.
Employing someone without the right to work can cost up to £45,000 per worker for a first breach and £60,000 for a repeat, and a missing or badly recorded check is what removes your defence. Yet the check itself takes minutes when you know the process. The right to work share code is at the centre of it, and with physical immigration documents now largely a thing of the past, every UK employer needs the digital routine down cold. Here’s the whole process, from what is a right to work share code through to keeping the evidence that protects your organisation.
What Is a Right to Work Share Code?
A right to work share code is defined as a nine character code, usually beginning with the letter W, that a candidate generates from their UKVI account so an employer can view their immigration status directly on the Home Office database. Since Biometric Residence Permits stopped being valid at the end of 2024, almost every non British, non Irish worker holds a digital eVisa instead, and the share code is how they prove it. For eVisa holders, the prescribed right to work check is carried out digitally through the Home Office service.
Key definition: a share code gives you a time limited window onto the candidate’s live immigration record. It stays valid for 90 days from generation and can be used by more than one employer in that time, so a candidate interviewing widely can share the same code with everyone.
One distinction worth knowing early. GOV.UK issues different codes for different purposes, and only a code generated for work will do. A code created for Right to Rent or a status check won’t give you a statutory excuse, which is the legal protection that shields you from a penalty if something later turns out to be wrong.
Step 1: How to Get a Right to Work Share Code from Your Candidate
Before you can run the check, you need two things from the candidate: their code and their date of birth. Here’s how to get both right first time.
Send them to the official service. The candidate generates the code through GOV.UK’s Prove your right to work service using their UKVI account. Third party sites can’t produce a valid code, so link them to GOV.UK directly.
Make sure they pick the work option. The service issues different code types. Choosing the right to work option produces a code starting with W; anything else will be rejected by the employer portal.
Collect the code and date of birth in writing. You’ll enter both exactly as given, so ask for them by email rather than over the phone.
Check the code is still in date. Codes expire 90 days after generation. If your recruitment process has run long, ask for a fresh one before you proceed.
Pro tip: a code for employment always starts with W. If you’re handed one with a different first letter, it was generated for the wrong purpose. Ask the candidate to repeat the process and select the work option.
Step 2: Run the Check on the Home Office Portal
With the code and date of birth confirmed, the employer side takes five minutes:
Go to the official portal. Use GOV.UK’s View a job applicant’s right to work service. This is the only route that gives you a statutory excuse.
Enter the code and date of birth exactly. A single wrong character returns an error, so check both fields before submitting.
Read the profile properly. Look for restrictions on hours or role types, and note any expiry date on the permission to work.
Match the photo to the person. The photograph on the digital profile must match the candidate in front of you, in person or on a video call. A mismatch makes the check invalid regardless of what the portal says, and this is the step busy teams skip most often.
Step 3: Save the Evidence and Secure Your Statutory Excuse
The portal result isn’t the finish line. Your statutory excuse only exists if you keep the proof, and this is where manual processes quietly fall apart:
Download the PDF result immediately. It’s time stamped and tied to the share code, and it is your evidence of a compliant check.
Keep it securely for the whole employment plus two years after the person leaves. That’s a legal requirement, not guidance.
Diarise a follow up check before any expiry date on time limited permission. A missed follow up is one of the most common ways employers lose their protection.
- File the record centrally in your HR system, not a local folder or an email thread. Illegal working enforcement visits rose 48% year on year to May 2025, according to Home Office transparency data, and scattered records are a liability in an inspection.
This is exactly the kind of repeatable, deadline driven admin that belongs inside an onboarding workflow rather than a spreadsheet, with the evidence stored alongside the rest of your HR documents and compliance records.
What’s Changing: Checks Are Extending Beyond Employees
Right to work compliance is about to get wider. The Border Security, Asylum and Immigration Act 2025 received Royal Assent on 2 December 2025, and it will extend right to work check obligations beyond direct employees to individuals on workers’ contracts, individual subcontractors and people engaged through gig economy platforms. The detailed implementation is being brought into force through secondary legislation. If your organisation engages casual, freelance or platform based workers without checking them today, that gap is closing, and the organisations with a clean, digital, repeatable checking process will absorb the change without breaking stride.
Make Every Check Consistent, Evidenced and On Time
Reliability comes down to three habits. Check before the first shift, never after. Store the evidence centrally with the date it was obtained. And diarise every time limited permission the day you record it, so the follow up check happens before the expiry, not after someone flags it.