Freelance Contract Red Flags
Short answer: most freelance contracts that go wrong were readable from the start — the warning signs were right there in the clauses. The big red flags are vague scope, unlimited revisions, slow or conditional payment (net 60+, "paid when we get paid"), broad IP grabs, no termination or kill fee, "to our satisfaction" approval, exclusivity/non-competes, and one-sided indemnification. None of these mean you walk away — they mean you negotiate the clause before you sign. Here's what each one really costs you and the wording to ask for instead.
Before you sign anything, make sure the price itself is right. The free Freelance Rate Calculator → shows your real hourly take-home after self-employment tax and expenses, so you can tell whether a contract's number actually covers you before you start arguing about clauses.
The 8 red flags at a glance
| Red flag | Why it bites | Ask for instead |
|---|---|---|
| Vague scope ("design the website") | Everything becomes "included," and you work for free | Specific deliverables, quantities, and an out-of-scope line |
| Unlimited revisions | The project never ends; your effective rate collapses | A named number of rounds, extras billed hourly |
| Net 60 / Net 90 | You finance the client for months | Net 15–30, deposit upfront, milestone billing |
| "Paid when we get paid" | You carry the risk of their client not paying | Payment tied to your delivery, not their cash flow |
| Broad IP / work-for-hire grab | You sign away tools, templates, and portfolio rights | Transfer on full payment, you keep your reusable tools |
| No termination clause | Client can vanish mid-project with nothing owed | A kill fee and a notice-and-pay-for-work-done clause |
| "To client's satisfaction" | Approval is subjective and never final | Acceptance tied to the written spec being met |
| Exclusivity / non-compete | You can't take similar work — for free | Strike it, or get paid a retainer for exclusivity |
1. Vague scope
This is the root of most freelance disputes. "Build a website," "manage social media," "write the copy" — none of these have an end. If the deliverables aren't specific and countable, the client's idea of "done" will keep expanding and yours won't matter. Insist the contract (or an attached statement of work) lists exactly what you'll deliver, in what quantity, and — just as important — what is not included. This is also your best defense against scope creep.
2. Unlimited revisions
"Revisions until the client is happy" sounds generous; it's a trap. There is always one more tweak, and each one is unpaid. Cap revisions at a specific number of rounds (two is standard) and state that further changes are billed at your hourly rate. This protects your time and, paradoxically, gets you cleaner feedback — clients prioritize when rounds are finite.
3. Slow or conditional payment terms
Net 60 and Net 90 terms mean you've delivered the work and then financed the client for two or three months. Worse is "paid when we get paid," which makes your income hostage to their client paying them — a risk that isn't yours to carry. Push for Net 15–30 terms, a deposit upfront, and milestone billing on larger projects so you're never far out of pocket.
Is the contract's number even high enough to absorb slow payment? Use the free Freelance Rate Calculator → to check your real take-home after tax and expenses. A contract with great clauses still loses money if the rate was too low to begin with.
4. Broad IP and work-for-hire clauses
Many contracts quietly claim all intellectual property you create, sometimes including the reusable tools, templates, and code libraries you bring to every job. That's overreach. Standard practice: ownership of the final deliverable transfers to the client on full payment — not before — while you keep the underlying tools and the right to show the work in your portfolio. If a clause grabs everything, narrow it.
5. No termination or kill fee
If the contract doesn't say what happens when the project ends early, the default is bad for you: a client can cancel halfway through and owe nothing. Add a termination clause that requires notice and payment for work completed, plus a kill fee for the income you lose when a booked project disappears. Pair it with a non-refundable deposit and your downside is covered.
6. "To the client's satisfaction"
Acceptance language matters. "Work will be approved when the client is satisfied" makes sign-off purely subjective — there's no objective point at which you're finished and owed final payment. Tie acceptance to the written specification being met: once the deliverables match the agreed spec, the work is accepted and the final invoice is due, regardless of mood.
7. Exclusivity and non-competes
A clause that bars you from working with the client's competitors — or anyone in their industry — can quietly wipe out a chunk of your market for no extra pay. If exclusivity matters to the client, it's worth real money: strike the clause, or convert it into a paid retainer that compensates you for turning down that work.
8. One-sided indemnification and liability
Watch for clauses that make you liable for unlimited damages, or indemnify the client against problems outside your control. You should stand behind your own work, but your liability should be capped — a common cap is the total fees paid under the contract. If you see "unlimited liability" with no cap, ask for one.
How to push back without losing the job
You rarely need to reject a contract outright. The move is to propose a specific edit:
Happy to move forward — a couple of standard adjustments before I sign. I cap revisions at two rounds with further changes billed hourly, and I work on Net 15 terms with a [50%] deposit to start. I've marked the changes; everything else looks good. Want me to send the updated version?
Most professional clients accept these without blinking, because they're industry-standard. The ones who fight every reasonable edit are showing you how the whole project will go — which is its own useful signal. Sending a clean, fair agreement of your own is even better; a solid freelance contract template means you're the one setting the terms, and a tight proposal sets expectations before the contract stage.
Watch-outs
- Read the whole thing — red flags hide in the back, in "miscellaneous" and "general terms."
- Get every change in writing — a verbal "don't worry about that clause" is worth nothing.
- Never start work before it's signed — leverage to fix a clause evaporates once you've delivered.
- A deposit is your real protection — even a fair contract is only as good as your ability to collect; money upfront beats clauses on paper.
A contract is one piece of protecting your business — alongside getting a deposit upfront, setting clear payment terms, and a smooth client onboarding process that puts all of this in front of the client from day one.
Sign contracts off a rate that actually covers you
The best clauses in the world won't help if the price underneath them is too low. The $9 Freelance Rate & Tax Calculator spreadsheet nets your income against self-employment tax and expenses so you know the real take-home before you agree to any contract. Sending clients clean paperwork too? Get the calculator + a professional invoice template in the $14 Starter Pack →
Frequently asked questions
What are the biggest red flags in a freelance contract?
The most common are vague scope, unlimited revisions, slow or conditional payment terms (Net 60 or "paid when we get paid"), broad intellectual-property grabs, no termination or kill fee, subjective "to the client's satisfaction" approval language, exclusivity or non-compete clauses, and uncapped one-sided liability. Each one shifts risk or cost onto you, and each can be renegotiated before signing.
Should I sign a contract with unlimited revisions?
No. Unlimited revisions mean the project never truly ends and your effective hourly rate collapses with each unpaid tweak. Cap revisions at a specific number of rounds — two is standard — and state that any further changes are billed at your hourly rate. Finite rounds also produce sharper, more prioritized client feedback.
What payment terms should a freelancer accept?
Aim for Net 15 to Net 30, a deposit of 25 to 50 percent upfront, and milestone billing on larger projects so you are never far out of pocket. Avoid Net 60 or Net 90, which force you to finance the client for months, and refuse "paid when we get paid," which makes your income depend on the client's own customer paying them.
Who owns the work in a freelance contract?
Standard practice is that ownership of the final deliverable transfers to the client on full payment — not before — while you keep your reusable tools, templates, and the right to display the work in your portfolio. Watch for broad work-for-hire clauses that try to claim everything you create, including the underlying tools you bring to every job, and narrow them.
How do I negotiate a contract clause without losing the client?
Propose a specific edit rather than rejecting the contract outright. Frame your changes as standard adjustments — a revision cap, Net 15 terms, a deposit — mark them clearly, and send the updated version. Most professional clients accept industry-standard terms readily, and those who fight every reasonable change are signaling how the whole project will go.