How to Write a Freelance Contract: The Complete Guide

Working without a contract is the single biggest financial risk a freelancer can take. Yet a surprising number of freelancers still operate on verbal agreements, email threads, or vague one-page documents that leave them exposed when things go wrong. A solid freelance contract protects your income, defines expectations, and gives you legal standing if a client refuses to pay or demands work outside the original agreement.

This guide walks through the 10 essential sections every freelance contract needs, with practical language you can adapt for your own agreements. Whether you're a designer, developer, writer, consultant, or any other type of freelancer, these principles apply universally.

Why Every Freelancer Needs a Written Contract

Before diving into the sections, it's worth understanding why a written contract matters so much. Verbal agreements are technically enforceable in many jurisdictions, but proving what was agreed becomes a nightmare. A written contract does three things:

• Sets clear expectations — both you and the client know exactly what's being delivered, when, and for how much
• Prevents scope creep — when a client asks for additional work, you can point to the contract and discuss a change order
• Provides legal protection — if a dispute reaches court or mediation, a signed contract is your strongest evidence

The good news is that a freelance contract does not need to be written by a solicitor. It needs to be clear, specific, and signed by both parties. Plain English is not only acceptable — it's preferable. Courts interpret contracts based on what was clearly communicated, not on how much legal jargon was used.

1. Scope of Work

The scope of work is the most important section of your entire contract. It defines exactly what you're delivering, and just as importantly, what you're not delivering. A vague scope is the root cause of most freelancer disputes.

What to include:

• A detailed list of specific deliverables (e.g., "5-page marketing website with responsive design" rather than "a website")
• File formats for final deliverables (PSD, PDF, HTML, etc.)
• What is explicitly excluded from the project
• The process for handling additional requests that fall outside the original scope

Example language: "This agreement covers the design and development of a 5-page responsive website (Home, About, Services, Portfolio, Contact). Content writing, photography, and ongoing maintenance are not included. Any additional pages or features requested after signing will be scoped and quoted separately."

The more specific your scope, the easier it is to push back on requests that fall outside it. If you find yourself writing a scope that feels too detailed, you're probably getting it right. For a deeper dive, see our Freelance Scope of Work Template guide.

2. Payment Terms

Payment terms should leave zero ambiguity about how much the client owes, when they owe it, and what happens if they pay late. This is where many freelancers are too soft, and it costs them dearly.

Key elements:

• Total project fee — state the exact amount and currency
• Payment schedule — when payments are due (e.g., 50% upfront, 50% on delivery)
• Payment method — bank transfer, PayPal, Stripe, etc.
• Payment deadline — NET 14, NET 30, or on receipt of invoice
• Late payment penalties — interest rate or flat fee for overdue invoices
• Deposit requirements — non-refundable deposit to secure your calendar

A 50% upfront deposit with the balance due on delivery is the gold standard for project-based freelance work. For retainer or ongoing arrangements, monthly invoicing with NET 14 terms works well. Never agree to NET 60 or NET 90 unless the project fee justifies the wait — those terms were designed for large corporate procurement, not freelancers who need to pay rent.

For more on structuring payment terms, read our guide on payment terms in contracts and our practical guide to late payment clauses for freelancers.

3. Intellectual Property Rights

The IP section determines who owns the work you create. This is one of the most commonly misunderstood areas in freelance contracts, and getting it wrong can mean losing ownership of your creative output entirely.

There are two common approaches:

• Full IP transfer on payment — you create the work, the client receives full ownership once they've paid in full. This is the most common arrangement and is generally fair, provided the transfer is conditional on payment.
• Licence model — you retain ownership and grant the client a licence to use the work. This is common for photographers, illustrators, and other creatives who want to retain portfolio rights or resell the work.

The critical point is that IP should never transfer before payment. If the contract says ownership transfers "upon creation" rather than "upon receipt of full payment," you could deliver work, never get paid, and have no legal claim to the work you created.

