Outsourced procurement - run it in-house, or hand it to us.

What outsourced procurement actually means

The term covers a spectrum rather than a single service. At one end is task based support: someone runs a specific tender end to end, from specification challenge through to award and contract signature, and then leaves. In the middle sits managed service provision, where an external team runs a defined portion of the pipeline continuously, typically a category or a spend band, working inside the authority's governance. At the far end is a full managed procurement function, with the external provider operating as the commercial team.

What never transfers is accountability. The contracting authority remains the contracting authority. It signs the contracts, it publishes the notices in its own name, it answers to auditors and to challenge, and it carries the consequences if a procedure is run badly. An outsourced provider can prepare, advise, run process and draft everything, but the decisions are the authority's decisions and must be recorded as such.

This is why the design of the arrangement matters more than the brand of the provider. The question to answer before going to market is not who does the work, it is which decisions remain with named officers, what evidence those officers need in order to take them properly, and how that evidence is captured so it survives the provider leaving.

• Task based support: single procurement, defined start and end
• Category or portfolio support: continuous, defined scope, authority governance
• Managed function: provider operates the commercial team day to day
• Interim resource: individuals filling gaps, managed by the authority

When outsourcing is the right answer

The strongest case is a capacity spike with a hard deadline. A grant funded programme with a spend deadline, a wave of contract expiries landing in the same quarter, or a transformation programme that generates twenty procurements in a year will overwhelm a small in house team. Hiring against a temporary peak is slow and leaves you overstaffed afterwards. Buying capacity for the peak is the sensible answer.

The second strong case is genuine specialism. Complex construction, energy, clinical services, insurance, major IT and concession style arrangements all reward experience that a generalist team will not have. Buying that experience once, and having it work alongside your own people rather than behind a closed door, is usually cheaper than learning it live on a high value contract.

The weakest case is using outsourcing to avoid fixing something structural. If procurements are slow because requirements arrive late, business cases are vague and stakeholders will not commit to a specification, an external team will be slowed by exactly the same things. They will simply be slowed at a higher day rate, and the authority will conclude, wrongly, that outsourcing does not work.

What good looks like in a managed procurement service

Good providers work in the authority's systems, not their own. If tender documents, clarifications, evaluations and moderation notes live in the provider's platform and leave with them, the authority has bought a service and lost an asset. Insisting that everything is created and stored in the authority's own source to contract environment costs nothing at mobilisation and saves a great deal at exit.

Good providers also make the pipeline visible. A weekly view showing every live procurement, its stage, its owner, the next decision needed and the date it is needed by is worth more than a monthly report full of narrative. Most disputes about outsourced performance are actually disputes about whether the authority provided an input on time, and a shared pipeline settles those quickly.

Finally, good providers transfer capability deliberately. That means in house officers named on procurements alongside the provider, templates left behind in usable form, and short structured sessions on the things the team will have to do alone: market engagement, evaluation moderation, standstill handling and contract mobilisation. Capability transfer that is not scheduled and measured does not happen.

• Work in the authority's systems so records stay with the authority
• One shared pipeline with stages, owners and next decisions
• Named in house officers shadowing each procurement
• Templates, playbooks and training left behind as contract deliverables
• An exit plan written at mobilisation, not at termination

Buying the service compliantly

Procurement support is itself a procurement, and it is one that auditors look at closely because the appearance of a friendly arrangement is easy to create and hard to defend. Value has to be aggregated properly across the likely term and across departments, because support bought in slices by four directorates is one requirement, not four. Direct award is rarely justifiable simply because a provider knows the organisation well.

There are compliant routes that are quick. Commercial frameworks and dynamic markets for consultancy and procurement support exist, and a well run further competition can be completed in weeks. Under the Act, a Dynamic Market is permanently open, so a competent provider that was not a member when the market was set up can join and compete, and pending applications must be considered before a competition concludes. That widens the field compared with a closed framework.

Whichever route is used, price transparency is worth designing for. Day rates alone are a weak basis for comparison because they say nothing about how many days a procurement will take. Asking for indicative effort against a defined set of typical procurements, alongside rates by grade, produces a far more useful comparison and gives you a baseline to manage against later.

Multi client and shared arrangements

Many providers, and many public sector shared services, work across several clients at once. That is often a strength: patterns, benchmarks and market intelligence from one client improve outcomes for another, and a shared team can carry specialisms no single small authority could justify. It also creates obligations that need to be dealt with explicitly rather than assumed away.

The first is confidentiality and conflict. If the same team supports two authorities buying from the same small supplier base, information barriers need to be real, documented and testable, and any individual conflict declared. The second is capacity contention. If three clients hit a peak in the same month, whose work slips, and who decides? A contract that is silent on prioritisation will be resolved in favour of whoever complains loudest.

