A briefing for corporate advisers on what the 31 October 2026 pensions dashboards connection deadline actually requires, what happens to schemes that miss it, and why the member engagement conversation is about to change once dashboards go live to the public.
In reading this article you will understand:
- Why the 31 October 2026 connection deadline matters, and roughly where the market stood against it as of mid-2026.
- What tPR’s compliance and enforcement policy means for a scheme that misses its deadline, and where the Regulator draws the line between genuine non-compliance and a third-party delay.
- Why a scheme being connected and a scheme being visible to members are two different milestones, and how to prepare employer clients for the point at which the second one arrives.
The clock on pensions dashboards is nearly out. By 31 October 2026, every occupational pension scheme with 100 or more relevant members, and every FCA-regulated personal pension provider, must be connected to the central dashboards architecture, the infrastructure that lets a saver log in once and see every pension they hold in one place. As of July 2026, around 85% of in-scope pension records, more than 70 million of them, were reported as connected, with almost 1,500 providers and schemes having completed the process since April 2025. That looks like a market comfortably on track. It also means around 15% of records, and an unknown but real number of schemes serving your employer clients, had not yet connected. The question worth asking now isn’t whether a client’s scheme is on track to connect. It’s whether it actually has.
The current position
Connection was never a single deadline. It is a staged timetable set by the Department for Work and Pensions and run by scheme size and type. The largest master trusts led the way, with those of 20,000 or more members due to connect by 30 April 2025 and other schemes of that size a month later, followed by progressively smaller bands through 2025 and 2026. The final bands, schemes with 100 to 124 members, were due to connect by 30 September 2026. 31 October 2026 is the long-stop: the point by which every in-scope scheme, whatever its own staged date, must be connected regardless. Schemes with fewer than 100 relevant members sit outside the mandatory regime and may connect voluntarily, but only after the deadline has passed.
The practical point is that connection is a status to verify, not an assumption to make from a provider’s size or reputation. There is no official public register of connected schemes to check against, so ask the scheme’s administrator to confirm its connection date directly and in writing. Where a client’s scheme connects through a third-party administrator, as most do, check that the third party’s progress actually covers that specific scheme; a large administrator’s overall status doesn’t automatically extend to every scheme it runs.
What happens if a scheme misses the deadline
tPR has been explicit that missing the deadline isn’t a paperwork problem to shrug off. Nina Blackett, then its interim executive director of strategy, policy and analysis, put it bluntly in a blog on dashboards duties: “Failure to meet your duties is therefore not an option.” Where tPR identifies or suspects a breach, its escalation path runs from investigation through compliance notices to penalty notices, calibrated to the breach’s nature and the number of members affected.
The regulators have shown some pragmatism about one specific failure mode, though: a scheme that has done everything asked of it but is stuck waiting on an administrator or software provider that hasn’t yet connected. tPR and the FCA have both said there will be no regulatory intervention where a scheme misses its connect-by date solely because of that dependency. It is a narrow concession rather than a blanket excuse; it’s aimed at schemes that can show they, and their administrator, are actively working towards connection, not at schemes that simply haven’t engaged. An employer client relying on “our administrator is dealing with it” as a complete answer needs that claim tested, not taken on trust.
Connected is not the same as live
Be precise with employer clients about what the 31 October 2026 deadline actually changes, because it isn’t public access. Connection means a scheme’s data is queryable through the dashboards ecosystem. It doesn’t mean members can log in and see it yet. The MoneyHelper Pensions Dashboard, the free, government-backed dashboard operated by the Money and Pensions Service, remains in restricted testing. Oliver Morley, chief executive of the Money and Pensions Service, said in May 2026 that the public dashboard is expected to launch in the 2027/28 financial year. The programme has committed to giving six months’ notice before that date, and the final call rests with the Secretary of State for Work and Pensions.
That gap matters for how you brief clients. Connection is a compliance milestone that happens more or less invisibly to members. Going live is a member-experience event that will generate scheme queries almost as soon as it happens. Getting a client’s scheme connected by October 2026 closes off the near-term regulatory risk, but not the conversation about what happens once members can actually use it.
What it means for employer clients
For a scheme sponsor, a late or failed connection isn’t only a regulatory exposure sitting with the trustees. It reflects on the employer that chose the scheme, and on the adviser who recommended it. A scheme that misses its deadline, attracts a compliance notice, or turns out to have connected with poor-quality data is a visible failure in an area employees increasingly expect their employer to have sorted, particularly once colleagues start comparing notes on what they can and can’t see through a dashboard. Make scheme connection status a standing item in reviews between now and the deadline, not a one-off check. Ask for the connection date itself, not just confirmation that connection is planned, and ask what data-quality checks the provider has completed; a scheme can be technically connected while still returning incomplete or unmatched records against a member’s search.
What it means for advisers
Once the MoneyHelper dashboard, and any commercial dashboards built on the same architecture, go live, the member engagement conversation changes shape. Savers will be able to see pensions they’d forgotten they had, including small pots from short spells of employment that auto-enrolment has quietly accumulated. That is a real benefit to members and part of the policy case for dashboards. It will also send a wave of queries into HR teams, and by extension to the advisers who support those employers, from members asking what a newly visible pot is and whether to consolidate it.
Building that into client communications now, well ahead of the 2027/28 launch, puts employer clients ahead of a predictable spike rather than scrambling after it. It is also an opening to talk to scheme sponsors about the quality of their own scheme’s data, since a member’s first sight of a newly visible pension is a poor advert for the scheme if the figures on screen are wrong or incomplete. The deadline gets a scheme connected; the months before launch are for getting right what happens next.
Things to reflect on for CPD
- Which of your employer clients have you asked for their scheme’s actual connection date, in writing, rather than relying on a provider’s general assurance that connection is “on track”?
- If a client’s scheme depends on a third-party administrator to connect, how would you establish whether the regulators’ pragmatic approach to that specific delay applies, or whether the scheme itself is falling short?
- How would you explain to an employer client the difference between their scheme being connected and members being able to see it on a live dashboard?
- What’s your plan for the member queries a live MoneyHelper dashboard is likely to generate about small or forgotten pots, and which of your clients’ schemes are most exposed to that?
