Freelance Contracts: What to Include & Why You Need One

A contract is not a sign of distrust — it is a sign of professionalism. It protects both you and your client by putting expectations in writing before work begins. Without a contract, you are relying on memory, assumptions, and goodwill, all of which tend to fail when money and deadlines are involved.

The most common freelance disputes — scope creep, late payment, disagreements about revisions, and unclear deliverables — are almost entirely preventable with a well-written contract. A contract forces both parties to agree on the details upfront, which means fewer surprises and fewer arguments down the line.

In the UK, a contract does not need to be drafted by a solicitor to be legally binding. A clear, written agreement signed (or digitally agreed) by both parties is enforceable. That said, having a solicitor review your standard contract template once is a worthwhile investment — typically £200-£500 for a review that protects you for years.

If a client resists signing a contract, that is a red flag, not a negotiation. Professional clients expect contracts. They want clarity. The ones who push back are usually the ones who plan to change the scope, delay payment, or dispute your work later. Walk away from any client who will not put the agreement in writing.

The scope of work clause is the most important part of your contract. It defines exactly what you will deliver, in what format, and by when. Vague scope is the number one cause of freelance disputes, so be as specific as possible. "Design a website" is a disaster waiting to happen. "Design and develop a 5-page Shopify website (Home, About, Shop, Contact, Blog) with up to 20 products, delivered as a live site on the client's hosting" is a clear, enforceable scope.

List every deliverable explicitly. If you are a designer, specify the number of concepts, the number of revision rounds, the file formats you will deliver, and what is not included (e.g., photography, copywriting, print production). If you are a developer, define the browsers and devices you will test on, the hosting and deployment responsibilities, and the post-launch support period.

Include a clear process for handling work outside the original scope. The standard approach is: any additional work requested by the client will be quoted separately and agreed in writing before work begins. This is your defence against scope creep — the gradual expansion of work that turns a profitable project into an unprofitable nightmare. For more on defining scope effectively, see our guide to scope of work.

Attach a timeline with milestones where appropriate. For larger projects, break the work into phases with specific deliverables and deadlines for each. This gives both parties checkpoints to ensure the project is on track and provides natural points for feedback and approval.

Your contract must specify: the total fee, the payment schedule, the payment method, and the consequences of late payment. For project work, a common structure is 50% upfront and 50% on completion, or 30/30/40 across three milestones. Never start work without at least a deposit — 30-50% upfront is standard in the UK freelance market.

Set clear payment terms. Net 14 (payment within 14 days of invoice) is reasonable for most freelance work. Net 30 is acceptable for larger companies. Avoid Net 60 or longer — as a freelancer, you cannot afford to wait two months for payment. State your preferred payment method (bank transfer is standard in the UK) and include your bank details on your invoices.

Include a late payment clause. Under the UK Late Payment of Commercial Debts Act 1998, you are entitled to charge interest on overdue invoices (currently 8% above the Bank of England base rate) plus a fixed compensation amount (£40-£100 depending on the debt size). Reference this in your contract — even if you never enforce it, its presence encourages timely payment.

For ongoing retainer work, specify the monthly fee, what it includes, the billing date, and the payment terms. Also include a clause about unused hours or deliverables — do they roll over to the next month, or are they lost? And define the notice period for either party to end the retainer, typically 30 days.

Who owns the work you create? This is one of the most misunderstood areas in freelancing. In the UK, the default legal position is that the creator of a work owns the copyright — meaning you, the freelancer, own everything you create unless your contract says otherwise. This surprises many clients who assume they automatically own what they pay for.

The standard approach is to include an IP assignment clause that transfers ownership of the final deliverables to the client upon full payment. This is fair to both parties: the client gets what they paid for, and you retain leverage until the bill is settled. Be explicit about what is transferred (the final, approved deliverables) and what is not (your working files, templates, tools, and pre-existing IP).

Consider retaining a licence to use the work in your portfolio. Most clients are fine with this, but it should be stated in the contract rather than assumed. If you work in a sensitive industry (e.g., finance, healthcare, defence), the client may reasonably request that you do not showcase the work publicly — negotiate this upfront.

For software development, the IP clause needs extra care. Distinguish between bespoke code written specifically for the client (which should transfer) and any libraries, frameworks, or reusable components you have built over time (which should remain yours, licensed to the client). Without this distinction, a client could argue they own your entire toolkit.

Revisions. Unlimited revisions is a recipe for misery. Specify the number of revision rounds included in the fee — two or three rounds is standard for most creative work. Define what constitutes a "round" (a single batch of feedback, consolidated into one set of changes). After the included rounds, additional revisions are billed at your hourly rate or an agreed per-round fee.

Be specific about the feedback process. Require the client to provide all feedback in writing (not verbal), consolidated into a single document per round. Set a deadline for feedback — if the client does not respond within, say, 10 business days, the deliverable is deemed approved. This prevents projects from dragging on indefinitely because a client cannot make up their mind.

Termination. Both parties should have the right to end the contract with reasonable notice. A typical clause allows either party to terminate with 14-30 days' written notice. Specify what happens to work completed up to the termination date: the client pays for all work done, and you deliver whatever has been completed. Include a kill fee for early termination — typically 25-50% of the remaining project value — to compensate you for turning down other work and the disruption to your schedule.

If the client terminates for cause (e.g., you have genuinely failed to deliver), the kill fee may not apply, but they should still pay for work completed. If you terminate for cause (e.g., the client is abusive, unresponsive, or in material breach), you should be paid in full for completed work and retain all IP until payment is received.

Confidentiality. A mutual non-disclosure clause is standard in freelance contracts. You agree not to share the client's confidential business information, and they agree not to share your proprietary methods or pricing with competitors. Keep this clause reasonable — it should cover genuinely sensitive information, not prevent you from ever mentioning that you worked with the client.

Limitation of liability. This clause caps your financial liability if something goes wrong. The standard cap is the total fee for the project. Without this clause, a client could theoretically sue you for consequential damages far exceeding what they paid you. For example, if a website you built goes down and costs the client £100,000 in lost sales, your liability should be limited to the £5,000 they paid you, not the £100,000 they lost.

Dispute resolution. Include a clause that specifies how disputes will be handled. The most cost-effective approach for freelancers is: first, the parties will attempt to resolve the dispute through good-faith negotiation; if that fails, through mediation; and only as a last resort, through the courts. Specify the jurisdiction — typically England and Wales for UK-based freelancers.

Other useful clauses to include: force majeure (neither party is liable for delays caused by events beyond their control), non-solicitation (the client will not hire your subcontractors directly), and entire agreement (the contract supersedes all previous discussions and verbal agreements). The more comprehensive your contract, the fewer grey areas there are to argue about later.