Procurement consultancy and training.

What procurement consultancy covers

Advisory work in public procurement usually falls into four groups. Readiness and compliance work looks at whether an organisation's rules, templates and behaviours match the current law. Strategy work looks at what is bought, from whom, on what terms, and whether that structure still serves the organisation. Delivery support puts experienced hands on specific complex procurements. Capability work builds the skills of the people who will still be there in two years.

The four are related but not interchangeable, and confusing them is the most common reason consultancy disappoints. A readiness review will not fix a category structure. A category strategy will not make evaluators score consistently. Training will not compensate for a delegation scheme that forces every decision through one overloaded committee. Being precise about which problem is being solved is the first job, and a good adviser will push back if the brief and the symptom do not match.

The other distinction worth drawing is between advice and decision. An adviser can recommend a procedure, draft an evaluation model, or propose a contract structure. The contracting authority takes the decision, records the reasons, and answers for it. Arrangements where that boundary is blurred tend to produce records that cannot be defended later, because nobody can say who decided what.

Procurement Act 2023 readiness in practice

Most organisations have done the awareness training. Far fewer have worked through the operational consequences. Readiness is not knowing that Dynamic Purchasing Systems became Dynamic Markets, it is knowing which of your live arrangements were affected, what your transitional position is, and whether the templates your officers open on a Monday morning reflect any of it.

A useful readiness review is document led rather than interview led. It reads the contract procedure rules, the delegation scheme, the standard tender documents, the selection questionnaire equivalent, the evaluation templates, the standstill letters and the contract register, and tests them against the Act's requirements: the notice regime across the contract lifecycle, exclusion and debarment handling, the design and description of the competitive flexible procedure, assessment of conflicts, and contract performance and payment publication for larger contracts.

The output that actually helps is a prioritised fix list with owners and dates, not a maturity score. Three or four things usually matter far more than the rest: notices being published late or incompletely, evaluation records that do not show rationale, contract registers with unreliable expiry dates, and procedure descriptions that the authority then departs from. Fixing those four removes most of the real risk.

• Contract procedure rules and delegations tested against the Act
• Template pack refreshed, including notices, evaluation and standstill
• Notice publication checked end to end for a sample of live procurements
• Exclusion, debarment and conflicts processes documented and usable
• A short prioritised fix list with named owners and dates

Commercial strategy and category work

Category strategy in the public sector is often written as if the organisation had a free hand, then filed. The versions that work start from three constraints: the money that is actually committed and when it becomes uncommitted, the capacity of the team to run competitions in that window, and the state of the supply market for that category. A strategy that ignores contract expiry dates is a wish list.

The most valuable early exercise is usually a spend and expiry map. Pulling together what is spent, with whom, under which contract, expiring when, and under what route, exposes the real picture: a long tail of maverick spend, several arrangements that quietly rolled over, and a cluster of expiries in the same quarter that the team cannot possibly service. That map does more to change behaviour than any strategy document.

From there the choices become concrete. Which categories justify their own competition and which should use a framework or dynamic market. Where lotting could open the field to smaller suppliers. Where consolidation genuinely reduces cost rather than just reducing the number of invoices. Where the current contract model transfers risk to suppliers who cannot carry it, which is where mid contract failures come from.

Evaluation design and evaluator training

Evaluation is where most procurement disputes are won or lost, and it is the area where practice is weakest. Common problems are consistent across sectors: criteria that repeat each other so a single strength is rewarded three times, weightings set after the questions were written, scoring scales with vague descriptors that different evaluators interpret differently, and price models that mathematically decide the outcome regardless of quality scores.

Better design starts from the award criteria and works backwards. Decide what genuinely differentiates a good supplier for this requirement, write questions that only a supplier who can do it could answer well, and set a scoring scale with descriptors specific enough that two evaluators reading the same answer land within one point of each other. Then model the price mechanism against plausible bid scenarios before publication, to check it behaves the way you intend.

Training evaluators matters as much as the design. Subject matter experts are drafted in from services, score once every two years, and are rarely told what an audit trail requires. A short, practical session covering how to score against the descriptors, how to write rationale that supports the score, what moderation is for and what not to write in an email is one of the highest return interventions available.

Moderation deserves its own attention. Moderation is not averaging, and it is not the loudest evaluator winning. It is a documented discussion that produces a consensus score with reasons, recorded at the time. Where that record exists, challenges tend to fail early. Where it does not, even a sound decision looks arbitrary.

• Criteria that differentiate rather than duplicate
• Scoring descriptors specific enough to be applied consistently
• Price mechanism modelled against scenarios before publication
• Evaluator briefing on rationale writing and record keeping
• Moderation recorded as consensus with reasons, at the time

