How to unify talent and learning across an NHS Region — without losing local control

If you're a regional workforce leader in the NHS, the chances are you're trying to build a coherent talent strategy across Trusts that each run their own learning management system, their own HR platform, and their own approach to workforce data. Succession plans arrive as emailed spreadsheets. Talent pool membership lives in one system; the learning content meant to develop those people lives in another. EDI data sits somewhere else entirely. And the regional picture? That's assembled manually, if it's assembled at all.

This isn't a niche problem. NHS Trusts spent a combined £4.1 billion on IT in 2024/25 — a 9% increase on the previous year. The government's State of Digital Government Review estimates that £45 billion per year in unrealised savings and productivity benefits could be unlocked through full digitisation of public services. Yet 45% of NHS services still lack a digital pathway, and as much as 70–85% of existing technology budgets are consumed by maintaining legacy systems rather than modernising them.

The result is a health service where individual Trusts operate in digital silos — each with their own LMS, their own HRIS, their own talent data — while regional workforce leaders stitch together a picture of their patch from disconnected sources. In a sector managing over 1.5 million staff across 42 Integrated Care Systems (now merging into as few as 26 by April 2027), the structural tension between local autonomy and regional oversight isn't just an inconvenience. It's a talent development risk — one that compounds into retention problems and widening skills gaps when leaders can't see the full picture.

So how do you solve it? How do you give each Trust control over their own talent data, succession plans, and learning programmes — while giving regional and national leaders the aggregate visibility they need to make strategic decisions? The answer isn't more systems. It's fewer, better ones.

The fragmentation problem

The government's own assessment is unambiguous. Its State of Digital Government Review found that public sector technology is fundamentally fragmented and duplicative, with most organisations implementing bespoke solutions even for common needs. The NHS's structure, the review concluded, actively drives this fragmentation — constraining buying power, shared capabilities, and the ability to manage talent effectively.

This plays out in workforce and learning management every day. A regional talent lead responsible for succession planning across six or seven Trusts typically has no single system that shows them the leadership pipeline across their patch. Each Trust may use a different LMS, a different HRIS, different talent management tools — or no dedicated tools at all — for tracking board composition, identifying successors, assessing flight risk, or managing talent pools. The data arrives in different formats, at different times, with different definitions of readiness, risk, and role criticality.

The result is a regional workforce function that spends more time aggregating data than acting on it. Weeks of manual collation to produce a report that's already outdated by the time it reaches a committee. No ability to spot cross-Trust patterns — such as multiple organisations struggling to fill Chief Nurse or Chief Digital Officer roles — because the data never sits in the same place at the same time.

And beneath this operational frustration sits a deeper structural problem. When every Trust operates a separate LMS, a separate HRIS, or a separate tenancy within a shared platform, the duplication isn't just financial. It fragments governance, creates inconsistent data standards, and makes regional coordination functionally impossible without manual intervention.

What separate LMS and HR tenancies actually cost

The traditional approach to managing multiple organisations within a learning or HR platform is multi-tenancy: giving each Trust its own separate instance, with its own data, its own configuration, and its own administration. On the surface, this seems sensible. Each organisation maintains control. Learner data stays within boundaries. Local L&D needs are met.

But in practice, separate tenancies create a set of compounding problems that become increasingly expensive as the number of organisations grows.

First, there's duplication of effort. Every Trust separately configures the same succession planning templates, the same competency frameworks, the same learning pathways, the same reporting formats. What should be set once at regional level and inherited locally is instead rebuilt from scratch in every tenancy. When NHS England updates its guidance on succession returns, mandatory training requirements, or EDI reporting standards, that change has to be manually replicated across every separate instance — with no guarantee of consistency.

Second, there's the reporting gap. A regional talent lead who needs a cross-Trust view of succession readiness, diversity pipeline strength, or talent pool participation can't simply run a report. They have to request data exports from each Trust, manually aggregate them, reconcile different formats, and produce a summary. This isn't a technology problem — it's an architecture problem. Separate tenancies are designed to keep data apart, which is precisely what makes regional oversight so difficult.

Third, and most critically, there's the governance paradox. Separate tenancies are often chosen specifically to maintain data governance — to ensure one Trust can't see another's sensitive workforce data. But the manual workarounds required to achieve regional visibility (emailed spreadsheets, shared folders, ad hoc data exports) actually create far greater governance risks than a properly designed single system with role-based access controls. Every time sensitive succession data is exported to a spreadsheet and emailed across organisational boundaries, the data governance framework that justified separate tenancies in the first place is undermined.

The NHS structure demands a different approach

The NHS isn't a single organisation. It's a complex hierarchy — seven regions, each overseeing multiple Integrated Care Boards, each containing multiple Trusts, each with their own board, leadership team, and operational context. The current restructuring programme — with ICBs clustering and merging to reduce running costs by 50% — is only adding complexity to an already intricate governance landscape.

