Freelance Contract Red Flags: 11 Clauses That Cost You Money
The payment triggers, IP timing, revision traps and uncapped indemnities that turn a friendly client contract into an expensive one - and how to fix each.
The payment triggers, IP timing, revision traps and uncapped indemnities that turn a friendly client contract into an expensive one - and how to fix each.
Freelance contracts that cause problems are rarely predatory. They are short, friendly, and silent on the things that decide whether you get paid. Silence is the real red flag; these eleven are the specific ways it shows up.
The worst one, and a one-sentence fix. If ownership passes when you hand the files over, a client who stops paying already owns the work and you are left suing for a debt.
All intellectual property rights in the Deliverables shall transfer to the Client upon receipt by the Contractor of payment in full.
If payment depends on the client accepting the work and nothing defines acceptance or limits how long they have, you have handed them an indefinite option not to pay.
Deliverables shall be deemed accepted unless the Client provides written notice of specific non-conformance within ten (10) business days of delivery.
"Until the Client is satisfied" is a scope with no floor. Two rounds included, further rounds at an hourly rate, is the standard and it is what makes a fixed price possible.
Without both, net-60 becomes net-120 and there is nothing you can do about it. Ask for statutory or contractual interest, and for the right to suspend work on written notice after a stated number of days overdue.
This is the clause with the largest tail. An indemnity requires you to cover the client's losses — often including their legal costs — with no limit, against a project fee that might be a few thousand.
Ask for it to be mutual and capped at fees paid, with the usual carve-outs.
Separate from the indemnity. A cap at the greater of fees paid or a stated sum is normal. Without one, a project worth $4,000 carries unlimited exposure. More on caps.
The client can walk away mid-project. That is often acceptable — but not without paying for work already done.
On termination for convenience, the Client shall pay for all work performed up to the date of termination and for any non-cancellable commitments made.
If you assign "all intellectual property created in connection with the Services" and you used your own component library, you may have just assigned it. Every freelance contract should carve out background IP and license it instead. The difference.
If the assignment is total and confidentiality is broad, you cannot show the work. Ask for a right to display it publicly after launch, or after a stated period.
Occasionally hidden in a services agreement: a promise not to work for competing clients. For a freelancer, that can remove most of your addressable market. If they want exclusivity, it should be paid for.
A clause requiring disputes to be heard in a distant forum makes a small claim uneconomic to pursue. For contracts under a modest value this effectively removes your remedy.
If you only have time to change three things, change these:
Those three cover most of the financial risk in most freelance agreements, and all three are routinely accepted because they are objectively reasonable.
Do not return a marked-up document with forty changes. Send three sentences:
The contract looks good. Three small things before I sign: could IP transfer on payment in full rather than on delivery, could we add a 10-working-day deemed acceptance so the project can close cleanly, and could the liability clause be mutual and capped at the fees? Happy to start Monday once those are in.
A defined scope with a revision limit, a payment schedule with dates rather than events, late payment interest, IP transferring on final payment, a liability cap at or near the contract value, and payment for work done if the client terminates early.
Whoever the contract says — which is usually the client from delivery unless you change it. Tying the IP transfer to receipt of payment in full is the single most valuable edit in most freelance agreements.
It is common in client-drafted paper and it is not something to accept without thought. One claim under an uncapped indemnity can exceed everything you earned from that client. Ask for mutual and capped at fees paid.
Where you can, do — the drafter sets the defaults. Where you cannot, do not try to rewrite their paper. Fix the three or four terms carrying real financial exposure and leave the rest.
A clause saying deliverables count as accepted if the client does not raise specific problems within a set window. Without it, "payment on acceptance" gives the client an indefinite reason not to pay.
Upload it and see which of these clauses are actually in your document, quoted with the line number, compared against market standard, with replacement wording for each problem. It costs $49, needs no account, and is refunded if it finds nothing you can act on. There is a complete sample report published in full if you want to see the depth first.
Scan my freelance contractThis report is automated contract analysis, not legal advice, and no attorney-client relationship is created by using it. Have a qualified lawyer in the relevant jurisdiction review anything you are about to sign. How this guide was researched.
Spotted an error? Tell us and we will correct it.
Assignment transfers ownership permanently; a license grants permission. Where the line sits in employment, freelance and brand contracts - and why it matters.
How liability caps are usually set, which claims are carved out and become uncapped, and why the carve-out list matters more than the number itself.
When a one-way NDA is appropriate, when asking for mutual is reasonable, and the six clauses that behave differently depending on which you sign.