5 Clauses Every Freelance Contract Needs

Most freelance contracts fail not because the client is dishonest, but because both parties had different assumptions about what they agreed to and the contract didn't resolve the difference. The client assumed revisions were included. The freelancer assumed the project had a fixed scope. The contract said nothing specific about either.

A good freelance contract doesn't need to be long. It needs to be precise about the five things that actually cause disputes. Here they are.

1. Scope of work — in concrete, measurable terms

The scope clause is the most important and the most commonly botched. "Design a website" is not a scope. "Write copy for a marketing campaign" is not a scope. These descriptions leave every meaningful question unanswered: how many pages, how many rounds of revision, in what format, by what deadline, to what specification?

A useful scope clause answers three questions specifically:

• What will be delivered? List the deliverables explicitly. Not "website design" but "design files for five pages: homepage, about, services, contact, and blog index, in Figma." Not "copywriting" but "1,200–1,500 words of body copy across three product pages."
• What is explicitly not included? This is the clause most people omit and most regret. If you're not doing development, say so. If you're not providing photography, say so. If the scope covers one round of feedback and not three, say so.
• What happens when the scope changes? Specify your process for scope changes: how they're requested, how they're priced, and that they must be agreed in writing before work begins. A sentence here prevents months of dispute later.

2. Payment terms — including what triggers each payment

Payment clauses routinely omit the one thing that matters most: what exactly triggers each payment. "50% upfront, 50% on completion" is almost a scope clause — it's missing the definition of "completion." Completion as defined by whom? What if the client is not satisfied? Does dissatisfaction delay the final payment indefinitely?

A payment clause that holds up specifies:

• The amounts and when they're due. If you use milestones, define the milestones. "On delivery of first draft" is better than "on completion of phase one."
• The payment method and currency. Obvious, but frequently omitted. If you invoice in EUR and the client pays in USD, specify who bears the exchange rate risk.
• What happens if payment is late. A late payment clause — typically interest at a specified rate per month after a grace period — changes the incentive structure. Even if you never enforce it, clients who know it exists pay faster.
• Whether approval is required before the final payment is due. If your contract says the client must "approve" the work before the final payment is triggered, define what approval means and how long the client has to provide it. Silence here allows clients to withhold approval — and payment — indefinitely.

3. Intellectual property — who owns what, and when

The default intellectual property position in most jurisdictions is that the creator owns the work they create. This surprises a lot of clients who assume they own everything they've paid for. Your contract needs to resolve this explicitly, before work begins, not after the invoice is disputed.

There are two common structures:

• Assignment on payment. All intellectual property in the deliverables transfers to the client upon receipt of full payment. This is the most common structure for work-for-hire engagements. It gives the client clear ownership and gives you a strong incentive mechanism — the client doesn't own the work until they've paid for it.
• License on payment. You retain ownership of the underlying work and grant the client a license to use it. This is more common in situations where the work incorporates existing intellectual property — a library, a framework, a set of assets — that you want to keep reusing. Define the license scope carefully: exclusive or non-exclusive, the territory, the duration, and permitted uses.

Also specify what you retain regardless of the IP structure: the right to include the work in your portfolio, to reference the client's name in your marketing, and to use anonymized versions of the work as examples. These are standard rights that clients rarely object to — but you need to ask for them explicitly to have them.

4. Revision and approval process — exactly how many and how long

Unlimited revisions is not a creative service — it's an indefinite obligation with no end date. Yet "revisions included" appears in countless freelance contracts without any specification of what that means.

A revision clause should specify:

• How many rounds of revisions are included and what constitutes a "round" (typically one consolidated set of feedback per round, not multiple separate emails).
• How additional rounds are priced if the client needs more than the included number.
• How long the client has to provide feedback on each round. Without this, a project can stay open indefinitely because the client hasn't gotten around to reviewing the work. Seven to fourteen business days is standard; after that, work is either deemed approved or re-engagement is treated as a new project.
• What "approval" means and what happens to scope and payment if the client requests substantive changes after approval.

5. Termination — by either party, with clear consequences

Most freelance contracts include a termination clause that says one party can terminate with notice. Almost none of them specify what happens to money and deliverables when they do.

A termination clause that actually works addresses three scenarios:

• Termination by the client before completion. What happens to work already done? The standard position is that the client pays for all work completed to the date of termination, calculated on a pro-rata or time-and-materials basis, plus a kill fee if the termination is without cause. The kill fee — typically 20–30% of the remaining project value — compensates you for the opportunity cost of the reserved time.
• Termination by the client for cause (your breach of the contract). What's the cure period? What constitutes a material breach? What remedy does the client have? Defining this protects both parties from disputes about whether a minor delay or a subjective quality disagreement justifies termination.
• Termination by you. Freelancers sometimes need to exit projects — the scope has changed beyond what's workable, the client relationship has broken down, or circumstances have changed. Specify your right to terminate with notice and what happens to payment and deliverables when you do.

What to do with the rest of the contract

Boilerplate provisions — governing law, entire agreement, severability, notices — are worth including but don't need to be long. One or two sentences each. The provisions described above are where disputes originate; everything else is housekeeping.

The goal of a freelance contract is not comprehensiveness. It's clarity. A clear, specific contract that both parties have actually read is worth more than an exhaustive template that nobody understands.