DevOps Engineer IR35 Agreement Template UK
DevOps engineers operating through a Personal Service Company face significant exposure under Chapter 10 of the Income Tax (Earnings and Pensions) Act 2003, commonly known as IR35. Without a properly drafted contract, HMRC can challenge your outside-IR35 status, resulting in substantial tax liabilities, interest, and penalties. A robust IR35 agreement demonstrates genuine business-to-business arrangements by evidencing substitution rights, lack of control, and mutuality of obligation — the three pillars HMRC scrutinises most closely. For medium and large engagers, the off-payroll working rules since April 2021 place the Status Determination Statement obligation squarely on the client, making contractual clarity essential for both parties. Whether you are a DevOps contractor or a hiring business, a well-structured agreement protects everyone involved. Generate your DevOps Engineer IR35 Agreement now to stay compliant and contracting with confidence.
Generate your IR35 Agreement free →Key clauses in a IR35 Agreement
Right of Substitution
This clause establishes the contractor's genuine right to provide a suitably qualified substitute to perform the DevOps services without requiring the client's consent beyond reasonable vetting. Under IR35 case law, including Autoclenz Ltd v Belcher [2011], HMRC and tribunals examine whether substitution rights are real and exercisable in practice, making this one of the most powerful indicators of outside-IR35 status.
Mutuality of Obligation Exclusion
This clause explicitly states that the client is under no obligation to offer work and the contractor is under no obligation to accept it, negating the employment-like expectation of ongoing engagement. Mutuality of obligation is a fundamental employment test established in cases such as Nethermere (St Neots) Ltd v Gardiner [1984], and its absence is critical evidence that a DevOps contractor sits outside IR35.
Status Determination Statement Acknowledgement
This clause records the client's Status Determination Statement issued under Chapter 10 ITEPA 2003, confirming the client has fulfilled its duty to assess and communicate the contractor's IR35 status with reasoned conclusions. Since the April 2021 off-payroll working reforms, medium and large private sector clients are legally required to provide this statement, and its inclusion in the contract creates an auditable record that protects both the PSC and the engager.
Generate your IR35 Agreement in 2 minutes
AI-powered. Jurisdiction-aware. No account required for your first contract.
Generate free →Frequently asked questions
Does a contract saying I am outside IR35 actually protect me from HMRC?
A contract alone does not determine IR35 status — HMRC and employment tribunals look at the reality of the working arrangement, not just what the written contract says, as confirmed in Autoclenz Ltd v Belcher [2011]. However, a well-drafted contract that accurately reflects genuine working practices, including real substitution rights and no mutuality of obligation, is strong supporting evidence of outside-IR35 status. It should be used alongside a CEST tool assessment and consistent day-to-day working practices to build a robust defence.
Who is responsible for issuing the Status Determination Statement for my DevOps contract?
Since April 2021, under the off-payroll working rules in Chapter 10 ITEPA 2003, the responsibility for issuing a Status Determination Statement lies with the end client if they are a medium or large private sector organisation. The statement must set out the client's conclusion on IR35 status and the reasons behind it, and must be passed down the supply chain to the fee-payer. Small companies, as defined under the Companies Act 2006, are currently exempt, meaning the IR35 assessment responsibility reverts to the PSC contractor.
Can I use the same IR35 contract template for every DevOps engagement?
Using an identical contract without tailoring it to each specific engagement is risky, as HMRC will scrutinise whether the contract genuinely reflects the actual working arrangement with that particular client. Key terms such as the scope of DevOps services, substitution provisions, control mechanisms, and project deliverables should be specific to each engagement to withstand challenge. A template is an excellent starting point, but it must be reviewed and customised to accurately represent the nature of each individual contract.
The information on this page is for general informational purposes only and does not constitute legal advice. Contracto generates AI-assisted contract templates — they are not a substitute for advice from a qualified solicitor. For high-value or complex engagements, always seek independent legal review.