Guidance

Alternative provision census 2016: technical specification

Business and technical specification for local authorities and software suppliers to prepare for the alternative provision census 2016.

From:
Department for Education
Published
20 July 2015
Last updated
24 December 2015 — See all updates

This publication was withdrawn on

These documents are for the 2016 alternative provision census. For the current census, visit our guide to submitting data for the alternative provision census.

Applies to England

Documents

Alternative provision census 2016: business and technical specification, version 1.4

Ref: DFE-00218-2015

PDF, 691 KB, 34 pages

Alternative provision census 2016: validation rules, version 1.8

MS Excel Spreadsheet, 210 KB

This file may not be suitable for users of assistive technology.

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 alternative provision census 2016.

It’s for:

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

The specification describes:

  • what data local authorities should supply
  • how to structure the data in XML

Software suppliers should use the list of validation rules so that local authorities 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 alternative provision census is available.

Published 20 July 2015
Last updated 24 December 2015 + show all updates

  1. Updated the validation rules document. See the document's version history for description of changes.

  2. Updated the validation rules document to version 1.7. Changes are described in the version history within the document.

  3. Updated technical specification to version 1.4. Changes are set out in the document's version history.

  4. Updated the validation rules document. Change is described in the document's version history.

  5. Updated the validation rules document. Changes are set out in the document's version history.

  6. Updated the business and technical specification and validation rules documents. Changes are set out in the documents’ version histories.

  7. First published.

Related content