The NHS spends significant sums on digital and data consultancy every year. The case for doing so is clear: NHS digital programmes are complex, time-pressured, and demand specialist expertise that most Trusts cannot maintain in-house across every domain. External consultancy brings accelerated access to skills, methods, and experience that would take years to develop internally.

But there is a well-documented failure mode in how NHS consultancy is structured and delivered. Consultancy provides incremental capability, but it often fails to build the residual capability that stays within the NHS once the contract expires. When consultants leave, they take the knowledge with them. The Trust is left with a deliverable, sometimes a document, sometimes a system, sometimes a set of recommendations, but without the internal understanding to sustain, evolve, or build on it.

This is not an argument against consultancy. It is an argument for structuring consultancy differently. Knowledge transfer is not a nice-to-have at the end of an engagement. It is a programme design requirement that should be specified, contracted for, and held to account from the outset.

The Problem Is Structural, Not Accidental

The tendency for NHS consultancy to create dependency rather than capability is not primarily the result of bad intentions on the part of consultants or complacency on the part of NHS commissioners. It is a structural consequence of how most NHS consultancy engagements are designed and procured.

Procurement focuses on deliverables: a strategy document, a system implementation, a discovery report, an architecture design. The deliverable is what is specified in the contract, what is evaluated at project close, and what is invoiced against. Knowledge transfer, if it appears at all, appears as a line in the scope of work with no measurable success criteria and no mechanism for holding the supplier accountable for it.

The Health and Social Care Committee has explicitly identified over-reliance on commercial consultancy as a consequence of significant staffing gaps in the NHS digital, data, and technology workforce. A 2025 survey of digital health professionals found that 96 percent believe workforce pressures are preventing digital progress. The NHS Chief Information Officer for Humber Teaching Foundation Trust wrote publicly in early 2026 that consultancy provides incremental capability but often fails to build the residual capability that stays within the NHS once the contract expires, and that when veteran staff leave, the hidden knowledge of why systems fail in live clinical environments leaves with them.

These are not fringe observations. They reflect a systemic pattern that is well understood within NHS digital leadership but has not consistently changed how engagements are designed.

The question NHS leaders should ask of any consultancy engagement is not only what will be delivered, but what will remain after delivery. Those are not the same question, and they require different contract provisions to answer.

Why It Matters More Now Than It Did Five Years Ago

The case for genuine knowledge transfer in NHS consultancy has always existed. What has changed in 2025 and 2026 is the scale and complexity of the digital transformation programme the NHS is undertaking, and the pace at which the skills required to support it are evolving.

The 10 Year Health Plan and Sustained Transformation Requirements

The NHS 10 Year Health Plan published in July 2025 sets out transformation at a scale and pace that cannot be delivered through episodic consultancy engagements. The three shifts it describes, from hospital to community, analogue to digital, and sickness to prevention, all require internal NHS capability to sustain and build on digital investments over years and decades. A Trust that implements an EPR or cloud data platform with the help of external consultants, but that has not built the internal capability to optimise, govern, and evolve those systems, will find itself dependent on external support for every subsequent development.

NHS England's What Good Looks Like framework for digital transformation explicitly includes workforce capability and leadership as core dimensions. The Digital Maturity Assessment, now in its third year and tracking progress against What Good Looks Like, identifies skills, governance, and integration capability as the areas where further work is most needed across NHS organisations. Building these capabilities cannot be outsourced. They have to exist inside the Trust.

The NHS Digital Workforce Gap

Lord Darzi's 2024 investigation into the NHS concluded that the service is in the foothills of digital transformation and that digital maturity lags other industries. One of the contributing factors he identified was the gap between the scale of digital ambition and the internal workforce capable of delivering it. The NHS 10 Year Workforce Plan, due in 2026, is expected to address this, but workforce development at scale takes years.

