What is find data?
Find data refers to the data items that the pensions dashboards ecosystem will send to providers in a find request. You can find a full list in the Data Usage Guide but, in summary, it is the personal data and contact information that providers will receive, so they can look inside their own record keeping systems, to see if the find request relates to one of their members. We call this process of looking, ‘matching’.
What do I do with it?
Each pension provider will be responsible for deciding which of the data items it will use to match against its members’ data. To do that, you will need to measure how much you trust the data you hold to be correct. Once you know that, you can decide what your matching process should be.
You can find initial industry guidance on how to approach these decisions, which has been developed in collaboration with a number of industry bodies, on the PASA website. The Pensions Regulator (TPR) is planning to issue guidance on matching.
Please note that each data provider will need to record and store details on the decisions made on their chosen matching processes (ie the policy and criteria used) plus any changes to this for a period of at least six years.
Steps to connection
Perform an audit of the required data items. Understand what data gaps exist and how you will plan to fill them.
Identify what key data is held in a non-digital format. Understand how you will input this information into your core database to ensure this can be accessed digitally, on-demand.
Understand how your data cleanse activities for dashboards can complement your other data cleanse projects. Where possible, this may reduce your overall effort in cleansing data.
Determine the matching approach you will use to process a find request. This will involve determining which personal data fields you will compare, such as name, date of birth and National Insurance number for example, to validate a positive match. We suggest you work with your software provider and/or administrator to help identify the best approach. Remember to record the decisions and processes that you decide on.
Perform an audit of the data fields used to perform the matching process, to understand what gaps may be present.
Consider your approach to partial matches.
Consider how you will continue to monitor the accuracy and presence of find data.
Progress any required data cleansing or work required to fill missing data items.
Maintain ongoing data validation and audit of key data fields over the period prior to connecting with the ecosystem.
You will have agreed an approach for how you will deal with partial matching.
You are confident in your ability to provide all the required data items.
Any non-digital data has now been loaded on to your core systems and is now digital.
You have an agreed matching basis. This has been tested and assessed through the testing of your find functionality prior to your agreed staging date.