Freelance Contracts 101: The 8 Clauses That Actually Protect You

Ask freelancers about their worst client experience and you'll hear the same stories with different scenery: the project that grew forever without growing its fee, the invoice that aged into a donation, the client who vanished mid-project, the work that got used in ways nobody discussed. Here's the thing — almost none of these are villain stories. They're ambiguity stories. Two reasonable people remembered a conversation differently, and there was nothing written down to settle it.

That's what a contract is actually for. Not litigation — a solo freelancer suing a client is rare, expensive and usually not worth it — but preventing the disagreement from existing. The document forces the awkward questions to get answered on day one, when everyone's friendly, instead of in month three, when money's involved.

The eight clauses that do the real work

1. Scope — what you're doing, and what you're not

The most important clause and the most commonly botched. Describe the deliverables specifically enough that a stranger could judge whether they've been delivered: "a five-page website (home, about, services, blog index, contact)" not "a website." Then add the sentence that prevents scope creep: anything not listed here is a separate quote. Scope creep doesn't arrive as a demand; it arrives as "could we just also…" — and this clause is what lets you say yes cheerfully, with a price attached.

2. Payment terms — amount, schedule, and the deposit

The fee, when it's due, and how it's paid. For projects: a deposit (30–50%) before work starts, with the balance on delivery or at milestones. The deposit isn't just cash flow — it's a seriousness test that filters the clients who were never going to pay well (more on getting paid in our invoicing guide). Include late-payment interest; you'll rarely charge it, but it converts "please pay me" into a term you're graciously waiving.

3. Revisions — a number, not a vibe

"Includes two rounds of revisions; further rounds billed at £X/hour." Unlimited revisions is how a profitable project becomes an unprofitable relationship. A stated number resets the client's mental model from "we iterate until I'm happy" to "I should collect my feedback properly."

4. Intellectual property — who owns what, and when

The standard freelance arrangement: the client owns the final deliverables once paid in full; you keep your pre-existing tools, and the right to show the work in your portfolio. The "once paid in full" part is your single strongest lever — ownership transferring on payment means an unpaid invoice is also an unlicensed asset, which concentrates minds in accounts departments wonderfully.

5. Termination — the exit both sides hope not to use

Projects die: budgets vanish, companies pivot, people leave. A kill clause makes it undramatic — either side can end with written notice; the client pays for work completed to date (deposits non-refundable). Without it, a cancelled project becomes a negotiation with someone who's already stopped caring.

6. Timeline and dependencies — deadlines run both ways

Your delivery dates, and what you need from them by when: content, feedback, approvals, access. The magic sentence: delays in client materials extend the timeline accordingly. Half of "the freelancer missed the deadline" stories are actually "the client sat on the copy for three weeks" stories; this clause keeps the record straight.

7. Limitation of liability — the sanity cap

A clause saying your total liability is capped (commonly at the project fee) and excluding indirect damages — so a £2,000 website can't theoretically expose you to a £200,000 lost-revenue claim. This clause pairs with, rather than replaces, professional indemnity insurance — and if you're wondering how it relates to an LLC, that's a different layer of protection again.

8. The boring administration

Which country/state's law governs, that this document supersedes the email thread and the pub conversation, and how it can be amended (in writing). Thirty seconds of boilerplate that decides who wins every "but you said" dispute.

Red flags in the client's paperwork

Bigger clients will often send their contract. Sign nothing until you've scanned for these:

• Unlimited or uncapped indemnification — you covering their legal costs for broad categories of claims. Push for mutual, capped indemnity.
• IP transferring before payment, or "work for hire" language with net-60 terms — the combination that leaves you owning nothing and owed everything.
• Non-competes that outlaw your profession — "won't work with any company in our industry for two years" is your client list being confiscated. Narrow it to named direct competitors, or strike it.
• Payment on "acceptance" with no acceptance deadline — an invoice that ages until someone feels like approving. Add "deemed accepted after X days."

Pushing back is normal. Professionals negotiate contracts; the clients who bristle at reasonable terms are running a preview of the whole relationship.

Template, AI, or lawyer?

For routine freelance work: a good template covers you — freelancer unions and professional bodies publish solid ones, and an AI assistant is genuinely useful for translating clauses into plain English, adapting a template to a specific project, and spotting the red flags above in a client's contract (paste it in, ask "what here is unusual or unfavourable to the contractor?"). Where a human lawyer earns their fee: contracts worth multiples of your monthly income, anything with equity or exclusivity, US work-for-hire nuances, and the one master services agreement you'll reuse for years — have that built properly once, then run on it.

A contract isn't a sign you distrust the client. It's the reason you'll never have to.

Frequently asked questions

Do freelancers really need a contract for small projects?

Yes — though for small jobs it can be light: a one-page agreement or even a detailed email the client confirms ("Reply 'agreed' and I'll get started") creates a written record of scope, fee and terms. The disasters contracts prevent — scope creep, non-payment, ownership confusion — don't check project size first.

What should a freelance contract include?

Eight essentials: specific scope with "anything else is quoted separately," payment terms with a deposit, a fixed number of revisions, IP transferring on full payment, a termination clause, timeline including client dependencies, a liability cap, and governing law. Most template contracts include all eight — check rather than assume.

Can I use AI to write my freelance contract?

As a drafting and translation tool, yes — AI is genuinely good at adapting templates, explaining clauses in plain English and flagging unfavourable terms in a client's contract. Treat the output as a strong draft, not legal advice: for high-value or unusual agreements, have a lawyer review the master version once, then reuse it.

What if a client refuses to sign a contract?

Treat it as information. Reasonable clients accept reasonable paperwork — it protects them too. If a contract feels too formal for the relationship, offer the lightweight version: a scope-and-terms email they confirm in writing. A client who won't commit to anything in writing is showing you how the invoice conversation will go.