Dynamic Markets and framework strategy

The Act replaced Dynamic Purchasing Systems with Dynamic Markets and replaced utilities qualification systems with utilities dynamic markets, and the strategic implications are still working through. A Dynamic Market is permanently open, membership cannot be capped, applications must be assessed within a reasonable time, and pending applications must be considered before a competition concludes. That makes it a genuinely different tool from a closed framework, not a rebrand.

For advisory work the question is which categories suit which vehicle. Dynamic Markets fit fragmented, changing supply bases and repeat requirements: trades and maintenance, professional services, care providers, transport, small works. Frameworks still fit where a stable, pre priced arrangement with a defined group of suppliers gives certainty, and where the effort of setting up a market would not be repaid. Many organisations need both, structured deliberately rather than by accident.

There is also a status point that advisers should raise early. Utilities operating utilities dynamic markets may charge suppliers membership and award fees and may run member only tenders. General contracting authorities may not charge membership fees. Organisations that sit near the boundary, or that are considering operating a market for others to use, need that question resolved before design begins rather than after.

Below threshold, transparency and the long tail

Below threshold spend gets less attention than it deserves. It is where most transactions happen, where most officers actually experience procurement, and where most local supplier relationships are made or broken. It is also subject to its own transparency expectations, and a below threshold process that is undocumented is still a decision that can be questioned.

The practical goal is proportionality with a trail. A three quote exercise for a low value requirement does not need a full tender pack, but it does need a record of what was asked for, who was approached, what came back, why the winner won and who approved it. When that is captured in a workflow rather than an inbox, the long tail becomes visible and category planning suddenly has data behind it.

The same discipline surfaces problems worth solving. Repeat low value purchases from the same supplier that together exceed a threshold. Requirements split across cost centres. Departments buying the same thing four different ways. None of these are visible when below threshold activity lives in email, and all of them are straightforward to fix once they are.

Choosing and managing an adviser

Buying consultancy is a procurement, and it should be run like one. Aggregate the likely spend across the organisation rather than slicing it by department, use a compliant route, and ask for a proposal against a defined problem rather than a capability statement. The most informative selection question is usually a short worked response to a real situation you are facing, because it exposes judgement rather than credentials.

Scope should be written as outputs and outcomes, not days. A deliverable such as a refreshed template pack adopted by the organisation and used on three live procurements is testable. Twenty days of advisory support is not. Where knowledge transfer is expected, name it as a deliverable with the sessions, materials and participants specified, otherwise it will be the first thing squeezed when the timetable slips.

Manage the engagement with the same rhythm as any contract: a short weekly checkpoint, a shared list of decisions needed from the authority, and an explicit change control for anything that moves scope. Most consultancy overruns come from the client, not the consultant, and a visible list of overdue client decisions solves that faster than any escalation.

• Brief against a defined problem, not a general capability need
• Ask for a worked response to a real scenario at selection
• Write scope as outputs and adoption, not days
• Name knowledge transfer as a deliverable with sessions and participants
• Track decisions owed by the authority, weekly

Making advice stick after the adviser leaves

The failure mode of procurement consultancy is well known: a good report, genuine agreement, and no change six months later. It happens because recommendations sit outside the systems people work in. If the improved evaluation approach exists in a PDF, officers will keep using the old template that is already in the folder they open every day.

Advice sticks when it is embedded in the workflow. New templates loaded as the default. Approval steps built into the process rather than remembered. Notice publication prompted at the right point in the procurement rather than depending on someone's diary. Contract expiry dates driving a pipeline that generates work automatically instead of relying on a spreadsheet owner who has since moved roles.

That is why readiness work and platform work are more effective together than separately. The review identifies what should change, and the system makes the change the path of least resistance. Organisations that do the review alone tend to repeat it in two years with a similar findings list.

How eSourcing Data supports advisory work

eSourcing Data covers source to contract in a single environment: sourcing and tendering, supplier onboarding and assurance, evaluation and moderation, contract management, governance and audit, analytics and reporting, and below threshold workflows. For advisory engagements that means recommendations can be implemented as configuration, templates and workflow rather than left as guidance, and the resulting practice is visible and auditable from day one.

It also gives advisers a factual starting point. A contract register with real expiry dates, spend analytics, and a below threshold workflow that captures the long tail turn a strategy conversation from opinion into evidence. Evaluation and moderation records built in mean the improvements to scoring practice are enforced by the tool rather than by memory.

The software 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. The Procurement Library sets out the official Procurement Act guidance, Procurement Policy Notes and commercial playbooks that underpin the advice, so teams can check the source rather than take it on trust.