You finish a project. The client is happy. Then comes the familiar message: “Can you just stay on for a bit and pick up whatever comes in?”
That's where many limited company contractors drift into trouble.
On the surface, it looks harmless. No big renegotiation. No formal new statement of work. Just more work, same team, same rhythm. But that casual extension can change the tax position of the whole engagement. If the relationship starts to look like the client must keep feeding you work and you're expected to keep taking it, IR35 mutuality of obligation becomes a live issue.
Most contractors obsess over substitution and control. Fair enough. They matter. But MOO is often the more basic question. If the engagement carries an ongoing obligation on both sides, HMRC has a much easier route to saying the arrangement looks like employment for tax purposes. And if you get that wrong, the cost isn't theoretical.
The sharp contractors don't just ask whether a contract says “outside IR35”. They ask whether the actual engagement still looks like a project business, or whether it has effectively become a rolling role.
The MOO Question Every Contractor Faces
You finish the project you were hired to deliver. Then the client asks you to stay on, keep an eye on things, pick up odd jobs, and be available while they work out what comes next.
That is the point where many outside IR35 engagements start to go wrong.
A defined project with a clear outcome usually supports an independent contractor position. An open-ended extension usually weakens it. Once your company is no longer being paid for a specific piece of work and starts being paid to remain available, HMRC has an easier argument that the relationship looks employment-like.
The problem is not the extension itself. It is the shift in obligation. If the client expects to keep providing work and your company is expected to keep accepting it, MOO becomes a significant risk. And if your company carries little commercial risk because payment continues regardless of defined output, HMRC will say the arrangement looks less like a business and more like a role.
Practical rule: If the original scope has ended, do not roll forward casually. Stop and assess the new engagement before any extension is agreed.
Business risk is the point many directors miss. A genuine contractor takes on uncertainty. There may be a fixed scope, milestone pressure, rework exposure, gaps between projects, and no guarantee of follow-on revenue. An employee-style arrangement removes that uncertainty. The work keeps coming, the pay keeps flowing, and your company stops looking like it is operating on a project basis.
Ask these questions before you agree to any renewal:
- What is my company being engaged to deliver now? If there is no clear deliverable, you have a status problem.
- What commercial risk does my company carry on this phase? If payment depends mainly on turning up and staying available, your position is weaker.
- Can the client stop offering work without breaching the deal? If there is an expectation of a steady pipeline, MOO risk rises.
- Can my company decline work outside the agreed scope? If refusal is unrealistic in practice, independence is already being eroded.
HMRC does not care what you call the engagement; it cares what the relationship is.
The smart move is to treat every extension as a fresh status review. If the new phase does not have a defined outcome, a real right to refuse extra work, and visible business risk on your side, fix it before you sign.
What Mutuality of Obligation Really Means
At its simplest, mutuality of obligation asks whether the client is obliged to provide paid work and whether the worker is obliged to accept and perform it. HMRC's own Employment Status Manual makes the point clearly: Mutuality of obligation is a foundational employment status test in the UK's IR35 legislation, requiring that an engager is obliged to provide paid work and the worker is obliged to accept and perform it; without this 'wage-work bargain,' no contract of any kind exists, making MOO a pre-condition to establishing employment status under HMRC's Employment Status Manual (ESM0543), as set out in HMRC Employment Status Manual ESM0543.
The irreducible minimum
Many contractors often find this confusing. They hear “mutuality of obligation” and assume any paid contract automatically makes them inside IR35.
That's too crude.
There is an irreducible minimum in almost any contract. Someone agrees to do work. Someone agrees to pay for it. Without that bargain, there's no contract at all. Contractor Calculator summarises this point well in its explanation that the minimum obligation to pay for work and provide work or skill exists in both employment and self-employment arrangements, so it doesn't by itself distinguish one from the other in this overview of MOO under ESM0543.
So the basic wage-work bargain isn't the whole test. It's just the starting point.
The real commercial question
The practical issue is whether obligations extend beyond the specific task or deliverable.
That's what matters in real-world IR35 mutuality of obligation analysis. If your company is hired to complete a defined piece of work, gets paid for that work, and then the relationship ends unless both sides actively renegotiate, that looks much more like a business-to-business arrangement.
If, on the other hand, the client is expected to keep feeding work into the relationship and you're expected to keep accepting it, the arrangement starts to look employment-like.
A sensible way to test this is to strip out the legal language and ask:
- Is this a project or a role?
- Does the engagement end when the agreed result is delivered?
- Would refusing extra work cause friction, penalty, or termination?
The best outside-IR35 contracts don't just say there is no obligation for future work. The working relationship proves it.
Where contractors go wrong
Many limited company directors rely too heavily on wording. They insert a “no obligation to offer or accept further work” clause and assume they're covered.
That clause helps. But it won't rescue a bad reality.
If you attend every planning meeting, remain continuously available, and accept whatever lands in your queue after the original scope has finished, you're giving HMRC a much stronger picture than the contract text.
The plain-English definition is this: MOO becomes a risk when the engagement stops being a discrete commercial purchase and starts looking like an ongoing commitment on both sides.
How HMRC and Tribunals Test for MOO
The law has moved in HMRC's favour. If you're still relying on old contractor folklore about MOO, you're behind.
The major turning point was the UK Supreme Court ruling in mid-September 2024, which sided with HMRC against Professional Game Match Officials Limited. The Court held that merely agreeing to work for an organisation is sufficient to establish mutual obligations, which supports the methodology behind HMRC's CEST tool, as explained in this analysis of the PGMOL Supreme Court ruling.
What that ruling changes
The practical message is blunt. You can't build your entire defence around the idea that MOO only exists if the client must keep offering work forever and you must keep accepting it forever.
That narrower reading has taken a hit.
The Supreme Court position gives HMRC stronger footing to say that once work is agreed and done for payment, the basic mutual obligation is already there. That means the battleground shifts. Contractors need to spend less time pretending MOO doesn't exist at all and more time proving the engagement is still a genuine contract for services when viewed as a whole.
That includes control, the shape of the assignment, and the actual commercial behaviour between the parties. If you need a broader grounding on how this fits into status reviews, read this IR35 guide.
Tribunals look at behaviour, not slogans
This is the point many directors still miss. A contract can say all the right things and still fail if daily reality says something else.
Tribunals don't stop at the paperwork. They examine how work flowed, who decided what happened next, whether the contractor had real freedom to decline extra tasks, and whether the arrangement kept rolling by default.
Watch this for a useful overview before you assess your own position:
The no-obligation clause is not magic
A “no obligation” clause is still worth having. But don't kid yourself. It's evidence, not protection.
If the client always has work waiting, if your company is retained to be generally available, and if nobody seriously treats each new piece of work as optional or separately negotiated, HMRC will argue the actual relationship overrides the drafting.
That's why the strongest outside-IR35 engagements feel commercially distinct in practice. They start with a defined need, run to an agreed output, and end unless both sides make a fresh decision.
If your contract says one thing and your calendar says another, HMRC will care more about the calendar.
The key lesson from HMRC and tribunal behaviour is simple. MOO isn't tested in a vacuum. It sits inside the wider factual picture. And after PGMOL, contractors need better evidence, not better wishful thinking.
MOO in Practice Inside vs Outside IR35
Theory is useful. Diagnostics are better.
When you assess IR35 mutuality of obligation, stop asking whether the contract contains the right buzzwords and start asking how work is created, assigned, and extended. Practical indicators for outside IR35 status include engagements defined by specific outcomes rather than hours, negotiated extensions instead of assumed continuations, and the ability to refuse unrelated work without consequences. MOO is more likely to be present if notice periods exceed 30 days or assignments are framed around ongoing presence rather than results, as outlined in this practical guide to MOO indicators.
MOO indicators inside vs outside IR35
| Indicator | Sign of MOO (Likely Inside IR35) | Sign of No MOO (Likely Outside IR35) |
|---|---|---|
| Basis of engagement | You are engaged for ongoing support, capacity, or presence | Your company is engaged for a defined outcome or deliverable |
| Workflow | Tasks continue to arrive automatically | New work is separately agreed |
| Extensions | Renewals happen by default | Extensions are negotiated as fresh commercial decisions |
| Ability to refuse work | Refusing extra tasks would create problems | Your company can decline unrelated or additional work |
| Time expectation | The client values attendance and continuity | The client values completion of agreed results |
| Notice period | A long notice period points to an enduring relationship | End dates are linked to project completion or agreed milestones |
| Scope creep | You absorb new requests as part of the role | Out-of-scope work triggers a new quote, change request, or separate agreement |
Two common contractor scenarios
The first is the project contractor. Your company is brought in to deliver a migration. The statement of work sets out the output. When the work is done, the engagement ends unless there is a separate negotiation for a new phase. You can reject unrelated work without penalty. That's the shape you want.
The second is the rolling team member. The original project finishes, but your company keeps supplying you to pick up tickets, attend recurring internal meetings, and remain on hand for whatever comes next. Nobody revisits scope properly. That's where MOO risk grows fast.
If your engagement looks more like the second scenario, you should review it against broader outside IR35 indicators and planning points.
Red flags worth taking seriously
Not every warning sign is fatal on its own, but combinations matter.
- Long notice periods: They suggest the parties expect an ongoing relationship rather than a finite piece of work.
- Hours over outcomes: If the client buys your weekly availability instead of a business result, the arrangement looks less like consultancy.
- Assumed continuation: If everyone treats renewal as automatic, the engagement starts to resemble a role.
A contract can be labelled “outside IR35” and still fail the reality test if the assignment is built around continuity rather than delivery.
Use the table above impartially. Don't score yourself based on what the contract intended at the start. Score the engagement as it operates today.
How to Evidence a Lack of Mutuality
Your contract says “project delivery”. Six months later, your company is still supplying you three days a week, picking up whatever lands in the queue. That is how an outside IR35 position weakens. If you want a defensible MOO position, build the evidence while the engagement is live.
Start with the point many directors leave too late. Business risk is not a side issue. It is one of the clearest ways to show the client is buying a service from a business, not retaining a worker on an ongoing obligation basis. Then make sure the contract and day-to-day reality support that position.
Contract drafting that helps
Draft for a commercial project, not a role.
- Define deliverables and acceptance criteria: Tie payment to outputs, milestones, or a specified phase of work.
- State there is no obligation for further work: Make it explicit that once the agreed scope ends, neither party must offer or accept anything else.
- Require a fresh agreement for extras: New tasks should sit under a change request, new statement of work, or separate contract.
- Keep notice periods short and commercial: Long notice periods suggest ongoing commitment, which weakens your MOO position.
- Include rectification terms: If your company must fix defective work at its own cost, that supports business-to-business status.
A clean contract will not save poor facts. It does give you a much better starting point.
Working practices that carry more weight
HMRC will look past nice wording if the engagement operates like a standing arrangement.
Act like a supplier. Record scope changes in writing. Push back on work that falls outside the agreed brief. If the client wants more, reset the terms and document it. If your setup runs through a personal service company in the UK, that discipline matters even more because the company, not you personally, should be seen as taking on the work and the risk.
One practical test helps. Ask yourself what happens when the agreed task ends. If the answer is “we wait for the next piece and carry on”, your evidence is weak. If the answer is “we stop, renegotiate, and issue fresh paperwork”, your position is stronger.
Why business risk matters so much
A strategic point most articles miss is the importance of business risk.
Real financial exposure cuts directly against HMRC's preferred story on MOO. If your company only gets paid when agreed work is accepted, has to correct defects without charging again, or can make more profit by delivering efficiently, the client is paying for a result. That is a business relationship. It is not a promise to keep providing work and pay for your ongoing availability.
Use that deliberately. Build commercial terms that show your company can lose margin, incur rework cost, or wait for acceptance before invoicing. Those features do more than improve the optics. They help prove that your availability alone does not create an open-ended expectation of paid work.
Key distinction: Employment points toward payment for doing a role. Independent contracting points toward payment for delivering an agreed result and bearing the commercial consequences.
Keep evidence HMRC can actually test
Opinions are useless without documents.
Keep signed statements of work, change requests, milestone approvals, invoices tied to accepted deliverables, and emails showing that extensions or new phases were separately negotiated. Keep records where your company rejected out-of-scope work or priced it separately. If you rely on rectification terms or acceptance-based payment, keep the paperwork that proves those clauses were used in practice.
That file is what protects you. Without it, you are left arguing intention after the event.
Financial Risks and When to Seek Advice
Your contract says outside IR35. Six months later, you are still with the same client, still doing whatever lands in the queue, and no one has signed a new statement of work. That is when MOO starts costing real money.
If HMRC decides the engagement operated like employment, the fallout is rarely limited to a technical disagreement about wording. You can face backdated tax, National Insurance, interest, and significant financial penalties. The bigger problem is usually preventable drift. The contract began as project work, but the engagement evolved into paid continuity.
Where the financial pain usually starts
The warning sign is not just a bad clause. It is a pattern.
A defined piece of work becomes ongoing support. New tasks get added without fresh pricing. Acceptance criteria disappear. Payment starts looking less like a fee for a result and more like money for showing up and staying available. Once that happens, HMRC has a much easier story to tell.
Business risk is your strongest counterweight here. If your company can lose margin, absorb rework costs, wait for sign-off before invoicing, or quote separately for changes, that points away from mutuality and toward a genuine supplier relationship. Directors often underuse that argument. They focus on substitution and control, then leave out the commercial facts that show the client was buying an outcome, not your ongoing presence.
When self-assessment stops being enough
Get a proper review if any of these apply:
- The engagement now looks like BAU support: regular operational work is harder to defend than a defined project.
- Extensions were agreed informally: repeated carry-ons without new scope suggest continuing obligation.
- Your company is paid on a time basis with little delivery risk: that weakens the argument that you were engaged for a commercial result.
- Rectification, milestone acceptance, or out-of-scope pricing exist on paper but were never used: HMRC will test what happened in practice.
- The client expects continuity from your company rather than a specific deliverable: that is where MOO arguments gain traction.
- You cannot show real business risk: no exposure to overrun, rework, delayed acceptance, or reduced margin leaves your position exposed.
One weak point can be manageable. Several together usually mean the engagement needs immediate attention.
A practical decision test
Ask three blunt questions.
If the current assignment ended today, would the client owe your company more work? Could your company refuse the next piece of work without commercial fallout beyond ending the engagement? Do your documents and invoicing records show payment for defined deliverables, with genuine financial exposure if delivery went wrong?
If you cannot answer yes, yes, and yes, stop relying on assumptions.
Seek advice when the facts have become muddled, not when the tax enquiry arrives.
The sensible next step
A good IR35 review should do more than label the contract high or low risk. It should identify what needs changing in the actual engagement: scope, renewal process, deliverables, acceptance terms, rectification obligations, pricing for change, and evidence of business risk.
Act before the next extension. Once a rolling arrangement settles into habit, fixing the paperwork alone will not rescue the position.
If your current contract has become a rolling engagement, or you're not sure whether the working practices still support an outside-IR35 position, Tax Compass can help you understand the issues clearly and decide whether a specialist review is worth taking further.