Freelancer Contracts: 7 Clauses Every Agreement Needs Before You Start Work
Most freelance disasters do not start with bad work. They start with no contract. A client who "just needs it quickly" and promises to pay when it is done, a scope that quietly doubles, an invoice that sits unpaid for two months — none of these are surprises. They are what happens when the agreement lives in a chat thread instead of on paper.
A freelance contract does not need a lawyer to write it, and it does not need to be long. It needs seven clauses. With these seven in place before you start, almost every common freelance problem becomes a clause you can point to instead of an argument you have to win.
1. Exactly what you are delivering
The contract has to name the deliverable in concrete terms: what it is, how many of them there are, and in what format. "A spreadsheet" is not a deliverable. "A 5-sheet budget workbook (monthly budget, paycheck planner, debt payoff, savings goals, tax set-aside) delivered as an .xlsx file" is a deliverable.
Vague scope is how a $2,500 project becomes a $2,500 project plus three extra reports, two extra dashboards, and a training session. If it is not named in the contract, it is not included in the price — and the contract should say exactly that.
2. The price, the deposit, and when the rest is due
Money terms need three numbers: the total fee, the deposit, and the payment schedule. A common shape is 50% up front and 50% on delivery. In the sample, a $2,500 project means $1,250 before work starts and $1,250 when the work is delivered.
The deposit is not a nice-to-have. It is the filter that separates real clients from people collecting free ideas, and it is the money that pays you if the project dies halfway through. A client who will not pay a deposit is telling you, before you have done any work, how the rest of the project will go.
3. Payment terms and a late fee
"Payment due on delivery" means nothing without a deadline and a consequence. Put a number on it: payment due within 14 days of invoice, and a late fee after that — 1.5% per month on the unpaid balance in the sample. The late fee is rarely about the money itself. It is about the invoice no longer being the easiest thing to ignore.
A 30-day cap helps too: if the invoice is still unpaid 30 days after delivery, work pauses and the remaining deliverables stop until the account is current. Clients who pay late once will pay late twice unless the contract makes lateness cost something.
4. How many revisions are included
Unlimited revisions is how a three-day project becomes a three-week project. The contract should state a number — two rounds of revisions in the sample — and a price for anything beyond it.
A revision round also needs a definition: one consolidated list of changes from the client, not a drip-feed of new comments every day for a month. When the client knows the second round is the last free one, the feedback gets specific fast.
5. Who owns the work, and when
Ownership should transfer when payment clears — not when the file is delivered. That one sentence protects you in the most common freelancer nightmare: the client who has your work, is using your work, and has not paid for your work.
Until the final payment lands, the work is licensed for review, not owned. The contract should also say what you keep: the right to show the work in your portfolio, and the right to reuse your own templates, tools, and methods on other projects. The client owns their deliverable; they do not own your toolkit.
6. A kill fee for cancelled projects
Projects get cancelled. Budgets get cut, priorities change, the client's boss changes their mind. Without a kill fee, a cancellation at 80% complete pays you 0% — because you never delivered, and the contract only promised payment on delivery.
A sample kill fee is 50% of the remaining fee if the client cancels after work has started, on top of the deposit already paid. It does not make cancellations pleasant. It makes them survivable, and it makes the client think twice before cancelling over something small.
7. What happens when something goes wrong
The last clause is the least exciting and the most valuable: a short line on disputes. How much notice either side gives to end the agreement (14 days in the sample), which country's law applies, and a first step before anything formal — a written attempt to resolve it directly within 14 days.
Almost no freelance dispute ever reaches a courtroom. But the clause does its work long before that: it tells both sides, on day one, that the agreement has a way out and a way to end cleanly. That alone keeps most disagreements small.
The quick setup
Before the next project starts, write these seven down in one page: the exact deliverable, the total fee with a 50% deposit ($1,250 on a $2,500 sample project), payment within 14 days with a 1.5% monthly late fee, two included revision rounds, ownership transferring when payment clears, a 50% kill fee if the client cancels, and a 14-day notice and direct-resolution step for disputes. Get it agreed in writing — an email the client replies "agreed" to is enough to start. Then track it the same way you track everything else: one line per client with the fee, the deposit status, the invoice dates, and the payment terms, so no agreement ever lives only in your memory.
You don't need new software for this. A client tracker for the agreement terms and the money owed, an invoice tracker for the dates and the late fees, and a budget planner for what the deposit and the final payment actually mean for the month. The contract protects the work; the tracking is what makes the contract real.
Alex Lin — fishdp@proton.me. I build small tools and spreadsheet templates that save you time: https://payhip.com/AlexLin
- Freelancer Client Tracker ($10): https://payhip.com/b/coiFO
- Freelancer Invoice Tracker ($10): https://payhip.com/b/VkExQ
- Freelancer Budget Planner ($14): https://payhip.com/b/Es7B5
Top comments (0)