Iteration 2

We reviewed the first iteration with designers from adjacent teams and made some improvements based on their feedback.

Service name

We tweaked the service name from “Find your TRN” to “Find out your TRN”.

Emailing the result instead of magic links

Iteration 1 verified the user’s email by sending them a magic link. This was done to enable an audit trail of the TRN requests, by ensuring that the recipient of the TRN had access to the email address at the time of the request.

The Apply for teacher training team fed back to us that magic links are a source of friction for their users, because:

magic links move the user to a different tool (their inbox) and back, thus fragmenting the journey
the email sometimes doesn’t arrive quickly enough
the email can get lost in the spam folder

Since we wanted to avoid that friction early on in the user journey, we:

took out the magic link verification
stopped displaying the TRN at the end of the successful journey, and added the TRN instead

This still ensures that only the person with access to the email address can access the TRN.

Simplifying the “do you have a TRN” interaction

Iteration 1 had dedicated pages for “Do you know if you have a TRN?” and “Do any of the following apply to you?”. For iteration 2, we combined these into a single “Check if you have a TRN” page.

In early user research, users haven’t been getting stuck or misreading this page.

Checking your answers for the success path

We added a “check your answers” step for both success paths:

when the email matches exactly
when 3 pieces of data match

This helps the user to catch any typos in the email address that they entered.

Previous names

The name page in Iteration 1 included contextual guidance about previous names, to help those users who had changed their name since their data was added to DQT e.g. as a result of marriage, divorce or a legal name change.

For Iteration 2, we introduced conditional previous name fields, to allow previous names to be matched against the DQT record. This affects the matching logic, meaning there are 2 possible scenarios for a successful name match:

provided current name matches current name in DQT
provided previous name matches current name in DQT

National Insurance number

We turned the prompt for a NINO into a Do you have a NINO? yes/no question, to avoid a separate link.

ITT provider question

We tweaked the question about the user’s teacher training provider, to avoid having 2 ‘Yes’ options.

New screen flow

Screen flows PDF

Screenshots

Check if you have a TRN

Your email address

Your name (previously changed)

Your date of birth

Do you have a National Insurance number

Have you ever been enrolled in initial teacher training in England or Wales

have-you-ever-been-enrolled-in-initial-teacher-training-in-england-or-wales.png

Other manuals

Standards and assurance

Working in DfE