What are the biggest red flags in a freelance contract?

Unlimited revisions, IP transferring on signature instead of final payment, long payment terms (Net-45+), termination for convenience with no kill fee, broad indemnification, and unrealistic warranties. Each shifts risk onto you.

When should IP transfer in a freelance contract?

On receipt of final payment, not on signature or creation. If IP transfers before you're paid, you hand over the work and lose your leverage to get paid.

What payment terms are fair for freelancers?

Net-15 or Net-30. Avoid Net-45 or longer — you'd be financing the client's business interest-free. Add a late fee to give the due date teeth.

Freelance · Contracts

Freelance contract red flags: 8 clauses to check before you sign

A practical guide — 6 min read

Most freelance contracts aren't malicious. They're just written by the client's side, for the client's benefit, and they quietly move risk onto you one clause at a time. The damage rarely shows up at signing — it shows up three months in, when you're doing unpaid rework or waiting 60 days to get paid.

Here are the eight clauses that wreck freelancers most often, what each really means, and the exact line you can use to push back.

Unlimited revisions

"Contractor shall provide revisions until the Client is fully satisfied." There's no ceiling here — one project can become months of unpaid rework, and "satisfied" is entirely their call.

Push back: "Happy to include 2 rounds of revisions per deliverable; further rounds billed at my hourly rate."

IP transfers on signature (not payment)

If ownership of the work passes to the client the moment you sign — or on creation — you've handed over the deliverable before you've been paid, and lost your only leverage.

Push back: "IP and ownership transfer to the Client upon receipt of final payment."

Long payment terms (Net-45 or more)

Net-60 or Net-90 means you're financing the client's business, interest-free, for one to three months.

Push back: "Payment terms are Net-15" (or Net-30). Add a late fee of ~1.5% per month.

Termination for convenience with no kill fee

"The Client may terminate at any time, for any reason." Fine — but if they cancel when you're 70% done and there's no kill fee, you're owed nothing for the work already delivered.

Push back: "On termination, Client pays for all work completed to date plus a cancellation fee of [X]."

Broad indemnification

Indemnity clauses can make you cover the client's legal costs for claims — sometimes far beyond your control or your fee.

Push back: Cap your total liability (e.g. to the fees paid under the contract) and narrow what you indemnify to your own work.

Overbroad non-compete or exclusivity

A wide non-compete can block you from working in your own niche; exclusivity stops you taking other clients entirely.

Push back: Narrow the scope, time and geography — or accept exclusivity only if it's a retainer that pays for the lost capacity.

Unrealistic warranties

"Contractor warrants the software will be error-free and operate uninterrupted." No one can promise perfection — this sets you up to be in breach the moment any bug appears.

Push back: Warrant your workmanship (that the work is done professionally), not a bug-free, error-free guarantee.

Penalties and liquidated damages

Fixed penalties for delay (e.g. "$500 per day late") can quickly dwarf your entire fee, even for delays you didn't cause.

Push back: Make any penalty mutual, capped, and limited to delays actually caused by you.

Scan a contract in seconds. Paste any contract or SOW into our free contract red-flag checker → and it highlights these traps in plain English. No signup, nothing leaves your browser.

The mindset that protects you

You don't need to win every point. You need to catch the few clauses that turn a good project into an unpaid one — payment timing, IP timing, revision limits, and a kill fee. Push back politely and specifically, and most reasonable clients will agree, because your asks are fair. The ones who won't budge on any of these are telling you something useful about what working together will be like.

Never sign blind again

The red-flag checker is one of a small kit of free freelance tools. If you'd rather have a Claude Code skill read the whole contract and explain every risky clause for you, that's /redline — one of 7 in the Claude Code Freelancer Pack.

See the Freelancer Pack — $27

Common questions

When should IP transfer? On receipt of final payment — never on signature or creation.

What payment terms are fair? Net-15 or Net-30, with a late fee. Avoid Net-45+.

Is unlimited revisions ever okay? Only with a defined scope and a cap. "Until satisfied" with no limit is the trap.

This is general information, not legal advice. The checker catches common freelance traps but can miss things — for anything high-stakes, have a lawyer review it.