Buying consultancy well starts with proving you did not need it

Capability gap or capacity gap? The question that decides everything

The Playbook draws a firm distinction between consultancy and contingent labour, and it is not academic. Consultancy means advice outside the business as usual environment, expertise or data not available in house, defined deliverables, and supplier responsibility for delivering them. Contingent labour means named individuals performing a role that already exists in the organisation, where the client keeps day to day management responsibility.

Buy consultancy to solve a capacity problem and you get the worst of both. You pay advisory rates for people doing operational work, you take on IR35 risk because the consultants are embedded and working like employees, and you build no lasting capability because there was no knowledge gap to close in the first place. The Playbook specifically flags that where a capacity shortage exists, a Statements of Work solution through Crown Commercial Service may be the better route.

This distinction is also why the Playbook pushes umbrella contracts and delivery partner arrangements to apply governance at the level of each individual call off. A framework that was justified on capability grounds can quietly become a route for filling capacity, one call off at a time, unless someone checks internal options and knowledge transfer every time it is used.

What most organisations get wrong in the specification

Consultancy tenders default to input based specifications: how many partners, how many days, which methodology, which workstreams. It feels like control. What it actually does, in the Playbook's words, is limit creative and bespoke approaches by rigidly specifying how consultants should deliver. Buyers end up paying expert firms to execute the buyer's own plan and then wondering why the advice was not sharper.

The alternative is to describe the problem and stay neutral on the process. That takes more work upfront, not less. It needs meaningful market engagement before the specification is drafted, close involvement of the project team, and advice from commercial and legal colleagues, because a problem based approach can be difficult to administer. It also needs specific, measurable milestones aligned to the timeline and pointed at the areas that represent the biggest value or risk, otherwise open ended becomes unmanageable.

The same prescriptiveness shows up in evaluation. Bidders consistently report that consultancy invitations to tender do not give them room to demonstrate how they create value. Open questions, clearly defined deliverables and scoring bands that actually differentiate are how you fix that, along with the quality threshold that stops a low day rate from buying its way past quality.

Knowledge transfer is a deliverable, not a hope

The headline change in version 1.1 is the emphasis on knowledge generation, transfer and sharing, supported by a dedicated guidance note and by the GCH Knowledge Exchange, which exists to capture and share across the Civil Service the tools, methodologies and thinking that government typically buys through consultancy spend. The ambition is straightforward: stop buying the same knowledge twice.

That only works if knowledge transfer is treated as contractual. The Playbook says specifications shall include deliverables on knowledge and skills transfer and that evaluation should include questions on it, with the onus on the buyer to be clear about what knowledge is expected to be generated and which skills should be developed. A single line asking bidders to describe their approach to upskilling is not that.

It also requires the buyer to be an effective client during delivery: collaborative working, sufficient time and resource devoted to governance and contract management, experienced client side senior responsible owners, and a plan for handover and exit agreed before the engagement ends rather than during its final fortnight.

SME access is a value for money issue

The SME Roadmap runs through the whole document rather than sitting in a box at the end: lotting requirements to match firms' expertise, engaging a range of supplier profiles during market engagement, publishing and maintaining pipelines so smaller firms can plan resources, applying proportionate timescales that allow credible bids and account for security clearance and onboarding, and designing evaluation so quality is not bypassed by the lowest day rate.

The Playbook makes the commercial argument bluntly. Do not fall into the trap of only going for known suppliers. Ministers are increasingly looking for subject matter experts in specific sectors rather than generic advice, and that generic advice is often more expensive than the real experts. Smaller and lesser known suppliers may hold exactly the expertise being sought.

None of that happens by accident. It happens because someone published a pipeline, ran an open request for information, allowed enough time in the timetable, and wrote lots that reflect how the market is actually structured rather than how the internal programme happens to be organised.

The takeaways

• Exhaust internal options and reuse existing knowledge before going to market. That test drives everything else.
• Consultancy fills capability gaps. Capacity shortages belong to contingent labour or a Statements of Work route.
• Specify the problem and the outcomes, not the inputs, and back it with measurable milestones.
• Make knowledge and skills transfer a specified, evaluated and contracted deliverable, not an aspiration.
• Assess IR35 case by case, and take specialist advice where consultants sit inside Civil Service teams or move into delivery.

Want the full breakdown?

The complete explainer covers the key facts, the requirements in detail and a practical action list, free and printable in the Procurement Library.