Guidance

SLASC 2018: technical specification

Technical specification and validation rules describing the requirements for the school-level annual school census (SLASC) 2018.

This publication was withdrawn on

These documents are for the 2018 school-level annual school census (SLASC). For the current census, visit our guide to submitting data for SLASC.

Applies to England

Documents

School-level annual school census 2018: validation rules

Request an accessible format.
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email alternative.formats@education.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

School-level annual school census 2018: validation rules

Request an accessible format.
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email alternative.formats@education.gov.uk. Please tell us what format you need. It will help us if you say what assistive technology you use.

Details

This is technical information about submitting data for the school-level annual school census 2018.

It’s for:

  • suppliers of software for school management information systems (MIS)
  • users of school MIS software

It applies to registered independent schools only.

The specification describes:

  • what data schools should supply
  • how to structure the data in XML

Software suppliers should use the list of validation rules so that schools can validate the data they submit.

You should also read the common basic data set (CBDS). This defines common data items that schools use in MIS software and that we use in our data collections.

More guidance on submitting data for the school-level annual school census is available.

Updates to this page

Published 14 July 2017
Last updated 31 January 2018 + show all updates
  1. Updated validation rules spreadsheet. The document's version history explains the changes.

  2. Updated validation rules documents. The documents' version histories explain the changes.

  3. Updated business and technical specification. The document's version history explains the changes.

  4. Updated documents. The documents' version histories explain the changes.

  5. Updated documents. The documents' version histories explain the changes.

  6. First published.

Sign up for emails or print this page