Programme directors face the “how do we deliver this?” question dozens of times a year. Contract or SoW is one of the most consequential answers, and one most organisations default on rather than genuinely evaluate.
The default is usually contract. Framework agreements exist, procurement processes are familiar, and the hiring team knows how to source bodies. SoW gets treated as a specialist option.
That’s usually the wrong way round. The delivery shape should determine the commercial vehicle, not the other way around. Here are the five signals that consistently point toward SoW. If two or more apply to your programme, it’s worth a proper conversation before you build the contract shortlist.
1. You can describe “done” more clearly than you can describe “who”
If you can articulate the destination more easily than the team you need to get there, that’s SoW territory.
“The CRM migrated to the new platform, with these five integrations, by end of Q1” is an outcome. Working out whether you need three senior engineers or six mid-level ones is a harder question. In SoW, the supplier owns that. You own the definition of done.
2. The scope is delivery, not discovery
SoW works when the destination is known and the path is buildable. It works badly for genuinely exploratory work.
If the programme involves testing hypotheses or making architectural decisions that could go multiple ways, contract fits better. If discovery is done and what remains is execution against a defined target, SoW aligns the commercial and delivery incentives cleanly.
3. You don’t have internal leadership bandwidth
Contract engagements assume you have the internal capacity to direct the work. A team of contractors needs a technical lead, a delivery lead, and someone accountable for day-to-day priorities.
Without that scaffolding, contractor spend often disappoints. SoW removes the requirement. The supplier owns delivery leadership as part of the engagement.
4. You need budget predictability more than flexibility
Contract engagements are typically time-and-materials. Flexible, but exposed to overruns and hard to defend mid-programme.
SoW, priced correctly, gives you a defined spend envelope tied to defined outcomes. The commercial conversation with finance is easier. So is the internal reporting, because progress against milestones is more legible than burn rate against headcount. As we set out in our recent piece on the procurement shift toward SoW, budget predictability is one of the biggest reasons buyers are asking for outcome-based structures in 2026.
5. The IR35 or supply chain risk profile is tightening
With April 2026’s Joint and Several Liability rules now applying to umbrella arrangements, contractor supply chains carry materially more compliance weight than they did twelve months ago. HMRC can pursue unpaid tax through the chain, including at end-client level in some circumstances.
SoW moves that compliance burden onto the supplier. If your internal audit, finance, or procurement teams have flagged contractor risk in the last six months, SoW is worth evaluating seriously.
When contract is still the right call
None of this means contract is the wrong shape for every programme. It remains the better option when the work is genuinely exploratory, when strong internal leadership is already in place, when scope is likely to shift materially, or when what you need is specialist surge capacity rather than delivery ownership. As we’ve set out previously, contract and SoW solve different problems.
The bottom line
The choice isn’t a procurement preference. It’s a delivery decision with commercial consequences. Programmes that suit SoW are the ones where the destination is clearer than the crew, where budget predictability matters more than flexibility, and where the risk profile of a scoped engagement genuinely fits the work.
If you’re scoping a programme for Q3 or Q4 delivery, and want a second opinion on the right shape before committing, get in touch.
