Updating and maintaining the current CLA cohort

NCER -  Content Editor
NCER - Content Editor
  • Updated

Key Facts...

This import is restricted to users with Keypas CLA permissions so you may need to ensure that all users who should be accessing this import, such as a virtual head, have the permissions to do so. 

Permissions.png

Your current CLA cohort can be viewed in Insight for all Key Stages. Please note that this dataset is only available in Nova for KS4 reports using the Results Day source. 

Your current CLA cohort will initially be populated by the children that were part of your last SSDA903 census return. See the guide to importing the SSDA903 for further details. The children in your SSDA903 will be matched to school census records where possible so details such as ethnicity and language can be included.

The purpose of the import process described below and the accompanying Keypas grids are to allow you to update your CLA cohort, and this can be done in a couple of ways:

  1. If a child in your SSDA903 cannot be matched to a school census record, you can update the record in your current CLA cohort with information such as ULN or ethnicity.
  2. If there are children that are not in your SSDA903 because they have become looked after since your last census return, you can add these children to your current CLA cohort using the import.

Why update the current cohort?

Reports associated with the CLA cohort are based on the cohort as it was on the census date. By the time that the census is submitted to DfE that information is already 3 months out of date with new children being added to the cohort and some no longer looked after. By updating the current cohort (as well as using the process to correct any errors/omissions) you can have a view in reports of both the 'statutory' SSDA903 cohort that will mirror that used in DfE statistics, but also the option to produce reports based on the current, up to date cohort (which can be updated as often as you need to during the year)

Despite the name 'Current', this cohort does not have to be the most up to date version of the cohort. You could go back to a previous point for reporting. The only limitation is that you can only hold one Current CLA cohort in Nexus per year at a time, though this can be changed as often as needed. (The SSDA903 version of the cohort is separate and not affected by loading or changing the Current CLA cohort)

 

Current CLA Cohort Import

Your import file for the current CLA cohort can be exported from the Keypas grid called Manage Current CLA Cohort.

CLA_Current_Cohort_Grid.gif

For those children already on the grid you can manually update the records directly on the grid or export the grid to update their information. 

Once you have updated the records in your CSV or added new children you can import this data back into Nexus.

Keypas>>Imports>>Import New File>>Current CLA Cohort

You don't need to re-import ALL children if you have no updates for those records, but it is also acceptable to do this rather than removing them from your CSV.

You can also get a copy of the CSV template from the link on the import page, if you are only importing new children and not updating existing ones.

mceclip0.png

 

Previous step

Obtaining and importing the CLA data (SSDA903)