This structure doesn't suit a one-size-fits-all approach of either a single flat tenancy or completely separate instances. It demands something more nuanced: a system that mirrors the NHS's own organisational hierarchy, where each level sees exactly what it needs to see, controls exactly what it needs to control, and nothing more.

In practical terms, this means a Trust CPO can manage their own board succession plan, configure their own role structures, and control who within their organisation has access to sensitive talent data — without any visibility of, or exposure to, another Trust's information. At the same time, a regional talent lead can see aggregate patterns across their ICB or region: how many Trusts have completed succession plans, where the common gaps sit, which talent pools are under-subscribed, and where flight risk is concentrated — all without accessing individual-level data that should remain within each Trust.

This isn't a theoretical distinction. It's the difference between a regional workforce function that can proactively identify and address pipeline weaknesses, and one that discovers them reactively when a critical leadership role falls vacant with no ready successor.

The real cost: Talent you can't see is talent you can't develop

The most damaging consequence of fragmented learning and HR systems isn't duplication of effort or reporting delays — it's the talent development that never happens because nobody had the full picture.

When succession planning sits in one system and learning delivery sits in another, the gap between identifying a future leader and actually developing them becomes structural. A Trust CPO names a successor for a board role. That person should be enrolled in a leadership development programme, assigned to a talent pool, given access to targeted learning content, and tracked against readiness milestones. But if the succession plan lives in a spreadsheet and the learning platform doesn't know about it, none of that happens automatically. The connection depends on someone remembering to make it — and in a sector managing 100,000 vacancies with stretched HR and L&D teams, manual follow-through is the first thing to fall away.

The same pattern plays out at regional level. A regional talent lead might know that Chief Nurse roles carry elevated succession risk across multiple Trusts — but if each Trust's learning data sits in a separate system, there's no way to see whether the people identified as successors are actually progressing through development. Are they engaged with the regional talent pool? Have they completed the leadership modules mapped to their future role? Are they showing signs of disengagement that might indicate flight risk? Without a connected view, the region is planning talent strategy with half the picture.

This is how skills gaps widen invisibly. Not because organisations aren't investing in development — most are — but because the investment isn't strategically connected to the demand signal coming from succession planning and workforce forecasting. Learning content gets consumed, but not by the people who most need it for the roles the organisation most needs to fill. Development budgets are spent, but without evidence that they're closing the specific capability gaps the leadership pipeline demands.

Research consistently shows that employees who see visible career growth opportunities are significantly less likely to leave, and that learning opportunities are now the number one retention strategy. But visibility requires connection. When a named successor can't see their own development pathway — because the succession plan that identified them exists in one system and the learning that should develop them exists in another — the organisation loses its most powerful retention lever. The successor doesn't feel invested in, because structurally they aren't.

In an NHS where over 20,000 secondary care doctors left NHS organisations in a single year, and where 65% of nurses report high stress and burnout, the cost of this disconnection isn't theoretical. Every successor who leaves because they couldn't see a future, every talent pool that atrophies because nobody tracked engagement, every skills gap that widens because development wasn't targeted to pipeline need — these are the compounding consequences of systems that were never designed to talk to each other.

What a unified approach actually looks like

The concept is deceptively simple: one regional system, with the NHS's organisational hierarchy built into its permission structure. Region at the top, ICBs beneath, Trusts beneath them. Each level manages its own data independently, with cascading permissions that ensure appropriate access at every tier.

But the simplicity of the concept masks the sophistication required to make it work — particularly in a healthcare context where data sensitivity is paramount, organisational independence is deeply valued, and the connection between talent identification and talent development is the whole point.

A well-designed unified approach delivers several things simultaneously:

It connects succession planning to learning delivery within a single environment. When a Trust CPO identifies a successor and assesses them as "ready in one to two years," the system can surface that person's current development activity, recommend relevant learning pathways, and track their progression against the capabilities the future role demands — without anyone having to manually cross-reference between platforms.

It gives Trust CPOs full operational control within their own organisation — the ability to configure succession plans, manage talent pools, assign learning content, and produce reports without needing to escalate to a regional administrator or raise a support ticket. Local autonomy isn't compromised; it's enabled by a permission structure designed around it.

It gives regional talent leads aggregate visibility without individual exposure. They can see that Chief Digital Officer roles carry elevated flight risk across five Trusts. They can see that a regional talent pool has 43 members but only 28 are actively engaged with development content. They can identify common capability gaps across the region and commission targeted learning interventions — all without accessing individual-level data that should remain within each Trust.

It eliminates the duplication of configuration and administration that separate LMS and HR tenancies create. Succession planning templates, competency frameworks, learning pathways, EDI reporting structures, and talent pool criteria can be defined once at regional level and inherited by Trusts — who can then adapt them to local needs without rebuilding from scratch.

