FairClause › Guides

Contract Red Flags Freelancers Shouldn't Sign

You do not need to read a contract like a lawyer. You need to recognise about seven patterns — these are the red flags in a contract that actually cost freelancers money.

Non compete clause

A non compete clause stops you working for competitors, sometimes for a period after the project ends. In a freelance agreement it is usually far wider than the work justifies — a three-month website build should not cost you a whole sector for a year.

Ask for instead: narrow it to genuinely competing products, cap it at six months, and limit it to the specific client account you worked on. Or ask to swap it for a non-solicit, which protects their staff and clients without touching your ability to earn.

Work for hire clause

A work for hire clause assigns ownership of everything you produce to the client, often including drafts, working files and anything "conceived during the engagement". The last part is the problem — read literally it can reach work you did on your own time.

Ask for instead: assignment limited to the deliverables actually paid for, transferring on final payment. Keep a licence to show the work in your portfolio; almost every client agrees to that when asked.

Pay-when-paid

Your invoice only becomes due once the client's own customer has paid them. You have taken on a credit risk in a relationship you cannot see, influence or chase.

Ask for instead: payment due a fixed number of days from invoice, independent of any third party. This is the one to hold firm on.

Unlimited revisions

No cap and no definition of "satisfactory" means the project ends when the client says so. Fixed fee plus unlimited revisions is how a profitable month becomes a loss.

Ask for instead: a stated number of rounds, with further rounds billed hourly. Two is normal and rarely argued with.

Indemnity clause

An indemnity clause makes you cover the client's losses and legal costs if something goes wrong. Uncapped and mutual-in-name-only, it is the clause with the largest downside on the page — potentially far beyond the project fee.

Ask for instead: cap total liability at the fees paid under the agreement, and limit the indemnity to claims arising from your own work rather than anything connected to the project.

Unilateral termination

They can end the agreement at any time for any reason; you cannot, or you owe something if you do. Fine in isolation, expensive when it sits next to a milestone payment schedule you have already worked past.

Ask for instead: equal notice on both sides, and payment for work completed and accepted up to the termination date.

Vague scope

Not a clause so much as an absence of one. If the deliverables are described in a sentence, every disagreement later is a matter of interpretation, and the party with the lawyer wins interpretations.

Ask for instead: a numbered deliverables list, an explicit out-of-scope list, and a named process for handling change requests.

How to check your own

Reading for seven patterns is easy to describe and tedious to do at eleven at night on the contract you want to sign tomorrow.

Next: how to negotiate a freelance contract — what to actually say once you have found these.

FairClause is automated pattern analysis and drafting help, not a law firm and not legal advice. Jurisdictions differ, and a clause that is unenforceable in one is routine in another. For anything binding, talk to a licensed lawyer where you are.