Merge pull request #353 from DFE-Digital/fix-sit-stuff

Update allowing-multiple-school-accounts.md

app/posts/ecf-v2/allowing-multiple-school-accounts.md

@@ -1,13 +1,15 @@
 ---
 title: "Allowing multiple accounts for schools"
-description: "Why we want to let schools have multiple accounts and no longer collect who the school induction tutor is"
+description: "Why we want to let schools have multiple accounts to register ECTs and mentors."
 date: 2024-09-06
 author: Claire Hughes
 ---
 
-When building new services to facilitate the delivery of the early career teaching reforms, we decided to make two key changes:
-- we will allow multiple user accounts for schools, as opposed to one
-- we will no longer collect who the school induction tutor is directly from schools
+When building new services to facilitate the delivery of the early career teaching reforms, we decided to allow multiple user accounts for schools, as opposed to one. 
+
+In ECF1, only one account can be created per school. This is because of a misunderstanding of the policy behind the early career framework. Originally, it was thought there was only allowed to be one school induction tutor per school. So, they thought only one person - the school induction tutor - would need to access the service. 
+
+However, in reality a school can have multiple induction tutors, and people other than these induction tutors might need to view and update data for EXTs and mentors.
 
 ## Allowing multiple user accounts for schools
 
@@ -22,17 +24,17 @@ This is because:
 
 In the new digital service we will allow multiple accounts per school. These will be administered by DfE Sign in, as discussed in the [Exploring using DfE Sign in](https://teacher-cpd.design-history.education.gov.uk/ecf-v2/exploring-using-dfe-sign-in/) post.
 
-## No longer collecting who the school induction tutor is
+## No longer assuming who the school induction tutor is
 
 In the current service, only one user is allowed to sign in. It's asked that this user is the school induction tutor. However, we know from research and support tickets this is not always the case.
 
-In the new service, we are currently not planning to collect from schools directly who the school induction tutor is.
+In the new service, we are not assuming every user of the service is a school induction tutor. This is because in reality we already know they aren't.
 
-This is because we could not directly infer it when we have multiple users and we don't want to add another question for users to think about and answer.
+We can't directly infer it when we have multiple users. In future, we might consider other ways to gather who the school induction tutor is.
 
-We could not find any evidence that we or lead providers needed to know who the school induction tutor was.
+Some lead providers need to understand who the school induction tutor is for training.
 
-However, we know that the lead provider needs to know someone to contact at the school who is adminstrating the registration deals of that mentor or ECT.
+We know that all lead providers need to know someone to contact at the school who is adminstrating the registration deals of that mentor or ECT.
 
 Therefore we need to work out how we can surface contact details for one or more of the school users to lead providers via the API.
 
@@ -42,8 +44,6 @@ This could be passing the emails for all school accounts, or just giving them th
 
 We're still a long way off releasing anything. However, we still need to consider the impacts of this decision and how we can still best meet the needs of users in a way that is technichally feasible.
 
-First, we should check with other teams in DfE if there are negative ramifications of this decision we haven't considered. We're hoping this design history will help us to do this.
-
-We need to check how we can make these changes whilst not adversely impacting the API lead providers use. We'll work with the team that currently works on the API to find out how we can best communicate school contact details to lead providers.
+First, we need to consider how we could find out who the school induction tutor is for a school, and if it's high priority enough to be part of our initial release.
 
-We also need to research with lead providers to see what would be most helpful to them.
+We also need to check how we can make these changes whilst not adversely impacting the API lead providers use. We'll work with the team that currently works on the API to find out how we can best communicate school contact details to lead providers.