NHS Procurement Transformation: What Value-Based Procurement Means for the Operating Model

What has changed, and what has not

The Department of Health and Social Care published national value-based procurement guidance for medical technology on 11 June 2026. It provides questions and scoring criteria for buyers assessing medical devices, including associated services. It considers whole-life cost alongside five value domains: social value, efficiency, patient and staff, supply chain, and purpose. [1]

A written parliamentary answer on 14 September 2026 subsequently confirmed that NHS Supply Chain had moved to a "comply or explain" approach for future frameworks. The answer also stated that pricing thresholds are considered case by case, rather than applied to all framework tenders. [2]

These statements need to be read in context. The national guidance is not a complete end-to-end procurement manual, and it calls for buyers to obtain legal assurance for their particular procurement. The parliamentary answer concerns NHS Supply Chain's framework approach, not a blanket instruction covering every NHS purchase. [1][2]

The recommendations below are PearsonGoldman's interpretation of the organisational work needed to support value-based procurement. They are not additional government requirements.

Value is broader than the price paid

NHS Supply Chain describes value-based procurement as moving beyond reductions in product cost to considering the total cost within a patient pathway, with tangible benefits for efficiency and patient care. [3]

That distinction changes the business question.

Instead of asking only, "Which compliant option costs less to purchase?", leaders also need to ask, "What does each option require us to change, what will that change cost, and how will we know whether the expected benefit materialises?"

A higher purchase price does not automatically mean better value. Equally, a lower price does not settle the question. The comparison needs credible assumptions, an appropriate time horizon and an honest view of implementation.

A published NHS Supply Chain example illustrates the connection. Its May 2022 account of a catheterisation pilot at University Hospitals of North Midlands described objectives around reducing variation in practice, improving consistency of equipment use and reducing procedure time. The implementation included supplier training and audit. [4]

The operating-model lesson is not that another organisation should buy the same product. It is that the purchasing decision, working practices, training and measurement were considered together. A product choice was part of a wider change in delivery.

The procurement operating model must connect five decisions

An operating model is more than an organisation chart. It describes how work gets done: who makes decisions, how teams interact, what information they use and who remains accountable after implementation.

For healthcare procurement transformation, the critical connection runs from the original service need through the commercial decision to performance in use.

The following is an illustrative ownership model, to be adapted to local governance rather than adopted as a mandated structure.

On narrower screens, scroll the table horizontally to view all columns.

One person may hold more than one role. Existing committees may already provide the necessary governance.

The essential point is that "joint ownership" must not become a substitute for a named decision-maker. Each important decision needs an owner with the authority to resolve it, not merely a group of people expected to attend a meeting.

Carry the value case beyond contract award

The business case, tender evaluation, mobilisation plan and operational review should not tell four different stories.

A practical starting point is a value-and-delivery record that follows the procurement through its lifecycle. For every material benefit, record the intended outcome, the evidence supporting it, the implementation conditions, the accountable owner and the measure that will demonstrate progress.

This is particularly important when a supplier's proposition depends on changes the buying organisation must make.

For example, an anticipated reduction in administration may depend on an interface being delivered, a legacy process being retired and staff using the new workflow. Those are delivery commitments, not incidental details.

They should become visible work with owners, resources and decision dates. Otherwise, the commercial case can retain the benefit while the implementation plan quietly loses the work required to achieve it.

Contract award is a decision to proceed. It is not evidence that the promised value has been delivered.

Make the financial trade-offs visible

A procurement proposal can create costs in one budget and benefits in another.

An operational team may need to fund training or additional implementation capacity, while the expected improvement appears in a different service. Without an agreed funding decision, an attractive organisation-wide case can become an unaffordable local one.

Finance involvement should therefore extend beyond approving the purchase.

We recommend distinguishing between an actual reduction in expenditure, future costs avoided, capacity made available and improvements in service or patient experience. These benefits may all matter, but they should not be presented as interchangeable.

Consider an illustrative scenario in which a new process releases staff time. That does not, on its own, reduce payroll expenditure. The organisation needs to decide whether the time will support additional activity, reduce reliance on temporary staffing or create another measurable benefit.

The benefit claim should reflect that decision.

Sensitivity matters too. Test what happens if adoption is slower, activity differs from the forecast or implementation costs more than expected. A credible case shows which assumptions could change the decision, rather than presenting a single optimistic number.

This is where finance transformation and procurement improvement need to meet: in a shared view of cost, value and accountability.

Connect data without creating another reporting burden

Value cannot be governed consistently when the relevant evidence is scattered across disconnected procurement records, finance reports and operational spreadsheets.