The third is data. Multi client working means the provider holds tender data, supplier data and pricing information from several authorities. Each authority needs clarity on where its data sits, who can see it, whether anything is aggregated for benchmarking, and what happens to it at exit. Separation by client at the platform level, with clear roles and permissions, is the practical answer.

Shared arrangements between authorities themselves, such as a lead authority procuring on behalf of others, need their own care. The lead must have authority to act for the others, the notices must name the beneficiaries correctly, and each participant must understand what it is committing to before the procurement starts rather than after award.

Governance, decisions and the audit trail

The Procurement Act 2023, in force since 24 February 2025, front loads transparency. Planned procurement and preliminary market engagement notices, tender notices that accurately describe the procedure you designed, award and contract details notices, and ongoing information for larger contracts all have to be published in the authority's name. If an outsourced provider is preparing these, the authority still needs a mechanism to check and approve them before publication.

The competitive flexible procedure raises the stakes further. Because the authority designs the procedure, the description in the tender notice becomes the rulebook. An outsourced team that designs a clever multi stage process and then quietly adjusts it because the timetable slipped has created a real challenge risk. Change control on the procedure itself, with a documented decision each time, is not bureaucracy, it is the defence.

The practical test of governance is whether an officer who was not involved can open the record for a procurement and understand what happened and why. Scores with rationale, moderation notes, clarification logs, the decision to shortlist, the standstill correspondence, all in one place and attributable to named people. If that record only exists in the provider's inbox, the authority is not governed, it is dependent.

Cost, value and how to measure whether it worked

Outsourced procurement is often justified on savings, which is the least reliable measure available. Savings figures depend entirely on the baseline chosen, and a provider with an incentive to report savings will choose a helpful one. Better measures are cycle time from requirement approval to contract signature, the proportion of procurements completed within their planned timetable, bidder numbers and quality, challenge and clarification volumes, and the number of contracts that reach expiry without an emergency extension.

Emergency extensions are a particularly honest indicator. They almost always mean a procurement started too late, and they usually mean the authority paid more than it needed to. An arrangement that steadily reduces them is delivering value even if the headline savings number is unremarkable.

Capability transfer should also be measured, because it is the thing most often promised and least often delivered. Count the procurements led in house with support versus those run entirely by the provider, and track that ratio over the term. If it does not move, the arrangement is producing dependency rather than capacity, and the next renewal will be a negotiation you cannot win.

• Cycle time from approval to contract signature
• Percentage of procurements delivered to their planned timetable
• Number and quality of bids received per competition
• Emergency extensions and retrospective approvals per year
• Procurements led in house with support, as a share of the total

Exit, handback and keeping the institutional memory

Every outsourced arrangement ends, and the ones that end badly do so because nobody wrote down what handback meant. At minimum the authority should get back a complete set of live contract records with dates, values, owners and expiry, all procurement files with evaluation evidence intact, the supplier records including assurance documents and their expiry dates, and the templates and process documents used during the term, in editable form.

The cleanest way to achieve that is to never let the records leave in the first place. If the source to contract platform belongs to the authority and the provider works inside it with appropriate roles and permissions, handback is a permissions change rather than a data migration project. That single design decision removes most exit risk from the arrangement.

It is also worth agreeing a handover period with overlap. A month where the incoming team, whether internal or a new provider, works alongside the outgoing one, with a defined list of live procurements and their status, prevents the familiar situation where three tenders stall for six weeks because nobody knows what was agreed with the bidders.

How eSourcing Data supports outsourced and managed procurement

eSourcing Data is built for source to contract, which is exactly the span an outsourced arrangement covers: sourcing and tendering, supplier onboarding and assurance, evaluation and moderation, contract management, governance and audit, analytics and reporting, and below threshold workflows. Because it is one environment rather than a chain of tools, the record of a procurement stays complete regardless of who did the work.

For multi client providers and shared services, roles and permissions allow separate client environments with controlled access, so a consultant can work across accounts without clients seeing each other's data. For authorities, the same structure means a provider can be given precisely the access their role requires and no more, and that access can be withdrawn on the day the contract ends without touching the records themselves.

The platform is available to public buyers through RM1557.15 G-Cloud 15, with 28 software services listed on the Digital Marketplace plus cloud support services, and framework purchases are made as call off contracts. Data is held in the UK and the platform is GDPR compliant. Authorities running or considering their own Dynamic Markets can operate them in the same environment, which keeps membership assessment, category structure and call off competitions in one auditable place.