We estimate that we will be able to surface a NINO for around 50% of users. For the remaining users, we'll still need to ask them to enter their NINO themselves.
For users where we can surface a NINO, we need to make sure the information we hold is correct before using it to verify their employment.
The design challenge
We considered using a single page where every user either confirms or enters their NINO. This would provide a consistent experience and avoid the need for a separate experience for users where we already have the information.
However, this would mean asking users to provide information that we may already hold, rather than making use of the data available to us.
There is also a significant user risk with playing back a NINO. If we show a user a NINO that they believe is incorrect, this could cause concern and leave them unsure about what they need to do to resolve it.
We therefore need to balance two things:
- making use of existing data where we can
- giving users a clear route forward if the information we show them is incorrect
What we’re testing
For users where we have a NINO available, we'll play it back to them and ask them to confirm whether it is correct.

This allows us to use the data we already have while giving the user an opportunity to identify an issue before it is used to verify their employment.
For users where we don't have a NINO available, we'll continue to ask them to enter it themselves.
What happens if the National Insurance number is incorrect?
One of the key areas we're exploring is what support users need if the NINO we show them isn't correct.
The NINOs surfaced from TRS come from the Teacher Pensions Service (TPS), which receives NINOs from employers and provides them to TRS. TRS then verifies these against HMRC.
Because the integrity of this data is important, we need to make sure that users who identify an incorrect NINO understand what they need to do next.
We're therefore exploring different ways of providing this guidance, including additional content in the service or providing a message that users could send directly to their employer.
Making sure support agents have all the information they need
We will also be making it clear to support agents processing the claims if the teacher has stated their National Insurance number is incorrect. This will ensure they have all the information they need to consider a claim.
Why we’re testing this in public beta
We considered removing the playback step and asking everyone to provide their NINO directly. However, this would prevent us from testing the use of existing data and moving towards a service that makes better use of information already available to us.
We've therefore decided to test the playback approach in public beta.
This will allow us to understand how often the NINO we surface is incorrect and, importantly, how users respond when they believe the information is wrong.
If we find that incorrect NINOs are rare and the experience works well for users, we can consider whether the playback step should remain in the live service. If we find that it creates significant confusion or concern, we'll use what we've learned to reconsider the approach.
The public beta will therefore help us test both the quality of the data and the user experience of making use of it.