As mentioned in the previous post, we're currently focusing on how we can make the existing user journey (which is a transactional user journey with lots of questions) more seamless by using DfE Identify. By asking a user to authenticate who they are, we can find information about them and ask them to confirm it rather than ask them to enter it.
This means we can remove questions such as asking the user about their name and date of birth, identifiers such as teacher reference number, and even information about what qualification route they took and when they qualified.
If a user answers to confirm the information we've found about them as correct, we've designed to ask the user only a handful of questions from the existing journey, which is for information we can't find about them from other sources.
If a user answers to say the information we've found about them is incorrect, we have initially designed to signpost the user to the existing journey which contains the full set of questions.
We're still working on how we present this guidance to users in an effective way, and we'll be working on the content for that in the coming sprints.