The sample dashboard below (Sample004) shows a simple table of my pensions, assuming they can all be digitally found, in chronological order. Click or tap the Pension names to go to each pension scheme’s / provider’s website to find out more details about each pension.

(Sample004 is similar to the PDP mock-up – see PDP July 2021 research, Figure 3, page 14.)

Table in start date order


Date last
Date payable
State Pension8 Aug 198313 Aug 20218 Aug 2034£9,490 a year
Pension Protection Fund5 Oct 1987? ??? ????8 Aug 2027
8 Aug 2032
£140 a year
£1,500 a year
Prudential Staff Pension Scheme1 Oct 19917 Jul 19958 Aug 2027£1,130 a year
Prudential Staff Pension Scheme9 Apr 199631 Dec 19988 Aug 2027£1,020 a year
Centrica Pension Plan1 Jan 199928 Aug 202131 Aug 2032£2,160 a year
Aon Master Trust1 Feb 200113 Aug 20218 Aug 2041£3,750 a year
Aviva1 Nov 20038 Jul 20218 Aug 2041£12,500 a year
Nest1 Jul 201631 Mar 20218 Aug 2041£19,100 a year
Scottish Widows1 Sep 20208 Mar 20218 Aug 2032£120 a year

Discussion topics

What are the problems with a table format like this?

Readability: The table really has to be a multi-column table, showing each pension’s multiple dates (which I’ll discuss later). But, given many users will be using dashboards on their mobile phones, will a multi-column table be easy to interpret on a phone? Rotating the phone sideways could help a bit:

Invalid user totalling: In addition to the table formatting issues, showing a column of amounts (in this case, the far right “Annual amount” column) is an invitation to the user to add these up to get a total.

In Sample001 and 002, I can’t see my different pension amounts at the same time. When I expand one pension, the other pensions collapse. This is deliberate.

When pension amounts are shown together, there’s a natural tendency to add them up.

We know from the extensive Dutch research in 2019 (see The Netherlands page) that people want to see their total pension income. So if the different pension income amounts are displayed next to each other (for example, in a table as above), users will very likely attempt to add them together to get a total. Beta testing should explore the extent to which users instinctively do this.

But of course it’s not valid to add together these amounts because they are not updated to the same date.

The “Date last updated” column shows that some of the Annual amounts are out of date (for example, see my two Prudential pensions which are as at 1995 and 1998). Unless the user carefully studies the “Date last updated”, they might not realise this.

One way to make this easier to see and understand might be to display the pensions in order of “Date last updated”. See Sample005 for an example of this.