In the interim, the risk is straightforward. NHS Trusts are commissioning complex, multi-year digital programmes in data architecture, EPR implementation, AI adoption, and FDP integration. If the skills required to sustain those programmes after delivery exist only in the consultancy teams that built them, the NHS is trading long-term dependency for short-term delivery speed.

What Genuine Knowledge Transfer Actually Looks Like

The term knowledge transfer is used loosely in the consultancy market. In practice it covers a wide range, from a handover document handed over at project close to a sustained, structured programme of skills development running throughout an engagement. The former is not knowledge transfer. It is documentation. NHS organisations commissioning digital and data consultancy need to be specific about which they are requiring and how they will measure it.

Embedded Working, Not Parallel Working

Genuine knowledge transfer begins with how consultants and NHS teams are structured to work together. In a parallel working model, consultants work in a separate workstream, producing outputs that are handed to NHS staff at defined milestones. NHS staff review and accept the outputs but do not participate in producing them. When the engagement ends, the outputs exist but the understanding does not.

In an embedded working model, consultants and NHS staff work as integrated teams on the same tasks. NHS staff are not observers or reviewers. They are co-designers, co-analysts, and co-decision-makers throughout the programme. The consultant's role is to bring expertise and accelerate progress. The NHS team's role is to bring contextual knowledge and develop capability through participation. This takes more time in the short term and requires more deliberate programme design. It produces different outcomes.

Structured Skills Development Within the Programme

Beyond working model, knowledge transfer requires deliberate skills development activities that are planned, resourced, and held to account. This means training programmes aligned to the specific technical and methodological domains of the engagement, not generic digital literacy courses. For a data architecture programme, it means NHS staff developing working knowledge of cloud data platforms, data governance frameworks, and integration standards. For an EPR programme, it means clinical informatics leads developing capability in data migration quality assurance and EPR configuration management.

NHS England's Health and Care Digital Capability Framework and the profession-specific frameworks it supports provide a structured basis for defining capability targets at the outset of an engagement. These frameworks set out what good capability looks like across digital, data, and technology domains. They can be used to assess the Trust's starting position, define the capability development objectives for the engagement, and evaluate progress at defined intervals.

Documentation That Enables, Not Just Records

Documentation produced during a consultancy engagement is typically designed to record what was decided or built. Documentation that enables future capability is designed differently. It explains the reasoning behind decisions, not just the decisions themselves. It describes how processes work, not just what they produce. It is written so that an NHS team member who was not present during the engagement can understand, operate, and evolve the system or framework without having to re-engage the original consultants.

The difference is a meaningful one and it takes more effort to produce. Enabling documentation requires consultants to invest time in structured knowledge capture throughout the engagement rather than producing a summary at the end. It requires NHS programme leads to specify this standard in the contract and evaluate deliverables against it.

Transition Planning as a Programme Workstream

The end of a consultancy engagement is often treated as a risk event, a point at which the consultant teams leave and the Trust somehow maintains what was built. Effective knowledge transfer treats the transition not as a risk to manage but as a programme workstream to deliver. This means a defined transition plan that specifies what internal capability is required to sustain each programme deliverable, what activities will develop that capability during the engagement, what support arrangements will be in place after the engagement ends, and who is accountable for the capability being in place at the point of transition.

A well-designed transition plan produces a Trust that is less dependent on external support six months after an engagement ends than it was at the start. A poorly designed or absent transition plan produces a Trust that is calling the same consultancy back within a year to troubleshoot problems in the systems it built.

What NHS Organisations Should Demand

The responsibility for structuring consultancy engagements to produce genuine knowledge transfer sits primarily with the NHS organisations commissioning them. Consultancies will deliver what is specified and measured. If knowledge transfer is not in the specification, it will not be in the delivery.

At Procurement Stage

1. Require suppliers to describe their approach to knowledge transfer in bid submissions, with specific reference to how it will be structured, resourced, and measured in the proposed engagement.

2. Specify capability development objectives as contractual deliverables with defined success criteria, not as aspirational statements in the scope of work.

