Freelance Contract Red Flags: 6 Clauses to Watch Before You Sign

When you send your own contract, you control the terms. But sooner or later a bigger client sends theirs — a multi-page document written by their lawyers, to protect them, that they expect you to sign without reading. That's exactly when freelancers get burned: not by the work, but by a clause they skimmed past. Here are the six red flags to look for before you sign, what each one really means for you, and how to push back without blowing up the deal.

This is practical guidance, not legal advice. For high-value or complex contracts, a one-hour review by a lawyer in your jurisdiction is cheap insurance — these flags help you know when it's worth it.

First principle: a client contract is written for the client

Nearly every contract a client hands you is drafted to protect them and shift risk onto you. That doesn't make them villains — it's just whose lawyer wrote it. Which means: you are allowed to negotiate. "I'd like to adjust a couple of clauses" is a normal, professional request, not a deal-breaker. Reasonable clients expect redlines; the ones who refuse any change at all are themselves a red flag.

The 6 red flags

1. IP that transfers on delivery, not payment

Most client contracts assign intellectual property to the client — that's normal. The trap is timing: a clause transferring ownership upon delivery rather than upon final payment means you hand over the rights before the money lands, gutting your leverage if they pay late or not at all. Push back: "IP and ownership transfer upon receipt of final payment." Simple, fair, standard.

2. IP assignment so broad it eats your toolkit

Aggressive "work-for-hire" clauses can claim everything you create on the project — including your reusable templates, processes, frameworks, and pre-existing IP you brought to the table. Sign it and you can't reuse your own components or methods for other clients. Push back: carve out your pre-existing and general-purpose IP: "Contractor retains ownership of pre-existing materials, tools, and methodologies; client receives a license to use them as embedded in the deliverables." Assign the project-specific work, not your whole toolbox.

3. Uncapped indemnification

This is the scariest and most overlooked. A broad indemnity clause makes you responsible for all claims and legal costs related to the project — and without a cap, a single dispute could expose you to damages far exceeding your entire fee. A $2,000 project should not carry six-figure liability. Push back: cap your total liability at the fees paid (or a fixed amount), and narrow indemnification to losses caused by your negligence or breach — not anything and everything.

4. Unlimited or "until the client is satisfied" revisions

"Revisions until the client is satisfied" sounds generous and reads like a trap, because a client can simply decide they're never satisfied. It's open-ended scope creep written into the contract. Push back: define a number — "Includes two rounds of revisions; additional rounds billed at $X/hour" — and an acceptance/approval mechanism so "done" has a definition.

5. Termination for convenience with no kill fee

Many contracts let the client terminate "for convenience" — i.e., anytime, for any reason. Fine if there's a kill fee. Without one, a client can cancel after you've done 80% of the work and owe you for none of it; you absorb the entire loss of a project you planned around. Push back: add a kill/cancellation fee — "On termination, client pays for all work completed plus a cancellation fee of X% of the remaining contract value" — and/or keep your deposit non-refundable.

6. Vague scope and payment terms

Not a single clause but a pattern: fuzzy deliverables, no payment dates or terms, undefined acceptance criteria. Every ambiguity is resolved in the drafter's favor — and that's not you. Push back: insist scope, deliverables, timeline, and payment schedule are spelled out (a statement of work attached to the contract is ideal). Specificity protects the side with less power — you.

A few more worth a second look

• Non-compete / exclusivity clauses that bar you from working with anyone in the client's industry — fine for a big retainer, unreasonable for a one-off gig.
• Confidentiality (NDA) that's one-directional or perpetual — usually fine, but read what you're barred from disclosing and for how long.
• "Net 60/90" payment buried in the terms — see payment terms explained; negotiate it down or require milestones.
• Auto-renewal clauses that lock you (or them) into another term unless you cancel in a narrow window.

How to push back without losing the deal

Most reasonable clients accept fair, specific edits — especially payment-on-IP-transfer, a liability cap, and a revision limit. If a client refuses any change and insists you sign a one-sided contract as-is, that resistance tells you how the working relationship will go.

The bottom line

When a client sends their own contract, the danger isn't the work — it's the fine print written to shift risk onto you. Watch for IP that transfers before payment, overbroad IP grabs, uncapped indemnification, unlimited revisions, termination without a kill fee, and vague scope. Read it, flag the few clauses that matter, propose specific fixes, and negotiate calmly. The freelancers who get burned are the ones who didn't read; the ones who thrive treat the contract as something to discuss, not just sign.