Freelance Contracts 101: Clauses You Should Never Skip

TL;DR: Every freelance contract needs at least eight essential clauses: scope of work, payment terms, IP ownership, a kill fee, revision limits, timeline protections, liability caps, and termination terms. Skipping any of these leaves you exposed to scope creep, late payments, cancelled projects with no compensation, and legal disputes that cost more than the project was worth.

---

A handshake is not a contract. Neither is a Slack message that says "sounds good, let's do it."

85% of freelancers experience late payments at least some of the time. 19% have an unpaid invoice sitting in their inbox right now. And the average freelancer spends 102 hours per year chasing money they already earned. That's over two full work weeks, gone.

Most of these problems are preventable. Not with better clients, but with better contracts.

You don't need a law degree to protect yourself. You need eight clauses, written in plain language, that cover the situations most likely to go sideways. Here's what they are and why each one matters.

Important: This article is educational, not legal advice. Contract law varies by jurisdiction, and your specific situation may require different language. Consult a qualified attorney before relying on any contract template.

1. Scope of Work

This is the single most important clause in any freelance contract, and the one most people write too vaguely.

A good scope of work lists every deliverable explicitly and states that anything not listed is out of scope. That means "design the app" becomes "5 screens at 1x and 2x resolution, delivered as Figma files." It means "build the website" becomes "6-page Next.js site with contact form, deployed to Vercel."

Without this clause, scope creep is inevitable. The client treats every "quick addition" as part of the original deal, and you have no paper trail to push back.

Include a revision limit here too (e.g., "2 rounds of revisions included; additional rounds billed at $X/hour"). This one sentence will save you from the endless feedback loop.

2. Payment Terms

Spell out the total fee, the payment schedule, the due dates, late fee policy, and accepted payment methods. Leave nothing implied.

A structure that works well for most projects:

• Deposit: 25-50% due before work begins (non-refundable)
• Milestone payments: tied to specific deliverable approvals
• Final payment: due on delivery, before source files or code access is transferred
• Late fee: 1.5% per month on unpaid balances after 30 days

That last point matters more than you think. Withholding final deliverables until payment clears is standard practice, and stating it explicitly in the contract removes any awkwardness. If you're looking for ways to structure your freelance finances around these payment schedules, this guide on how freelancers manage their bank accounts covers practical systems that work.

New legal protections are catching up, too. New York's Freelance Isn't Free Act (2024) and California's Freelance Worker Protection Act (2025) now require written contracts for engagements over $800 and $250, respectively. Late payment can mean double damages for the client. The law is increasingly on your side, but only if you have a written agreement.

3. Intellectual Property and Ownership

Here's something that surprises most clients: as a freelancer, you retain copyright over your work by default. Unless you sign a written transfer or work-for-hire agreement, you own what you created, even if the client paid for it.

This is where contracts get tricky, especially for developers and designers. You have three options:

Full transfer on payment: All IP transfers to the client once they've paid in full. Clean and simple.

License only: You keep copyright but grant the client a perpetual license to use the work. Good if you want to reuse components or approaches in future projects.

Work-for-hire: The work belongs to the client from the moment of creation. But for independent contractors, this only applies to 9 specific statutory categories under US copyright law. For everything else, you need an explicit assignment clause.

If you write code, be careful with blanket IP transfers. A clause that says "all intellectual property created during this engagement" could include your personal utility libraries and reusable frameworks. Limit the transfer to project-specific deliverables.

And always, always reserve the right to show the work in your portfolio. Add a portfolio-use carve-out unless there's a genuine confidentiality reason.

4. Kill Fee / Cancellation Clause

You blocked three weeks on your calendar. You turned down other work. Then the client emails: "We're going in a different direction."

Without a kill fee clause, you get nothing for that lost time.

A staged kill fee structure protects you proportionally:

| When the client cancels | Kill fee | |---|---| | Before first draft/milestone | 25% of total contract value | | After first draft/milestone | 50% | | After revisions begin | 75% |

Kill fees aren't punitive. They compensate for the opportunity cost of blocked calendar time and turned-down alternative work. Most professional clients expect this clause. If a client pushes back hard on it, that's a red flag.

5. Revision and Change Request Process

"Two rounds of revisions included" is not enough by itself. You also need to define what counts as a revision round.

The language that works: "A revision round is defined as a consolidated set of feedback submitted in a single document. Additional revision rounds are billed at [hourly rate] per round."

Without this, clients send piecemeal feedback across five emails over two weeks, and every message becomes its own revision round. Defining "round" as a single consolidated submission keeps the process manageable.

6. Timeline and Deadlines

Deadlines should apply to both parties, not just you. If the client delays feedback by three weeks, they shouldn't expect the original delivery date to hold.

Good timeline language: "If client feedback is delayed by more than 5 business days beyond the scheduled review date, the project timeline extends by an equal number of days."

This clause saves you from the most common freelance frustration: a client who goes silent for a month, then suddenly expects everything done by Friday.

7. Limitation of Liability

This clause caps the maximum damages you can be held responsible for, typically at the total project fee.

Without it, a client could theoretically sue for consequential damages. Imagine: "Your code had a bug, our site was down for a week, and we lost $200K in sales." Even if you win that case, the legal costs could be devastating.

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

8. Termination Clause

Either party should be able to end the contract cleanly, with clear notice requirements and payment terms for completed work.

"Either party may terminate this agreement with 14 days' written notice. Client shall pay for all work completed through the termination date."

This gives both sides a clean exit. Without it, you're stuck arguing about whether the contract is "over" when things go badly.

Red Flags in Client-Provided Contracts

When a client sends you their contract instead, watch for these:

• Unlimited revisions ("until client is satisfied") with no cap
• IP transfer before full payment is received
• No payment schedule, just "upon completion" with no defined completion criteria
• Blanket confidentiality that prevents you from ever showing the work in your portfolio
• Unilateral modification rights letting the client change terms at any time
• Dispute resolution in a jurisdiction that's inconvenient for you

A client's "standard contract" is standard for the client. It's not necessarily fair to you. Always read every clause, even with repeat clients. Relationships change when money gets tight.

---

FAQ

Q: Do I need a lawyer to create a freelance contract?

A: Not necessarily for a basic contract, but having a lawyer review your template at least once is a smart investment. A one-time legal review typically costs $200-500 and gives you a solid foundation you can reuse across projects. For complex projects or large budgets, get project-specific legal advice.

Q: Should I use a contract even for small projects?

A: Yes. New York and California now legally require written contracts for freelance engagements over $800 and $250, respectively. Even where it's not required by law, a simple one-page agreement protects both you and the client. The smaller the project, the shorter the contract can be, but it should still exist.

Q: What's the difference between work-for-hire and copyright assignment?

A: Work-for-hire means the client owns the work from the moment it's created, as if they made it themselves. But for independent contractors, this only legally applies to 9 specific categories under US copyright law (like contributions to a collective work). For most freelance work, you need a separate copyright assignment clause to transfer ownership. If your contract says "work-for-hire" but doesn't include an assignment backup, the client might not actually own what they think they own.

Q: What happens if I don't have a contract and a client doesn't pay?

A: Without a written agreement, you still have some legal options (like small claims court), but proving the terms you agreed to becomes much harder. It's essentially your word against theirs. A contract turns a "he said, she said" dispute into a clear-cut breach with documented terms, due dates, and consequences.