9 Freelance Contract Red Flags You Should Never Sign

A client contract almost always arrives written by the client, for the client. That does not make it malicious — most are copy-pasted templates nobody on either side fully read. But the cost lands on you: the freelancer who signs it. The good news is that the dangerous clauses repeat. Once you can recognize them, you can push back on the two or three that actually matter and let the rest go.

Here are the nine red flags that show up most often, what each one really means in practice, and the reasonable alternative you can ask for without sounding difficult.

1. Open-ended or unlimited liability

Look for the phrase "including but not limited to" attached to indemnity or liability. It means your financial exposure has no ceiling — a dispute over a $2,000 project could, in theory, follow you for far more. Ask for a liability cap tied to the total fees paid under the agreement, and make it mutual.

2. Overbroad IP assignment

Many contracts assign the client "all work created in connection with" the project. Read literally, that can sweep up your reusable templates, frameworks, internal tools, and pre-existing code or design systems. Ask for a carve-out: the client owns the specific deliverables; you keep your pre-existing and reusable IP.

3. Payment tied to vague "satisfaction"

If a milestone is payable only when the client is "satisfied," there is no objective finish line — they can withhold payment indefinitely. Replace it with written acceptance criteria and a fixed review window (for example, deemed accepted if no written objection within 5 business days).

4. Net-60 or Net-90 payment terms

Long payment windows quietly turn you into the client's lender. Net-60 means you may wait two months after delivery to get paid. Ask for a deposit up front, shorter terms (Net-15 or Net-30), and a simple late-fee provision.

5. Termination for convenience with no kill fee

This lets the client cancel any time and only pay for work they formally accepted — so your in-progress work goes unpaid. Ask for payment for completed and in-progress work plus a modest fee on the remaining scope if they cancel without cause.

6. Non-competes defined by category

A non-compete that blocks you from working with "similar companies" can cut off an entire slice of your pipeline. Narrow it to a short term and a named list of direct competitors only — and push back on anything broader.

7. No scope-change (change-order) process

Without a change-order clause, feature creep erases your margin while the contract still expects delivery on the original budget. Add a clause that says any change to scope is handled in writing with an adjusted fee and timeline.

8. One-sided indemnification

If you must indemnify the client but they owe you nothing in return, you are carrying all of the legal risk for a shared project. Ask to make indemnities mutual and to exclude claims arising from the client's own materials, instructions, or chosen vendors.

9. Auto-renewal and exclusivity buried in the fine print

Retainers sometimes auto-renew or quietly demand exclusivity. Make sure renewal requires affirmative agreement, and that any exclusivity is scoped, time-limited, and — if it blocks other income — paid for.

How to actually respond

You do not need to fight every line. Pick the two or three clauses with the most financial impact, propose specific alternative wording, and frame it as making the deal work for both sides. That calm, concrete approach gets far better results than a vague "I'm not comfortable with this."

If you want a faster path, fynPrint reads the whole contract, flags exactly these red flags with a risk score, and drafts a professional negotiation email you can send — so you spend your energy on the deal, not on decoding legalese.