As a freelancer, contracts are your lifeline. They define what you do, what you get paid, and what happens when things go sideways. But many clients present contracts written by their lawyers — and those contracts are designed to protect them, not you.
Here are 8 clauses that freelancers should scrutinize before signing.
1. “Work Made for Hire” on Everything
The problem: The client owns everything you create — including preliminary sketches, unused concepts, and work product that doesn’t make it into the final deliverable. You can’t use any of it in your portfolio without permission.
What’s fair: The client owns the final deliverables after full payment. You retain rights to preliminary work and can use finals in your portfolio. License the work rather than transferring full copyright when possible.
Watch for: “All work product, including but not limited to drafts, concepts, and preliminary materials, shall be considered work made for hire.”
2. Unlimited Revisions
The problem: No cap on revisions means a project that should take 2 weeks drags on for 3 months. Each round of “just one small change” eats into your hourly rate until you’re working for pennies.
What’s fair: Define a specific number of revision rounds (2–3 is standard) with additional revisions billed at your hourly rate. Define what constitutes a “revision” vs. a “new request.”
Watch for: “Contractor shall make all revisions requested by Client” or no mention of revision limits at all.
3. Broad Non-Compete Clauses
The problem: You can’t work with any of the client’s competitors — which the client defines as broadly as possible. For a tech company, that could mean half the industry. A 12-month non-compete can effectively shut down your freelance business. Our deep dive into non-compete agreement red flags covers exactly what makes these clauses dangerous and when they’re unenforceable.
What’s fair: Non-competes should be narrow in scope, geography, and duration. For freelancers, a 3–6 month period with specific named competitors is more reasonable. Many states (including California) don’t enforce non-competes at all.
Watch for: “Contractor shall not provide similar services to any competitor” — especially without defining who competitors are.
4. Net-60 or Net-90 Payment Terms
The problem: You finish the work in January but don’t get paid until March or April. For freelancers living project-to-project, waiting 60–90 days for payment can create serious cash flow problems.
What’s fair: Net-15 or Net-30 is standard for freelance work. Better yet: 50% upfront, 50% on delivery. For larger projects, milestone-based payments keep cash flowing throughout.
Watch for: “Payment shall be due within 60/90 days of invoice” or “payment upon client’s final approval” with no deadline for that approval.
5. Scope Creep Protection (or Lack Thereof)
The problem: The contract describes a vague scope of work, and the client keeps adding requests that weren’t in the original agreement. Without clear boundaries, you end up doing double the work for the same price.
What’s fair: Detailed scope of work with specific deliverables listed. A change order process for anything outside the original scope. Additional work billed at agreed-upon rates.
Watch for: Vague language like “and other tasks as assigned” or “including but not limited to.” If the scope isn’t specific, neither is your obligation.
6. One-Sided Termination Clauses
The problem: The client can terminate at any time without cause or payment, but you’re locked in for the full project duration. Some contracts even require you to return deposits if the client terminates. If you’re already stuck in a lopsided agreement, our guide on how to get out of a contract can help.
What’s fair: Both parties should have equal termination rights with reasonable notice (14–30 days). You should be paid for all work completed up to the termination date, plus any expenses incurred.
Watch for: “Client may terminate this agreement at any time” paired with “Contractor must provide 30 days’ notice.” Asymmetric termination rights are a major red flag.
7. Indemnification That Goes Too Far
The problem: You agree to indemnify (pay for) the client’s losses, even if those losses aren’t your fault. A broad indemnification clause could make you liable for the client’s own negligence. If you’re unsure what this language actually commits you to, read our explainer on what indemnification means in a contract.
What’s fair: Indemnification should be mutual and limited to losses caused by the indemnifying party’s actual negligence or breach of contract. Your total liability should be capped — typically at the total contract value.
Watch for: “Contractor shall indemnify, defend, and hold harmless Client from any and all claims, damages, losses…” without limiting the scope to your actual work.
8. Ownership Tied to Final Payment
The problem: This one can actually work in your favor if used correctly — but many freelancers miss it. Some contracts transfer IP ownership immediately upon creation rather than upon final payment, meaning the client owns your work even if they never pay you.
What’s fair: IP transfer should happen only after full payment. Include a clause that grants the client a limited license to use work-in-progress, with full ownership transferring upon final payment.
Watch for: “Ownership of all work product shall vest in Client upon creation” rather than “upon receipt of final payment.”
Before You Sign
Every freelance contract is negotiable. If a client won’t budge on any of these points, that tells you something about what kind of client they’ll be. Many of these tactics overlap with the broader fine print tricks companies use in all kinds of agreements.
Use Fineprint to scan any freelance contract in seconds. It’ll flag these red flags automatically and explain each clause in plain English — so you can negotiate from a position of knowledge, not guesswork.
Your work has value. Make sure your contracts reflect that.