Freelancing
How to Read a Freelance Contract (Before You Sign)
By FixMyContractLast updated Jul 3, 20269 min read
A freelance contract is the agreement that defines what you deliver, when you get paid, who owns the work, and who carries the risk if something goes wrong. The five clauses that most often work against freelancers are payment terms, scope and revisions, intellectual-property timing, termination, and indemnification — this guide explains each in plain English, with the exact fix to ask for.
You found the client. You agreed on the work. Then a PDF lands in your inbox titled "Master Services Agreement" — eight pages of dense legal text. Most freelancers skim it, sign, and hope. That's how you end up unpaid, owning none of your own work, or on the hook for a client's mistake.
You don't need a law degree to read a freelance contract. You need to know what each section is for, which clauses quietly favor the client, and what a fair version looks like. This guide walks the whole document, top to bottom.
What should you check first? The 60-second skim
Before reading line by line, locate the five clauses that decide whether a freelance contract is fair:
- Payment — how much, when, and what happens if they pay late.
- Scope & revisions — what you owe, and what counts as "extra."
- Intellectual property (IP) — who owns the work, and when ownership transfers.
- Termination — how either side ends the deal, and whether you're paid for work done.
- Liability & indemnification — who pays if something goes wrong.
If those five are fair, the rest is usually negotiable detail. At a glance:
| Clause | Biggest risk | Ask for |
|---|---|---|
| Scope of work | Open-ended scope on a fixed fee | Defined deliverables + "extra work billed at $X/hour" |
| Payment | Everything due "on completion" | 25–50% deposit, milestones, late-payment interest |
| Revisions & acceptance | Unlimited revisions, no sign-off deadline | Capped rounds + deemed acceptance in 7 business days |
| Intellectual property | IP transfers before you're paid | "IP transfers on receipt of full payment" |
| Termination | Client cancels anytime, owes nothing | Kill fee + mutual 14-day notice |
| Indemnification & liability | Uncapped, one-way risk | Mutual indemnity, liability capped at fees paid |
Now the full walkthrough.
1. What should the scope of work include?
The opening names the parties and references a Statement of Work (SOW) or exhibit describing the project. This is where over-commitment hides.
- Look for: a specific, bounded description of deliverables — not "all services the Client may reasonably request."
- Red flag: open-ended scope ("and related tasks," "as needed") with a fixed fee. That's unpaid scope creep written into the contract.
- Fix: tie the fee to a defined deliverable list, and add: "Work beyond this scope is billed at $X/hour upon written approval."
2. How do acceptance and revisions work?
Defines what "done" means. The danger is acceptance and revision language.
- Red flag: unlimited revisions, or acceptance "at the Client's sole satisfaction" with no deadline. The client can withhold sign-off — and payment — indefinitely.
- Fix: cap revision rounds (e.g. "two rounds of revisions included"), and add a deemed-acceptance clause: "Deliverables are accepted if the Client does not provide written objections within 7 business days."
3. What payment terms should a freelancer ask for?
Read this twice. Check four things:
- Amount and schedule: Is there a deposit (25–50% up front is standard for project work)? Are there milestones, or is everything due at the end?
- Net terms: "Net 30" means you wait 30 days after invoicing. "Net 60/90" is a cash- flow trap for a solo business.
- Late fees: A fair contract lets you charge interest on overdue invoices (e.g. 1.5%/month). If it's silent, add it.
- Expenses: Are reimbursable costs (software, stock, travel) covered?
4. Who owns the work — and when does IP transfer?
Most client work is work-for-hire: the client owns the final deliverables. That's normal. The trap is the timing and the scope of the assignment.
- Red flag: IP assigns to the client on creation or regardless of payment — meaning they own your work even if they never pay.
- Fix: make assignment conditional: "All IP transfers to the Client upon receipt of full payment." Until then, you hold it.
- Also check: carve-outs for your pre-existing tools, templates, and know-how (your "background IP"), and your right to show the work in your portfolio.
5. What's reasonable in a confidentiality clause?
Usually reasonable, but watch the duration and the definition.
- Red flag: "perpetual" confidentiality covering "all information," or a one-sided NDA that binds only you. (See our NDA guide.)
- Fix: mutual confidentiality, a 2–3 year term, and standard exclusions (info that's public, already known, or independently developed).
6. What happens if the client cancels? Termination and the kill fee
How the deal ends. Two failure modes: you can't get out, or you get nothing if they bail.
- Red flag: the client can terminate "for convenience" at any time with no payment for work already done.
- Fix: add a kill fee — payment for all work completed plus a percentage of the remaining fee — and a notice period (e.g. 14 days). Make termination rights mutual.
7. What are indemnification and limitation of liability?
The scariest-looking section, and where freelancers take on the most hidden risk.
- Indemnification = you promise to cover the client's losses/legal costs in defined situations. Red flag: broad, one-way indemnification making you liable for any claim, including the client's own conduct.
- Limitation of liability = a cap on what you could owe. Red flag: no cap on your liability, or a cap far above your fee.
- Fix: make indemnification mutual and tied to your actual fault, and cap your total liability at the fees paid under the contract.
8. The boring clauses that bite
- Governing law / jurisdiction: which state/country's courts apply. A dispute across the world is effectively un-enforceable for a solo freelancer.
- Non-compete / non-solicit: can quietly bar you from working with similar clients. Keep these narrow in time, geography, and scope.
- Independent contractor status: confirms you're not an employee — protects both sides on tax and benefits.
Freelance contract red-flag checklist
Copy this. If a contract trips three or more, renegotiate before signing:
- Open-ended scope with a fixed fee
- No deposit and no milestone payments
- Net 60+ payment terms
- Unlimited revisions / acceptance "at sole satisfaction"
- IP assigns before (or regardless of) payment
- No portfolio / background-IP carve-out
- One-sided, perpetual confidentiality
- Termination for convenience with no kill fee
- Uncapped or one-way indemnification
- No limitation-of-liability cap
Get a thorough first read in minutes
Reading every clause yourself is the gold standard — but when a contract lands an hour before a deadline, FixMyContract reads it for you: upload the PDF (or snap a photo), and get a clause-by-clause risk score with a plain-English fix for each flagged term.
👉 Analyze your contract free — 3 analyses every month, no card.
Sign contracts often? Join the Pro waitlist — early members lock in founding pricing.
FAQ
Do I really need a written freelance contract? Yes. A written agreement is your only reliable proof of scope, price, and payment terms if a client disputes the work.
Can I edit a contract a client sends me? Absolutely — that's normal. Redline the clauses above and send it back. Negotiating terms is expected, not rude.
What's the difference between work-for-hire and an IP license? Work-for-hire transfers ownership to the client. A license lets them use the work while you keep ownership. Licensing is often better for reusable work (design systems, code).