Is “services procurement” holding back SOWs?
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
- Ask your procurement and workforce teams what they each mean by "services procurement". The answers are often revealing.
- Map how a SOW engagement currently moves from request to contract, and where it slows down.
- Agree a simple, shared definition of what counts as a SOW and what doesn't.
- Set up a lighter-touch route for SOWs below an agreed value or risk level.
- 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.
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.









