Is “services procurement” holding back SOWs?

28 October 2026

Often, yes. "Services procurement" means one thing to procurement teams and something quite different to workforce teams, and when SOW engagements get lumped in with it, they pick up a reputation for bureaucracy they don't deserve. Clearer language and a shared approach between the two teams let SOWs do what they're good at.


One term, two meanings


For procurement teams, services procurement usually means categories, frameworks and supplier contracts. For workforce teams, it often means engaging external people through statements of work.

It's a bit like the word "diet". For one person, it means a structured eating plan; for another, it just means what they eat every day. Say "I'm starting a diet" and the listener has to guess which one you mean. In a business, that kind of confusion wastes time and switches stakeholders off.


Why it gets in the way


It sounds like bureaucracy. For many managers, "procurement" signals cost control, approvals and slow processes. When SOW engagements are filed under that heading, they lose their appeal as a fast, flexible way to get a defined piece of work done.


The teams measure different things. Procurement tends to focus on supplier categories, value and cost. Workforce teams focus on outcomes, speed and compliance. When both are talking about "services procurement", they can agree on the words while meaning different things.


The data doesn't line up. Even where systems such as a VMS and the finance system are connected, each team reports on different measures, and nobody gets the full picture.


Why SOW engagements deserve better


Used well, SOWs are one of the most useful ways to engage external expertise:


  • Clearer compliance. A well-written SOW is built around deliverables, milestones, and outcomes, rather than a person filling a role, making it easier to stay on the right side of IR35 and off-payroll rules. It only works if the SOW reflects how the work is really delivered.
  • Better value. You pay for an outcome, not hours, so the supplier carries more responsibility for delivery.
  • Flexibility. SOWs let you scale expertise up and down around projects without adding permanent headcount.


Getting the language and the approach aligned


This isn't about abandoning good procurement practice. It's about being precise:


  • Let "services procurement" stay with procurement, covering its categories and contracts.
  • Treat SOW engagements for external people as an outcome-based way of engaging talent, with a process designed for speed and clear deliverables.
  • Agree, between procurement and workforce teams, who owns which part: sourcing, contracting, compliance checks and performance management.
  • Report on both cost and outcomes, so each team sees what matters to the other.


What to do next


  1. Ask your procurement and workforce teams what they each mean by "services procurement". The answers are often revealing.
  2. Map how a SOW engagement currently moves from request to contract, and where it slows down.
  3. Agree a simple, shared definition of what counts as a SOW and what doesn't.
  4. Set up a lighter-touch route for SOWs below an agreed value or risk level.
  5. Check a sample of current SOWs against how the work is actually being delivered.


How I can help



I help organisations set up SOW processes that are quick to use and stand up on compliance, and bring procurement and workforce teams onto the same page.

How I support businesses

A first conversation, on me

Tell me what's going on with your business. You'll come away with a clearer view of your options, whether or not we work together.

More Insights

Calendar on a teal background, illustrating running a staffing tender to a fixed deadline
20 November 2026
How to run a staffing supplier tender against a fixed go-live date: work backwards, settle the big decisions early and protect time for mobilisation. Be Pro-active!
Cog on a teal background, illustrating implementing an MSP and VMS programme
18 November 2026
Most MSP and VMS rollouts struggle because of process, people and suppliers, not the technology. What to get right before, during and after go-live is critical.
Mobile phone on teal background, illustrating workforce technology for blue-collar and white-collar
16 November 2026
Shift pay rules, approvals, pricing and invoicing all work differently for blue-collar staff. Why one workforce system rarely handles both well and what to do.
Microchip on a teal background, illustrating AI tools for managing the external workforce
13 November 2026
AI tools can transform how you source and manage external workers, but only with a clear strategy. Five things to get right before you invest.
Clock face on a teal background, illustrating measuring contractor results rather than hours
11 November 2026
Timesheets show how long contractors worked, not what they achieved. How to measure contingent workers on outcomes, even in traditional engagements.
ID card on a teal background, illustrating how external workers are classified and engaged
9 November 2026
Misclassification isn’t only an IR35 issue. How the wrong engagement model creeps in, the early warning signs, and three simple fixes at the start.
Eye icon on a teal background, illustrating visibility of the whole external workforce
6 November 2026
Most organisations track contractors but not consultants and SOW workers. Why that gap exists, the risks it creates and how to close it without losing flexibility.
Circular arrows on a teal background, illustrating staffing models chosen out of habit
4 November 2026
Traditional contingent staffing often wins because it’s familiar, not because it fits. The four mindset barriers behind it, and how to choose the right model.
Cricket stumps on a teal background, illustrating the strategy behind a statement of work
2 November 2026
A statement of work documents the plan, but it isn’t the strategy. Seven things to settle before you write a SOW, explained with a little help from cricket.