A contract is not there to win a court case. It is there so that both of you know what was agreed before anybody is annoyed. Here are the clauses that actually do work, and the ones that only sound impressive.
Seven things: who the parties are, exactly what you will deliver, exactly what you will not, when, for how much, when you get paid, and what happens if either side wants to stop.
Everything else is refinement. If those seven are clear and written down, most of the arguments that end freelance relationships never start.
A short contract that both people have read beats a long one that neither has. This is not a compromise — it is the point. A document nobody understood is not protection, it is decoration.
Almost nobody ends up in court. The contract does its work long before that.
Its real job is to make you both say what you mean, at the beginning, while everybody is still pleased with each other. Most disputes are not caused by bad faith. They are caused by two people who agreed on a summary and assumed the same detail underneath it — and who each kept a slightly different version in their head for six weeks.
Writing it down forces the detail into the open. Half the time, drafting the scope reveals that you and the client were describing different jobs. Finding that out on day one costs an email. Finding it out in week six costs the relationship.
The second job is to be the thing you point at, calmly, when something goes sideways. Not as a threat — as a shared reference. "Let's check what we agreed" is a very different conversation from "that's not what I remember".
Scope, in specifics. Not "design a website" but the number of pages, the number of concepts, what you are given and by when, what technology, what happens with content. Vague scope is the single biggest cause of freelance losses.
What is not included. As valuable as the scope itself. Name the things a reasonable client might assume were part of it and are not: hosting, copywriting, ongoing support, training, source files, printing.
Revisions, with a number. Two rounds included, further rounds charged at a stated rate. Without a number, "a few small changes" is infinite, and every freelancer who has skipped this has the same story.
Timeline, with dependencies. Your dates should be conditional on theirs. If they owe you content or approval by a date and it arrives two weeks late, your deadline moves by two weeks — automatically, because you wrote it that way.
Payment: amount, schedule, and terms. A deposit before starting is normal and reasonable. Staged payments on longer work protect both sides. State how many days after invoice, and state that late payment carries interest, whether or not you ever charge it.
Ownership, and when it transfers. Say clearly what the client owns at the end, and that it transfers on final payment rather than on delivery. Say what you keep — your tools, your methods, and usually the right to show the work in your portfolio.
Termination. Either side may stop, with notice. Work completed to that point is paid for. This clause feels pessimistic to write and is the one that stops a bad engagement becoming a bad month.
Variations. Extra work is agreed in writing, with a price, before it starts. One sentence, and it prevents most of what goes wrong.
Long definitions sections that define ordinary words. Paragraphs of "notwithstanding the foregoing" that turn out to say nothing enforceable. Penalty clauses so aggressive that no court would apply them, which means they do nothing except make the client uneasy about signing.
Blanket unlimited liability, in either direction. Sensible contracts cap liability at something proportionate — commonly the value of the contract.
And a non-compete on a small freelance job. Largely unenforceable in many places, actively off-putting, and pointless.
The test for any clause: could you explain, in one sentence, what happens when it is triggered? If not, it is not protecting you. It is just weight.
A 600-square-metre fit-out. Everything is agreed verbally, the relationship is good, and the client keeps asking for small additions. Each one is minor. Each one is agreed with "don't worry, we'll sort it out at the end."
At the end, the client declines to sign for the extra work. There is nothing showing what was requested, when, or at what price — only two sincere and incompatible memories. The extras are absorbed, and the job's entire profit goes with them.
One sentence would have prevented it: extra work is priced and agreed in writing before it starts. Not because the client was dishonest, but because nobody had written down what "sort it out" meant.
Do I need a lawyer?
For routine work at ordinary values, a solid template you understand is usually proportionate. For anything where a failure would seriously hurt you — large sums, valuable intellectual property, regulated work — have it reviewed. This guide is not legal advice, and contract law differs by country.
Is email enough?
An email exchange where both sides clearly agree terms is a contract in most jurisdictions. It is just harder to find and read six months later than one document.
What if the client sends their own contract?
Read it, and negotiate the parts that are wrong. Unlimited revisions, unlimited liability, payment on undefined milestones and ownership of everything you have ever made are all common and all negotiable.
Should I sign electronically?
Yes — electronic signatures are valid nearly everywhere for this kind of agreement, and the friction of printing and scanning is the reason half of freelance contracts never get signed at all.
The KISS Freelance Contract is a Word template covering the seven essentials and the clauses that actually do work — scope, exclusions, revision limits, dependencies, payment, ownership, termination and variations — in language you can read once and understand. No impressive paragraphs that cover nothing. Ten euro, one file.
See the templates →