Most freelancers start using contracts after they get burned. An unpaid invoice. A project that tripled in scope. A client who wanted unlimited revisions. A dispute with nothing in writing.
Don’t wait to get burned. A solid freelance contract costs nothing to set up and protects everything you’ve worked to build.
This guide covers the 8 clauses every freelance contract must have — and the language that actually does the protecting, not just the language that looks good.
Why “I’ll Just Send an Email” Doesn’t Work
A project kickoff email is not a contract. It’s a record of enthusiasm. When a dispute happens, enthusiasm doesn’t determine who’s right — signed terms do.
A proper contract establishes:
- Exactly what you’re delivering and what you’re not
- When you get paid and what happens if you don’t
- Who owns the work
- What happens if either party wants to walk away
Fifteen minutes with a good contract template is worth more than hours of uncomfortable client conversations after things go sideways.
The 8 Essential Clauses
1. Scope of Work
This is the most important clause — and the one that prevents scope creep, which is the silent killer of freelance profitability.
Your scope of work should describe:
- Exactly what you’re delivering (specific deliverables, not categories)
- The format and specifications of deliverables
- What is explicitly NOT included
Weak scope: “Design a website for the client.”
Strong scope: “Design and deliver a 5-page WordPress website including: homepage, about page, services page, contact page with form, and blog index page. Includes two rounds of revisions per page. Does not include copywriting, photography, SEO implementation, or ongoing maintenance.”
If it’s not written down, clients will assume it’s included. Be specific to the point of obvious.
2. Timeline and Milestones
State the project start date, the expected delivery date, and any intermediate milestones. Include what deliverables are expected at each milestone.
Crucially, include client obligations in the timeline. Most scope creep and delays happen because the client was slow providing materials, feedback, or approvals.
Example language:
“The final delivery date of [DATE] assumes the client provides all required materials by [DATE] and provides feedback on each milestone within 5 business days of delivery. Delays caused by client response times may extend the final delivery date.”
This isn’t aggressive — it’s fair. You’re holding yourself accountable to a timeline that depends on their participation.
3. Payment Terms
Define all of the following:
- Total project fee (or hourly rate and estimated hours)
- Payment schedule: upfront deposit, milestone payments, final payment
- Payment method and currency
- Payment due date (e.g., “Net 14” means 14 days after invoice)
- Late payment policy
The standard structure that protects you: 50% upfront deposit before work begins, 50% upon final delivery. Never start work without the deposit.
Late payment language:
“Invoices unpaid after 15 days accrue a 1.5% monthly late fee. Final deliverables will not be transferred until payment is received in full.”
State clearly that you retain the work until payment is complete. This is your leverage. Don’t give it up until you’re paid.
4. Revision Policy
Define what a “revision” means versus what constitutes new work. This is where vague contracts cost you the most time.
Example:
“This project includes two rounds of revisions per deliverable. A revision is defined as minor adjustments to existing approved work. Requests that change the direction, scope, or core concept of a deliverable constitute new work and will be billed at $[RATE]/hour.”
Clients rarely intend to take advantage of you — they just don’t know where the line is unless you draw it.
5. Intellectual Property and Ownership
Who owns the work? The answer is not always obvious and varies by what you agreed.
By default under U.S. copyright law, the creator (you) owns the work unless you transfer it in writing. Most clients assume they own work they pay for — but legally, they don’t unless the contract says so.
Two common approaches:
Full transfer on payment: “Upon receipt of full payment, all intellectual property rights in the deliverables transfer to the client.” This is the most common for project-based work.
License (not transfer): “Freelancer retains copyright. Client receives a perpetual, non-exclusive license to use the deliverables for [PURPOSE].” Better for templates, frameworks, or work you want to reuse.
Also address: what you retain the right to use for your portfolio. If you do good work, you want to show it.
6. Confidentiality
If you’ll access sensitive business information — client lists, revenue numbers, internal processes, unreleased products — include a confidentiality clause.
Simple language:
“Each party agrees to keep confidential any non-public business information shared by the other party in connection with this project and not to disclose it to third parties without written consent.”
Many clients will request this anyway. Including it proactively signals professionalism.
7. Termination Clause
What happens if either party wants to walk away mid-project?
This clause protects both sides. Without it, a client can end the project and demand their deposit back, or you can be held liable for abandoning work.
Standard terms:
“Either party may terminate this agreement with 14 days written notice. Upon termination, the client shall pay for all work completed to the date of termination. The upfront deposit is non-refundable if work has commenced. Deliverables completed to the date of termination will be transferred upon receipt of outstanding payment.”
The key points: you get paid for work done, the deposit isn’t automatically refundable, and transfer of work is conditional on payment.
8. Limitation of Liability
If something goes wrong — a website goes down, a financial projection turns out wrong, a design doesn’t convert — limits your exposure.
Standard clause:
“Freelancer’s total liability for any claims under this agreement shall not exceed the fees paid by the client in the three months preceding the claim. Freelancer is not liable for any consequential, incidental, or punitive damages.”
This is standard in professional services contracts. Clients with reasonable expectations won’t object to it.
Additional Clauses Worth Including
Governing Law: Which state’s law governs disputes? Usually where you’re based.
Dispute Resolution: Specify mediation or arbitration before litigation — it’s faster and cheaper for both sides.
Independent Contractor Status: A clear statement that you’re an independent contractor, not an employee. Important for tax and legal purposes.
No Guarantee of Results: For marketing, SEO, or consulting work especially — you’re responsible for delivering the work, not for specific outcomes.
The Contract Signing Process
- Send the contract before any work starts — before the kickoff call, before the first draft
- Use e-signature (Bonsai, HelloSign, DocuSign, or even a PDF signed and scanned) — emails saying “looks good to me” are ambiguous
- Both parties sign — a client who won’t sign a contract before you start is a client worth reconsidering
- Keep a signed copy — in your files, accessible
Never start work without a signed contract and the deposit in your account. These two things, consistently applied, eliminate most freelance payment problems.
Frequently Asked Questions
Do I need a lawyer to write my contract? Not for standard project-based work. A well-reviewed template from a source like Bonsai, AND.CO, or a freelance legal guide is sufficient for most engagements. Consult a lawyer for unusually large contracts, equity arrangements, or NDAs with significant stakes.
What if a client refuses to sign a contract? Take it seriously. Clients who push back on basic professional terms are more likely to cause problems later. You can explain that contracts protect both sides — but if they still refuse, reconsider whether you want the engagement.
Should I use one contract template for all clients? Start with a solid template and customize the scope and payment terms per project. The protective clauses (IP, liability, termination) can stay consistent.
Can I use a contract for small projects? Yes. Even a short SOW and payment terms via email, if explicitly agreed to in writing, provides more protection than nothing. For small recurring clients you trust, a lightweight “project order form” style agreement works fine.
What’s the most common clause freelancers forget? The revision definition, by far. It’s the source of more disputes and scope creep than any other single issue.
Freelancer Finance Starter Kit
Rate calculator + quarterly tax estimator + first 30-day checklist.
No spam. Unsubscribe any time.