Contract Red Flags
Most problematic contract clauses don't look dangerous at first glance. They're written in standard legal language and buried in long documents. Here are the ones that cost freelancers the most.
March 2026
Many contracts include a clause that says something like: "All work product created under this agreement shall be the sole property of Client upon delivery."
The problem: delivery happens before payment. Once the client owns the work, they have little incentive to pay you — and if they don't, your legal options are limited because they technically own the work.
What to ask for instead: IP transfers upon receipt of final payment, not upon delivery. This keeps the leverage where it belongs until you're paid.
Payment conditions that require client approval before payment is released create an easy path for clients to delay or avoid payment forever. Language like "payment due upon client's written acceptance" or "final payment contingent on client approval of deliverables" can mean you never get paid if the client simply refuses to approve.
What to ask for instead: Payment triggered by delivery or a defined timeframe (e.g., "net-30 from invoice date"), with a clear process for handling disputes about quality — not a unilateral approval right.
If a client can cancel a project at any time with no financial obligation, you bear all the risk. You might spend weeks on a project, turn down other work, and end up with nothing if the client decides to pull the plug.
A kill fee protects you by guaranteeing partial payment for work already completed if the client cancels. The absence of a kill fee in a project of any significant size is a red flag.
Standard kill fee: 25–50% of the remaining project value, or payment for all work completed to date at your hourly rate.
You wouldn't sign a contract that says you'll deliver "as many revisions as the client requests" — but a surprising number of freelancers do, just not in those words. Watch for language like "until client is satisfied," "all changes requested by client," or revision terms with no limit or no additional compensation after a certain point.
What to ask for instead: A defined number of revision rounds (e.g., "up to 2 rounds of revisions") with additional revisions billed at your hourly rate.
Scope creep is one of the most common reasons freelancers get underpaid. If the contract doesn't clearly define what's included, clients can add work indefinitely while arguing it falls within the original agreement.
Watch for contracts with vague deliverable descriptions ("ongoing web support," "marketing assistance," "design as needed") and no explicit out-of-scope list.
What to ask for instead: Specific, numbered deliverables. Explicit exclusions. A defined process for change orders when scope expands.
Non-compete clauses that cover your entire industry, have no geographic limit, or last more than a year or two can seriously restrict your ability to earn a living after the engagement ends — especially if you're a specialist.
This is especially common in agency-to-freelancer contracts, where the agency wants to prevent you from working directly with their clients. Some restriction on this is reasonable; a blanket industry-wide non-compete for a design project is not.
What to ask for instead: A narrowly scoped non-solicitation (don't pitch clients you met through this engagement) rather than a broad non-compete, with a clear time limit.
Some contracts allow the client to terminate the agreement immediately and for any reason, while requiring the freelancer to give 30 or 60 days notice — or limiting the freelancer's ability to terminate at all. This asymmetry leaves you with no protection if a project turns toxic, while the client can exit the moment it's convenient for them.
Look for clauses that say something like "Client may terminate this agreement upon written notice" without a corresponding right for you.
What to ask for instead: Symmetric termination rights — if the client can terminate with 2 weeks notice, so can you. Or at minimum, ensure your termination rights are reasonable even if they're not identical.
All seven of these red flags share something in common: they transfer risk from the client to you, often without any corresponding compensation. A well-balanced contract allocates risk fairly — not perfectly equally, but proportionally to each party's ability to manage it.
When you spot these clauses, don't panic. Most clients expect some negotiation on contract terms. Raise specific concerns clearly, explain why the language is problematic, and propose specific alternative language. Most clients who are acting in good faith will engage with reasonable requests.
Don't read every clause manually
Upload your contract PDF to ReadThePrint and get an instant breakdown of risky clauses, a risk score, and plain-English explanations. Free to try — no account needed.
Upload a contract — it's freeRelated guides