Most freelance contracts fall into one of two categories: a three-line email that says "sounds good, let's do it," or a twelve-page PDF a lawyer wrote for a different industry a decade ago. Neither of them protects you when something goes wrong — and something goes wrong in roughly one in five freelance engagements.
A good freelance contract is shorter than you think, plainer than you think, and covers a much smaller set of things than you think. What it covers, it covers tightly. This guide walks through every clause a freelance contract actually needs, gives you copy-paste templates for the load-bearing ones, and explains the reasoning behind each — so you can adapt them to your situation instead of pasting boilerplate and hoping.
If you want the short version: scroll to the full template at the bottom. If you want to understand why each clause is there — which is the part that determines whether the contract actually holds up — read the rest.
Why a written contract matters (even for a €500 gig)
Freelancers skip contracts for two reasons: the project feels too small, or they're afraid asking for one will scare the client off. Both are expensive mistakes.
A contract is not a statement of distrust. It is a shared memory. It's the document you both come back to when someone forgets whether the revision was included, whether the deposit was 30% or 50%, whether the deadline was "end of April" or "by April 15." Ninety percent of freelance disputes are not bad-faith disputes — they're memory disputes. A contract is what makes the memory canonical.
It also matters when things actually go bad. If a client refuses to pay, the first thing a small claims court, collections agency, or demand letter recipient will ask is: can you produce a signed contract? If the answer is no, you are not automatically out of luck — but you are starting from behind. Emails and invoices can substitute for a contract in many jurisdictions, but "substitute for" is not the same as "replace."
A one-page contract, signed before work starts, costs you about ten minutes. A dispute without one costs you weeks.
The nine clauses every freelance contract needs
Anything beyond these nine is usually lawyer theater. Anything missing from them is a hole a client can fall into.
- Parties and project description
- Scope of work and deliverables
- Payment terms
- Late payment and interest
- Revisions and change requests
- Intellectual property and ownership
- Kill fee and termination
- Confidentiality
- Governing law and signatures
Let's go through each. The clauses you can copy are marked with a code block.
1. Parties and project description
Full legal names of both sides. If you're a sole proprietor, use your real legal name, not a brand name — Jane Smith trading as "Smith Studio" rather than just "Smith Studio." If the client is a company, write the registered company name and address. This is the detail that gets forgotten and turns out to matter when an invoice is disputed six months later and you realize you don't actually know which legal entity you were working for.
This agreement is made on [date] between:
[Your full legal name / business name]
of [your address]
("Contractor")
and
[Client full legal name / registered company name]
of [client registered address]
("Client")
for the project described in Section 2 below.
Keep it that plain. "WHEREAS" and "hereinafter referred to as" are free to leave out.
2. Scope of work and deliverables
This is where most freelance contracts fail. "Design a website" is not a scope. "Write a book" is not a scope. A scope is a list that a reasonable stranger could read and tell whether you've done the work or not.
Good scopes list:
- What you will deliver — exact number of pages, words, designs, features, revisions.
- What you will not deliver — the stuff the client might assume is included. Hosting. SEO. Copywriting. Stock imagery. Integration with their CRM. Write it down if it's not yours to do.
- The format of delivery — Figma file, Google Doc, ZIP of PDFs, live staging URL.
- The acceptance criteria — what "done" looks like. Usually some variation of "Client will review within X business days and either accept the deliverable or provide a single consolidated list of revisions."
2. Scope of Work
The Contractor will deliver the following for this project:
(a) [Specific deliverable 1 — e.g., "a five-page marketing
website with home, about, services, case studies, and
contact pages"]
(b) [Specific deliverable 2]
(c) [Specific deliverable 3]
Deliverables will be provided in [format — e.g., "Figma source
files and a deployed Vercel preview URL"] on or before
[target date].
Not included in this scope: [list exclusions — e.g., "copywriting,
stock imagery licensing, ongoing hosting, SEO services, and
post-launch changes"].
The Client will review each deliverable within [X] business days
of receipt and either (i) accept it, or (ii) provide one
consolidated written list of revisions. If the Client does not
respond within that period, the deliverable is deemed accepted.
The "deemed accepted" clause is the one that saves you when a client goes silent for three weeks and then, after you've invoiced, suddenly has feedback. Put it in.
3. Payment terms
This clause decides how and when you get paid. It needs to answer five questions with no ambiguity:
- How much — flat fee, hourly rate, milestone payments, retainer.
- When — deposit up front, payment schedule, final payment on delivery.
- How — bank transfer, Stripe, PayPal, Wise. Include your actual payment details or say where they'll be listed.
- What the payment term is — Net 7? Net 14? Net 30? Default to the shortest terms the client will accept. Net 30 is a legacy of corporate AP departments, not a law of nature.
- What the currency is — critical if you and the client are in different countries.
3. Payment Terms
Total project fee: [amount + currency].
Payment schedule:
(a) [e.g., "50% deposit, due upon signature of this agreement,
before work begins"]
(b) [e.g., "25% due on acceptance of [milestone]"]
(c) [e.g., "25% due on delivery of the final deliverables"]
Each invoice is payable within [7 / 14 / 30] days of the invoice
date by bank transfer to the account provided on the invoice.
All amounts are stated in [currency] and exclude any applicable
taxes, which are the responsibility of the Client.
Work will not begin until the deposit has been received in full.
The Contractor may pause work if any invoice becomes overdue.
The deposit line is the single most valuable sentence in any freelance contract. A deposit does three things at once: it filters out clients who were never really going to pay, it funds the start of the work, and it legally establishes the engagement so that a dispute about cancellation has a financial anchor. Do not start work without one. For small projects, 30% is the minimum; for most projects, 50% is standard; for speculative or fast-turnaround work, 100% up front is perfectly reasonable.
The pause work line is just as important. It's the lever you pull when an interim invoice goes unpaid, and it's the difference between delivering all your work and then begging for the final payment, versus stopping the clock at the moment the client first breaks the deal.
4. Late payment and interest
This clause is what turns "you're late" into "you owe extra." Without it, a client has almost no financial incentive to pay on time — the worst case for them is paying the same amount, eventually. With it, the clock starts ticking and the number gets bigger.
4. Late Payment
If any invoice is not paid by its due date, the Client will owe
interest on the overdue amount at a rate of [the higher of (i) 8
percentage points above the [ECB / Bank of England / Federal
Reserve] reference rate, or (ii) 1.5% per month], calculated from
the day after the invoice due date until the date of full payment.
In addition, the Client will owe a flat late-payment compensation
fee of [€40 / £40 / $40] per overdue invoice, plus any reasonable
costs of recovery (including collection agency fees or legal
costs).
The Contractor reserves the right to invoice interest and fees
separately and to refer overdue amounts for collection after
[30 / 45] days past due.
A few notes. The "higher of statutory rate or 1.5% per month" pattern is a common drafting trick: in most EU and UK jurisdictions, statutory late payment law already gives you a right to interest at 8 points above the central bank rate, so you inherit that floor anyway. Adding "or 1.5% per month" gives you a contractual backstop that works in jurisdictions without a statutory rate (or where the statutory rate is lower). The flat fee mirrors the EU's €40 late-payment compensation and the UK's £40–£100 scale under the Late Payment of Commercial Debts Act 1998.
If you'd rather see exact numbers for a specific jurisdiction, run the free late-fee calculator — it handles EU Directive 2011/7, UK LPCDA 1998, and common US state rules, and prints a number you can paste straight into an invoice or demand letter.
5. Revisions and change requests
The second-biggest killer of freelance margins, after unpaid invoices, is scope creep: the project that started as "a five-page website" and somehow became "a five-page website, a blog, a newsletter integration, and a logo redesign" with no extra fee. The revision clause is what puts a lid on it.
5. Revisions and Changes
The project fee in Section 3 includes up to [number] rounds of
revisions per deliverable. A "round of revisions" is one
consolidated written list of requested changes, delivered to
the Contractor in a single document.
Any additional revisions, or any changes that fall outside the
scope described in Section 2, will be treated as a change request
and billed at the Contractor's standard rate of [amount + currency]
per hour, with a written estimate provided before work begins.
Change requests that materially alter the scope may also require
an adjustment to the project timeline.
Two rounds of revisions is the sensible default for most projects. Three is generous. "Unlimited revisions" is a trap, and anyone promising it is either charging 3× to cover the risk or planning to burn out.
6. Intellectual property and ownership
This is the clause clients care about most — and the one freelancers sign away fastest, often giving up more than they need to.
The core question is: when does the IP transfer, and what do you keep? The answer that protects you is: IP transfers on full payment, and you retain portfolio rights.
6. Intellectual Property
Until the Contractor has received the full project fee, all
intellectual property rights in the deliverables remain with the
Contractor. The Client is granted only a limited licence to
review and provide feedback on the deliverables during the
project.
Upon receipt of the final payment in full, the Contractor assigns
to the Client all intellectual property rights in the final
deliverables, except for:
(a) any pre-existing materials, tools, code libraries, or
frameworks owned by the Contractor, which are licensed
non-exclusively to the Client for use within the
deliverables;
(b) any third-party assets (fonts, stock imagery, open-source
libraries) used under their respective licences; and
(c) the Contractor's right to display and describe the
deliverables in portfolios, case studies, and marketing
materials, subject to any confidentiality obligations in
Section 8.
The "IP transfers on payment" line is the other half of the deposit — it's what stops a client from delivering the work without paying for it. Until the final payment clears, the client does not legally own what you made. That is a powerful lever, and more importantly it is automatic. You don't have to enforce it. It just is.
The portfolio carve-out is non-negotiable for most freelancers. If a client refuses it, either they have a legitimate confidentiality concern (a prototype for an unreleased product, say) or they don't understand how freelance careers work. If the former, negotiate a delay — you can show the work publicly six or twelve months after launch. If the latter, walk away or charge significantly more.
7. Kill fee and termination
A kill fee (sometimes called a cancellation fee) protects you if a client pulls the plug before the project is done. Without one, a client can cancel after you've spent two weeks on their project and pay only for "work completed to date" — which is often impossible to quantify and always an argument you're going to lose.
7. Termination and Kill Fee
Either party may terminate this agreement with [7 / 14] days'
written notice.
If the Client terminates the agreement before completion for any
reason other than a material breach by the Contractor:
(a) the deposit paid under Section 3 is non-refundable;
(b) the Contractor will invoice for all work performed up to
the date of termination, based on the hourly rate in
Section 5 or the pro-rated project fee, whichever is
greater;
(c) the Client will also owe a kill fee equal to [25% / 50%]
of the remaining unpaid balance of the project fee.
If the Contractor terminates for cause (including non-payment of
an invoice for more than [14 / 30] days), all work performed up
to that date is due and payable immediately, and the deposit is
retained in full.
The "deposit is non-refundable" line is the one clients push back on. Hold firm — it's the entire point of a deposit. If the deposit is refundable on cancellation, it's not a deposit, it's a hostage.
8. Confidentiality
Usually short. You agree not to share their non-public information; they agree not to share yours. This is mostly a client-comfort clause, but it's worth including because it also caps your own exposure — a confidentiality clause that runs both ways means the client can't publicly rubbish your work without breaching the contract.
8. Confidentiality
Each party agrees to keep confidential any non-public information
of the other party that it learns in the course of this
engagement, and to use such information only for the purposes of
this project. This obligation survives termination of the
agreement.
Confidential information does not include information that is
(i) already public, (ii) independently developed by the receiving
party, or (iii) required to be disclosed by law.
9. Governing law and signatures
Pick one jurisdiction. If you and the client are in different countries, it's usually easier to choose yours — the alternative is learning someone else's courts.
9. Governing Law
This agreement is governed by the laws of [your country / state],
and any disputes arising from it will be resolved in the courts
of [your city / region].
10. Signatures
Signed by the Contractor:
_______________________________ Date: _______________
[Your name]
Signed by the Client:
_______________________________ Date: _______________
[Name, Title]
Electronic signatures (DocuSign, HelloSign, PandaDoc, or even a typed name on an emailed PDF that's been agreed to in writing) are legally binding in the EU (eIDAS), the UK (Electronic Communications Act 2000), the US (ESIGN Act), and most other common-law jurisdictions. You don't need a wet signature. You do need proof that both parties agreed — a signed PDF returned by email is enough.
The full template
Putting it all together:
FREELANCE SERVICES AGREEMENT
This agreement is made on [date] between:
[Contractor name]
of [address]
("Contractor")
and
[Client name]
of [address]
("Client")
1. Project
The Contractor will provide the services described in
Section 2 for the fee described in Section 3.
2. Scope of Work
[Deliverables, format, exclusions, acceptance criteria —
see Section 2 above]
3. Payment Terms
[Fee, schedule, method, payment term, currency —
see Section 3 above]
4. Late Payment
[Interest rate, compensation fee, recovery costs —
see Section 4 above]
5. Revisions
[Number of rounds, hourly rate for extras —
see Section 5 above]
6. Intellectual Property
[Transfer on payment, portfolio rights —
see Section 6 above]
7. Termination and Kill Fee
[Notice, non-refundable deposit, kill fee —
see Section 7 above]
8. Confidentiality
[Mutual NDA-lite — see Section 8 above]
9. Governing Law
[Jurisdiction — see Section 9 above]
10. Signatures
Contractor: __________________ Date: ________
Client: __________________ Date: ________
Fill in the bracketed sections, print it or send it through an e-sign tool, and you have a contract that will hold up in virtually any freelance scenario.
Common mistakes that make a good contract useless
Even a well-written contract fails if you undermine it in practice. Watch for:
- Starting work before the contract is signed. "We'll get the paperwork sorted later" is how freelancers end up a week into a project with no deposit and no agreed scope. The signed contract is the moment work starts. Not the kickoff call, not the purchase order, not the Slack DM.
- Accepting changes by text. A scope or schedule change agreed to in WhatsApp is technically binding in most jurisdictions, but it's a mess to prove. If a client asks for a change, reply with "happy to — I'll send a change request note to confirm the scope and timing" and email it. The paper trail has to live in one place.
- Letting overdue invoices slide. If your contract says "work will pause if any invoice is overdue" and you keep working anyway, you've just told the client the clause is decorative. Enforce the pause the first time it comes up, even if it feels awkward. It's always less awkward than the alternative.
- Using a contract from a different legal system. A contract that references "Section 1981" or "the Truth in Lending Act" when you're in Berlin is not going to help. Adapt the jurisdiction and legal references to where you are, or where you'd actually file a claim.
- Relying on generic online templates with no review. The clauses in this guide are a solid baseline, but for large projects (€10,000+), retainers, or anything touching regulated industries (finance, health, legal), spend the couple hundred euros for a lawyer in your jurisdiction to review once. That review applies to every contract after it.
What to do when a good contract still isn't honored
Even a tight contract doesn't prevent every dispute. What it does is make the dispute tractable. When an invoice goes unpaid and the contract is in place, the escalation path is much clearer:
- Send a friendly reminder, quoting the invoice and the payment term from Section 3.
- If that fails, invoke the "pause work" clause and tell the client the project is on hold until the overdue invoice clears.
- If that fails, send a formal demand letter, reference the contract clauses you're enforcing, and state the interest and fees owed under Section 4.
- If that fails, the contract is also what makes small claims court, collections, or the full escalation playbook a much less scary prospect — a judge reading a one-page contract, a signed deposit, and a demand letter has a very easy decision to make.
The contract is not the thing that gets you paid. Your work is. But the contract is the thing that makes sure the work you did turns into money in your account — and turns every subsequent step, from reminders to court, from a debate into a checklist.
The short version
- Write it down. Even a one-page contract beats a three-line email every time.
- A good freelance contract has nine clauses: parties, scope, payment, late payment, revisions, IP, termination, confidentiality, governing law.
- Always take a deposit. 30% is the floor, 50% is standard.
- IP transfers on full payment, not on delivery. Keep your portfolio rights.
- Cap revisions at two rounds. Bill extras at your hourly rate.
- Include a statutory-floor late fee clause and a kill fee — both are invisible until you need them, and then they are the whole contract.
- Sign electronically. Wet signatures are overrated.
- Enforce the clauses the first time, not the fifth.
A freelance contract is not about distrust. It's the document that makes disagreements survivable — and most of the time, having it is what keeps the disagreement from happening at all.
PayShield is building the freelance operating system that automates the parts of this guide you'd rather not think about: contract e-sign, deposit collection, late-fee math, and automatic demand letters when a client goes quiet. Join the waitlist to get early access.