Most freelancers learn the value of a contract the expensive way: a project that ballooned from "a quick landing page" into six weeks of unpaid revisions, or a client who vanished the day the deposit was due, or a logo that ended up on a competitor's storefront because nobody wrote down who owned the files. Every one of those problems is a missing paragraph.
A freelance contract isn't about distrust, and it isn't about lawyering the relationship to death. It's a shared memory. Six months from now, when you and the client remember the deal differently — and you will — the contract is the version that wins. This guide walks through every clause that earns its place, in plain English, with the wording you can adapt. Once the terms are agreed, the invoice generator turns them into clean, on-brand bills; but the money only flows smoothly when the agreement underneath it is solid.
Why a handshake isn't a contract (even when it feels like one)
A verbal agreement can be legally binding, but "binding" and "enforceable" are different things. If a client disputes a verbal deal, you're left arguing your memory against theirs with no evidence — and courts, mediators, and payment processors all want documents. A signed contract does four practical jobs at once:
- It defines "done" so a project can actually end.
- It sets when and how you get paid, which is the whole point of working.
- It assigns ownership of what you create.
- It gives you an exit if the relationship goes wrong.
You don't need a lawyer to draft one for most freelance work. You need the right sections, filled in honestly. Here they are.
The clauses every freelance contract needs
1. The parties and the date
Name both sides in full — your legal or business name and the client's — plus the effective date. If the client is a company, name the company, not just the person emailing you, so you know who actually owes the money.
2. Scope of work (the clause that saves your life)
This is the single most important section, and the one most freelancers write too loosely. Describe exactly what you will deliver, in countable terms.
The Freelancer will design one (1) five-page marketing website in Figma, comprising Home, About, Services, Pricing, and Contact pages, delivered as a responsive desktop and mobile design.
Notice what that does: it fixes the number of pages, the tool, and the format. "A website" is a lawsuit; "one five-page website in Figma" is a finish line. Pair the scope with an explicit out-of-scope list — copywriting, hosting, ongoing edits, extra pages — so there's a named home for every "can you just…" request. For anything beyond scope, point to your change-order process for scope creep.
3. Deliverables and timeline
List each deliverable with a due date, and — this is the part people forget — make client dependencies explicit. Most missed deadlines are actually the client sitting on feedback.
Timeline assumes client feedback within 3 business days of each delivery. Delays in feedback extend all subsequent dates by the same period.
That one sentence stops you from being blamed for a slip that wasn't yours.
4. Payment terms
Be specific enough that there is nothing to interpret:
- The total fee, and whether it's fixed, hourly, or milestone-based.
- A deposit — commonly 30–50% up front, non-refundable, before work begins. Asking for one is standard practice; here's how to ask for an upfront deposit without it feeling awkward.
- The payment schedule — e.g. 50% on signing, 50% on final delivery, or monthly for retainers.
- Payment window — Net 7 or Net 14 is healthier for freelancers than Net 30.
- Late fees — a stated percentage per month keeps invoices near the top of the pile. See how to calculate late fees.
5. Revisions
Unlimited revisions is how a profitable project becomes a loss. Cap them.
The fee includes two (2) rounds of revisions per deliverable. Additional rounds are billed at $[X]/hour.
Now "one more tweak" for the fifth time is a paid line item, not a favour.
6. Kill fee / cancellation
If the client walks away mid-project, you should still be paid for work done and time reserved. A kill fee protects the calendar you blocked for them.
If the client cancels after work has begun, the deposit is retained and the client pays for all work completed to the cancellation date, plus a cancellation fee of 25% of the remaining balance.
7. Intellectual property and ownership
This clause decides who owns what you make — and when. The freelancer-friendly default: you retain ownership until final payment clears, at which point rights transfer to the client. Until the invoice is paid, they have a licence, not the files.
Ownership of all final deliverables transfers to the Client upon receipt of full payment. Until then, the Freelancer retains all rights.
Also state what you keep: the right to show the work in your portfolio, and ownership of any pre-existing tools, templates, or code you brought to the project.
8. Independent-contractor status
One line that protects your tax and legal standing — you're a contractor, not an employee, responsible for your own taxes, and free to work with other clients. This matters more than freelancers realise, especially with worker-classification rules tightening in many regions.
9. Confidentiality
If you'll see anything sensitive, a short mutual confidentiality clause covers both sides. Keep it proportional — a full NDA is overkill for a poster design.
10. Liability limit
Cap your liability at the total fee paid. You're a freelancer, not an insurer; you shouldn't be exposed to damages many times your fee because a client's site had a bad day.
11. Termination and governing law
State how either side ends the agreement (usually 14–30 days' written notice), what happens to payment on termination, and which region's laws govern the contract. For international clients, this pairs with knowing how to invoice international clients.
The freelance contract checklist
| Clause | What it locks down | Skip it and… |
|---|---|---|
| Parties + date | Who owes whom | You chase the wrong person for payment |
| Scope of work | What "done" means | Endless unpaid additions |
| Deliverables + timeline | Dates + client dependencies | You're blamed for their delays |
| Payment terms | Fee, deposit, schedule, late fees | You fund the project yourself |
| Revisions | How many rounds are included | "One more tweak" forever |
| Kill fee | Payment if they cancel | You eat the lost time |
| IP / ownership | Who owns the files, and when | Your work used before you're paid |
| Contractor status | Your tax/legal standing | Misclassification headaches |
| Confidentiality | Handling sensitive info | Awkward disputes over leaks |
| Liability limit | Your maximum exposure | Damages far above your fee |
| Termination + law | The exit + jurisdiction | No clean way out |
Common mistakes that make a contract useless
- Copy-pasting a template you don't understand. A borrowed contract with the wrong ownership terms is worse than none, because it feels safe.
- No signature. An unsigned draft is a wish. Get a signature — an e-signature is fine and legally valid in most regions.
- Vague scope to "keep it friendly." Friendliness costs you money. Specifics are the kindness; they protect the relationship from the argument.
- Ignoring your own terms. If your contract says Net 7 and you never enforce it, you've trained the client to pay late.
Put it to work
You don't need eleven pages of legalese. You need one or two clean pages that name the parties, pin down the scope, set the payment schedule, cap revisions, assign ownership on payment, and give both sides an exit. Write it in plain language — a contract a client can actually read is a contract that gets signed.
Get the agreement signed first, then let the free invoice generator handle the billing that follows: deposit, milestones, and final payment, on your own branding, with no signup. The contract sets the terms; the invoice collects on them.