IR35 for IT Contractors: The Complete Guide

IR35 has always applied across every sector, but technology contractors - software developers, architects, DevOps engineers, data scientists, business analysts, and project managers - face a specific set of structural challenges that make careful IR35 management particularly important. The nature of IT work creates patterns that can look like employment even when the contractor is genuinely operating an independent business.

Why IT contractors attract IR35 scrutiny

Several characteristics of IT contracting commonly arise in IR35 investigations:

• Long-duration single engagements. IT projects frequently run for 12-24 months or longer. A contractor who has worked at the same client for two years, embedded in a product team, looks more like an employee than a short-term specialist brought in to solve a discrete problem.
• Deep workflow integration.Modern software development typically means using the client's tools - Jira, Confluence, Slack, GitHub repositories - following the client's processes, and reporting progress through the client's management structure. All of these can look like integration.
• Substitution limitations. Technical clients often resist substitution on grounds of system access, security clearances, NDA requirements, and the practical cost of knowledge transfer. These commercially understandable restrictions weaken what would otherwise be a strong outside-IR35 indicator.
• High day rates. HMRC is financially motivated by high-value cases. IT contractors at the senior end - architects, engineering managers, data leads - typically command day rates that make the tax at stake significant.

Control in an Agile environment

The control test asks who determines how, when, and where work is done. In a modern Agile team, this can be difficult to assess cleanly. A contractor who is part of a scrum team, attends daily stand-ups, takes work from a sprint backlog, and follows the client's engineering standards appears, superficially, to be under significant control.

The distinction that courts draw is between control over the methodof work and coordination for the purposes of a project. Following an industry-standard development process (Agile, Scrum, Kanban) does not of itself indicate employment control - any more than a building contractor following a client's specifications is an employee. What matters is whether the client dictates how the contractor solves technical problems, rather than simply defining the outcome required.

Relevant questions for an IT contractor:

• Can you choose your own approach to solving a technical problem?
• Are standups voluntary coordination, or mandatory reporting with performance management?
• Can you choose when to work (within reasonable project constraints)?
• Do you have the ability to work remotely or at a time that suits your working style?
• Is there a senior employee who functions as your day-to-day line manager?

Substitution in IT

IT contractors frequently face genuine commercial obstacles to substitution: systems access requires security clearance, codebases require knowledge transfer time, financial services and government clients have strict vetting requirements. These are legitimate business reasons for limiting substitution - but they weaken one of the strongest outside-IR35 indicators.

The following approaches help preserve the substitution argument in an IT context:

• Ensure the contract includes a substitution clause, even if subject to security vetting approval - a client can reasonably approve competency without approving a specific individual
• Make the clause substantive: the substitute should be at your cost, from your business network, with a handover you are responsible for
• If you have ever arranged cover for a client - even informally - document it
• Avoid language where substitution is “at the client's sole discretion with no obligation to accept” - this effectively nullifies the clause

Part and parcel - integration risks in IT

IT contractors are particularly susceptible to integration indicators:

• Client email address. Being given a client email (name@client.com) is a significant integration indicator. Avoid using it for anything other than internal coordination where necessary, and ensure your own business email is visible to third parties.
• Staff directory listing.Appearing on the client's public website or internal directory as a team member, not a contractor, points to integration.
• ID badge and permanent desk. Having the same access and facilities as a permanent employee - rather than visiting access - is an integration indicator, though not conclusive.
• Performance management.Receiving a performance review, having an “objective-setting” meeting, or being included in team development planning are employment characteristics.
• Internal-only meetings. Regular attendance at all-hands meetings, company away-days, or other events not open to external suppliers contributes to the integration picture.

Building a strong BOOA case as an IT contractor

Business on own account (BOOA) is often the factor that saves an otherwise borderline case. IT contractors have genuine advantages here if they cultivate them:

• Multiple clients. Even working for two clients in a 12-month period - not necessarily concurrently - demonstrates a business operating in a market rather than attached to a single employer.
• Professional indemnity insurance. PII is standard for IT professionals and is strong evidence of operating as a business. Make sure it is in your company name and is current.
• Own equipment.A laptop, development tools, and test equipment in your company's name - even if a specific client requires you to use their hardware on site - supports BOOA.
• Business website and LinkedIn as a company. A professional business identity separate from your employment at any one client signals genuine independence.
• Fixed-price or deliverable-based engagements. If any of your work is priced by output rather than by time, this is powerful BOOA evidence.
• Defect liability. Ensuring your contracts include a clause requiring you to fix defects at your own cost - rather than charging extra - demonstrates financial risk consistent with self-employment.