Freelance Contract Template UK — 12 Essential Clauses Every Freelancer Must Include

No contract, no protection. Every year, thousands of UK freelancers lose money, ownership of their work, or both — because they started a project on a handshake. This guide walks you through the 12 clauses your freelance contract needs, why each one matters, and exactly how to write them.

Why Every Freelancer Needs a Written Contract

Let's start with the uncomfortable truth: most freelancers in the UK don't use contracts. A 2023 IPSE survey found that nearly 40% of self-employed workers had started at least one project without a written agreement in the previous year. The reasons are always the same — "it's a small job," "I know the client," "I didn't want to seem difficult."

Here's what happens when you don't have a contract:

A graphic designer agrees to create a logo for £800. The client approves the initial concept but then requests twelve rounds of revisions over three months, fundamentally changing the brief each time. Without a contract specifying revision limits, the designer has no grounds to push back or charge extra. She eventually delivers after 60+ hours of work — on a project she'd quoted eight hours for.

A web developer builds a complete e-commerce site for a startup. They agree on £4,500 over email. The developer delivers. The client loves it — then ghosts. No contract means no specified payment terms, no late payment penalties, no kill fee. The developer eventually recovers £2,000 through small claims court, eight months later, after spending £455 in court fees and dozens of hours on paperwork.

A copywriter produces 10,000 words of website copy for a marketing agency. Six months later, she discovers her words are being resold to the agency's other clients. There was no IP clause, no usage agreement, nothing in writing about what "delivering the copy" actually meant in terms of ownership.

These aren't edge cases. They're Tuesday. They happen constantly, and they're almost entirely preventable with a proper contract.

A written freelance contract does three things:

• It sets expectations. Both parties know exactly what's being delivered, when, and for how much — before any work begins.
• It provides legal protection. If things go wrong, you have an enforceable document, not a string of vague WhatsApp messages.
• It filters out bad clients. Serious clients expect contracts. Clients who resist signing one are telling you something important about how they operate.

Under English law, verbal agreements are technically enforceable — but try proving what was agreed six months ago when it's your word against theirs. Written contracts remove ambiguity, protect your income, and frankly, they make you look more professional. Let's walk through the 12 clauses yours needs to include.

The 12 Essential Clauses

This is the single most important clause in your contract. If you get nothing else right, get this right. The scope of work defines exactly what you're going to deliver — and, just as importantly, what you're not going to deliver.

Vague scope is the root of almost every freelance dispute. "Design a website" means very different things to different people. To you, it might mean a five-page brochure site. To the client, it might mean a full e-commerce platform with user accounts, a blog, and a custom booking system.

Your scope clause should include:

• Specific deliverables — not "website design" but "Design and development of a 5-page responsive website (Home, About, Services, Portfolio, Contact) using WordPress"
• Quantities — number of pages, words, designs, hours, or whatever unit applies to your work
• Format — file types, dimensions, platforms
• Timeline — key milestones and final delivery date
• What's excluded — hosting, stock photography, ongoing maintenance, content writing — whatever isn't part of this engagement

Anything outside this scope is additional work, quoted and agreed separately. This is your best defence against scope creep — the silent profit killer that turns a profitable project into unpaid overtime.

Your contract must spell out how much you're being paid, when payment is due, and how you'll be paid. No ambiguity, no room for "I thought it was less" or "I'll pay when I can."

Include:

• Total project fee (or hourly/daily rate)
• Payment schedule — 50% upfront, 50% on delivery is standard for project-based work. For larger projects, consider thirds: 33% upfront, 33% at midpoint, 34% on completion
• Payment deadline — NET 14 is the freelancer standard. Specify days from invoice date
• Accepted payment methods — bank transfer, Stripe, PayPal
• Currency — especially important for international clients

Your payment clause should also state that work won't begin until the deposit is received and that final deliverables won't be released until the balance is paid in full. This gives you leverage — and removes the uncomfortable scenario of chasing payment after you've already handed everything over.

Getting paid late isn't just annoying — it's expensive. When a client sits on your invoice for an extra 30 days, that's a month of your cash flow disrupted. Rent doesn't wait. Software subscriptions don't wait. Your mortgage certainly doesn't wait.

Under the Late Payment of Commercial Debts (Interest) Act 1998, UK freelancers have a statutory right to charge interest on overdue invoices. You don't need the client's permission — it's the law. But putting it in your contract makes it explicit and enforceable without argument.

The statutory entitlements are:

• Interest: 8% per annum above the Bank of England base rate (currently 4.5%, making the total 12.5%)
• Fixed compensation: £40 for debts under £1,000 · £70 for debts under £10,000 · £100 for debts of £10,000+