It closes the loop between demand and supply. Succession planning surfaces the demand — the roles that need filling and the capabilities those roles require. Learning and development provides the supply — the programmes, pathways, and experiences that build those capabilities. When both sit in the same system, the gap between them becomes visible, measurable, and actionable. When they sit in separate systems, it becomes invisible — and that's when skills gaps compound.

The structural moment

The NHS is in the middle of a once-in-a-generation structural reorganisation. ICBs are merging, with the number set to reduce from 42 to approximately 26 by 2027. NHS England is being absorbed back into the Department of Health and Social Care. Regional footprints are being redrawn. Provider collaboratives are reshaping how Trusts work together.

Every one of these changes makes the case for unified, hierarchical systems stronger — and the cost of fragmented, siloed approaches higher. When two ICBs merge, any separate tenancies they maintained need to be consolidated — a technically complex, operationally disruptive, and financially expensive exercise. When regional boundaries shift, data that was previously isolated needs to be re-aggregated under new structures. When national reporting requirements change, every separate system needs to be updated independently.

Organisations that have already adopted a unified approach can restructure their permission hierarchy without migrating data, without disrupting local operations, and without losing continuity in their talent intelligence. Those operating across separate tenancies face a far more costly and risky transition every time the structure changes.

In a sector where structural change is the only constant, the architecture of your workforce technology is a strategic decision — not just a procurement one.

What forward-thinking healthcare organisations are doing differently

The organisations leading the way share a common principle: they treat their learning and workforce technology architecture as a talent strategy decision, not just an IT one.

They mirror the NHS regional hierarchy inside a single platform, with delegated administration at every level — so each Trust retains the operational autonomy that matters to them, while feeding into the regional and national picture that strategic workforce planning demands.

They connect the talent identification pipeline directly to development delivery. When a successor is named, they're automatically visible for talent pool enrolment, learning pathway assignment, and readiness tracking — without manual handoffs between HR and L&D teams operating in separate systems.

They use role-based access controls rather than system separation to enforce data boundaries. This means a Trust CPO sees only their Trust's data, a regional talent lead sees aggregate data across their patch, and a national programme lead sees thematic patterns across regions — all within the same system, with every boundary explicitly defined and auditable.

They eliminate the spreadsheet layer. Instead of exporting sensitive workforce data to files that circulate via email, they generate reports within the governed platform — with threshold-based controls that prevent identification of individuals in small cohorts.

They design for restructuring. When ICBs merge, when Trusts join provider collaboratives, when regional boundaries shift, they adjust their permission hierarchy rather than migrating between systems. The data stays. The structure adapts. The talent intelligence continues unbroken.

And they make career pathways visible. When succession planning, talent pools, and learning content exist in the same environment, aspiring leaders can see a coherent development journey — from being identified, to joining a programme, to building the capabilities their future role demands. That visibility is what turns a name on a plan into a person who stays, develops, and is ready when the moment comes.

Making it practical

For healthcare workforce leaders evaluating their current approach, here are five questions worth working through:

Map your data flows. How does succession, talent, and EDI data currently move from Trusts to regional and national levels? How many manual steps are involved? How many uncontrolled copies of sensitive data exist in spreadsheets, shared drives, and email inboxes?

Quantify the duplication. How many times is the same configuration — the same role structure, the same reporting template, the same talent pool criteria — being built independently across Trusts in your region? What would be saved if it were configured once and inherited?

Trace the development gap. For every named successor in your region, can you see whether they're actively engaged with a relevant development programme? If that answer requires cross-referencing between systems, the gap between identifying talent and developing talent is wider than you think.

Plan for structural change. With ICB mergers, provider collaboratives, and regional restructuring already under way, consider the cost and risk of adapting separate systems versus restructuring permissions within a unified platform.

Evaluate architecture, not just features. When assessing learning and talent platforms, ask how they handle organisational hierarchy, delegated administration, and role-based access. An LMS feature list matters far less than the structural ability to mirror how your organisations actually work together.

In summary

The NHS spends billions on technology and still struggles to achieve the regional visibility that effective talent strategy demands. The government's own review identifies fragmentation as a root cause — not just of inefficiency, but of missed opportunities to develop, retain, and strategically deploy the workforce the NHS needs.

The answer isn't another LMS or HR platform bolted on top of existing silos. It's a fundamental rethink of how workforce and learning systems are architected — moving from separate, disconnected tenancies towards unified platforms that mirror the NHS's own organisational hierarchy: one system, with local autonomy, regional oversight, and national governance built into its structure.

For Chief People Officers, regional talent leads, and national programme directors navigating an era of structural change, the question is straightforward: do your learning and talent systems reinforce the fragmentation the NHS is trying to move beyond, or do they provide the unified foundation that effective talent development requires?

In a health service carrying 100,000 vacancies, where leadership turnover is accelerating and where every structural reorganisation exposes the cost of siloed systems, the organisations that can see their talent pipeline clearly — from identification through development to readiness — will be the ones best positioned to retain, develop, and grow the leaders the NHS needs next.

‍