Open mason-emily opened 3 months ago
Spoke to Nathan and want to highlight:
From Colin:
The problem is probably best to go to Pete and Tony. It’s about induction records getting jumbled, not necessarily the transfer. UCL in August withdrew 178 participants, they were active, but they’re not training with UCL. They were with other 5 lead providers but UCL had trained them at some point but hadn’t offboarded them properly. Teachfirst saw the most recent induction record. In august, UCL made induction records go back to front. It’s contractually fine, but the service didn’t like it. A SIT might transfer an ECT into their school, and it ends up that at the previous school that the teacher joined a school before they left, the induction records get twisted. It sent 178 emails to the wrong school, to withdraw participants, generated lots of queries. Teachfirst came to us with the SIT’s concerns. Induction record pointing at the wrong record. A teacher always has to join a school before they leave. Need logic checking that Claire is leaving school A on 29th October, joining on 1st October – that's impossible.
Emily added: when providers submit a withdrawal at the moment, they aren't able to give a date for the person leaving, so the date it's submitted is just recorded
When a transfer is reported, we should consider automatically withdraw from the provider A, to provider B.
This epic covers reporting relevant changes in a participant's situation via the school-facing service, including:
This does not cover:
Outcomes
Tasks
Related information
Colin let us know about issues some lead providers have with transfers currently, which then can confuse start dates and end dates.