Around 71% of freelancers have experienced a contract dispute — unpaid invoices, stolen work, or scope creep with no real recourse. Most of those disputes trace back to a single clause that nobody read closely before signing. The good news: the dangerous clauses are predictable, and once you know what they look like, they take seconds to spot.
This guide breaks down the seven clauses that most often hurt freelancers, what each one actually means in plain English, and what to change before you sign. None of this is legal advice — for high-value or unusual deals, get a lawyer — but for everyday contracts, knowing these seven is most of the battle.
1. Unlimited liability
An unlimited liability clause makes you responsible for the full cost of anything that goes wrong — with no cap. If a client claims your work caused $200,000 in damages, an uncapped clause means you could owe all of it, even though the project paid you $2,000.
What to look for: language like "the Contractor shall indemnify the Client against all losses" with no dollar limit or carve-outs.
How to fix it: add a limitation-of-liability clause capping your exposure — commonly at the total fees paid under the contract — and exclude indirect or consequential damages.
2. The IP grab
This is the clause that decides who owns the work you make. A buried IP-assignment clause can transfer ownership of everything you create — sometimes including tools, templates, or pre-existing material you brought to the project.
What to look for: "all work product, including pre-existing materials, shall be the sole property of the Client," or assignment that triggers before you've been paid.
How to fix it: transfer IP only on full payment, and explicitly exclude your pre-existing IP and reusable tools. If you license rather than assign, say so.
3. One-sided termination
A one-sided termination clause lets the client walk away at any time, for any reason, with little or no notice — while you stay locked in. You can finish 80% of a project and be owed nothing.
What to look for: "the Client may terminate this Agreement at any time for convenience" with no matching right for you and no kill fee.
How to fix it: make termination mutual, require reasonable notice, and add a kill fee covering work completed plus a percentage of the remaining contract.
4. The auto-renewal trap
An auto-renewal (evergreen) clause silently renews the contract — and its obligations — unless you cancel within a narrow window you probably forgot about.
What to look for: "this Agreement shall automatically renew for successive 12-month terms unless either party gives 90 days' notice."
How to fix it: shorten the renewal term, widen the cancellation window, or replace auto-renewal with an explicit opt-in at each term.
5. Non-compete overreach
A non-compete can bar you from working with whole industries or regions for months or years after the contract ends — a serious problem when freelancing is your only income.
What to look for: broad scope ("any competing business"), long duration, or no geographic limit. Note that enforceability varies a lot by jurisdiction — some places restrict or ban non-competes for contractors.
How to fix it: narrow it to specific named competitors, a short period, and a defined region — or replace it with a non-solicitation clause that only protects the client's actual customers.
6. Payment terms that delay your money
Slow or vague payment terms are how freelancers end up financing their clients for free. "Net 90," payment "upon project completion," or "after client approval" can leave you waiting months.
What to look for: long net terms, payment tied to vague approval, no deposit, and no late-payment interest.
How to fix it: require a deposit up front, set clear milestones, shorten net terms (Net 14–30), and add interest on late payments so the deadline has teeth.
7. The vague scope of work
A vague scope of work is the root cause of scope creep — endless "small changes" you never agreed to do for free. If the deliverables aren't specific, every disagreement defaults to the client's interpretation.
What to look for: deliverables described in a sentence, no revision limit, and no definition of what is out of scope.
How to fix it: list specific deliverables and milestones, cap included revisions, price extra work, and state clearly what the project does not include.
How to check a contract in under a minute
You don't need to memorise legal language to catch these. Read the contract once asking four questions:
- If something goes wrong, what's the most this can cost me? (liability)
- Who owns the work, and when? (IP)
- How do I get out, and what am I owed? (termination)
- When and how do I get paid? (payment terms)
If any answer is "unclear" or "all on me," that's the clause to negotiate.
This is exactly what Contract Sense automates: upload any contract and Lexly reads every clause, scores the risk from 1–100, flags the red ones, and explains them in plain English — so you catch these seven before you sign, not after. And when you need to send a contract, Contract Forge drafts a balanced one with fair versions of all seven clauses built in.
The bottom line: most freelance contract disputes are preventable. The dangerous clauses are predictable, and reading for liability, IP, termination, and payment catches the majority of them in under a minute.
Lexly is not a law firm, and AI-generated contracts are not a substitute for legal advice. For complex, high-value, or unusual agreements, consult a qualified attorney.