Most bad freelance contracts do not look obviously evil. They look "standard" until a project drags, a client cancels halfway through, or ownership transfers before you've been paid. This checklist shows the clauses most likely to cost freelancers money, leverage, or sleep.
See ContractGhost demo Join the waitlistIf the contract is vague about what the client gets, strict about what you owe, and weak about when you get paid, you are probably carrying too much risk.
Watch for phrases like "reasonable revisions", "as needed", or deliverables described so loosely that the client can keep expanding the work.
Why it matters: a fixed-fee project turns into endless unpaid rounds.
Safer pushback: define exact deliverables, number of revision rounds, and hourly pricing for out-of-scope work.
Many contracts quietly say all work product becomes the client's property immediately upon creation, not on payment.
Why it matters: if the client stalls payment, they may still claim ownership of your work.
Safer pushback: ownership transfers only after all invoices are paid in full.
No deposit, vague milestone triggers, long payment windows, or missing late-fee language are all danger signs.
Why it matters: you end up financing the project while the client controls delivery acceptance.
Safer pushback: ask for a deposit, milestone-based invoicing, and clear overdue penalties or pause rights.
If the client can terminate anytime for convenience but the contract says little about what happens to your fees, you're exposed.
Why it matters: a project can be cancelled after you've reserved time or done substantial work.
Safer pushback: require payment for work completed, committed time, and any non-refundable deposit.
Some contracts ask freelancers to indemnify the client for nearly everything, even issues outside the freelancer's control.
Why it matters: this can create outsized legal and financial exposure relative to a small project fee.
Safer pushback: narrow indemnity to breaches you directly caused and cap liability where possible.
A contract may cap the client's liability while leaving yours unlimited, or carve your obligations out of the cap entirely.
Why it matters: the downside becomes asymmetric fast.
Safer pushback: use mutual caps tied to fees paid under the agreement.
Retainers and recurring agreements can quietly renew unless notice is given in a tight window.
Why it matters: you can get locked into a relationship or termination process you didn't expect.
Safer pushback: add clear renewal dates, reminder timing, and a simple termination path.
These often appear broader than they need to be, especially in consulting and strategy work.
Why it matters: one client can quietly limit your ability to earn elsewhere.
Safer pushback: narrow the clause by geography, duration, and direct competitor definition — or remove it.
If payment depends on subjective approval, the client may be able to stall indefinitely by saying work is not yet satisfactory.
Why it matters: the review cycle becomes leverage against your invoice.
Safer pushback: define objective acceptance criteria and automatic approval after a set review period.
ContractGhost is best used as a first-pass screening layer, not a replacement for qualified legal advice.
ContractGhost is being built to rank these risks for you, explain the real-world downside in plain English, and suggest negotiation-ready rewrite language.
Try the sample analysis Send your biggest riskAlso see: how ContractGhost works, scope creep checklist, late payment red flags, IP transfer before payment.