In ECF1, we ask schools to tell us the AB they're working with. We ask for the whole school, despite the fact in reality schools may work with more than 1 AB. However, in ECF2 we want to change this so the AB is given on an individual ECT level. This is typically for 2 reasons:
1) The ECT cannot work with the usual AB the school works with, as they did initial teacher training with that AB
2) The ECT has already started induction at another school, and they're sticking with the same appropriate body at a second school
There will be a concept still of a school default of AB, LP, DP and programme type to speed this up.
In ECF2, we're going to continue to ask schools the appropriate body. We think this is still useful because:
whilst this isn't surfaced to lead providers now, we can pass this on to LPs which might be helpful when they need to check about if induction is extended, reduced or other issues
it can pass on to the AB in the new induction service this school intends to work with them, and hopefully prevent schools forgetting to register with an AB which can lead to delays in induction
we hope by gathering data from schools in the DFE service, we can minimise schools having to reach out to loads of other organisations to register initially, but instead the AB can come to them
where an AB has forgotten to claim an ECT's induction, this can remind them
where a school is mistaken, the AB they've 'nominated' can reach out to them to solve the issue and make sure they're set up with the right AB
However, now the new induction service is being created, we'll be storing the AB when the AB claims the ECT. This might not always agree with what the schools put. We need to work out how we want to store the school-submitted AB, and the AB-submitted AB.
We need to think through how this impacts induction periods and other parts of the data model.
Some of the options Tony and I discussed are:
Creating a new table to hold expressions of interests/school-submitted data on what organisations they're working with
Write what the school has submitted in the data model as currently planned, and over-write it with what the AB states if needed
Create some other kind of temporary table to store data and delete if necessary
What?
Work out how this impacts the data model
Work out the best way to store school-submitted appropriate body info
Out of scope
No code work here, just working out how it impacts the data model
Why?
In ECF1, we ask schools to tell us the AB they're working with. We ask for the whole school, despite the fact in reality schools may work with more than 1 AB. However, in ECF2 we want to change this so the AB is given on an individual ECT level. This is typically for 2 reasons: 1) The ECT cannot work with the usual AB the school works with, as they did initial teacher training with that AB 2) The ECT has already started induction at another school, and they're sticking with the same appropriate body at a second school
There will be a concept still of a school default of AB, LP, DP and programme type to speed this up.
In ECF2, we're going to continue to ask schools the appropriate body. We think this is still useful because:
However, now the new induction service is being created, we'll be storing the AB when the AB claims the ECT. This might not always agree with what the schools put. We need to work out how we want to store the school-submitted AB, and the AB-submitted AB.
We need to think through how this impacts induction periods and other parts of the data model.
Some of the options Tony and I discussed are:
What?
Out of scope
No code work here, just working out how it impacts the data model
Helpful links or other information
I did some analysis here on how we might want to handle this: https://educationgovuk.sharepoint.com/sites/TeacherServices/_layouts/15/doc.aspx?sourcedoc={ac32389e-06a8-4d1e-8f26-95defcdd0961}&action=edit