Also consider including a portfolio rights clause that allows you to showcase the work in your portfolio regardless of who owns the IP. Most clients are fine with this, but it needs to be in the contract. Learn more in our IP clauses guide for freelancers.

4. Revision Policy

Without a clear revision policy, clients can request endless changes, turning a profitable project into a time sink. Your contract should define:

• The number of revision rounds included (2-3 is standard)
• What constitutes a "revision" vs. new scope
• The cost of additional revisions beyond the included rounds
• A timeframe within which revisions must be requested

Example language: "This project includes two rounds of revisions. A revision is defined as a change to existing work within the original scope. Requests for new features, additional pages, or work not covered by the original scope will be quoted as a separate change order. Additional revision rounds beyond the included two will be billed at [hourly rate] per hour. Revision requests must be submitted within 14 days of delivery; after this period, additional revisions will be billed at the standard hourly rate."

5. Termination Clause

Every contract needs an exit strategy. Things change — clients lose funding, projects get cancelled, working relationships break down. A fair termination clause protects both parties.

Essential elements:

• Notice period — how much advance notice is required (14-30 days is standard)
• Payment for completed work — the client must pay for all work completed up to the termination date
• Kill fee — an optional fee to compensate for cancelled work (common in creative industries)
• Return of materials — what happens to files, access credentials, and work-in-progress
• Mutual termination rights — both parties should have the right to terminate, not just the client

Watch out for contracts where only the client can terminate. This is a major red flag in freelance contracts. Fair contracts give both parties equal termination rights.

6. Liability and Indemnification

The liability section caps your financial exposure if something goes wrong. Without it, you could theoretically be sued for damages far exceeding your project fee.

Key provisions:

• Liability cap — limit your total liability to the amount the client has paid you. A cap of 1x the total contract value is standard; 2x is generous. Never agree to unlimited liability.
• Exclusion of consequential damages — state that you're not liable for indirect losses such as lost profits, lost business, or reputational damage
• Client responsibility for content — if the client provides content, copy, or materials for you to use, they should warrant that they have the right to use it

Example language: "The Contractor's total liability under this agreement shall not exceed the total fees paid by the Client. In no event shall the Contractor be liable for any indirect, incidental, or consequential damages."

7. Confidentiality

Many clients will want a confidentiality or non-disclosure provision in your contract. This is reasonable — you may have access to sensitive business information during the project. However, the confidentiality clause should be balanced.

• Define what's confidential — vague definitions like "all information shared" are too broad. Specify categories: business plans, financial data, customer lists, trade secrets
• Set a time limit — confidentiality obligations should expire (2-5 years is typical)
• Include standard exclusions — information that's publicly available, independently developed, or required by law should be excluded
• Make it mutual — if possible, ensure the client also agrees to keep your proprietary methods and pricing confidential

Be cautious of confidentiality clauses that are actually disguised non-compete agreements. If a clause prevents you from working in your field, that's a non-compete, not a confidentiality provision. Read our NDA review checklist for more on this.

8. Dispute Resolution

Nobody enters a contract expecting a dispute, but having a resolution mechanism in place saves enormous time and money if one arises. Without this clause, the default is litigation — which is slow, expensive, and stressful for everyone.

Common approaches:

• Negotiation first — require both parties to attempt to resolve the dispute informally before escalating
• Mediation — a neutral third party helps both sides reach an agreement. Cheaper and faster than arbitration or court
• Arbitration — a binding decision made by an arbitrator. Faster than court but the decision is final
• Governing law — specify which jurisdiction's laws apply (usually where you're based)

Example language: "Any dispute arising from this agreement shall first be resolved through good-faith negotiation. If unresolved within 30 days, the parties agree to submit to mediation before pursuing any other remedy. This agreement is governed by the laws of England and Wales."

9. Timeline and Milestones

A clear timeline protects you as much as the client. Without specific dates, a client can claim the project is "late" based on their own unstated expectations, or conversely, delay providing feedback indefinitely, leaving you in limbo.

