Freelance Contract: the 9 Essential Clauses Before Starting a Project
Most freelancers sign their first real contract after their first real problem: a client who disputes the scope, a project abandoned midway, a design reused without permission. A solid contract doesn't prevent disagreements — it makes them short and cheap. Here are the 9 clauses that make the difference, and why your client brief is the centerpiece.
Signed quote, standard terms, or contract: which does what?
A signed quote already forms a contract: it binds both sides on scope and price. Standard terms of service add your general rules (payment, liability, termination) that apply to all clients. A dedicated service contract combines both and adds what gets negotiated case by case: intellectual property, confidentiality, timeline, client obligations. Small project: detailed quote + standard terms. A project worth several thousand, or involving creative work: dedicated contract.
This article offers general guidance and is not legal advice. Rules vary by country — for a specific situation, consult a legal professional.
The centerpiece: the client brief attached to the contract
Nearly every freelance dispute comes down to the same question: what exactly was agreed?The client swears the newsletter was included; you know it wasn't. Without a written record, it's word against word — and it's usually the freelancer who gives in, out of exhaustion or fear of a bad review.
The simplest protection isn't a clause but an annex: the brief filled out by the client themselves, timestamped, referenced in the contract as defining the scope. Their own written answers — goal, expected pages, features, constraints — become the binding reference:
- →The scope is defined by the client, in their own words: impossible to claim they were misunderstood
- →Any request absent from the brief is visibly a new request — the amendment justifies itself in one sentence
- →The document exists before the contract: no extra drafting, just an annex to reference
- →If the brief is vague, the problem surfaces before the signature — exactly when it can still be fixed
A client who returns a vague brief despite a structured form is warning you before the commitment — one of the signals to take seriously.
Your contract's scope, written by the client themselves
Briefly collects your client's answers in a structured, timestamped brief — goal, scope, constraints — that you attach to the contract. If a disagreement comes up, the written reference already exists.
Create my brief link →The 9 essential clauses
Each clause answers a scenario that actually happens: a late client, an abandoned project, a reused design, requests that keep growing. If you have to prioritize, the first four alone prevent most conflicts.
Subject and scope of work
The most important clause — and the most rushed. Describe the deliverables precisely and attach the client brief: the client's own written answers define the scope better than any legal phrasing. Anything not in it is out of scope.
Price and payment terms
Amount, deposit (30 to 50%), milestones, payment deadline (30 days is a common default between businesses), and late-payment penalties. Spell out what happens when an invoice is late — it's exactly the clause you'll be glad to have if one ever is.
Timeline and client obligations
Your deadlines only hold if the client holds theirs: providing content, sign-offs within X days, an available point of contact. Include an automatic schedule shift when the client is late — it's the clause that keeps you from absorbing delays alone.
Revisions and additional requests
Number of revision rounds included per deliverable, the window to submit them, and pricing for out-of-scope requests (amendment or hourly rate). This is your contractual firewall against scope creep.
Intellectual property
In many jurisdictions, the creator keeps their rights by default: without an explicit transfer clause (scope, duration, territory, media), your client may not own what you create. Also state what you keep: tools, libraries, and the right to show the work in your portfolio.
Confidentiality
A mutual commitment not to disclose sensitive information exchanged during the project. Keep the clause proportionate: total, perpetual confidentiality would forbid you from even naming the client as a reference.
Liability and warranties
Cap your liability at the contract amount and exclude indirect damages (lost revenue, lost data). Define the warranty period on deliverables (bug fixes, touch-ups) and what it covers.
Termination
How each party can exit the contract: notice period, grounds, and above all what happens to money owed — work completed up to termination stays paid, the deposit stays earned. Without this clause, a client who abandons their project leaves you holding the bill.
Independent contractor status
State that you work as an independent: free organization of your work, no subordination, multiple clients allowed. This clause protects both parties from the risk of the relationship being reclassified as disguised employment.
5 contract mistakes that cost dearly
Starting work before the signature
The pressure of "we'll sign in parallel, go ahead and start" flips the balance of power: once the work has begun, the client has no reason left to sign. Signature + deposit, then kickoff — in that order.
Copying an online template without adapting it
A software development contract applied to a branding project leaves gaping holes (copyright, deliverables, warranties). The template is a starting point; the scope, deliverables and IP transfer get rewritten for each type of engagement.
Defining the scope with a vague phrase
"Creation of the client's website" protects no one. Scope is defined by a list of deliverables and by the attached brief — not by a generic sentence that will be interpreted against you.
Forgetting what happens when the client is late
A contract that only binds the contractor is a classic trap: your deadlines run, but nothing obliges the client to deliver content or sign-offs. Every obligation on your side needs its counterpart on theirs.
Neglecting the termination clause
Projects that stop midway are more common than lawsuits. Without a clear clause on what's owed at termination, every abandoned project becomes a negotiation — one you start from a position of weakness.
Your contract's scope, written by the client themselves
Briefly collects your client's answers in a structured, timestamped brief — goal, scope, constraints — that you attach to the contract. If a disagreement comes up, the written reference already exists.
Create my brief link →In practice: a process, not paperwork
The contract fits naturally into a structured client onboarding: brief filled out, scoping call, quote, then signed contract and depositreceived before the kickoff meeting. Presented that way — "this is how I work with all my clients" — the contract reassures more than it worries: it signals an organized professional.
Once your template is dialed in, each new contract takes fifteen minutes: the scope comes from the brief, the price from the quote, and the rest barely changes. It's the best protection-to-effort ratio in your entire business.
Related reading
Frequently asked questions
Is a signed quote enough as a freelance contract?
In most jurisdictions, a signed quote forms a contract: it binds both parties on the work and the price. But it covers neither intellectual property, nor termination conditions, nor liability when something goes wrong. For small projects, a detailed quote plus standard terms of service is often enough; beyond a few thousand euros or dollars, or whenever the project involves creative work (design, code, content), a dedicated contract is worth it.
Do I need a lawyer to write a freelance contract?
Not to get started: solid templates exist and cover the classic service scenarios. A lawyer becomes relevant when the stakes grow — recurring contracts with large accounts, non-compete clauses, complex intellectual property, or your first serious dispute. The right approach: a proven template you adapt, reviewed once by a professional, then reused.
What if a client refuses to sign a contract?
A professional client who refuses any written commitment is a major red flag. First offer a lighter version (detailed quote + standard terms) if the full contract scares them. If they refuse that too, require at minimum a deposit and a written email agreement on scope and price — and think seriously about whether this relationship should continue.
Does a client brief have contractual value?
Yes, if it's attached to the contract or quote and referenced as defining the scope. It's actually the most protective use of a brief: the client's own written answers (goal, content, expected features) become the binding reference if a disagreement arises about what was planned. A timestamped brief filled out by the client beats ten meeting summaries.
Your contract's scope, written by the client themselves
Briefly collects your client's answers in a structured, timestamped brief — goal, scope, constraints — that you attach to the contract. If a disagreement comes up, the written reference already exists.
Create my brief link →