When a client sends you their own contract to sign, it's tempting to skim it and say yes — especially if you're eager for the work. But contracts sent by clients are written to protect the client, not you. Knowing the warning signs can save you from unfair arrangements, unpaid work, and legal trouble.
Red Flag #1: Unlimited Revisions
Any clause that entitles the client to "unlimited revisions" or "revisions until satisfied" is dangerous. Without a clear limit, a single project can become an endless loop of changes. Some clients use this to extract significantly more work than the agreed fee covers.
What to do: Counter-propose a specific number of revision rounds (e.g., 2 rounds included, additional revisions at your hourly rate).
Red Flag #2: Work-for-Hire Language That Covers Everything
In US law, a "work for hire" clause means the client — not you — is legally the author and owner of the work you create. This is normal for some deliverables, but watch for clauses that cover all your work, including any pre-existing materials, tools, or methods you bring to the project.
A clause like "all work product, including all tools, processes, and pre-existing materials used to create deliverables, shall be owned by the client" is extremely unfair. You'd be handing over your entire toolkit.
What to do: Limit IP transfer to the specific deliverables, not your pre-existing work or general methods.
Red Flag #3: Vague or Missing Payment Terms
If a contract says "payment upon completion" without specifying what "completion" means, who decides when it's complete, or when payment is actually due, you have a problem. You could deliver the work and wait indefinitely while the client claims it isn't "complete."
What to do: Require specific payment milestones and due dates. "50% on signing, 50% due net 14 from final delivery" is clear and enforceable.
Red Flag #4: Non-Compete Clauses
Some client contracts include non-compete clauses preventing you from working with competitors for months or years. For a freelancer, this could effectively prevent you from working in your industry at all.
What to do: Push back on any non-compete clause. If they insist, negotiate a narrow scope (limited time, specific named competitors, specific geographic area) and factor the restriction into your fee — you're giving up income, so you should be compensated.
Red Flag #5: Unilateral Contract Modification Rights
Watch for clauses like: "The client reserves the right to modify this agreement at any time." This means the client can change the terms of your contract after you've signed it — potentially changing your fee, scope, or payment terms without your consent.
What to do: All modifications should require written agreement from both parties. Never sign a contract that gives one party unilateral modification rights.
Red Flag #6: Indemnification Clauses That Are Too Broad
An indemnification clause requires you to compensate the client for losses they suffer because of your work. A reasonable clause covers losses caused by your own negligence or breach of contract. An unreasonable clause might require you to indemnify the client against ANY losses, even those caused by the client's own actions.
Clauses like "Freelancer shall indemnify Client against all claims, losses, and expenses arising from or related to the services" are dangerously broad.
What to do: Add "solely caused by Freelancer's gross negligence or willful misconduct" to limit your exposure.
Red Flag #7: Ownership of "Ideas" and "Concepts"
Some contracts try to claim ownership not just of the final deliverables, but of any ideas, concepts, or approaches discussed during the project — even if never developed. This could mean a client claims ownership of concepts you developed independently and use across many client projects.
What to do: Limit IP transfer to the specific, agreed deliverables only. Exclude any pre-existing IP, general methodologies, and non-commissioned concepts.
Red Flag #8: Payment Tied to Client Satisfaction
Any clause that links your payment to the client's "satisfaction" or "approval" rather than to objective delivery milestones gives the client a potential escape route from paying. A client who decides they don't want to pay can simply claim to be "unsatisfied."
What to do: Payment should be triggered by delivery of specified deliverables, not by subjective approval. If approval is involved, include a reasonable approval period and a "deemed accepted" clause (e.g., "If client does not provide written feedback within 5 business days, deliverables shall be deemed approved").
What to Do When You Spot a Red Flag
Don't just refuse to sign and walk away from the work. Instead:
- Flag the specific clauses in writing via email
- Propose alternative language
- Explain why the change is important (protect the working relationship)
- If they refuse any negotiation, that tells you something about how the project will go
Most clients who present unfair contracts haven't deliberately designed them to be unfair — they're using a template their lawyer created to protect them. Reasonable clients will negotiate.
Use Your Own Contract Instead
Generate a fair, professional freelance contract that protects your interests — not just the client's.
Generate Your Contract →Frequently Asked Questions
What makes a freelance contract unfair?
Unfair clauses include: unlimited revisions, overly broad IP transfers (including your pre-existing work), vague payment terms, non-compete clauses that restrict your ability to work, unilateral modification rights, and liability clauses that hold you responsible for the client's own actions.
Can I negotiate a contract sent by a client?
Yes, and you should. Flag problematic clauses in writing, propose specific alternative language, and explain why the change matters. Most clients using standard templates will negotiate reasonable changes. A client who refuses any negotiation is itself a warning sign.
What is a work-for-hire clause and should I sign one?
A work-for-hire clause makes the client the legal author of work you create, transferring all copyright. It's reasonable for final deliverables but problematic if it extends to your pre-existing tools, methods, or materials. Always limit IP transfer to the specific agreed deliverables only.
Should I sign a non-compete clause as a freelancer?
Be very cautious. A broad non-compete could prevent you from working in your entire industry for months or years. If you must accept one, negotiate for a narrow scope (specific named competitors, limited time) and factor the income restriction into your fee.
What should I do if I already signed a bad contract?
Review the contract carefully to understand your specific obligations. Some unfair clauses may be unenforceable under local law. You can try to renegotiate in writing. For significant concerns, consult a solicitor or attorney before taking any action.