Client contracts and statements of work — the clauses that actually matter

Every freelancer eventually gets burned by a bad contract — a scope that ballooned, an invoice they couldn't chase because payment terms weren't defined, IP the client claimed after the fact. The solution isn't a longer document. It's a shorter one that covers the five or six things that actually go wrong.

Here's how to think about the paperwork.

Two documents, one relationship

Most professional freelance engagements have two layers:

1. The Master Services Agreement (MSA) — the general legal terms that apply to any work you do for this client. Signed once. Rarely changed.
2. The Statement of Work (SOW) — the specific description of what you're doing on this engagement, when, and for how much. Signed per project.

The MSA covers "how we work together." The SOW covers "what we're actually building." A new SOW inherits the MSA. This separation lets you start new projects fast without renegotiating fundamentals every time.

If you're only ever going to do one project for a client, you can combine both into a single "Services Agreement." Once you're doing repeat work, split them.

The clauses that actually matter

Some contract terms exist to fill pages. Others determine whether you get paid, keep your IP, and can walk away when you need to. The ones that matter:

Scope

Vague scope is where projects die. A good SOW answers:

• What deliverables — enumerated, specific, unambiguous. "Homepage design and responsive HTML/CSS for one desktop and one mobile layout" — not "a website."
• What's explicitly out of scope — "does not include copywriting, hosting, or ongoing maintenance." This section prevents 80% of scope disputes.
• How change requests work — "changes to scope require a written change order signed by both parties" and a stated hourly rate for the additional work.
• What "done" means — acceptance criteria and a review process.

Payment

• Total fee or rate, clearly stated.
• Payment schedule — deposit, milestones, on delivery, or otherwise. Never "on project completion" for anything over a few weeks — you're funding their business otherwise.
• Payment terms — how many days after invoice date.
• Late payment interest — a stated rate (statutory in most of Europe, e.g., 8% + ECB base under EU Directive 2011/7/EU).
• Currency and payment method.
• Kill fee — some fraction of the total payable if the client cancels part-way. 25% is common; higher for tightly-scheduled work.

Intellectual property

The single most common freelance disaster is delivering work and finding out later the IP terms weren't what you thought. Options:

• Work-for-hire / full assignment on payment — the client owns the deliverables the moment they pay in full. Most enterprise clients require this. Fine, provided it's scoped to the deliverables, not your general tools/methods/pre-existing work.
• Licence — you retain ownership; they get a broad licence to use. Better for designers, writers, and creators building a portfolio and a body of reusable work.
• Reserved elements — always keep ownership of your background IP (things you brought to the project) and general tools, methods, and know-how (your professional toolkit). Cede only the specific deliverables.

Explicit portfolio rights — the right to publicly show the work as part of your portfolio — matter more than freelancers realise. Get it in writing.

Confidentiality

Standard mutual NDA is fine. Watch for:

• Overly broad definitions of "confidential information." "Everything either party discloses" is silly; a definition tied to what's marked confidential or would obviously be so is reasonable.
• Survival period — how long after the engagement ends. 2–5 years for ordinary commercial info; indefinite is reasonable only for genuine trade secrets.
• Return / destruction of materials — reasonable, but carve out an exception for your own working files and portfolio samples.

Liability

Almost every client draft caps liability in the client's favour and leaves yours uncapped. Fix this:

• Cap your liability at the fees paid under the engagement (or a modest multiple).
• Exclude consequential and indirect damages on both sides.
• Carry professional indemnity insurance appropriate to the type of work.

If a client refuses to cap your liability, and the work is anything more complex than a one-off deliverable, walk away or price the risk in.

Termination

• Either party can terminate for convenience with X days' notice (14–30 typical). Prevents you being trapped in a bad engagement.
• Termination for cause — immediate, defined causes (breach, insolvency).
• What happens on termination — you're paid for work performed to date. Any advance payments not yet earned are refunded (or not, depending on which side is walking away and why).

Independent contractor status

• Explicit statement that you are an independent contractor, not an employee.
• No exclusivity — you can work for other clients.
• You control how the work is performed.
• Client isn't responsible for your taxes, benefits, or insurance.

In several countries this clause is more than paperwork — it protects against mischaracterisation as an employee (IR35 in the UK, misclassification cases in Germany, Spain, France, and the US). If your engagement looks like employment, no clause will save you, but the clause is table stakes.

Governing law and dispute resolution

• Governing law and jurisdiction — try to make it yours. Realistically it'll be the client's for anything big. Accept it in the client's country only if there's an EU-wide or reciprocal enforcement framework (recast Brussels I within the EU is fine; US jurisdiction against a European freelancer is genuinely painful to defend).
• Dispute resolution — direct negotiation first, then mediation, then arbitration or courts. Arbitration is cheaper for cross-border disputes but the cost isn't zero.

The boilerplate you can accept without negotiating

Save your negotiation capital for the clauses above. These can usually be signed as-is:

• Notice provisions (how you send formal notices)
• Assignment (each party's ability to assign — usually restricted, fine)
• Severability (if one clause is invalid, others still apply)
• Entire agreement (this document is the whole deal)
• Amendments (must be in writing and signed)
• Counterparts (multiple signed copies OK)
• Force majeure (with a modernised list — include pandemics)

The one habit that changes everything

Never start work without a signed SOW. Ever. Not "I'll send the paperwork next week." Not "we're old friends." Not "the client is really big and moves slowly."

The projects that go bad are the ones where you started before the paperwork existed — because when the disagreement happens, you have nothing to point to but hopeful memory.

A short, clear SOW takes half a day to write. A dispute over an unwritten scope takes weeks or months. The maths is not close.