The power of this clause isn't just in enforcement — it's in deterrence. Clients who see a late payment clause on your contract are significantly less likely to pay late in the first place. For the full breakdown — including how to word it on your invoices — read our guide on how to add late fees to your freelance invoices. And for the complete legal picture, see our post on UK late payment law explained.

Projects get cancelled. It happens. The client's budget gets cut, priorities shift, the startup runs out of runway. That's business. But if you've blocked out three weeks for a project, turned down other work, and started delivering — you shouldn't walk away empty-handed.

A kill fee (also called a cancellation fee) is a pre-agreed amount the client pays if they pull the plug after work has begun. It compensates you for:

• Time already spent on the project
• Opportunity cost — the other work you turned down
• The disruption of having to suddenly find replacement income

Typical kill fee structures:

• Before work begins: Full refund of deposit (or 10% cancellation fee)
• After work begins but before 50% completion: 25–50% of total project fee
• After 50% completion: 50–75% of total project fee
• After final delivery: 100% of total fee is due regardless

"Can we just try one more thing?" is the sentence that has bankrupted more freelancers than any economic downturn. Without a revision limit, every project becomes open-ended — and every "quick change" chips away at your effective hourly rate.

Your contract should specify:

• How many rounds of revisions are included — two or three is standard for most creative work
• What constitutes a "revision round" — one consolidated set of feedback, not an endless drip of individual changes
• The cost of additional revisions — typically charged at your hourly rate
• A revision window — the client has 14 days to request revisions after delivery, after which the work is considered approved

This clause is especially critical for designers, writers, and developers — anyone whose work is subjective and therefore endlessly tweakable. For strategies on handling it when clients push beyond the agreed scope, read our guide on how to handle scope creep as a freelancer.

This is the clause most freelancers get wrong — or leave out entirely. And it's potentially the most expensive mistake you can make.

Under the Copyright, Designs and Patents Act 1988, the creator of a work owns the copyright by default — unless they're an employee (in which case the employer owns it) or there's a written agreement assigning it. As a freelancer, you're not an employee. So unless your contract says otherwise, you own the copyright to everything you create.

That might sound like a good thing — and sometimes it is. But most clients expect to own the work they pay for, and if you don't address this explicitly, you're setting up a dispute.

You have three main options:

• Full assignment: You transfer all IP to the client on payment. This is the most common approach for client work and what most clients expect. Specify that transfer only happens upon full payment — this gives you leverage if they don't pay.
• Licence: You retain ownership but grant the client a licence to use the work (exclusive or non-exclusive, for specified purposes). Common for photography, illustration, and stock content.
• Partial assignment: The client gets IP for the final deliverables, but you retain rights to underlying tools, templates, code libraries, or frameworks you built independently.

Most freelance work involves some degree of access to confidential information — client strategies, financial data, customer lists, unreleased products, internal processes. A confidentiality clause (sometimes called an NDA clause) protects both parties.

A reasonable confidentiality clause should cover:

• What's confidential — business information, trade secrets, customer data, project details
• What's not confidential — information that's already public, information you knew independently, and general skills or knowledge gained during the project
• Duration — typically 2–5 years after the project ends, not "in perpetuity" (which is unreasonable for most freelance work)
• Portfolio rights — explicitly state whether you can mention the client or show the work in your portfolio

Be wary of overly broad confidentiality clauses in client contracts. A clause that prevents you from ever mentioning that you worked with the client, or that covers "any information shared during the engagement" without limitation, is unreasonable and potentially unenforceable. Push for specificity.

Without a liability clause, you're theoretically on the hook for any losses the client suffers as a result of your work — including indirect and consequential losses that could dwarf the project fee. A website you built goes down and the client loses £50,000 in sales? Without a liability cap, they could come after you for all of it.

A liability limitation clause does two things:

• Caps your total liability — typically to the total fees paid under the contract. If the client paid you £3,000, your maximum liability is £3,000.
• Excludes indirect/consequential losses — lost profits, lost data, reputational damage, third-party claims. You're responsible for delivering what you promised, not for every downstream consequence.

Note: you cannot exclude liability for fraud, personal injury, or death caused by negligence — the Unfair Contract Terms Act 1977 prohibits this. But for standard commercial losses, a reasonable cap is both normal and expected.

If you work in a high-risk field (finance, healthcare, legal), consider professional indemnity insurance alongside your liability clause. It's relatively cheap and adds an extra layer of protection.

Force majeure — literally "superior force" — covers events that are genuinely beyond either party's control. Pandemics, natural disasters, government actions, wars, major infrastructure failures. If COVID taught freelancers anything, it's that the unthinkable can happen, and your contract should address it.

A force majeure clause typically:

• Lists qualifying events — pandemic, natural disaster, war, government order, major utility failure, cyber attack
• Suspends obligations — neither party is in breach while the force majeure event continues
• Requires notification — the affected party must inform the other as soon as reasonably possible
• Sets a termination trigger — if the event lasts beyond a certain period (e.g., 30 or 60 days), either party can terminate the contract

