Building on the work of Find a lost TRN, we are reusing our record checking questions to create a service for identifying users.
We are starting by prototyping the service as part of the NPQ registration journey, replacing their questions about identity with our service.
This means capturing the following personal information:
- teacher reference number (TRN)
- name
- previous name
- date of birth
- National Insurance number
- QTS awarding body
This information is then used to match against the database of qualified teachers (DQT) and the continuing professional development (CPD) databases. We keep asking for information until we make a match, we need a minimum of 3 matching details.
The quickest match happens if TRN, name and date of birth match. In this case the user would not be asked for their National Insurance number or QTS awarding body.
Why NPQs
Users registering for an NPQ must currently have a TRN. Anyone can take an NPQ – including people working internationally and people not working in education. These users do not have a TRN and need to get one before they can register for their NPQ. This can be a painful and slow process.
TRNs are meant for qualified teachers. By giving TRNs to people studying an NPQ we are polluting the database of qualified teachers.
By replacing questions about identity, we can create a way to register for an NPQ without a TRN.
Design decisions
No passwords
Early designs focused on accounts and passwords. We needed to justify why a user needs another email and password to remember.
We iterated to a simpler concept: next time you use this service, you can use your email address to skip these questions.
Seamless integration with a service
While users are navigating questions in the checking records service, the design of the pages matches the NPQ design. This means showing the NPQ service name in the header. We do not warn users that they are crossing service boundaries.
However – the services will likely have different policies on:
- cookies
- privacy and data retention
- accessibility
We might also find that maintaining a single-design between the services becomes unmanageable, for instance if they begin to use different versions of the GOV.UK design system.
A clear differentiation might be needed.
Creating a ‘checking records’ section in the journey
While we do not warn users about service boundaries, we did find it necessary to bookend the checking records part of the journey.
The beginning and end of the journey use blue interruption cards to achieve this. (The opening bookend and the closing bookend
By creating this context we can talk about skipping ‘these’ questions when it comes to using an email address to sign in next time.
Video walkthroughs
Latest iteration
NPQ registration, checking records as a service
This version uses the ‘skip questions using your email address’ concept.
Existing NPQ journey
You can compare our current designs with a video walkthrough of the existing NPQ journey:
In this version a user must have a TRN to continue.
First iteration
A version of the design that creates accounts and asks for passwords.
NPQ registration, checking records as a service, accounts with passwords
Screenshots
What is your email address?
Confirm your email address
First time user: We will ask you some questions
First time user: Do you have a TRN?
First time user: Do you know your TRN?
First time user: What is your TRN?
First time user: Your name
First time user: Your name (if they have no TRN)
First time user: Your date of birth
First time user: Do you have a National Insurance number?
First time user: What is your National Insurance number?
First time user: Do you have QTS?
First time user: Did a training provider award QTS?
First time user: Next time you use this service
First time user: Check answers
First time user: Check answers (if they have no TRN)
First time user: Finished asking questions
First time user: Finished asking questions, but no account made
Check answers at the end of the NPQ registration journey
Repeat user: You’re signed in
