Journey for users who’ve registered before
We did not build this design – instead we iterated it
Sometimes users are registering multiple times, there are 3 scenarios:
- They made a mistake with their course or provider and want to change it to something new
- They need to register twice, once for an NPQH and once for the Additional Support offer
- They are an admin user registering on behalf of people
The admin user problem
Consider a school user, say admin@school.gov.uk, registers Jane Doe for an NPQH. They then use the same email address to register Joe Bloggs for an NPQSL. The effect of this is that Jane Doe’s details get updated to Joe Blogg’s, the users are not adequately separated.
By creating a post-registration flow for existing users, we prevent the user details from being updated accidentally.
Bring the email question forward
We do not want to ask people that have registered before the same questions again.
We’ve brought the email part of the journey to the beginning, before the TRN and name change questions.
If a user signs in (using the code) with an existing email address, we’ll take them straight to the ‘You’ve registered before’ page.
The language on the email has been softened, the original content felt too abrupt when at the beginning of the journey.
Video walkthrough
What’s your email address?
You’ve already registered (one course)
You’ve already registered (multiple courses)
Add another course: Check your answers
Add another course: Check your answers (Additional Support offer)
