Freelance contract basics: what every agreement needs
Plenty of freelancers work on a handshake until the one project that goes wrong teaches them why contracts exist. It is rarely dramatic. Usually it is a client who remembers the scope differently, a project that stalls for four months with your work sitting on their server, or an invoice that goes unanswered while you discover you have nothing in writing about what happens next.
A written agreement is not about distrust. It is about both sides knowing the rules before anyone is emotionally or financially invested. You do not need a lawyer on retainer for everyday projects; you need a clear, plain-English document covering a handful of essentials. Here is what belongs in it and why each part earns its place.
Scope and deliverables
The single biggest source of freelance pain is scope creep, and the cure is writing scope down before it can drift.
List exactly what you will deliver — format, quantity, and how many rounds of revisions are included. Then list what is not included. That second list feels unnecessary while you are writing it and becomes the most valuable paragraph in the document the moment someone asks for "just one more thing". Anything outside the list becomes a paid change rather than a favour you resent doing at 11pm.
Be specific enough that a stranger could tell whether you had finished. "Website redesign" fails that test. "Five pages — home, about, services, blog index, contact — with two rounds of revisions per page" passes it.
Fees, deposit, and payment terms
State the total fee or rate, when it is due, and what a deposit secures.
Taking a deposit before work begins is standard and sensible: it filters out non-serious clients and protects you if a project stalls. 50% from a new client and 30% from a returning one with a track record is the common split. For anything longer than a couple of weeks, break the fee into milestones so a payment problem surfaces after one stage rather than after the whole project.
Add a clear payment window ("invoices due within 14 days") and a late-payment clause, so chasing money is a policy rather than an awkward conversation you have to invent under pressure. And if a client still goes quiet on you despite all of that, here's exactly what to do next.
Intellectual property
Decide who owns the work and when.
The cleanest arrangement for freelancers: the client receives full ownership of the final deliverables once payment is received in full — not before. That single condition quietly does more to secure payment than any late fee, because the rights the client actually needs only transfer when the invoice clears.
Two details worth adding. First, carve out anything you reuse across clients — your own templates, components or code libraries — so you are not accidentally selling your toolkit. Second, secure the right to show the work in your portfolio, with an exception the client can invoke if the project is genuinely confidential.
Cancellation and kill fees
Projects end early sometimes, and almost never at a convenient moment.
Spell out what happens: how much notice each side gives, that completed work is paid for at the point of cancellation, and that the deposit is non-refundable once work has begun. A short cancellation clause turns a stressful breakup into a pre-agreed process, which is worth far more than the money it protects.
Worth including too: what happens if the client causes the delay. A project that sits idle for three months because they never sent the assets has real cost to you — a clause stating that work paused beyond a set period may be re-quoted or re-scheduled prevents you being held to a price you set a season ago.
The boring clauses that matter
A few standard lines prevent outsized problems:
Confidentiality — a short mutual line is usually enough, and it reassures larger clients.
Independent contractor status — states you are not an employee and are responsible for your own taxes. In several countries this matters for classification rules on both sides.
Liability cap — limits your exposure to the fees paid under the agreement. Without it, a small project can theoretically carry unlimited risk.
Governing law — which country's law applies and where disputes are heard. Rarely used, painful to be without.
None of it is glamorous. All of it matters on the day something goes sideways.
How formal does it need to be?
Less formal than most people assume. A clear document both sides have agreed to in writing — including by email — is a contract in most jurisdictions. It does not need archaic language, and archaic language it does not need is often archaic language nobody reads.
What matters is that the terms are unambiguous and that you can show agreement. An emailed PDF with "confirmed, happy to proceed" in reply is a real paper trail. A verbal yes on a call is not.
Where to be careful: high-value contracts, anything involving personal data, exclusive licensing, or work in a regulated industry. Those are worth a local lawyer's time, because the cost of getting them wrong scales with the project.
Frequently asked questions
Do freelancers really need a contract for small projects? Yes, though it can be short. The cost of a one-page written agreement is fifteen minutes; the cost of not having one is a disputed scope or an unpaid invoice with nothing to point at. Scale the length to the project, but never skip it entirely.
What should a freelance contract include? Scope and deliverables with an explicit "not included" list, the fee and deposit, payment terms with a due date and late-payment clause, intellectual property transferring on full payment, a cancellation clause, and the standard protections — confidentiality, contractor status, a liability cap and governing law.
Is an email agreement legally binding? In most jurisdictions a clear written agreement accepted in writing is binding, and an emailed PDF confirmed by reply usually qualifies. What matters is that the terms are unambiguous and that acceptance is documented. A verbal yes on a call is far weaker.
Should a freelancer take a deposit? Yes. 50% upfront from a new client and 30% from a returning one is standard practice rather than a sign of distrust. It filters out non-serious clients, covers you if the project stalls, and a client's reaction to a completely normal request often tells you how the rest of the project will go.