3. Ask suppliers to provide evidence of knowledge transfer outcomes from previous NHS engagements: what capability did Trust staff have at the end of the engagement that they did not have at the start, and how is that evidenced.

4. Require a transition plan as a named programme deliverable with a defined delivery date before the engagement ends, not after.

During the Engagement

5. Include capability development progress as a standing agenda item in programme governance reviews, with the same weight given to it as milestone delivery and risk management.

6. Assign named NHS staff as counterparts to each consultant role, with a development plan for each counterpart that describes what they will be able to do independently by the end of the engagement.

7. Evaluate documentation deliverables against an enabling standard, not just a recording standard. Ask whether a capable NHS staff member who was not present during the engagement could use the document to understand, operate, and evolve the system it describes.

8. Track the ratio of consultants to NHS staff working on each programme workstream over time. Successful knowledge transfer should see that ratio shift as the engagement progresses, with NHS staff taking greater ownership of workstreams.

At Engagement Close

9. Do not accept project close until the transition plan has been executed, not just written.

10. Conduct a capability assessment of NHS staff at engagement close against the objectives defined at the start. If the capability targets have not been met, hold that to account before sign-off.

11. Negotiate post-engagement support arrangements that are explicitly structured as a capability bridge rather than a continuing dependency. Declining consultant time over a defined period, with explicit milestones for internal independence, is a structured transition. Ongoing support with no defined end point is a continuing dependency dressed in different language.

What Good Consultancy Partners Do Differently

NHS organisations bear the primary responsibility for specifying what they need. But there is a meaningful difference between consultancy engagements that are structured to build lasting capability and those that are not, and that difference is visible in how good consultancy partners approach their work.

Consultancies that build genuine capability are transparent about what NHS staff need to learn to sustain programme outcomes. They design their engagement models with embedded working as a default, not as an option. They invest in the documentation standard described above. They raise the transition plan early in the engagement, not in the final weeks. They measure their own success partly by the reducing rate at which clients call them back for issues that internal teams should be able to resolve.

This approach is less commercially convenient than one that maintains dependency. It requires honest conversations with clients about the difference between what a document says and what an internal team can do. But it produces a different kind of relationship, one built on demonstrated value rather than accumulated lock-in.

The measure of a good consultancy partner is not whether the deliverable was completed on time. It is whether the Trust is more capable, more independent, and better positioned to sustain and build on the work one year after the engagement ends.

The Connection to NHS Digital Maturity

NHS England's Digital Maturity Assessment measures organisational progress against the What Good Looks Like framework across seven dimensions, including leadership, workforce skills, and governance. These are not incidental dimensions. They are the ones that determine whether digital investments in technology and systems translate into sustained improvement in care delivery or become expensive systems that are poorly used, poorly governed, and frequently replaced.

The most recent DMA results show that while core digital infrastructure is increasingly in place across NHS organisations, the areas requiring further work are precisely those that knowledge transfer is designed to address: integration, optimisation, skills, and governance. These are not gaps that further technology investment will close. They are gaps that internal capability development, supported by consultancy partners who genuinely prioritise it, can address over time.

Trusts that commission digital and data consultancy with an explicit, measured, accountable knowledge transfer framework will find that their Digital Maturity Assessment scores improve faster and more sustainably than those that do not. Because the capability being measured is the capability that remains when the consultants have gone.

Where VE3 Can Help

VE3 designs its NHS engagements to build lasting capability within Trust teams. Our approach includes embedded working models, counterpart development plans for NHS staff, enabling documentation standards, and formal transition planning as a programme deliverable. We measure success in part by the extent to which Trust teams are more independent at engagement close than they were at the start.

If your Trust is planning a data architecture, EPR alignment, or cloud migration programme and wants to ensure the engagement builds internal capability rather than external dependency, we would welcome the conversation. Visit our solutions for more information. Contact us for more