Most freelancers sign contracts without reading them carefully. Not because they're careless — but because contracts are long, written in dense legal language, and the client is waiting. So you skim, sign, and move on.
That decision costs freelancers thousands of dollars every year. Not from dramatic legal battles, but from quietly unfavorable terms that silently limit what you can do, who you can work for, and what you own after the project ends.
Here are the seven red flags that appear most often in standard freelance contracts — and exactly what to do about each one.
1. The Overbroad Non-Compete
A non-compete clause restricts you from working with competitors after your engagement ends. In employment contracts, these are common and sometimes enforceable. In freelance agreements, they can be devastating — because your entire client base might operate in the same industry.
If you're a UX designer who works with SaaS companies, this clause could bar you from taking on any SaaS client for two years — even if you left voluntarily and the project went perfectly.
Courts in many U.S. states treat non-competes signed by independent contractors with skepticism, and some states (California, Minnesota, North Dakota) effectively refuse to enforce them at all. But "unenforceable" doesn't mean cheap to defend. If a client sends a cease-and-desist, you still pay a lawyer to respond.
"I'd like to remove Section [X] entirely, or alternatively narrow it to direct competitors only (defined by name) with a 3-month maximum window. A broad industry-wide restriction isn't workable for my practice."
2. The IP Overreach
Work-for-hire clauses are standard and reasonable — the client owns the deliverables you build for them. The problem is when the language extends beyond deliverables to everything you used during the project.
The word "used" is the problem. If you used a code library you built over five years, a design system you've refined across dozens of projects, or proprietary workflows — this clause technically hands all of it over. You'd be building your reusable assets into someone else's ownership.
"I'm happy to assign ownership of the specific deliverables described in this agreement. I'd like to exclude pre-existing tools, frameworks, and IP I bring to the project — happy to list these in a Schedule A if helpful."
3. Unilateral Termination Without Notice
Most contracts include a termination clause. The question is who can terminate, under what conditions, and with how much notice. Watch for asymmetry: clauses where the client can cancel anytime with zero notice, but you're locked in to obligations on your end.
This means a client could pull the plug the day before a major deliverable is due — after you've already spent two months on the project — and owe you nothing beyond work already invoiced. If your payment schedule is milestone-based, you could be left with unpaid work.
"I'd like to add a 14-day written notice requirement for termination, and a provision that any work completed but not yet invoiced is payable upon termination."
4. The Low Liability Cap
Limitation of liability clauses cap the maximum amount either party can recover if something goes wrong. A liability cap that's lower than the total contract value is a significant problem — it means the client's downside exposure for a failure is less than what you're being paid to deliver.
If you're on a $15,000 project and something goes wrong on the client's end that costs you money — a bounced payment, a scope dispute, a breach — you're limited to recovering $500 in damages. Meanwhile, you may have sunk weeks of work into the project.
"I'd like to adjust the liability cap to match the total contract value, or set it at the fees paid in the 3 months prior to the claim — whichever is greater."
5. The Auto-Renewal Trap
Auto-renewal clauses are extremely common in service agreements and almost always favor the vendor — in this case, your client. They lock you into successive contract terms unless you send written notice within a specific window before the renewal date.
Miss that 30-day window — because you were on a deadline, traveling, or simply didn't track it — and you're legally committed to another full year. These clauses rarely work in your favor as the service provider because they eliminate your leverage to renegotiate rates.
"I'd prefer to remove auto-renewal and require affirmative agreement to extend. If auto-renewal stays, I'd like the notice window reduced to 10 days and the renewal term changed to month-to-month."
6. Vague Scope Without a Change Order Clause
Scope creep is one of the most common ways freelancers lose money. It's rarely deliberate — it starts with one small request, then another, until months have passed and you've delivered twice what you agreed to for the same price. Contracts that define deliverables vaguely and include no mechanism for addressing scope changes make this almost inevitable.
Look for language like "and such other services as reasonably requested" or "including any related tasks necessary to complete the project." These are open-ended obligations that a client can use to expand scope without additional payment.
"I'd like to add a change order clause: any work outside the defined scope in Schedule A requires written agreement on additional fees before work begins."
7. No Kill Fee for Client-Caused Delays
You block off time for a project. The client goes quiet for two months, then comes back wanting everything delivered on the original timeline. Or they cancel midway through. Without a kill fee or a clause addressing client-caused delays, you have limited recourse for the time you held open and couldn't fill with other work.
This is especially common in project-based contracts where payment is tied to final delivery. If the project never completes — for any reason — you could walk away with nothing for months of work.
"I'd like to add two provisions: (1) a kill fee of 25% of remaining contract value if Client cancels after kickoff, and (2) a clause that if Client delays delivery of required materials by more than 14 days, the timeline extends accordingly and any milestone payments due become payable."
The Takeaway
None of these clauses make a client evil. Most appear in standard contract templates that haven't been reviewed in years. The client's lawyer drafted them to protect the client — that's their job. Your job is to catch them before you sign.
You don't need a law degree to do this. You need to actually read the contract, know what to look for, and be willing to send a short email asking for changes. In most cases, clients accept reasonable edits without pushback.
The easiest way to make sure you're catching everything: upload your contract to ClauseGuard before you sign. It flags these patterns automatically, explains what each clause means in plain English, and gives you ready-to-send counter-language for every red flag it finds.
Have a contract to review?
Upload it to ClauseGuard and get a full red flag report in 30 seconds — free, no credit card required.
Analyze a contract free →