Freelance Contracts UK

Why every freelancer needs a contract

Most freelancing disputes do not start with malicious intent. They start because two people had different assumptions about scope, ownership, payment, or what happens when a project changes direction. A contract makes those assumptions explicit before work begins.

Verbal agreements are technically legally binding in the UK, but they are almost impossible to enforce when a dispute arises. Without a written record, it becomes your word against the client's. A signed contract, or even a written email exchange that records the key terms, gives you something concrete to stand on.

Contracts also protect clients. When a client knows exactly what they are getting, when they are getting it, and what it will cost, there are fewer surprises on both sides. Proposing a contract is a professional signal, not a sign of distrust.

Essential clauses

You do not need a solicitor to write a basic freelance contract. A clear, plain-English document covering the following points is far better than nothing:

• Scope of work: what you will deliver, in as much detail as possible. List specific deliverables rather than broad descriptions. “A website design” is too vague; “five page designs in Figma, including homepage, about page, services page, contact page, and a blog template” is not.
• What is not included: explicitly listing exclusions prevents scope creep. If you are designing but not coding, say so.
• Timeline and milestones: when you will deliver, and what dependencies you have on the client (e.g. content, feedback, approvals).
• Revision rounds: how many rounds of revisions are included in the price. Additional rounds should be charged at your day rate.
• Payment terms: the total fee, payment schedule (upfront deposit, milestones, final payment), and when each payment is due.
• Late payment: what happens if payment is not received on time. Referencing the Late Payment of Commercial Debts Act puts the client on notice.
• Intellectual property: who owns the work and when ownership transfers. See the section below.
• Confidentiality: whether you can show the work in your portfolio, and what client information you are expected to keep confidential.
• Termination: what happens if either party wants to end the contract early, including what has been paid and what is owed.
• Governing law: confirm the contract is governed by English and Welsh law (or Scottish law if relevant).

Intellectual property: who owns what

Under UK copyright law, the creator of a work owns it by default. As a freelancer, this means that unless your contract says otherwise, you own the copyright in the work you produce, even if you have been paid in full for it.

Clients often assume that payment transfers ownership, but legally it does not unless there is a written assignment of rights. In practice, there are three common approaches:

• Full assignment: you transfer all intellectual property rights to the client on final payment. This is the most common expectation in creative services. Once assigned, you have no further rights to the work.
• Licence: you retain ownership but grant the client a licence to use the work in specified ways (e.g. on their website, for a specific campaign). You can charge more for broader licences or for exclusive use.
• Moral rights: even if you assign copyright, you retain moral rights in the UK, including the right to be identified as the creator. You can waive moral rights in writing if the client requires it.

Decide your IP policy before you start writing contracts. Most straightforward client work involves a full assignment on final payment. Licensing models are more common in photography, illustration, and software.

One important point: IP in works created by employees automatically belongs to the employer. If a client argues that your contract makes you look like an employee rather than a self-employed contractor, this could interact with IR35 rules. For more on that, see IR35 Explained.

Payment terms and late payment

Your contract should specify the full payment structure: the total fee, any deposit required before work begins, any milestone payments, and the final payment terms.

A common structure for project-based work:

• 50% deposit before work begins
• 25% on delivery of the first draft or a defined milestone
• 25% on final delivery

This structure means you are never more than 50% exposed at any point in the project. If a client disappears after receiving the first draft, you have already been paid for a significant portion of your time.

Include payment due dates (not just “30 days”) and a clear statement that overdue invoices will accrue statutory interest. For a detailed look at payment terms options, see Invoice Payment Terms.

Kill fees and cancellation

A kill fee (sometimes called a cancellation fee) is a charge that applies if a client cancels the project after work has begun. Without one, a client can walk away at any point and leave you with nothing for time you have already spent.

Common kill fee structures:

• Time-based: charge your day rate for all hours worked up to the point of cancellation, regardless of what was invoiced at each milestone
• Percentage-based: charge 25 to 50 percent of the remaining project value if cancelled after a defined point (e.g. after the first draft has been delivered)
• Non-refundable deposit: the simplest version — the deposit paid upfront is non-refundable if the client cancels. This is standard for many freelancers and is easy for clients to understand

Be clear in the contract about what triggers the kill fee and how it is calculated. Ambiguity here leads to arguments.

Working without a contract

Many freelancers do work without a formal contract, especially for quick projects or with long-standing clients. If you are in this position and a dispute arises, you are not entirely without protection, but your options are more limited.

Evidence you can use in the absence of a written contract:

• Email chains that describe the project scope, price, and timeline
• A quote that the client responded to positively (even just “sounds good, let's go ahead”)
• Messages or calls that demonstrate the client's agreement to the work
• Evidence of delivery (files sent, links shared, content delivered)

If a client disputes an invoice and there is no contract, the court will look at all the available evidence to determine what was agreed. A clear email trail can be just as useful as a formal document in many circumstances.

The lesson is not that you should work without contracts but that getting written confirmation of key terms — even informally — is always better than relying on a conversation.

Practical tips for getting contracts signed

The most common reason freelancers do not use contracts is that they feel awkward introducing one, especially with clients they have worked with before. A few things that help:

• Build it into your process: send your contract with every quote as a matter of routine. If it is always part of how you work, it never feels like a special imposition for a specific client.
• Use e-signature tools: tools like DocuSign or HelloSign make signing fast and friction-free. A client who would balk at printing, signing, and scanning a document will often sign digitally in 30 seconds.
• Keep it readable: legal jargon in a freelance contract does not make it more enforceable. A contract a client can actually read and understand is more likely to be signed without pushback.
• Do not start work until it is signed: this is the most important habit. Once you have delivered work, your negotiating position disappears. The contract exists to give you protection before that happens.
• For repeat clients: you can use a master services agreement (a contract that sets the general terms) and then a shorter “statement of work” for each individual project. This reduces friction while keeping protection in place.