Freelance contract red flags
10 Predatory Clauses Every Freelancer Should Watch For (With Examples)
Most predatory freelance contracts do not look aggressive at first glance. They look polished, standard, and non-negotiable. The real problem is buried in the details: vague scope language, slow payment terms, broad indemnities, and rights grabs that quietly shift all the risk onto you.
Key takeaways
- If a clause is vague, the client usually benefits from that vagueness.
- Payment, scope, IP, and liability language create the biggest freelancer downside.
- You do not need to reject a contract outright — you can counter with narrower, fairer wording.
1. Net-60 or Net-90 payment terms
Long payment windows turn you into your client’s bank. If you deliver in March and get paid in June, you are financing their business with your labor.
For freelancers, fair payment terms usually mean an upfront deposit plus the balance due within 7 to 15 days of invoice, not months later.
Watch for this
Client will remit payment within 90 days of receipt of approved invoice.
Ask for this instead
Client will pay 50% upfront and the remaining balance within 7 days of invoice delivery.
2. Unlimited revisions
Unlimited revisions sound client-friendly but destroy margins. Without boundaries, a three-round project can turn into a three-month loop.
A fair agreement specifies how many revision rounds are included and what counts as out-of-scope work.
Watch for this
Freelancer will provide unlimited revisions until Client is satisfied.
Ask for this instead
Project fee includes two rounds of revisions. Additional revisions are billed at the standard hourly rate.
3. Work made for hire plus blanket IP assignment
Clients often ask for more ownership than they actually need. Broad assignment language can strip you of reusable methods, portfolio rights, templates, and pre-existing materials.
Most fair contracts give the client ownership of final deliverables after full payment while you retain your tools, know-how, and pre-existing IP.
Watch for this
All work product, concepts, drafts, processes, and related materials created by Freelancer shall belong exclusively to Client in perpetuity.
Ask for this instead
Upon full payment, Client receives ownership of final approved deliverables. Freelancer retains ownership of pre-existing materials, processes, and portfolio display rights unless otherwise agreed in writing.
4. Broad indemnification
An indemnity clause can make you responsible for the client’s legal costs and losses, even when the claim was outside your control.
Freelancers should push for narrow indemnities tied only to their intentional misconduct, infringement of original work, or proven breach.
Watch for this
Freelancer shall indemnify Client from any and all claims, losses, damages, costs, and liabilities arising out of the project.
Ask for this instead
Freelancer’s indemnity is limited to third-party claims arising directly from Freelancer’s intentional misconduct or willful infringement in original deliverables.
5. One-sided termination rights
If the client can terminate at any time for convenience with no kill fee, you carry all the downside. They can pause or cancel after you have blocked out calendar time and completed substantial work.
Watch for this
Client may terminate this Agreement at any time without further obligation.
Ask for this instead
Either party may terminate with written notice. Client remains responsible for all work completed through the termination date plus any agreed kill fee.
6. Payment contingent on acceptance, launch, or client collection
This wording lets the client delay payment by claiming something has not been accepted yet, or by tying your invoice to their own cash flow. Your pay should never depend on whether they get paid by someone else.
Watch for this
Invoices are payable upon final acceptance by Client and receipt of payment from Client’s customer.
Ask for this instead
Invoices are due according to the payment schedule in this Agreement and are not contingent on third-party approval or collection.
7. Non-compete or overbroad exclusivity
Many freelance agreements sneak in language that blocks you from serving similar clients or working in the same niche. That is a serious revenue restriction unless the scope is extremely narrow and compensated.
Watch for this
Freelancer shall not provide services to any competitor of Client during the term of this Agreement and for two years thereafter.
Ask for this instead
Any exclusivity applies only to the named project category, for a limited period, and only if separately compensated.
8. Open-ended scope language
Phrases like ‘related tasks as needed’ make it easy for a client to keep adding work without revisiting budget or timeline.
A strong contract points to a defined scope of work and states that extra work requires written approval.
Watch for this
Freelancer will provide the services described above and any related services reasonably requested by Client.
Ask for this instead
Services are limited to the scope described in Exhibit A. Any additional work requires written approval and a revised fee or timeline.
9. Unlimited liability
Without a liability cap, one project can expose you to damages far beyond what you were paid. That is rarely a reasonable trade for a freelancer.
Watch for this
Freelancer’s liability under this Agreement shall be unlimited.
Ask for this instead
Freelancer’s total liability under this Agreement is limited to the total fees paid under the applicable statement of work.
10. Client can reuse unpaid concepts and drafts
Drafts, rejected concepts, and unpaid strategy are still work. If the contract lets the client use everything regardless of payment, you lose control over your own creative output.
Watch for this
Client may use any materials, drafts, or concepts created during the engagement whether or not selected or fully paid.
Ask for this instead
Rights transfer only to final deliverables that have been fully paid. Unused concepts and unpaid drafts remain Freelancer property.
What to do before you sign
If a clause feels one-sided, slow down and ask what happens in the worst-case version of this project. Who waits to get paid? Who absorbs extra work? Who carries legal risk? The answer tells you who the contract protects.
Before signing, run the full agreement through a line-by-line review tool so you can catch risky language in context, not just the obvious clauses with dramatic headings.
TermGuard CTA
Want the fast version of this review?
Paste your contract into TermGuard to flag payment traps, IP overreach, revision creep, and liability language in plain English before you sign.