Most freelance contracts are either copied off the internet by the freelancer, or imposed by the client and signed without reading. Both routes lead to the same place: an underprotected freelancer in a dispute they didn’t see coming. This guide walks through what every UK freelance contract should include in 2026, what to push back on, and the IR35 angle that’s easy to miss.
The non-negotiable clauses
Every UK freelance contract should cover seven core clauses. The parties – your full legal name and the client’s. The scope of work – specific deliverables and milestones. Fees and payment terms – amounts, dates, late-payment treatment. Intellectual property – who owns what. Confidentiality. Termination terms. Governing law (England & Wales, Scotland, or Northern Ireland). Anything thinner than this is asking for trouble.
Scope of work — be specific
Vague scope is the single biggest source of payment disputes. List specific deliverables and acceptance criteria. State explicitly what’s NOT included. Define the change-request process upfront – how out-of-scope work will be priced and approved. Two free revisions and a third charged separately is a fair starting point for most creative engagements. For consulting, define the methodology and the hand-over artefacts.
Payment terms that actually work
For project work, 50% upfront and 50% on completion is the freelance default. For retainers, monthly in advance. Late-payment interest under the Late Payment of Commercial Debts (Interest) Act 1998 accrues at 8% over Bank of England base rate, plus a fixed sum (£40, £70 or £100 depending on invoice size). Specify acceptable payment methods – no cheques in 2026; bank transfer or direct debit. Add a VAT line if you’re registered and make clear whether prices are exclusive or inclusive.
Intellectual property — who owns what
The default UK position is that copyright belongs to the creator (you), not the commissioner. Most clients will want assignment of the IP on payment. The compromise that protects both sides: licence rights for the agreed use during work, full assignment on full payment. Carve out your underlying tools, frameworks and pre-existing IP – you bring them in and you take them out, regardless of the engagement. For software, separate clauses for code you write versus open-source you incorporate.
Confidentiality and non-compete
A mutual NDA is standard. One-sided NDAs you’re asked to sign should be checked carefully – the obligations should run both ways. Typical duration: 2–5 years post-engagement. Non-compete clauses that try to prevent you working with competitors are often unenforceable in the UK if they’re too broad in scope, geography or duration; the courts apply a reasonableness test. Don’t sign global, perpetual non-competes for a freelance gig.
Termination clauses
Notice periods both ways – typically 14–30 days for retainer, on completion for project. Pay for work done up to termination. Return of materials clauses – their data goes back to them, your tools come back to you. “For cause” termination for serious breach (instant). Don’t accept a contract where they can terminate at will and you can only terminate for cause; the symmetry should run both ways.
IR35 considerations
For UK consulting through your own limited company, the contract should reflect outside-IR35 working practices. The three usual tests: substitution rights (you can send a replacement), no mutuality of obligation (no requirement to be available for unspecified work), and control over how the work is done. For contracts with medium or large clients (over £10.2m turnover or equivalent), the client now decides IR35 status – but the contract should still reflect a genuine B2B engagement. Avoid clauses that imply employment: set hours, fixed location, line management, or kit provided by the client.
Liability and indemnity
Cap your liability at the contract value, or a small multiple thereof. Exclude indirect or consequential losses (lost profits, lost data of end customers). Carry professional indemnity insurance – typically £1m–£2m cover, a few hundred pounds a year. Don’t accept unlimited indemnity for “any breach” – that’s an unreasonable risk transfer that no insurer will back you on. Push back firmly. Most clients will compromise once you explain the position.
A usable template structure
A solid contract follows this skeleton. Recitals (background, parties). Definitions of key terms. Services to be provided. Fees and expenses. Term and termination. Intellectual property. Confidentiality. Liability. General clauses (governing law, entire agreement, notices). Signatures. Most disputes pivot on one of the first four sections, so spend the most time getting them precise.
Frequently asked questions
The questions UK freelancers ask most often about contracts.
Can I just use a template I find online?
A solid template is a fine starting point, but never sign a template without tailoring scope, fees, and IP clauses to your specific engagement. For larger or higher-risk contracts (above £10-20k value, or anything safety-critical), have it reviewed by a solicitor — typically £200-£500 for a contract review.
Do I need a contract for every client?
Yes, even if it's brief. An email exchange confirming scope, fee, and payment terms can constitute a binding agreement, but a proper signed contract is much safer when disputes arise. For one-off small engagements (under £1,000), a written proposal accepted by email may suffice; anything bigger warrants a contract.
Can I send the contract by email or does it need to be on paper?
Email is fine in the UK. Electronic signatures (DocuSign, HelloSign, e-signature in PDF tools) are legally binding. Most freelance work is contracted entirely electronically now. Paper contracts are no more legally robust.
Who owns the work I create for a client?
Default UK position: the creator owns copyright, but the client typically requires assignment in the contract. Negotiate the assignment to apply only on full payment, and exclude any pre-existing tools, frameworks, or methods you bring to the engagement.
What if a client refuses to sign my contract?
That's a red flag. A client who won't sign a reasonable freelance contract before work starts is signalling they want flexibility on payment, scope, or both. Walk away. The exception: large enterprises that insist on their own paper. Read theirs carefully and push back on the IP, liability, and exclusivity clauses.
How does IR35 affect my contract?
For limited company contractors, the contract should reflect a genuine B2B engagement. Specifically: substitution rights (you can send a replacement), no mutuality of obligation (no requirement to be available for unspecified work), and control over how (not just what) work is done. For contracts with medium/large UK clients, the client makes the IR35 determination, but a poorly-worded contract is hard to defend.
What payment terms should I push for?
14-30 days for invoiced work, with 50% upfront for project work. Anything over 30 days is unusually slow and a cash-flow risk. The Late Payment of Commercial Debts Act gives you a statutory right to 8% above base rate plus a fixed compensation sum if a client pays late — quote this in your contract.
Can I have a 'kill fee' if the client cancels mid-project?
Yes, and you should. A kill fee covers your time invested up to cancellation plus a percentage (typically 20-40%) of remaining contract value. It compensates you for the opportunity cost of the work you'd lined up. Standard in creative and consulting freelance contracts.
