Are Your Statement of Work Contracts Actually Outside IR35?

Statement of work (SOW) contracts have become one of the most common ways businesses manage IR35 exposure since the 2021 off-payroll reform shifted status-determination responsibility onto end clients. A genuinely outsourced SOW moves that responsibility down the chain to the supplier. A SOW that only looks outsourced does not - and HMRC has had four years to learn the difference.

Here is what actually makes a SOW genuine, the five questions HMRC asks when it wants to challenge one, and how to check your own arrangements before Q4.

Key takeaways

• SOW-based engagements have grown since April 2021, because a genuinely outsourced service shifts IR35 determination responsibility to the supplier rather than the end client.
• A statement of work does not automatically place an engagement outside IR35 - HMRC assesses the reality of the working relationship, not the label on the contract.
• HMRC weighs five factors: control, mutuality of obligation, substitution, financial risk, and integration.
• The most common failure mode is misalignment - a contract with strong outside-IR35 clauses that does not reflect how the engagement actually runs day to day.
• HMRC also looks for pattern risk: a large number of similar roles all treated as outside IR35 through SOW arrangements draws more scrutiny, not less.

Why SOW contracts became the default workaround

Before April 2021, contractors operating through personal service companies were largely responsible for their own IR35 status. The off-payroll reform moved that responsibility onto the end client for most private sector engagements - specifically, the client became liable for issuing a correct Status Determination Statement and for any resulting tax liability if it got that wrong.

A fully contracted-out service works differently. Where a business genuinely outsources a piece of work to a supplier or consultancy - rather than simply hiring an individual's time through an intermediary - HMRC's guidance treats the supplier as the client for IR35 purposes. That shifts the determination burden, and much of the liability, down the chain. It is easy to see why SOW-based engagements became attractive: done properly, they move risk away from the end client entirely.

The problem is what HMRC's own guidance says next: it can see through an arrangement that is labour supply dressed up as a contracted-out service. If the reality is that a supplier is simply placing an individual into the client's team to do a job the client directs day to day, relabelling the contract as a SOW does not change the substance - or the liability.

What actually makes a SOW genuine

A genuine SOW is built around an outcome, not a person's time. The supplier owns delivery of a defined piece of work, manages how it gets done, and is paid against results rather than hours or days worked. A disguised employment arrangement dressed as a SOW usually still has all of the substance of ordinary staff supply - it has just had a different label put on the paperwork.

The distinction sits in the working reality, not the contract wording. A SOW that reads well on paper but does not match how the engagement actually operates carries little weight if HMRC ever looks at it.

The five questions HMRC asks

Control

Who decides how, when, and where the work gets done? Genuine outsourcing leaves that with the supplier, not the end client's line managers.

Mutuality of obligation

Is the client obliged to keep providing work, and the individual obliged to accept it, in the way an employer-employee relationship would require? A true SOW is bounded by defined deliverables, not an ongoing expectation of work.

Substitution

Can the supplier send a different, suitably skilled person to deliver the work without the client's say-so? A genuine and exercised right of substitution is one of the strongest outside-IR35 indicators.

Financial risk

Does the supplier carry commercial risk, for example through fixed-price or milestone-based payment, responsibility for correcting its own errors, or the ability to profit or lose on the engagement? An employee does not carry this kind of risk.

Integration

Is the individual operating as part of the client's own team and structure, or delivering a discrete piece of work from outside it? The more someone looks and functions like existing staff, the harder outside IR35 becomes to defend.

Where SOW arrangements typically fail

The patterns below are illustrative composites based on common failure modes we see across SOW arrangements, not specific client cases:

• A SOW described a fixed-price project, but invoices were raised monthly against time worked rather than milestones delivered - undermining the financial risk argument entirely.
• The contract included a substitution clause, but the individual was interviewed and approved by name before the engagement began, and no substitution was ever exercised in practice - a right that exists on paper but not in reality carries little weight.
• A supplier was engaged to deliver a defined outcome, but the individual attended daily stand-ups, took direction from the client's project manager, and used client equipment and systems alongside permanent staff - indistinguishable, in practice, from an employee.

In each case, the paperwork said one thing. The working practice said another. HMRC looks at both, and the working practice generally wins.

What a defensible SOW actually includes

A clear scope definition

The deliverable is described as an outcome, not a role or a set of hours.

Defined acceptance criteria

There is an objective basis for confirming the work is complete, separate from ongoing supervision.

Milestone or output-based payment

Fees are tied to delivery, not time spent, so genuine financial risk sits with the supplier.

Absence of day-to-day direction

The client can specify what it needs, but not how, when, or by whom the work gets done on a daily basis.

Auditing your existing SOW contracts before Q4

• List every current SOW arrangement and note whether payment is genuinely milestone-based or effectively time-based in practice.
• Check whether any substitution clauses have ever actually been used - an unused clause is a much weaker indicator than an exercised one.
• Ask whether the individual attends internal meetings, uses client systems, or takes direction in ways that mirror how existing staff work.
• Flag any pattern where multiple similar roles have all been engaged via SOW and treated as outside IR35 - consistency without genuine variation is exactly the kind of pattern HMRC's own compliance approach looks for.

If you're relying on SOW to manage IR35 exposure, now is the right time to check your arrangements hold up.

Contact us to see how we can help.

FAQs

What's the difference between a SOW and a standard contractor agreement?

A standard contractor agreement typically engages an individual's time and skills directly. A statement of work engages a supplier to deliver a defined outcome, with the supplier - not the end client - responsible for how that outcome gets delivered and, where genuine, for the IR35 status of anyone involved.

Does having a SOW automatically make an engagement outside IR35?

No. HMRC assesses the reality of the working relationship, not the contract label. A SOW that does not reflect genuine outsourced delivery - in control, risk, and independence - carries little weight if the engagement is challenged.>

What are the five tests HMRC uses to assess IR35 status?

Control, mutuality of obligation, substitution, financial risk, and integration. No single factor is decisive - HMRC and tribunals weigh the overall picture the working relationship presents.

How do I know if my SOW contracts need reviewing?

Start with payment structure and substitution: if invoices track time rather than milestones, or a substitution clause has never been exercised, those arrangements are worth reviewing first. A short self-assessment can flag the highest-risk areas quickly.

Who is liable if a SOW arrangement fails an HMRC challenge?

If HMRC decides an arrangement was not genuinely outsourced, the liability and determination responsibility can fall back on the end client, regardless of what the contract intended. This is why working practices need to match the paperwork, not just the other way around.

Sources

• HMRC, 'Understanding off-payroll working (IR35)' - gov.uk/guidance/understanding-off-payroll-working-ir35
• HMRC, 'Outsourcing off-payroll working responsibilities (GfC4, part 12)' - gov.uk/government/publications/help-to-comply-with-the-reformed-off-payroll-working-rules-ir35-gfc4/outsourcing-off-payroll-working-responsibilities-part-12/