8 Contract Clauses That Can Screw Freelancers (and Exactly What to Say Back)

What it is: A clause saying everything you create "shall be deemed work made for hire," or that you "irrevocably assign all rights, title and interest" in the work — often including drafts, source files, concepts, and anything you did before the project started.

Why it's dangerous: Taken literally, "all rights" means the client owns not just the final deliverable but every draft, sketch, concept, and iteration — plus anything derived from them and sometimes your general knowledge and tools. You lose the right to show the work in your portfolio, reuse a concept, or build on your own ideas. In the worst drafting, "all rights" even sweeps up pre-existing work you brought to the project.

"Freelancer agrees that all deliverables, including all drafts, concepts, source files, and preparatory materials, are works made for hire and become Client's sole and exclusive property, including all intellectual property rights therein."

What to push back on: Limit ownership to the final, accepted deliverable the client actually paid for, and carve out your pre-existing materials and tools. Keep the right to show the finished work in your portfolio (almost all clients accept this — it's free publicity for them). Something like: "Happy to assign full rights to the final accepted deliverable. Could we carve out my pre-existing concepts and source materials, and keep a license to show the finished work in my portfolio?"

What it is: A clause that silently renews a recurring engagement (monthly retainer, ongoing support), combined with a stricter "we can end this anytime" right for the client than for you.

Why it's dangerous: Auto-renewal means you can wake up a year in doing work for a contract you only sort of remember signing — at terms you never renegotiated. Unilateral termination means the client can walk with little or no notice while you can't, stranding you mid-project with work done but no recourse.

"This Agreement shall automatically renew for successive one-year terms unless either party provides written notice of non-renewal at least 90 days prior to the end of the current term. Client may terminate this Agreement at any time for convenience upon 7 days' written notice."

What to push back on: You want symmetry and no surprise lock-in. Ask for the same notice period for both sides, the option to renew only by mutual written agreement, and termination rights for you if the client doesn't pay or makes unreasonable demands. Try: "Can we make renewal opt-in instead of automatic, and give both sides the same notice period? I'd also like a termination right if my invoices go unpaid."

What it is: A clause making payment contingent on the client being satisfied, "approving," or "accepting" the work — often without defining what that means or how many rounds of review it covers.

Why it's dangerous: "Subject to Client's satisfaction" sounds fair but is an open door. If satisfaction is undefined, the client can reject the work indefinitely with no clear finish line, and you've effectively agreed to work until they're happy — however long that takes — with payment dangling the whole time. It converts a scope you agreed to into whatever the client decides they want.

"Freelancer shall be paid for accepted work only. Client's acceptance is at Client's sole discretion and subject to Client's approval of the deliverables."

What to push back on: Payment should gate on delivering what was agreed, measured against a written scope and spec you both signed — not on an undefined feeling. Ask for objective acceptance criteria and a defined review limit: "Can we tie acceptance to the scope and milestones in the brief, with two rounds of revisions included? Once I meet that, I'd like the fee to be due whether or not internal stakeholders approve."

What it is: A clause spelling out what happens if the client cancels mid-project — and, dangerously, what happens if you can't complete the work. Many contracts define a small kill fee for the client canceling, but none for work already performed.

Why it's dangerous: If the contract only says "client may cancel at any time," you can do weeks of work, get canceled on a Friday, and have zero right to compensation for what you already did. The vulnerability cuts both ways: if a contract imposes harsh fees on you for non-completion but nothing on the client for canceling, one side holds all the downside.

"Client may terminate this Agreement at any time upon written notice. Freelancer shall be paid only for deliverables completed and accepted prior to termination." (Note who carries the risk of abandoned work.)

What to push back on: Get a kill fee that compensates you for work-in-progress — commonly a percentage of the outstanding fee scaled to how much is done, or a minimum if anything has started. Something like: "If the project is canceled after I've started, I'd like compensation for work completed to date, or a kill fee of [X]% of the remaining fee if the project is less than halfway done. That keeps cancellation risk from landing entirely on me."

What it is: A clause where "revisions are included" has no cap, or where the scope is described so loosely ("and other services as reasonably requested") that new work keeps folding in without new money.

Why it's dangerous: Unlimited revisions is the classic freelancer trap — an open-ended time budget with a fixed price. Combined with loose scope language, the project grows, the cost doesn't, and you're either eating hours or having a tense conversation about the bill. The fix isn't greed; it's a boundary that keeps the project finite and the client's feedback loop accountable.

"The Project Fee includes all revisions requested by Client, regardless of number. Client may request such reasonable additional services as may be required to complete the Project."

What to push back on: Cap included revisions (two rounds is standard) and define what a "round" means. Scope new work out explicitly: "Can we include two rounds of revisions in the fee, defined as feedback on the full deliverable in one go, and quote any work beyond that separately? I'd also love the scope to list what's included so additions are paid."

What it is: Two clauses that usually appear together. A liability cap limits how much the client can ever claim from you (often to the fee you charged). An indemnification clause makes you responsible for costs, damages, or claims arising from your work — sometimes including the client's own third-party misuse.

Why it's dangerous: A cap at "the project fee" means for a $500 job, the most you're ever exposed to is $500 — that's actually good for you. The dangerous half is indemnification: it can make you liable for legal costs and damages that dwarf your fee, especially if the client down the line gets sued over the work by one of their customers. The combination that should alarm you is a tiny fee, a cap at that fee, and an indemnity that quietly exposes you far beyond it.

"Freelancer agrees to indemnify and hold harmless Client from any and all claims, damages, and costs, including attorneys' fees, arising out of or related to the services or deliverables."

What to push back on: Indemnification should be mutual and scoped to things that are genuinely your fault — not a blanket promise covering the client's own edits or third-party claims. Ask to cap indemnity at what you've actually been paid, and exclude liability for client-modified work or third-party content: "Can we make indemnification mutual and limited to claims resulting directly from my work as delivered — not from your edits or how you use it? I'd also like any liability capped at the fee for this project."

What it is: A clause restricting you from working for a competitor or in a related field for a period of time after the engagement ends.

Why it's dangerous: For a multi-month agency project, a broad non-compete might be reasonable. For a two-week freelance job, a clause that says "you can't serve any client in the same industry for 12 months after" is effectively a tax on your entire livelihood — and freelancers sign these under-scoped more often than you'd think. Non-competes are also legally messy, and many jurisdictions restrict or refuse to enforce them, which means you may be agreeing to something that's ambiguous rather than clearly valid.

"For a period of twelve (12) months following termination, Freelancer shall not provide services to any business that competes with Client or operates in Client's industry."

What to push back on: Ask for the non-compete to be removed, or at minimum narrowed to overlap with the actual engagement and a specific competitor (where there's a real trade-secret risk) rather than a whole industry. Better, ask for a non-disclosure agreement instead — protecting the client's confidential info is usually the actual concern: "A non-compete is a lot for a short project. Could we replace it with an NDA for your confidential information? I'm not sure a whole-industry restriction is enforceable here anyway."

What it is: A clause defining when payment is due and what happens if it's late — and, critically in bad contracts, whether you're allowed to stop working when you haven't been paid.

Why it's dangerous: If the contract is silent on late payment, "net 30" can drift into "net 90," and you have no leverage and no interest accruing in your favor. Worse, some contracts explicitly waive your right to stop work for non-payment, forcing you to keep delivering for a client who owes you — the worst of both worlds.

"Invoices are due within thirty (30) days of issuance. Client shall have ten (10) days to dispute an invoice. Freelancer waives any right to suspend services or withhold deliverables due to Client's failure to pay."

What to push back on: You want a clear due date, interest or a late fee that kicks in automatically, and the right to pause work (and withhold deliverables) until overdue invoices are settled. Most fair clients have zero problem with this — it protects them from bad billing as much as you from bad payers: "Can we add a late fee after the due date and a right for me to pause work until overdue invoices are paid? I just can't keep the project moving while a balance is outstanding."