Sisra Analytics: How do I ensure my student data reflects the Spring Census?

Overview

This article explains how to ensure your KS4 and KS5 leavers' data reflects that of the Spring Census. It lists two approaches you can use to align the student information stored in Sisra Analytics with the data captured during the Spring Census.

The Spring Census takes place on the third Thursday in January each year. It determines:

  1. The specific students reported on and the number of students.
  2. The students’ corresponding filter values, for example, SEN codes and Looked After. 

A small number of schools have reported that in some situations, a student’s filter value may have changed between the Autumn Checking Exercise and the Spring Census. The DfE bases exam result reporting on the student data from the Spring Census. For this reason, ensuring your data matches that of the Spring Census to ensure the accuracy of your student information for reporting in headline figures on Results Day.

Prerequisites

You must be an administrator.

Approaches

Depending on how many changes you need to make:

Option 1: Manually update Sisra Analytics (for a small number of changes)

  1. Use each student’s status to control whether they're included in school performance measures or not.
  2. Manually edit a student's individual filter values, for example, SEN codes or Looked After status as needed.

Option 2: Import a file (for larger updates)

  1. Prepare a Microsoft Excel spreadsheet comprising student data based on the Spring Census.
  2. Import this file into Sisra Analytics to apply updates in bulk.

If you have students in alternative provision, confirm whether they’ll be reported through your school and set their student status accordingly in Sisra Analytics.

Both options are covered in further detail in the Sisra Analytics articles listed below.

Related information

Updated

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request