What to include:

• Project start date — typically tied to receipt of the deposit
• Key milestones — checkpoints for approval before proceeding (e.g., wireframes, first draft, final delivery)
• Client response deadlines — how long the client has to provide feedback at each milestone
• Consequences of client delays — if the client takes two weeks to respond to a review, the project deadline shifts accordingly
• Final delivery date — contingent on the client meeting their own deadlines

Pro tip: Include a clause stating that the project timeline will be extended by one day for every day the client is late in providing feedback, materials, or approvals. This protects you from being blamed for delays caused by the client.

10. Amendments and Change Orders

Projects evolve. The client might want additional features, a different direction, or extra deliverables. Your contract should establish a formal process for making changes to the original agreement.

• All changes must be agreed in writing (email is fine, but it must be documented)
• Changes to scope, timeline, or cost require a signed change order or amendment
• Verbal changes are not binding unless confirmed in writing
• Each change order should specify the additional cost, revised timeline, and updated deliverables

Example language: "Any changes to the scope, timeline, or fees outlined in this agreement must be documented in a written change order signed by both parties. Verbal modifications are not binding. The Contractor reserves the right to adjust the project timeline and fees to reflect approved changes."

Putting It All Together: Your Contract Checklist

Before sending a contract to a client, run through this checklist to ensure you have covered everything:

1. Scope of work is specific, with deliverables listed individually
2. Payment terms include amount, schedule, method, and late fees
3. IP transfer is conditional on full payment
4. Revision rounds are capped with a clear definition
5. Both parties can terminate with reasonable notice
6. Liability is capped at 1-2x the contract value
7. Confidentiality obligations are time-limited and specific
8. Dispute resolution starts with negotiation before escalating
9. Timeline includes client response deadlines
10. Changes require a written change order

Common Mistakes to Avoid

Even with all 10 sections in place, freelancers often make these errors:

• Using someone else's template without customising it— generic templates miss the nuances of your specific work. Always tailor the contract to the project.
• Not signing the contract before starting work — a contract that's "in progress" while you're already working offers zero protection. Never start work without a signed agreement.
• Making the contract one-sided in your favour — a contract that feels exploitative to the client damages the relationship. Fair contracts build trust.
• Forgetting to account for expenses — if the project involves stock photography, hosting, software licences, or travel, specify who pays and how expenses are handled.
• Ignoring local laws — contract enforceability varies by jurisdiction. In the UK, the Late Payment of Commercial Debts (Interest) Act 1998 gives you statutory rights to charge interest on overdue invoices even if your contract does not mention it.

How to Present the Contract to Your Client

Many freelancers worry that presenting a formal contract will scare off clients. The opposite is true. Professional clients expect contracts, and presenting one signals that you run a serious business.

Tips for a smooth contract process:

• Send the contract early in the project discussion, not at the last minute
• Walk the client through the key sections in a brief call or email
• Be open to reasonable negotiation — a contract is a starting point, not a take-it-or-leave-it ultimatum
• Use e-signature tools for convenience (DocuSign, HelloSign, or even a signed PDF)
• Keep a copy of every signed version for your records

When to Get Professional Legal Advice

While you can write a solid freelance contract yourself, there are situations where professional legal advice is worthwhile:

• High-value projects (over £10,000) where the financial stakes justify the cost
• International clients where cross-border legal issues may arise
• Unusual IP arrangements (joint ownership, licensing, resale rights)
• When a client insists on using their own contract and you need help reviewing it

For everyday freelance contracts, an AI contract review tool can help you spot issues quickly and affordably, while a solicitor is better for complex or high-stakes situations.

Related Articles

• 7 Freelance Contract Red Flags That Cost You Money
• Freelance Scope of Work Template: What to Include
• Payment Terms in Contracts: A Freelancer's Guide
• Who Owns the Work? IP Clauses Every Freelancer Must Understand
• 5 Contract Negotiation Tips Every Freelancer Should Know