Contract clauses an AI consultant should never accept
6 minute read. Updated 2026-08-08.
Never sign an AI contract with uncapped liability, a broad indemnity for third-party claims arising from model behaviour, an IP assignment that swallows your pre-existing tools, or a warranty that a model will be accurate or bias-free. Ask for a liability cap tied to fees paid, a background IP carve-out, and a standard of reasonable care rather than a guaranteed outcome. Take legal advice before signing any contract you didn't write.
AI work needs sharper contract scrutiny than most consulting
A contract written for a generic software or advisory engagement doesn't anticipate what happens when the deliverable is a model that behaves probabilistically, keeps operating long after handover, and can affect thousands of decisions before anyone notices something is wrong. Clauses that would be routine in a fixed-scope build become dangerous when the thing you delivered keeps making decisions after you've left the room.
What follows describes the mechanics of clauses that come up repeatedly in AI engagements. It is not legal advice. Every contract is different, and a solicitor who has actually read yours is worth the fee before you sign anything with your name and your future exposure attached to it.
Uncapped liability
Some client-drafted contracts leave liability open-ended, or cap it so high it functions as open-ended in practice. In AI work this is a live risk, not a theoretical one: a model that produces a bad outcome across a large customer base can generate a loss far beyond anything you were paid to build it. Ask for liability capped at a fixed multiple of fees paid under the contract, commonly a figure equal to twelve months' fees, and get it written into the terms rather than promised verbally.
If a client insists their standard terms cannot be varied at all, treat that as information rather than a formality. It tells you how the relationship is likely to be conducted if something does go wrong later, and it's worth weighing against the fee before you sign.
Broad indemnity for third-party claims
An indemnity clause asking you to cover the client against any claim arising from your work sounds narrow until you notice it often doesn't distinguish between a mistake you made and a decision the client made about how to deploy what you built. If the client removes a safeguard you recommended and a customer is harmed as a result, a broadly worded indemnity can still land on you.
Ask that indemnity be limited to claims arising from your own negligence or breach of contract, and that it explicitly exclude any consequence of a decision the client made against your written advice. This is one of the clauses most worth a solicitor's time before you agree it.
IP assignment that swallows your background tools
Most contracts assign IP in the deliverable to the client, which is reasonable and expected. The danger is a clause broad enough to also assign IP in the frameworks, evaluation harnesses, or reusable code you brought with you and intend to use again for the next client. Without a carve-out, you can find yourself contractually unable to reuse your own toolkit on your next engagement.
Ask for a clear split: the client owns the specific deliverable built for them, you retain ownership of pre-existing background IP, and the client receives a licence to use it as embedded in what was delivered. Have the background IP listed by name in the contract or an appendix, not left implied by silence.
Warranties that guarantee a specific outcome
A clause warranting that a model will be accurate, unbiased, or will perform to a specified standard is a warranty you cannot actually keep, because model performance depends on data, deployment context, and use after handover, none of which stays under your control once the engagement ends. Signing it exposes you to a breach of contract claim over something that was never a fixed guarantee to begin with.
Ask instead for a standard of reasonable skill and care, evaluated against a testing methodology agreed and documented at the point of delivery, not against an outcome measured months later under conditions you never saw.
Non-compete clauses wider than the engagement
A non-compete preventing you from working for the client's competitors, or in the client's sector at all, for an extended period after the contract ends, is disproportionate for most independent AI work, because your value is built from working across similar clients repeatedly. Accept a narrow non-solicitation covering the specific team you worked with, not a sector-wide restriction that would effectively end your business.
If a client genuinely needs protection for confidential information, a well-drafted confidentiality clause covering their specific data and methods does that job without stopping you from working at all.
IR35 status left vague
Since April 2021, the client, not the contractor, makes the IR35 determination for medium and large private-sector clients. A contract that is silent on this, or that asserts an outside-IR35 status without matching working practices, leaves you carrying a risk that was never yours to carry in the first place.
Ask for the status determination statement in writing before you start, and check that the working practices described in the contract actually match how you will be treated day to day. A mismatch between what the paperwork says and how the engagement is run is where disputes come from later, not from the paperwork itself.
What to do about it
- Cap liability at a fixed multiple of fees paid, not left open-ended.
- Limit indemnity to your own negligence, excluding the client's own deployment decisions.
- Carve out and name your background IP before agreeing to any assignment clause.
- Refuse to warrant a specific model outcome; agree a standard of reasonable care instead.
- Push back on sector-wide non-competes; a narrow non-solicitation is usually enough.
- Get the IR35 status determination in writing before starting, and take legal advice before signing anything you didn't draft.
Questions people also ask
What liability cap should I actually ask for?
There is no universal figure, but a cap set at twelve months' fees under the contract is a common starting point for independent consulting work, and it gives a client a specific number to negotiate around rather than an unlimited exposure. What matters most is that a cap exists at all; the exact multiple is a negotiation, the absence of any cap is the real risk to worry about.
The client says their terms are standard and can't be changed. What then?
Every set of standard terms was written by someone and can be amended by someone; standard describes convenience, not law. If a client genuinely won't move on liability or IP, decide whether the fee and the relationship are worth the exposure, and get a solicitor to confirm exactly what you would be accepting before you decide either way.
Do I need my own solicitor, or is reviewing the contract myself enough?
Reviewing it yourself catches the obvious problems described here, but a solicitor who works with contractors will catch the ones specific to your situation, particularly around liability drafting and IP definitions that read reasonably but function badly in practice. For a contract of any meaningful value, the fee is small against the exposure it can prevent.
Does working through an umbrella company change any of this?
It changes how you're paid and taxed, not what the underlying contract says about liability, indemnity or IP. Deductions via an umbrella company reduce take-home pay, but they don't remove your exposure under the terms of the engagement, so every clause above still matters whether you're paid directly or through an umbrella arrangement.
Where the figures come from
Every rate and salary quoted in this article is a median or percentile of figures advertised in UK job postings over the six months to 8 August 2026. They are not rates paid, and the gap widens at the top of a range.
- IT Jobs Watch, UK contract rates, 6 months to 8 August 2026, read 2026-08-08.
- IT Jobs Watch, UK permanent salaries, 6 months to 8 August 2026, read 2026-08-08.