The Pensions Dashboard Programme connection deadline of 31 October is approaching fast, and for specialist SIPP and SSAS operators, the practical demands of compliance are starting to bite.
The dashboard itself is genuinely valuable consumer infrastructure, but its implementation is exposing a familiar regulatory flaw. Blanket deadlines that overlook the diversity of the UK pension landscape.
The programme requires every pension scheme administrator, including SIPP operators and SSAS trustees, to connect to the ecosystem by the end of October 2026. The mechanics are simple in principle. You must supply two categories of data.
First, to “find” data that allows members to locate their scheme and verify identity and second, to “view” data that delivers actual benefit information once clients are logged in.
The initial threshold is 80% member coverage with The Pensions Regulator (TPR) accepting that 100% is unrealistic from day one.
Most operators will need an Integrated Service Provider (ISP) to manage the technical connection and data flow. But choose your ISPs carefully. Many now serve this market but with varying support and integration levels and poor data quality and maintenance load can ultimately create a compliance risk.
The specialist operator challenge
This is where the regulatory thinking falls down.
The programme was designed with large master trusts and insurance-backed platforms in mind. Those operators hold standardised assets, typically pooled funds with daily live unit prices, and they administer thousands or millions of members on centralised systems. For them, connection is largely a lift-and-shift exercise.
SIPP and SSAS operators inhabit a fundamentally different world. A SIPP may hold bespoke assets such as commercial property, cash, or gold and valuing these for dashboard purposes is not straightforward. There is no fund manager price feed to pull. You need a surveyor’s valuation, a professional share valuation, or a member declaration. That takes time, costs money, and raises legitimate questions about the currency of valuations and how often they must be refreshed.
SSASs add further complexity. A typical SSAS has four to six member-trustees, often with similar or identical names appearing across multiple trustee records. Identity matching (the foundation of “find” data) becomes a delicate verification exercise but the standards assume clean data and straightforward valuations. Many specialist operators simply don’t have that.
TPR’s enforcement posture
TPR has been explicit. Failure to connect carries civil penalties of up to £50,000. Deliberate obstruction or refusal to provide data triggers criminal sanctions, including potential imprisonment. TPR has said publicly it will use these powers and the regulator treats the dashboard as a consumer priority.
For a specialist operator, the risk is real.
If your ISP connection fails, your remediation is incomplete, or you miss the deadline, which is absolute, with no built-in extension, then you face regulatory action and reputational damage.
The cost asymmetry problem
The current framework assumes a level playing field. It isn’t.
This is at the heart of the fairness question. The infrastructure investment to connect is a significant fixed cost. If a platform with five million members spreads that cost across the client base, the per-member impact is negligible.
But a SSAS administrator running four hundred schemes with perhaps two thousand total members faces the same absolute cost. The per-member impact is dramatically higher.
Layer on the specialist challenges already described like valuing bespoke assets, certifying them and refreshing them periodically, then you have an ongoing operational burden.
The current framework assumes a level playing field. It isn’t.
Smaller specialist operators bear a disproportionate compliance load, on thinner margins, with less capital to absorb it. This is a recurring regulatory pattern, namely, r: rules built for large schemes, applied uniformly to small ones, producing competitive distortion.
What operators must do now
If you have not selected an ISP, you are already behind. It’s crucial to evaluate the technical capability, pricing, support, and the vendor’s own regulatory standing. Do not leave this to the final quarter as you’ll need time to pilot the integration and fix issues.
Auditing every member record for completeness, accuracy and consistency must be started now, as should reviewing asset valuation processes for bespoke holdings. It’s laborious but unavoidable.
Test your ISP connection in beta where possible. Run sample data through verification, valuation and transmission end-to-end, and find the gaps early.
What comes next?
The dashboard is a genuine consumer win. Members have struggled for decades to see their retirement assets in one place. Visibility leads to better decisions and, arguably, better retirement outcomes nationally.
The objective is right. But the design and uniform deadline isn’t. Regulation designed for scale does not scale well to diversity.
The next six months will decide compliance outcomes. Operators who have started to engage, will connect. Those who haven’t are running a real enforcement risk. The regulatory environment will keep tightening; the dashboard is one milestone among many. The deadline is absolute.
The best time to prepare was 12 months ago. The second-best time is now.
Rob Shipman is group CEO at The UAP Group and director at Alltrust Services
