The biggest pensions story in local government right now is not the headline funding position. It is the quiet operational strain beneath it: councils are spending more, but much of that money is going into keeping pension administration functioning at all.
Across just five active councils — Harrow London Borough Council, Tower Hamlets London Borough Council, Bedford Borough Council, Aberdeen City Council and West Sussex County Council — QuorumInsight identified 80 relevant insights. Of those, 30 were about spending, 18 about opportunities, 13 about policy, 12 about pressure and 7 about action. That mix tells you a lot: this is a sector where the formal procurement market is thinner than you might expect, but the operational load is heavy and rising.
For suppliers, that matters because the demand is not for generic “transformation”. It is for precise help with actuarial valuation support, data cleansing, software limitations, manual recalculation work and staff capacity. For residents and scheme members, it matters because these are the systems that decide whether benefits are paid accurately and on time.
The real market signal: councils are buying capacity, not just compliance
If you work in the pensions market, the obvious assumption is that the money sits with investment advice and actuarial support. That is partly true. But the more revealing pattern is that councils are spending to absorb regulatory change that their existing systems and teams cannot handle cleanly.
Harrow’s 2026-27 pension fund budget was approved at £7.26 million, a 44% increase from the previous year. The council said this was “around a tenth of a percent of the overall assets under management”, but that framing can hide the practical point: £3.3 million of that budget is staff cost, and the rest is being pulled by governance, pooling, software and reorganisation pressures. In other words, pensions is no longer a quiet back-office function; it is a high-maintenance administrative operation.
The same theme appears in Highland-style valuation work even where the precise figures differ. One committee described the valuation as requiring “extra budget in for support from our investment advisor and our actuary to support this piece of work.” Another said, “the output from this will be the funding strategy statement that will come to pensions committee early 2027.” Those are not one-off advisory engagements. They are recurring, deadline-driven assignments with a clear timetable and a predictable need for specialist support.
That is the commercial opening. Suppliers with actuarial, legal, systems integration, data quality, payroll-pensions interface, and project capacity services are better placed than broad consultancies making generic efficiency promises.
Why the budget numbers matter
Budget approvals in pensions are often dismissed as routine because they sit inside trust structures rather than mainstream service committees. That would be a mistake. The budget lines tell you where the bottlenecks are.
In this sector, the money is consistently flowing into:
- staff costs and temporary capacity;
- software costs for pension administration systems;
- actuarial advisory support;
- investment consultant support;
- pooling-related fees and governance compliance;
- training for staff dealing with new regulatory duties.
That is not the profile of a mature, stable service. It is the profile of a service under persistent reconstruction.
McCloud is not a policy issue any more. It is an administration crisis
The most striking feature of the sector data is how often McCloud — or the “Mloud” wording used in transcripts — appears as a live operational burden. It is no longer discussed as a legal principle or a distant reform. Councils are talking about retrospective manual work, software defects and deadline risk.
One council said plainly: “we have been doing that work manually. So that's taken significant amount of training. um we've been reliant on assistance, you know, funds of shared shared um shared help with one another... We are redesigning the annual benefit statement as we speak.” That is a direct admission that automation is not yet carrying the load, and that peer support across funds is substituting for system capability.
Another report went further, warning that there are “critical issues still with the software release which mean we aren't able to progress to rectify those cases or estimate many of the um or provide accurate figures for the other rectification work.” The same meeting warned that if the work could not be completed by the 31 August 2026 deadline, discussions would follow “about reporting a possible breach of the law to the regulator”.
That is the most commercially important sentence in the whole sector data. Why? Because it points to a market where the downside is regulatory exposure, reputational damage and member complaint volume. Councils do not just need software that technically supports McCloud. They need systems that can absorb historical data, handle edge cases, and produce defensible outputs under deadline pressure.
For suppliers, the lesson is straightforward: McCloud work is still a live services market, not a settled compliance box. The buying window is open for case-management support, bulk recalculation tools, testing, specialist implementation help and training. For residents, the implication is less comfortable: if the system remains manual, the risk of delay and error stays high.
Manual work is now the norm in the difficult cases
The problem is not that councils are unaware of the deadline. It is that the difficult parts of the remedy are hard to automate.
One meeting noted that work includes recalculating benefits for members who retired from active status since January 2024, deferred members taking benefits since February 2025, transfer value calculations since September 2024, and survivor benefit cases. Another said there were “further changes with regards to Mloud remedy to correct issues with the original regulations” and to allow retrospective divorce cases to be recalculated.
That creates a very specific supplier opportunity. Councils are unlikely to buy a brand-new end-to-end pensions platform just for this. More likely, they will need targeted help around:
- workflow automation where software allows it;
- data cleansing before calculations begin;
- manual case handling support where it does not;
- member communications and annual benefit statement redesign;
- legal and actuarial validation of edge cases;
- dashboard-readiness work that reduces the chance of duplicated rework.
This is the kind of work that often gets fragmented across internal teams. That makes it attractive for specialist providers that can show they understand the case types, not just the legislation.
Staffing is the hidden crisis, and councils are saying it out loud
If McCloud is the technical burden, staffing is the structural one. This is the place where the sector data is most candid.
One board report said: “The board and committee are deeply concerned at the volume of work facing the pension team. And at the last meeting, the committee agreed for proposals that will help the team to get back on track... the statutory requirements are um ever changing um and there is an everinccreasing workload.” Another described staffing and workload as “the highest risk on the funds risk register”.
That is an unusually direct admission. Plenty of councils mention resilience. Fewer describe the pension team itself as the highest risk. That tells us the issue is no longer just a backlog; it is a capacity problem that threatens compliance.
Harrow’s November 2025 meeting shows how this plays out in practice. The committee said: “We still have some sickness in the team. We're in the process of doing job evaluations on the pensions officer job, the pensions admin job and the technical officer job and the supervisor job. They're going through reevaluation at the moment and once we get those graded if they do get regraded we can then recruit to the Vacancy that we have at the moment for the person that left.”
That sentence is full of market signals. Regrading before recruitment means the council is trying to solve a salary banding problem as much as a headcount problem. It also tells suppliers that workforce challenges are not being fixed by short-term cover alone. They are tied to role design, pay structures and the ability to attract specialist pensions staff.
What this means for the market
The clear implication is that vendors should not only sell systems or advice. They should sell capacity.
There is demand for:
- interim pensions administrators;
- team restructuring and job evaluation support;
- payroll-pensions interface improvements;
- training for staff handling complex calculations;
- managed service support for backlogs;
- documentation and knowledge-transfer packages so councils are less dependent on a few individuals.
That last point matters more than most suppliers realise. A council that depends on one or two technical people is more exposed to sickness absence, turnover and retirement. That is exactly the type of vulnerability now visible in the transcript data.
Dashboards have moved from preparation to consequences
Pensions dashboards are a useful test of whether the sector is still talking about readiness or actually dealing with live regulatory consequence.
Tower Hamlets gives the clearest example. On 2 March 2026, the Pension Fund reported that “By the 30th of January the pension regulator advised that Tower Hamlets Pension Fund is successfully connected to the pensions dashboards.” That is a milestone worth noting, but the more interesting point is the tone around it: connection is not the finish line. It is the start of a new service standard.
The same council’s earlier history is revealing. In 2020, a report referred to “considerable frustration in the board about the lack of progress around addressing issues in the Pensions' administration team”. That is useful context. It suggests the dashboard milestone is being reached against a background of long-running administrative weakness, not from a position of ease.
Highland-style dashboard preparation adds to the picture. One committee said the focus for the year was “reducing our volume of outstanding cases” because the fund would receive “6 months' notice before the pension dashboard is launched”. That is the right reading of the policy environment: dashboard connection is only possible when data quality and case completion are good enough to survive public-facing search and matching.
For suppliers, dashboards should be treated as a broader data-quality and cleansing programme, not a single technical integration. For residents, dashboards may eventually improve transparency, but only if councils can first clean up records that have been left unresolved for years.
Policy is driving the workload, not just responding to it
A lot of pensions commentary treats policy as background noise. The sector data says otherwise. Policy is now producing fresh operational work every year.
One council noted that “the instrument laid for this that was laid last Friday on the 6th and there is a significant amount of work administratively for us to look at here... survivor benefits and death grants. This is going to mean significant changes to our business as usual work... That will be work completed back to 2005.” That is not a routine update. It is retrospective processing on a scale that can swamp standard administration cycles.
Another council described the Funding Strategy Statement process as including “new mandatory gender pension gap reporting under Appendix D, Section D.3.” Elsewhere, a council approved communications policy updates and described them as “a regulatory requirement that the pension fund has a communications policy.” These are small policy phrases, but they create workstreams: communications content, employer engagement, reporting templates, website publication and compliance review.
There is also a governance layer. One committee authorised changes to constitution and delegation arrangements “required by the forthcoming legislation”. That is important because procurement around pensions is often influenced by governance redesign as much as by service change. If committee terms, delegations or reporting lines shift, the council may need legal support, document redrafting and advisory work before any technical change can land.
Supplier opportunities sit around the edges of policy change
There are no major procurement opportunities listed explicitly in the dataset for this sector, which is itself telling. The market is not being signalled through clean tender notices; it is being expressed through budget allocations and remediation work.
The best opportunities sit around:
- policy implementation support;
- communications and member engagement assets;
- legal drafting and governance updates;
- data reporting and gender pay/pension gap analysis;
- software changes to support revised regulations;
- employer consultation support during valuation cycles.
That makes the sales cycle more consultative and less transactional. Suppliers who can translate policy into operational steps will be stronger than those pitching abstract compliance packages.
Funding position gains are real, but they do not reduce the admin burden
It would be easy to confuse improved funding ratios with a healthier service. That would be a mistake.
Harrow’s 2025 valuation improved to 108%, up roughly 12% from the previous valuation at 96%. Another fund reported a funding level of 137% and a surplus of £350 million. East Riding’s valuation reached 154%, with the council noting “it does mean that um that we've got more money in the fund to pay those benefits when they fall due.”
Those are strong funding positions, and in some cases they create room for employer contribution relief. East Riding, for example, saw schedule body contribution reductions that can translate into real budget savings. But none of that reduces the administrative burden of statutory change.
In fact, strong funding can make the distinction sharper. When a fund is well-funded, the committee still has to deal with McCloud, dashboards, survivor benefits, communications policy, employer consultation, data quality and software limitations. So the funding story may be positive while the service story is still under strain.
That is the core sector paradox: better assets do not automatically mean better administration.
What to watch next
The most time-sensitive signals in the data are the deadlines.
- 31 August 2026 is the key McCloud remedy deadline repeatedly referenced in the meetings.
- Autumn 2026 is when multiple councils expect valuation results or initial outcomes.
- Early 2027 appears repeatedly as the point when funding strategy statements and employer rate-setting crystallise.
- Dashboard preparation is now tied to a live connection status and case-volume reduction, not abstract readiness.
Those dates matter commercially because they determine when councils will need help, and when they may already be too late to rely on internal capacity alone.
For residents, they matter because the risk of delay is now attached to specific legal and operational deadlines, not general concerns about efficiency.
What this means for suppliers, residents and partners
For suppliers: the best prospects are not in generic pensions outsourcing. They are in McCloud remediation support, data cleansing, annual benefit statement redesign, dashboard readiness, actuarial advisory work, and backfill capacity for overstretched administration teams. Harrow’s regrading and recruitment work, Tower Hamlets’ dashboards milestone, and the repeated references to software limitations all point to demand for specialist, deadline-driven support.
For residents and scheme members: the main risk is that statutory complexity is outpacing administrative capacity. That can mean slower correction of benefits, weaker communication, and more manual handling of historic cases. The good news is that councils are increasingly explicit about the problem, which suggests it is being seen as a governance issue rather than quietly absorbed.
For partners and advisers: the sector needs help translating policy into process. Valuation support, employer consultation, governance redrafting and training are not optional extras. They are part of how funds will survive the next 12 months of regulation-heavy work.
The most useful way to read this sector is not as a stable back office, but as a high-pressure compliance service with a growing manual workload. The councils in the data are telling us the same thing in different ways: the work is there, the deadlines are real, and the staffing model is not yet keeping up.