Pension Pot Consolidation for Contractors: A Guide for Umbrella Companies

A contractor who's worked with various umbrella companies can walk away with a separate pension pot from each one. The balances are small, reflecting the length of time worked on each contract. The contractor couldn't tell you how to access most of them, and has never linked them together. If a question about one ever comes up, payroll is the only contact still in the picture, so that's where it tends to land.

This guide is for operations and payroll leaders at umbrella companies and payroll bureaus who run pension enrolment for contractors. It covers why pot fragmentation compounds faster for contractors than for permanent staff, what the current small pots reforms will and won't change in the next few years, and what an umbrella can do now to cut the support queue this creates.

Why contractors lose pots faster than permanent employees

A contractor working two or three assignments a year through two or three different umbrellas can end up auto-enrolled two or three times, sometimes into a scheme they've never used before, each one starting from zero.

None of those pots disappear when the assignment ends. They sit unmanaged until the provider can no longer reach the member, which is how the Pensions Policy Institute defines a lost pot: the administrator loses contact, because contact details go out of date before anyone updates them. Contractors move between employers more often than permanent staff, and each move is a fresh chance for contact details to fall out of date.

The scale of the wider problem gives a sense of the trend. The Pensions Policy Institute's most recent count put the number of lost pension pots in the UK at 3.3 million, holding £31.1 billion. Contractors aren't broken out separately in that figure, but the mechanics behind it such as frequent job changes apply to contractors at large.

What scattered pots cost your team

Every scattered pot becomes a support ticket. A contractor who left eighteen months ago gets in touch asking where a pension from a placement they can barely remember has gone. The person who answers isn't the old scheme's administrator. It's whoever is on your support desk that day, working out which of several schemes across the client's history the query belongs to.

Re-engagement doubles the problem A contractor who worked for you last year and returns this year on a new assignment sometimes gets auto-enrolled from scratch again, unless the platform recognises them as a returning member. The contractor ends up with two pots instead of one, both starting at zero, both drifting toward the same fate.

A support agent spending an afternoon piecing together a contractor's placement history to answer a single query, is time that nobody has budgeted for.

##Why the government's fix won't help you this year

The Pension Schemes Act 2026 gives the government power to require auto-enrolment schemes to move pots that are both small and dormant into an authorised consolidator. “Small" means £1,000 or less, held in a default arrangement. A pot becomes eligible once it has gone twelve months without a contribution or an investment change. It targets the pattern contractors create: small pot, new scheme, no further activity once the placement ends.

For an umbrella running enrolments today, no one else is solving the fragmentation problem in the near term. It has to be managed inside the umbrella's own onboarding and leaver process. The duty to consolidate isn't expected until 2030, and the regulations that will confirm exactly how it works haven't been published yet.

What umbrella companies can do now

None of this requires waiting for 2030.

• Ask at onboarding whether the contractor has pensions from previous placements, umbrellas, or permanent roles, and point them to the government's Pension Tracing Service while the assignment is active and they're easy to reach.
• Flag consolidation at the leaver stage, not only at onboarding. A contractor is easiest to reach the day their assignment ends, not eighteen months later once the pot has gone quiet.
• Where possible, match a returning contractor to their existing pension account instead of re-enrolling them from scratch. That removes one pot from the count before it's created.
• Build a short consolidation reminder into standard leaver communications, alongside the P45 and final payslip, instead of running it as a separate campaign nobody opens.

Where a single account changes the shape of the problem

Jarvis maintains one account per worker across every payroll change instead of opening a new one each time. A contractor moving between assignments, even under different umbrellas on the same scheme, keeps the same account rather than starting again. Consolidation tools inside the platform let the worker trace and transfer in pensions from previous providers directly, without raising a support ticket.

With Jarvis, every new assignment feeds the same account instead of starting a new one, so the pot count and admin required stops growing. "Where's my pension" becomes something the worker can answer inside the Jarvis app, not something your team has to chase down.

Fragmented pensions won't wait for a policy landing in 2030. The mechanics that create lost pots are happening through your onboarding and leaver processes today.