Two Questions, One Calm Chat: Getting IR35 Off the Critical Path
Photo: Yazan.Masannat, CC0, via Wikimedia Commons
The first time a client asked me about IR35, I made the mistake of treating it like a court case. I turned up with printouts, acronyms and the facial expression of a man about to explain quantum mechanics to a dog. It went about as well as you’d expect.
These days I do it differently. I still care about the rules, but I start with two plain-English questions before the contract is signed. Not because I’ve become cavalier, but because a calm, early conversation is worth more than a panicked scramble in week six. I’m a consultant, not a tax adviser or employment lawyer, so this isn’t legal advice. It is the practical chat I wish I’d had years ago.
The conversation nobody wants to start
IR35 has a reputation problem. Mention it and people either glaze over or reach for a disclaimer. That’s understandable: the off-payroll working rules, which have applied in the private sector since 2021, ask whether a contractor would have been an employee if they’d been hired directly. The answer depends on the reality of the working relationship, not just the label on the contract.
For a solo consultant, the risk is obvious. For the client, there’s a compliance question and a reputational one. For the project, there’s a simpler risk: if nobody talks about status until the invoice stage, everyone starts making decisions in a fog. I’d rather clear a small amount of fog at the start.
Question one: who really controls the work?
The first question is about control. I ask: ‘On a normal week, who decides what the work looks like day to day?’
That usually opens a useful conversation. Does the client set the hours, or do I? Do they require me to be in their office or on their Slack all day? Do they direct the sequence of tasks, or do they agree the outcome and leave me to deliver it? Who approves the work, and how often? If something changes, who decides the new priority?
Control isn’t a single switch. It’s a set of habits. A client might not care where I work, but insist on signing off every small decision. Another might give me a desk and a login, then leave me alone for a month. The point isn’t to score points; it’s to notice what the working relationship will actually feel like.
If the answer is ‘we’ll direct you like a member of staff’, that’s worth knowing before signing. It doesn’t automatically mean the contract is inside IR35, but it does mean we need to talk about why, and whether the arrangement can be made clearer. If the answer is ‘we’re buying an outcome and you’ll tell us how you’ll deliver it’, the project has a better chance of staying clean. Either way, the answer belongs in the project file, not just in someone’s memory.
Question two: what happens if I can’t do it myself?
The second question is about substitution and personal service. I ask: ‘If I were ill or unavailable, what would you expect to happen?’
This one makes people pause. Some clients say, ‘We chose you — we want you.’ That’s flattering, and it’s also useful information. Others say, ‘We’d need someone with the same experience, but yes, we’d consider it.’ Others look at me as if I’ve asked whether they’d accept a horse.
The practical version is: could I send another suitably qualified person to do the work, and would the client accept them? If the answer is a flat no in every circumstance, that points towards personal service. If substitution is a real right, used in practice and not just buried in a contract schedule, that’s a different picture. The details matter, which is why I don’t try to settle it with a slogan.
I also ask what would happen in reality, not just on paper. A contract might say substitution is allowed, but if the client would never accept it, the paperwork is doing a lot of heavy lifting. That’s the sort of gap a calm conversation can surface early.
Write it down without playing lawyer
Once we’ve had the chat, I write a short note. Nothing theatrical: date, project, who was in the room, the two questions, and the answers in plain English. I add any agreed review point — for example, ‘revisit if the working pattern changes’ — and attach it to the statement of work or kick-off note.
Depending on the client’s size, the off-payroll rules may mean they issue a status determination statement. If they do, I read it properly and ask questions rather than filing it like a tax certificate. If they don’t, the note still helps. It gives both sides a shared record of what we understood at the start. It isn’t a legal opinion, and I don’t pretend it is. It’s a project document.
The rule I follow is simple: document the answer, not the argument. A note that says ‘client confirmed they will set priorities and approve deliverables, but not day-to-day methods’ is more useful than three pages of copied legislation. If the arrangement changes — a new manager, a longer stint, a different scope — we update the note. That’s it.
A calm start beats a scramble
The best IR35 conversation is boring. It happens before the contract, takes fifteen minutes, and ends with both sides knowing what they’ve agreed. The worst one happens in month four, when the client’s finance team asks a question and everyone suddenly remembers that status was never really discussed.
I’m not pretending two questions solve every case. They don’t. They won’t replace proper advice when the facts are messy, and they won’t make a badly designed engagement safe. But they do stop the subject becoming a taboo. They give the client a chance to say what they actually need, and give me a chance to decide whether I’m the right person to provide it.
For a solo consultant, that’s worth more than a folder of disclaimers. Get the chat on the calendar early. Ask the two questions. Write down the answers. Then get on with the work.