Without this clause, a failure to deliver on time — even due to circumstances entirely outside your control — could technically put you in breach of contract. Keep it straightforward and symmetrical — it should protect both you and the client.

Nobody signs a contract expecting a dispute. But if one happens, you want a clear process — and ideally, one that doesn't immediately involve solicitors and court fees.

A good dispute resolution clause sets out a stepped process:

1. Informal resolution — the parties try to resolve it through direct communication first (give this a deadline, e.g., 14 days)
2. Mediation — if informal resolution fails, both parties agree to mediation before going to court. Mediation is faster, cheaper, and less adversarial than litigation. The Centre for Effective Dispute Resolution (CEDR) offers mediation services in the UK.
3. Legal proceedings — if mediation fails, specify the jurisdiction (England and Wales is standard for UK freelancers) and the governing law

Always specify that the contract is governed by the laws of England and Wales (or Scotland/Northern Ireland, depending on where you're based). Without this, international clients might argue that their local jurisdiction applies — which could make enforcement far more complex and expensive.

If you're a UK freelancer working through a limited company, IR35 is the elephant in every contract. The off-payroll working rules (commonly known as IR35) determine whether HMRC treats your engagement as genuinely self-employed or as "disguised employment" — with significant tax implications.

Since April 2021, for medium and large private sector clients, the client is responsible for determining your IR35 status — not you. But your contract still matters enormously, because HMRC looks at both the written terms and the reality of the working relationship.

Your contract should include clauses that reflect genuine self-employment:

• Right of substitution — you have the right to send a suitably qualified substitute to perform the work in your place
• No mutuality of obligation — the client isn't obliged to offer you work, and you're not obliged to accept it
• Control — you determine how and when you perform the work, not the client. The client specifies the what, not the how
• Your own equipment — you provide your own tools, software, and workspace
• Financial risk — you bear the risk of errors and the cost of correcting them

Important: These clauses only protect you if they reflect reality. If your contract says you can send a substitute but the client would never actually accept one, HMRC will look through the written terms to the actual working arrangement. Your contract and your working practices need to align.

Every contract needs an exit. The termination clause defines how either party can end the engagement — both in normal circumstances and when things go wrong.

Include two types of termination:

• Termination for convenience — either party can end the contract by giving written notice (7–30 days is typical, depending on the project length). Payment is due for all work completed up to the termination date, plus any applicable kill fee.
• Termination for cause — immediate termination if the other party materially breaches the contract and fails to remedy the breach within a specified period (usually 14 days). Examples: non-payment, failure to provide necessary materials, breach of confidentiality.

Your termination clause should also address:

• What happens to work in progress — is partially completed work delivered to the client? Only upon payment?
• Surviving clauses — which parts of the contract continue after termination? (Confidentiality, IP, liability, and dispute resolution typically survive.)
• Final payment — when and how the final invoice is settled

Red Flags in Client Contracts

Sometimes you won't be using your own contract — the client will insist on theirs. That's fine, as long as you actually read it. Here are the red flags that should make you pause, push back, or walk away:

• "Work for hire" or blanket IP assignment — clauses that assign copyright in everything you create during the engagement, not just the deliverables. This could cover your personal blog posts, side projects, or open-source contributions.
• Unlimited revisions — if the contract says "revisions until the client is satisfied" with no cap, you've just signed up for unlimited free work.
• Payment on "acceptance" with no definition of acceptance — the client can withhold approval (and payment) indefinitely.
• Non-compete clauses — a clause preventing you from working with the client's competitors. Unless the scope and duration are very narrowly defined (and you're being compensated for it), this can destroy your ability to earn.
• Indemnification without limit — you agree to indemnify the client against all losses, claims, and expenses arising from your work, with no cap. This is unlimited personal liability.
• Unilateral termination without payment — the client can cancel the project at any time without paying for work already done.
• "The client may vary these terms at any time" — a clause that lets the client change the contract unilaterally makes the entire agreement meaningless.

If you encounter any of these, don't sign without negotiating. Mark up the contract, propose alternative wording, and explain your reasoning. A reasonable client will engage with this. An unreasonable client is someone you don't want to work with anyway.

Template Walkthrough — How to Customise for Your Industry

A freelance contract isn't one-size-fits-all. While the 12 clauses above apply broadly, different industries need different emphasis:

Designers and Creatives

• Emphasise revision limits (clients in design tend to treat revisions as unlimited by default)
• Be specific about IP and portfolio rights — can you show the work? Under what conditions?
• Define file formats and handover — will you provide source files (e.g., Figma, .ai) or only final exports?
• Include a clause requiring timely feedback — if the client takes 6 weeks to review, your timeline extends accordingly