That does not mean every organisation needs a new platform.

Start with the decisions leaders need to make. Identify the minimum evidence required, where it already exists and who is responsible for maintaining it.

A practical value record should connect the relevant supplier and contract to the implementation owner, benefit owner, agreed baseline, target, review date and latest evidence. Assumptions should remain visible when forecasts become reported results.

Avoid double counting. A single improvement should not appear as separate, additive benefits in procurement, finance and transformation reporting simply because each team has its own dashboard.

Data access also needs boundaries. Use appropriately aggregated information where possible and involve information-governance specialists when sensitive information is required. A general procurement benefits report should not become an unnecessary repository for identifiable patient information.

The objective is a reliable decision trail, not a larger reporting estate.

Technology should support the operating model

An ERP system or procurement platform should help enforce the decisions the organisation has made about ownership, approvals, data and controls.

It should not be expected to resolve decisions that leadership has left unanswered.

A requisition can pass through an approval workflow without demonstrating that the organisation is ready to implement the purchase. A supplier can be onboarded successfully while the owner of the resulting service change remains unclear.

For source-to-pay transformation, the design question is therefore broader than transaction efficiency. How does the workflow preserve the connection between the approved business case, the contract, implementation responsibilities and benefits?

The same principle applies when considering AI.

Before introducing an agent into an approval or evaluation process, establish which tasks it may perform, what evidence it must retain, who reviews its output and how exceptions are escalated. These are design decisions to make before extending its authority.

Automating a process should not make accountability harder to locate.

Treat adoption and supplier management as part of delivery

A supplier can meet a contractual delivery milestone while the buying organisation remains unprepared to use the solution effectively.

Separate the supplier's obligations from the organisation's own implementation responsibilities, then manage the dependencies between them.

Training, local procedures, support arrangements, data readiness and operational acceptance need owners. They should not disappear into a broad assumption that "the business will manage the change".

After implementation, review both the supplier's performance and the conditions affecting the intended benefit. A disappointing result might reflect supplier delivery, incomplete adoption, an unrealistic assumption or a combination of factors.

The response should follow the evidence.

A useful operating review asks what was expected, what has happened, why the two differ and what decision is now required. That is more valuable than repeatedly reporting a red indicator without identifying who can change the outcome.

Keep the response proportionate

Not every procurement requires an organisation-wide transformation programme.

Where decision rights, evidence and implementation arrangements already work, the answer may be a targeted improvement rather than a new operating model from scratch.

PearsonGoldman's recommendation is to intervene at the smallest scope that resolves the material problem.

A straightforward purchase should not inherit unnecessary committees and documentation. A complex acquisition that changes workflows across several services should not be treated as a simple catalogue substitution.

The same discipline applies to technology investment. Establish whether the problem is genuinely a system limitation, an unclear process, missing capability or unresolved ownership before deciding to replace a platform.

A practical first-90-days approach

The following is an indicative sequence for establishing an initial improvement programme. It is not a mandated timetable or a promise that procurement transformation can be completed in 90 days.

Days 1-30: diagnose one priority area

Choose a category or service where there is a clear problem and a willing accountable sponsor.

Map how a need becomes a procurement decision and how responsibility passes into implementation. Examine existing evidence, financial assumptions, decision rights and operational constraints.

The output should be a concise statement of the problem, the ownership gaps and the decisions needed to proceed. Avoid launching a large programme before those basics are understood.

Days 31-60: design the minimum viable change

Agree the value measures, ownership model, funding responsibilities and review arrangements.

Identify the changes needed in processes, data, contracts, technology and staff capability. Set out dependencies and the evidence required before implementation can proceed.

The output should be an executable plan, not simply a target-state diagram: named owners, sequenced work, decision points and a clear view of readiness.

Days 61-90: test and establish operational ownership

Where approvals and readiness allow, begin a bounded implementation or pilot.

Test whether the proposed reporting works, whether people understand their responsibilities and whether the expected changes are actually happening. Record early findings and revise unsupported assumptions.

Some outcomes will require a longer measurement period. Use the first review to establish a credible evidence base and the next decision, not to manufacture an early success claim.

The leadership question

Value-based procurement should not end with a more sophisticated explanation of why a contract was awarded.

Its practical value depends on whether the organisation can implement the decision and demonstrate what followed.

Before committing, leaders should be able to answer:

What outcome are we buying, what must change to achieve it, who owns that change, and what evidence will tell us whether it worked?

PearsonGoldman's approach connects operating-model design with finance, procurement, technology and accountable delivery. For healthcare leaders, the objective is a clear route from purchasing intent to operational ownership and measurable value.