What the UK school census asks for, module by module
The school census is not really a form. It is a request for data your school already holds, presented in a particular shape on a particular date. Schools that find it painful are usually not struggling with the submission — they are struggling because the data was never captured in one place.
Where each part comes from
Pupil-level data — the student record
Name, date of birth, gender, UPN, ethnicity, first language, EAL status, address and the enrolment status on census day. All of this belongs on the student record and should be captured at admission rather than gathered in January.
The field schools most often scramble for is UPN, particularly for in-year admissions. A pupil arriving mid-year brings a UPN with them; if it was never entered, somebody spends census week chasing the previous school.
Attendance — the attendance module
Sessions possible, sessions attended, and absences broken down by statutory code for the relevant period. This is the part that is either trivial or impossible: if you have been marking AM and PM sessions with the statutory code set all year, the numbers assemble themselves. If staff have been using approximations of the codes, no amount of effort at census time recovers it.
Exclusions — behaviour
Suspensions and permanent exclusions with dates, reasons and session counts. These need to be recorded as exclusions with statutory fields at the time they happen, not reconstructed from letters in a folder.
SEN — inclusion
SEN provision type (SEN support or EHCP) and primary and secondary need. This has to reflect the position on census day, which means the inclusion register needs to be current rather than updated annually.
FSM and Pupil Premium — the student record
Eligibility, and the date eligibility started. The start date matters for funding and is the field most often left blank.
The three that are always wrong
1. Address, when a family has moved
Families tell the class teacher, not the office. Unless there is a route from “mentioned at pick-up” to “changed on the record”, the census carries the old one. A parent-facing contact-update request solves it.
2. FSM start dates
Eligibility gets recorded; the date it began often does not. It affects funding, and it cannot be reconstructed later.
3. Attendance codes used loosely
Staff reach for a familiar code rather than the correct one — authorised where it should be unauthorised, or the wrong code for an educational visit. Every one of those lands in a statutory return. The fix is upstream: a short code set, named clearly, with the ambiguous ones removed from the picker entirely.
The step worth adding
Validate before submitting. A validation screen that flags missing UPNs, blank FSM start dates, pupils with no attendance and SEN records without a provision type turns census week from an archaeology exercise into a review. The data is nearly always there; what is missing is the check that it is complete.
CampusFlo prepares the census fields as a configurable export with a validation screen before submission, and keeps a submission log with a snapshot. The UK profile covers the statutory codes, UPN handling and SEND stages.