The 7 Clauses Every Freelance Contract Needs (In Plain English)

June 12, 2026 · 7 min read · Freelance contracts

Ask any freelancer who's been burned and the story is almost never “the client was a scammer.” It's a decent client, a vague agreement, and a disagreement nobody wrote down the answer to. Who pays for round six of revisions? When is the invoice actually due? Who owns the logo if the project dies halfway?

The fix isn't a 40-page contract. It's seven specific clauses, in plain English, agreed before the work starts. Here's what each one does, wording you can start from, and the dispute it prevents.

Quick note: this is general business information, not legal advice. For anything high-stakes or unusual, have a lawyer in your state look it over.

1. Scope of Work (What “Done” Means)

The single biggest source of freelance disputes is a scope that lives in someone's head. “Build me a website” means five pages to you and fifteen to the client. Your scope clause should name the deliverables, the quantities, and just as importantly, what's not included.

The “not included” sentence is the one most freelancers skip, and it's the one that ends the “I assumed that came with it” conversation before it starts.

2. Payment Terms (Amount, Schedule, and What Happens If They're Late)

Three things, all in writing: how much, when it's due, and the consequence of paying late. A deposit before work begins filters out the clients who were never going to pay. A late fee turns your invoice from a suggestion into a bill.

• Deposit: 30-50% upfront is standard for project work.
• Net-14 beats net-30 for solo operators. You are not a bank.
• “Work may pause” is your real leverage. Interest is the formality; stopping work is what gets invoices paid.

3. Revisions (A Number, Not a Vibe)

Unlimited revisions is how a $3,000 project becomes a $900 project on an hourly basis. Cap the rounds, define what one round is, and price the overflow.

The word “consolidated” matters. Without it, fourteen separate emails of one tweak each is legally one round. With it, the client gathers feedback into a single list, which is better for both of you.

4. Intellectual Property (Who Owns the Work, and When)

Default rules surprise people here. In the US, the creator generally owns the work until it's assigned in writing, even after the client pays. Clients assume the opposite. Say it explicitly, and tie the transfer to full payment.

“Upon receipt of full payment” is the clause doing the heavy lifting. A client who hasn't paid doesn't own the website, the logo, or the copy, and that fact resolves most payment standoffs by itself.

5. Termination (The Exit Both Sides Can Live With)

Projects die. Budgets get cut, companies pivot, people ghost. Without a termination clause, a dead project is a hostage negotiation. With one, it's an invoice.

Kill fees (a flat percentage owed if the client cancels mid-project) are common in design and writing work. Whether you add one or not, “paid for work completed” is the floor.

6. Timeline and Client Dependencies (Late Content, Late Launch)

Most missed deadlines aren't the freelancer's fault. They're the client's logo files that arrived three weeks late. If your deadline doesn't move when the client's inputs are late, you eat the delay and the blame.

That last sentence rescues you from the project that goes silent in month two and reappears in month seven expecting the old price and an instant restart.

7. Limitation of Liability (The Cap That Keeps a Bad Day Survivable)

If a bug in a site you built contributes to a client losing a big order, you don't want the dispute to be about their lost revenue. A liability cap ties your worst-case exposure to the size of the project, not the size of the client's business.

Nearly every agency contract on earth has this clause. Most freelance contracts don't, and freelancers are the ones who can least afford the gap.

The Pattern Behind All Seven

Every clause here answers a question before it becomes an argument: what's included, when money moves, how many rounds, who owns what, how it ends, whose delay it is, and how bad the worst case can get. None of it requires legalese. A short contract both sides actually read beats a long one nobody does.