What every freelance contract should include (and what most miss)

A contract that makes the client comfortable is not the same as a contract that protects you.

Most freelance contracts cover the basics — deliverables, price, timeline. The disputes that actually happen aren’t about any of those things. They’re about what happens when the client changes their mind, when the project stalls for three months, when they use your work before paying, or when the engagement ends before the work is done.

Those situations need specific clauses. Most standard contracts don’t have them.

Payment terms that don’t invite delay

“Net 30” is a default. It’s also an invitation to wait. Net 14 is increasingly standard for freelance work, and a 30 to 50% deposit upfront changes the dynamic before the project even starts.

The deposit matters for two reasons. First, it covers your time if the project is cancelled before completion. Second, it signals commitment — clients who resist an upfront deposit often become clients who resist the final invoice.

Add a late payment interest clause. State the rate (often the legal rate in your jurisdiction). You may never enforce it, but its presence signals that you track payment dates and that delay has a cost. Clients who see it take due dates more seriously.

Scope defined by what’s excluded, not just what’s included

Most scope definitions say what is included. The expensive disputes happen around what isn’t.

Explicitly list what the engagement does not cover: additional revision rounds beyond the agreed number, changes to brief after approval, work in adjacent areas that weren’t discussed. “Two rounds of revisions” is scope. “Unlimited revisions” is an open-ended commitment you’ll be held to.

Revision rounds are the single most common source of scope creep. Define the number, define what constitutes a revision versus a scope change, and define how out-of-scope changes are priced.

Kill fees: what happens when the client cancels

Clients cancel projects. Sometimes the brief changes and you’re no longer the right fit. Sometimes budgets disappear. Sometimes the internal project is killed.

Without a kill fee clause, a cancelled project means you’ve done work you won’t get paid for. With one, you’re compensated for time invested.

A reasonable kill fee structure: 100% of any milestone already delivered, plus a percentage of remaining work (commonly 25 to 50%) if cancelled after work has begun. The percentage isn’t punitive — it’s compensation for the opportunity cost of blocking time for a project that won’t complete.

State this clause clearly. Most clients don’t push back on it once they understand it’s standard practice.

IP transfer only upon payment

Intellectual property created during a project transfers to the client upon full payment — not upon delivery.

Without this clause, a client who hasn’t paid can still use your work. That’s the default in many jurisdictions. An explicit clause reversing this gives you meaningful leverage if a payment dispute arises. The work is yours until the invoice is paid.

This is especially relevant for design, writing, and code. A client who disputes an invoice can’t reasonably use the deliverable while the dispute is unresolved if the contract is explicit about when the transfer occurs.

The clauses clients push back on

Clients who resist basic protective terms are telling you something.

A kill fee clause is standard. A client who refuses to include one is signaling they may not honour commitments. Payment terms of net 14 are reasonable. A client who insists on net 60 is managing their own cash flow at your expense.

Pushback on contract terms is a client red flag worth taking seriously before you start. It’s much cheaper to walk away during negotiations than after three months of work.

Keep the signed contract where you can find it

The contract matters when something goes wrong — which is exactly when email threads are hardest to search.

File it by client, with date. Keep the invoice record alongside it. If a dispute escalates to formal recovery, the paper trail is your evidence. The combination of a signed contract and a timestamped billing record resolves most disputes before they become expensive.

Timescanner logs your hours by client from your calendar, creating the billing record that backs up your contract if a payment dispute arises. Works with any iCal-compatible calendar.