Freelance Contract Red Flags: 12 Clauses That Can Wreck Your Business
Most freelancers sign bad contracts without knowing it. Here's what to look for — and exactly what to say to fix it before you sign.
Why Contract Red Flags Matter (More Than Most Freelancers Realize)
A bad contract clause doesn't hurt you when the project is going well. It hurts you the moment something goes wrong — and in every freelance business, something eventually goes wrong. A client disputes your work. A project gets cancelled mid-stream. A client uses your deliverables in ways you never intended. The clause you glossed over becomes the entire dispute. By then, it's too late to negotiate.
Most bad contract clauses aren't malicious. Clients often use boilerplate agreements their lawyers drafted for employee relationships, not freelance engagements. Standard corporate contracts are written to protect the company — not the contractor. The clauses that strip your rights, eliminate your leverage, and leave you exposed weren't necessarily inserted to exploit you. They were just never written with you in mind. But “not intentional” doesn't mean “not harmful.”
Bad contract clauses cluster into three categories: payment risk (terms that make it easy for clients to delay, dispute, or avoid paying you), IP risk (clauses that transfer ownership of your work — or your entire creative process — to the client), and scope risk (language that lets the project expand indefinitely with no mechanism to charge for the growth). Most nightmare freelance engagements can be traced to one of these three categories in the original contract.
The good news: almost every red flag clause is fixable with one sentence before you sign. Clients who are reasonable will accept reasonable contract modifications. And the ones who won't? That refusal tells you exactly what working with them will be like when something goes sideways — which it will.
“67% of freelancers report at least one unpaid invoice — most stem from vague payment terms in the original contract.”
Want to build a contract that avoids these problems entirely? See our complete freelance contract guide →
The 12 Red Flag Clauses
What each clause looks like in a contract — and exactly why it's dangerous.
"Upon completion" payment terms
What it looks like
"Payment due upon completion and client approval of all deliverables."
Why it's dangerous
"Completion" is whatever the client decides it is. With no milestone triggers or defined approval window, clients can delay approval — and payment — indefinitely. You have no leverage because the contract gives you none.
Unlimited revisions
What it looks like
"Revisions until client is fully satisfied" or "changes at client's discretion."
Why it's dangerous
No revision cap means infinite unpaid labor on a fixed fee. Revision cycles become the project itself. A client who can't make decisions will use every round to restart from scratch — at no additional cost to them.
Work-for-hire + full IP assignment
What it looks like
"All work product, including unused concepts and preliminary designs, shall be considered work made for hire and shall become the sole property of Client."
Why it's dangerous
You surrender rights to everything you created — including sketches, drafts, and concepts the client never used. You can't show it in your portfolio. You can't reuse patterns or approaches you developed. The client owns your process.
Non-compete clauses
What it looks like
"Freelancer agrees not to provide services to any company in Client's industry for a period of 12–24 months."
Why it's dangerous
In a specialized niche, this clause eliminates your entire market. If you're a SaaS copywriter and your biggest client invokes this, you're banned from your own industry. May be unenforceable — but still chilling, and still expensive to challenge.
Exclusivity without premium
What it looks like
"Freelancer shall not perform services for any competitor of Client during the term of this agreement."
Why it's dangerous
You're being asked to turn away business with no compensation for that cost. Exclusivity is a legitimate ask — but only if the client is paying a premium that accounts for the revenue you're declining.
Unilateral termination, no kill fee
What it looks like
"Client may terminate this agreement at any time, for any reason, without notice or further obligation."
Why it's dangerous
Weeks of work can be cancelled with zero compensation. You absorb all the sunk cost — the time you blocked, the other projects you declined, the ramp-up work already done. The client walks away clean.
Net-60 or Net-90 payment terms
What it looks like
"Invoice payable within 60 days of receipt" on a project under $5,000.
Why it's dangerous
You're providing a 2–3 month interest-free loan on work you've already completed. For most freelancers, this creates a direct cash flow problem. Net-60+ is appropriate for enterprise contracts with commensurate project sizes — not standard freelance engagements.
Liability cap waivers
What it looks like
"Freelancer's liability shall not be limited and shall include all direct, indirect, and consequential damages."
Why it's dangerous
Any business loss the client suffers — even losses unrelated to your work — can be attributed to your deliverables. Without a liability cap tied to the contract value, a single dispute could expose you to claims that dwarf your fee.
Indemnification clause
What it looks like
"Freelancer shall indemnify and hold harmless Client from any claims, damages, losses, and attorneys' fees arising out of this agreement."
Why it's dangerous
You become responsible for the client's legal defense costs — even in frivolous suits brought against them by third parties. Even if the claim has nothing to do with your work, you could be on the hook for the legal fees to defend it.
Automatic renewal / rolling terms
What it looks like
"This agreement automatically renews for successive 12-month periods unless cancelled in writing 60 days prior to renewal."
Why it's dangerous
It's easy to miss a 60-day opt-out window. You can find yourself locked into another year at the same rate — or under the same unfavorable terms — simply because you forgot to send a cancellation letter in time.
Ownership of background IP
What it looks like
"Client shall own all intellectual property used in connection with this agreement, including any pre-existing materials contributed by Freelancer."
Why it's dangerous
The client claims your proprietary tools, templates, frameworks, and methodologies — things you developed before this project ever started. Your own processes become their property the moment you use them for this client.
Dispute resolution in another jurisdiction
What it looks like
"Any disputes arising from this agreement shall be resolved in the courts of [Client's State/Country]."
Why it's dangerous
Even if you win, the cost to pursue a claim in another state or country may exceed what you're owed. This clause effectively gives the client immunity from litigation — because they know you probably won't travel to collect.
Vague payment terms don't just create late payments — they make non-payment impossible to dispute. See our complete guide to getting paid as a freelancer →
How to Negotiate These Clauses (Without Sounding Difficult)
Most red flag clauses can be fixed with one sentence — a professional counter-proposal that protects you without making the client feel accused of bad intent. Use these scripts word-for-word or adapt to your voice.
Pushing back on unlimited revisions
"I noticed the agreement doesn't cap revision rounds. My standard terms include 3 rounds of consolidated feedback — this keeps the project on schedule and protects both our timelines. I'd propose adding this language: 'This agreement includes 3 rounds of revisions. Revision requests must be submitted as a single consolidated list within 7 days of each delivery. Additional rounds are billed at [rate] per round.' Would that work for your team?"
Note: Lead with the mutual benefit (schedule), not self-protection. Most clients accept this immediately — they weren't thinking about revision limits at all.
Pushing back on Net-60 payment
"The Net-60 terms would create a cash flow issue on my end for a project this size. My standard structure is 50% upfront before work begins and the balance due Net-15 on final delivery. This actually works better for both of us — you don't pay the full amount until you have the deliverables, and I'm not floating project costs for two months. Would you be open to adjusting to this schedule?"
Note: Frame it as 'works better for both of us' — because it genuinely does. A client who won't negotiate Net-60 on a small project is telling you something about how they run their business.
Pushing back on full IP assignment
"I'm happy to transfer ownership of the final deliverables upon receipt of full payment. I'd like to propose two small modifications to the IP clause: 1. I retain the right to display completed work in my portfolio, unless you need confidentiality — in which case I'm happy to discuss a reasonable window. 2. Any unused concepts or preliminary work that doesn't become part of the final deliverable remains my intellectual property. Everything you're actually receiving — the final deliverables — transfers to you in full. Does that work?"
Note: Portfolio rights are rarely a real concern for clients — they just forgot to carve them out. The unused concepts point is more important: you don't want a client owning ideas you'll reuse in your methodology.
Pushing back on no kill fee
"I noticed the agreement doesn't include a kill fee for early termination. I'd like to add this clause: 'If Client terminates this agreement after project kickoff, Client agrees to pay a kill fee equal to 50% of the remaining contract balance, in addition to payment for all work completed to date.' This is standard protection — it ensures I'm compensated for time already allocated to your project, and gives you a clear cost picture if circumstances change. I've had this in every contract and it's rarely come up — but it's good to have defined."
Note: The 'rarely come up' framing is disarming — you're signaling good faith, not adversarial positioning. Pair this with the deposit requirement so you're already protected for the first half of the project.
Scope creep often starts at the contract level — no revision cap, no change order process. See our scope creep guide for scripts and change order templates →
Don't Start From a Blank Contract.
SoloStack members get done-for-you contract templates, SOPs, and 50+ business documents — pre-built to protect you.
The Freelance Contract Minimum Checklist
Before you sign any contract — yours or theirs — run through this list. Every item you can't check is a gap a difficult client will eventually find.
Payment
Scope
IP
Protection
Need help building a contract that checks all 15 boxes? See our freelance contract guide with 8 must-have clauses →
Free Downloads — No Email Required
Three ready-to-use contract protection tools. Download any or all — no account, no signup, no catch.
Freelance Contract Red Flag Checklist
All 12 red flag clauses with severity ratings (high/medium) and exact fix language for each. Includes a 15-question pre-signing checklist and a 'safe to sign / negotiate first / walk away' scoring guide.
freelance-contract-red-flags-checklist.txt
No signup required
Contract Negotiation Scripts
12 word-for-word scripts — one per red flag clause — with both email and verbal versions. Plus 3 walk-away scripts for non-negotiable dealbreakers and 4 counter-proposal templates.
freelance-contract-negotiation-scripts.txt
No signup required
Freelance Contract Minimum Checklist
30-item checklist across 6 categories (identity, scope, payment, IP, termination, disputes). Each item tiered as must-have / nice-to-have / optional, with a scoring guide: 25–30 = protected, 18–24 = adequate, under 18 = vulnerable.
freelance-contract-minimum-checklist.txt
No signup required
Frequently Asked Questions
What's the most dangerous clause a freelancer can sign?
Can I cross out clauses in a contract and initial them?
Should I hire a lawyer to review every contract?
What if the client refuses to negotiate?
Are standard 'work for hire' agreements always bad for freelancers?
Stop Starting Projects on the Wrong Terms.
SoloStack's contract templates are pre-built to protect your income, IP, and time — no lawyer required.