Developers and Tech

• Address code ownership vs. licences — particularly for open-source components, third-party libraries, and reusable code you've built previously
• Define what "done" means — acceptance criteria, testing requirements, browser/device support
• Include a warranty period — 30 days of bug fixes after launch is standard, but it should be defined
• Specify hosting and maintenance are separate from development (and charged separately)

Writers and Content Creators

• Clarify usage rights — can the client repurpose or resell the content? Is it exclusive?
• Specify byline and attribution — do you get a credit, or is it ghostwritten?
• Define what "revision" means — a structural rewrite is not the same as fixing a few typos
• Address research and interview time — is that included in the fee or billed separately?

Consultants and Strategists

• Be explicit about deliverable format — a "strategy" could mean a 50-page report or a one-hour phone call
• Include implementation boundaries — you're advising, not executing (unless execution is scoped and priced separately)
• Address liability for outcomes — your advice is professional guidance, not a guarantee of results

Start with a solid base template, then add or modify clauses based on your specific discipline. Don't remove the core 12 clauses — just weight them appropriately.

Digital Signatures and Legal Validity in the UK

You've written a brilliant contract. Now you need to get it signed. The good news: you don't need to print, sign, scan, and post anything. Digital signatures are fully legal in the UK.

Under the Electronic Communications Act 2000 and the UK's retained version of the EU eIDAS Regulation, electronic signatures are legally valid and admissible as evidence in court. The Law Commission confirmed this in its 2019 report, stating that an electronic signature is capable of being used to execute a document, including a contract.

There are three levels of electronic signature under UK law:

• Simple electronic signatures (SES) — typing your name, clicking "I agree," or pasting an image of your signature. Legally valid for most commercial contracts.
• Advanced electronic signatures (AES) — uniquely linked to the signatory and capable of identifying them (e.g., DocuSign, HelloSign, Adobe Sign). Stronger evidential weight.
• Qualified electronic signatures (QES) — created by a qualified electronic signature creation device and based on a qualified certificate. The highest level of assurance, equivalent to a wet-ink signature under eIDAS. Rarely needed for standard freelance contracts.

For freelance contracts, AES (e.g., DocuSign or HelloSign) is the practical sweet spot. It's easy for clients to use, provides an audit trail with timestamps, and carries strong legal weight. Most platforms offer a free tier that's sufficient for freelance use.

One exception: deeds (which are sometimes used for IP assignments) historically required wet-ink signatures, but the Law Commission has confirmed that electronic execution of deeds is valid under current law — provided the electronic signature is witnessed. For standard freelance service contracts, this isn't relevant.

Where to Get Professional Contract Templates

You've now got a detailed understanding of what your contract needs to include. The question is whether to write it yourself or start from a professional template.

Our honest recommendation: start from a template. Writing legal clauses from scratch — even with a guide like this — is time-consuming and risky. A well-drafted template gives you a solid foundation; you just need to customise the specifics for each client.

Options, from most to least expensive:

• Solicitor-drafted bespoke contract (£500–£2,000+) — worth it if you're entering a high-value or complex engagement. For most standard freelance work, it's overkill.
• Professional template packs (£15–£100) — pre-written, legally informed templates you can customise. The best ones include multiple variations (project-based, retainer, day-rate) with clause-by-clause guidance.
• Free templates — available from various sources, but quality varies enormously. Many free templates are American (different legal framework), outdated, or dangerously incomplete.

Whichever route you take, make sure any template you use:

• Is written for UK/English law — not US, Canadian, or Australian
• Covers all 12 essential clauses listed above
• Is in plain English — not impenetrable legalese that neither you nor the client understands
• Is customisable — you need to be able to swap in your specific scope, fees, and terms for each project
• Has been updated recently — IR35 rules changed in 2021; the legal landscape doesn't stand still

The Bottom Line: Contracts Aren't Bureaucracy — They're Protection

A freelance contract isn't about distrust. It's about clarity. It's the document that turns "I think we agreed…" into "Here's exactly what we agreed." It protects your income, your intellectual property, your time, and your professional reputation.

If you take one thing from this guide, let it be this: never start work without a signed contract. Not for a "quick job." Not for a friend-of-a-friend. Not for a client who says "we'll sort the paperwork later." The paperwork is the job — at least, it's the part that ensures you get paid for the job.

Here's your action plan:

1. Get a template — either from the Contract Template Pack or another reputable source
2. Customise it for your industry using the guidance above
3. Use it on every single project — no exceptions
4. Pair it with solid payment terms and a professional invoicing process
5. Review and update it annually — laws change, your business evolves, and your contract should keep pace

Your future self — the one who isn't chasing a client through small claims court or fighting over who owns a piece of work — will thank you.

—

Written by the team at Landolio — tools and templates for freelancers who'd rather do great work than chase payments.