Freelancer Contracts: 7 Clauses That Save You From Bad Clients

Most freelancer disputes — late payments, scope creep, "we are not going to pay because we did not like the result" — trace back to a contract that did not anticipate the failure mode. The good news: seven clauses cover 95% of those cases.

Below is what each clause does, in plain English. None of this is legal advice; if you bill over $50k/year, get a one-time review from a lawyer.

1. Deposit clause

"Client shall pay 50% of project total upon contract execution, with the balance due upon delivery."

Why: Removes the worst-case outcome (you finish, they ghost, you have nothing). Deposit also signals commitment — clients who refuse to deposit at this stage are showing you who they will be at invoice time.

Standard rates: 50% on smaller projects, 30% on larger ones. For ongoing retainer work, the first month upfront.

2. Payment terms clause

"Invoices are due net 14 days from issue date. Payment may be made via [methods]."

Why: Without an explicit term, the legal default is "reasonable time" — meaningless. Specify the term, specify the methods. See how to choose payment terms.

3. Late fee clause

"Invoices outstanding more than 14 days past due will accrue a late fee of 1.5% per month."

Why: Without this written in the contract, your late fee on the invoice is not enforceable. With it, you have real leverage at day 30. See how to charge late fees legally.

4. Scope clause

"The scope of work is defined in the attached SOW. Changes to scope require a written change order and may incur additional fees."

Why: Scope creep is the silent killer of freelance profitability. This clause is the polite-but-firm way to say "I am happy to do more, but it will cost more, in writing."

5. Kill fee / cancellation clause

"If the client cancels the project after work has begun, a kill fee of [50% / hours billed to date] will apply."

Why: Without this, "we decided to pause indefinitely" two weeks into a six-week project leaves you with zero compensation for time already spent. The kill fee can be a flat percentage or hours-billed-to-date — the latter is more defensible for hourly work.

6. Intellectual property clause

"Intellectual property rights transfer to the client upon full payment of all invoices."

Why: The "upon full payment" qualifier is critical. If you transfer IP on delivery and the invoice never gets paid, the client owns your work and you have no leverage. Tie the transfer to payment.

7. Jurisdiction and dispute resolution

"This agreement is governed by the laws of [your state/country]. Disputes shall be resolved in [your county/court]."

Why: If a client in California stops paying and your contract says "California courts," you fly to California to sue them. If it says "your state," they fly to you. This clause alone discourages 90% of bad-faith disputes — the costs of escalation move against the client.

What about NDAs, indemnification, limitation of liability?

For higher-stakes work (over $10k/project, or involving sensitive data), add:

• Mutual NDA if the client is sharing real business intel.
• Limitation of liability capped at fees paid (so a $5k project does not expose you to a $5M lawsuit).
• Force majeure if your work involves physical delivery or coordination.

For most freelance contracts under $10k, the seven clauses above are enough.

Where to put them — one document, not two

Keep the contract and SOW (statement of work) as a single PDF, not two separate files. AP teams sometimes "lose" the contract while keeping the SOW. One document, one signature, one canonical source of truth.

And then — make the invoice match

The contract is only useful if your invoice reflects it. Every invoice should restate the payment term and late-fee clause in a "Terms" line. Duefy adds both to every invoice by default, so the contract and the bill always tell the same story.