The sample dashboard below (Sample006) shows a simple table of my pensions, assuming they can all be digitally found, in “Date payable from” order (earliest date first).
We know from previous research that all these dates will be confusing for users. This is discussed below the dashboard.
Table in payable from date order
|Prudential Staff Pension Scheme||1 Oct 1991||7 Jul 1995||8 Aug 2027||£1,130 a year|
|Prudential Staff Pension Scheme||9 Apr 1996||31 Dec 1998||8 Aug 2027||£1,020 a year|
|Pension Protection Fund||5 Oct 1987||? ??? ????||8 Aug 2027|
8 Aug 2032
|£140 a year|
£1,500 a year
|Scottish Widows||1 Sep 2020||8 Mar 2021||8 Aug 2032||£120 a year|
|Centrica Pension Plan||1 Jan 1999||28 Aug 2021||31 Aug 2032||£2,160 a year|
|State Pension||8 Aug 1983||13 Aug 2021||8 Aug 2034||£9,490 a year|
|Aon Master Trust||1 Feb 2001||13 Aug 2021||8 Aug 2041||£3,750 a year|
|Aviva||1 Nov 2003||8 Jul 2021||8 Aug 2041||£12,500 a year|
|Nest||1 Jul 2016||31 Mar 2021||8 Aug 2041||£19,100 a year|
Sample006 is exactly the same table as Sample004 except the pensions are ordered by “Date payable from”, earliest first. However, this mixes up the recent and historic amounts again (which Sample005 tried to solve), so we need to test how users feel about that too.
This is all pretty confusing. We need to explore all these three different dates for each pension (i.e. “Date started”, “Date last updated” and “Date payable from”) in a bit more detail. See Sample007 for a discussion about these three dates.