Your SOW is the game plan, not the strategy

2 November 2026

A statement of work (SOW) documents what will be delivered, but it doesn't create value on its own. Before you write one, you need to settle the outcome, the constraints, how success will be measured and who is accountable. Without that strategy behind it, even a well-written SOW leaves you unable to adapt when things change.


I love cricket, and it's a useful way to think about this. You can pick a strong XI, but without a plan for the conditions and the opposition, you're just hoping individuals perform.


  • The suppliers are your team sheet.
  • The SOW is your game plan.
  • The outcome-based strategy is the captaincy: the preparation, the tactics and the ability to adjust when the pitch changes.


The mistake: confusing paperwork with planning


An SOW feels like progress. It has structure, deliverables and milestones. But it only records the intent. If the thinking hasn't been done first, you're locked into a plan that can't flex when someone underperforms or the conditions change.


Seven things to settle before the SOW


1. The business outcome. Not "I need someone who can code", but "I need this module delivered, tested and handed over in four weeks". That clarity is the difference between staffing and buying a service.

2. The conditions. Every project has constraints: the budget, compliance requirements such as IR35, and how experienced the supplier is. Some suppliers need more captaincy than others.

3. How you'll measure success. Completion time, quality, performance after delivery? If you don't define this first, the SOW can't reflect it.

4. Accountability. The supplier owns the outcome, payment is tied to delivery, and changes to scope are handled through an agreed process rather than informally.

5. Dependencies and assumptions. Projects rely on things outside the supplier's control: internal approvals, other systems, access to people. Write them down, or your plan will be blindsided when they shift.

6. A definition of done. Is the work done when it's written, or when it's tested and live? Don't assume everyone agrees. Spell it out.

7. Contingency. Rain can turn a 50-over match into 20. Plan for scope changes, delays and supplier issues with clear change clauses and a fallback.


What happens without a strategy


  • Scope creep: no boundaries means overruns.
  • Compliance risk: vague deliverables make IR35 harder to defend.
  • Low accountability: suppliers get paid without delivering value.
  • Contractors treated like employees: people drift into ongoing roles with no clear outcome.
  • No way to adjust: when things change, there's no plan to change with them.


I regularly see SOWs that describe tasks and hours rather than measurable outcomes. If yours do, the underlying question is still the same one: do you need someone present, or something delivered?


What to do next


Before your next SOW, check you can answer:

  1. What's the outcome?
  2. What does success look like, and how will it be measured?
  3. Who owns delivery?
  4. What assumptions and dependencies are we relying on?
  5. Have we defined "done"?
  6. What happens if things go off-plan?


How I can help


I help organisations put the strategy in place before the SOW, set up practical SOW processes and keep them compliant.

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.
Magnifying glass on a teal background, illustrating a closer look at SOW contract myths
30 October 2026
SOW contracts are often seen as complex, costly and only for IT or big businesses. Here’s why those myths don’t hold up, and where SOWs really fit.