Freelance Contracts: Clauses That Protect You

Quick answer: A freelance contract protects you when it names the parties, the deliverables, the price, the payment trigger and the exit in writing, and when it turns anything outside the agreed scope into a new quote. The clauses that matter most are scope, revisions, payment terms, ownership, termination and a liability cap — each written in plain language you can enforce.

Key takeaways

• A contract is not a formality; it is the document that decides who pays for the extra round of changes and when.
• Vague scope is the most common reason freelancers lose money, and a numbered exclusions list fixes it.
• Payment terms need a deposit, a milestone schedule and a late fee sentence in days, not “upon completion.”
• When a client sends their own paper, five clauses are worth redlining before you sign.

What a freelance contract actually has to do

A freelance contract does five jobs: it identifies the parties, describes the deliverable, states the price, sets the payment trigger and defines the exit. If any of those is missing, you have a conversation, not an agreement. In a dispute, an email thread proves intent at best; it rarely proves what was promised, when it was due or what happens if it is late.

Email threads fail because they are fragmented. The brief is in one message, the price in another, the revision limit in a third, and the client’s approval in a fourth that says “looks good, let’s go” without referencing any of them. A contract pulls those threads into one document with a version you can point to. That single change is what turns a disagreement into a payment.

The five elements are not legal decoration. Parties matter because you need the right entity on the invoice. The deliverable matters because “a website” is not a deliverable; a five-page site with a contact form is. Price and payment trigger matter because “net 30” after delivery means you fund the project. The exit matters because clients cancel, and you need to know what you are paid when they do.

You do not need a lawyer for a standard project contract. You need plain language, a signature, and a copy stored somewhere you can find it. The clauses below are the ones that do the work.

Before the clauses: the discovery brief that stops scope fights

Most scope fights are not contract problems; they are briefing problems. If the client never wrote down what they wanted, the contract has nothing precise to enforce. A short discovery brief, written before you quote, gives the contract a spine.

A written brief contains the goal, the audience, the specific pages or assets, the format, the deadline, the review process and the definition of done. It also contains what the client will supply — copy, images, logins, brand files — and by when. That last part matters because half of all delays are client-side, and a brief that lists client responsibilities lets you point to them without sounding difficult.

The brief becomes an exhibit inside the contract. You do not paste it into the body; you attach it and reference it: “The services are described in Exhibit A, the brief dated [date] and agreed by both parties.” Now the brief is not a nice-to-have, it is the definition of the job. If the client later asks for a page that was not in Exhibit A, you are not arguing about memory; you are pointing at a document.

This is also where your quote becomes defensible. If you set your rate and project price using a structured method — the kind covered in this freelance pricing guide — the brief is what the price is based on. Without it, every change feels negotiable.

The scope clause: a deliverables list and an exclusions list

The scope clause has two halves, and most freelancers write only one. The first half is a precise, numbered deliverables list. The second half is a numbered list of what is explicitly excluded. The exclusions list is what saves you.

A deliverables list reads like this: “Five unique page designs (Home, About, Services, Blog index, Contact), responsive at three breakpoints, delivered as Figma files. One round of consolidated client feedback per page.” Notice what it does not say: it does not say “website design,” and it does not say “as needed.” It counts things. Counting is the whole trick.

The exclusions list names the things clients assume are included: copywriting, stock photography, hosting setup, SEO, ongoing maintenance, extra pages, logo design, email templates, accessibility audits beyond basic contrast checks. Write them down even when they feel obvious. The client who assumed copywriting was included is not acting in bad faith; they simply were never told.

Then add the sentence that turns anything outside the list into a new quote: “Any work not listed in Section 2 is out of scope and will be quoted separately before it begins.” That sentence is the difference between a conversation about money and an argument about it. It also gives you a polite script: “Happy to do that — it is outside the brief, so I will send a separate quote.”

Fixed-price packages on platforms get this right by design. On Fiverr, the gig scope and revision count are locked before the buyer orders, which is exactly the model to copy in your own contract: define the package, count the revisions, price the extras.

The revision clause: count them, define them, price the extras

A revision is a change to work already delivered within the agreed direction. A new direction is a different project. The contract needs to say that, because clients use the word “revision” for both.

Count revisions explicitly: “Two rounds of revisions are included. A round is one consolidated set of comments delivered within five business days of receiving the draft.” The word consolidated is doing heavy lifting. It prevents the drip-feed of one comment per day for two weeks, which is how a two-round project becomes a ten-round project.

Define what a revision is not: a change of direction, a new audience, a new page, a new brand, or a change requested after final approval. Then price the overflow: “Additional rounds are billed at [your hourly rate] per hour, invoiced before the round begins.” You do not need to guess the number of hours; you need the sentence that makes the next round a paid decision rather than a free habit.

Unlimited revisions is the clause that kills fixed-price projects. It sounds generous and it is uninsurable: the client has no reason to converge, and you have no mechanism to stop. Even a generous limit — three rounds, four — is better than infinity, because it creates a moment where the client has to decide what they actually want.

Money clauses: deposit, milestones, late fees and silence

Money clauses are where freelancers are most often polite to their own detriment. The contract should require a deposit before work starts — commonly a meaningful share of the project fee, not a token amount — because a deposit is the only reliable signal that the client is serious and funded.

For anything larger than a small project, use a milestone schedule: a deposit, a payment at an agreed midpoint, and the balance before final files are released. Each milestone should name the trigger in plain terms — “on approval of the homepage design,” not “on progress.” The trigger is what makes the invoice undisputable.

Payment terms belong in days, not adjectives. “Payment is due within 14 days of invoice date” is enforceable; “payment upon completion” is an invitation to debate what completion means. Add the late fee sentence: “Invoices unpaid after 14 days incur a late fee of [a stated percentage or flat amount] per week until paid.” You rarely need to charge it; you need the client to know you will.

Then cover the two scenarios nobody plans for. For chargebacks, state that work is suspended during any payment dispute and that delivered files remain licensed only on cleared payment. For the client who stops answering, state that the project is deemed approved if no feedback arrives within a set number of business days, and that the next milestone becomes due. Silence should have a price, or it becomes a strategy.

Ownership and licensing: when the client actually gets the work

Copyright transfer should be conditional on final payment. The clause is simple: “On receipt of full payment, the client owns the final deliverables. Until then, the freelancer retains all rights.” That single condition is your strongest collection tool, because the client cannot use what they do not own.

Keep the right to show the work. A portfolio clause — “the freelancer may display the work in a portfolio and on professional profiles” — costs the client nothing and is worth a great deal to you. If the client needs confidentiality, agree to a delay or an anonymised version rather than giving up the right entirely. Clients often judge you by past work before terms are ever discussed, which is why a visible portfolio and a clear profile matter as much as the contract itself; the habits in this profile optimisation guide feed directly into the work you are able to win.

Third-party assets need their own sentence. Fonts, stock images, plugins and icon sets carry licences that are not yours to transfer. State that such assets are licensed to the client under their original terms and that any extended or commercial licence is either included at a stated cost or purchased by the client. This prevents the awkward moment when a client assumes they own a typeface you licensed for one project.

The kill clause: what happens when the project stops

Projects end early for good reasons and bad ones. The contract should allow the client to terminate for convenience — most will insist on it — but it should also state what they pay when they do.

The core sentence: “On termination, the client pays for all work completed to the date of termination, plus any non-refundable third-party costs already incurred.” Add a kill fee for the disruption: a stated percentage of the remaining fee, or a minimum number of hours, payable on termination. A kill fee is not punitive; it covers the slot you reserved and the work you turned down.

Define handover. On termination and payment of the amount due, you deliver the files completed to that date, in their working format, and revoke any licence not yet paid for. If the client terminates before payment, they get nothing usable, which is the correct incentive. Keep the handover list short and specific — source files, exports, documentation, account access — so there is no argument about what “the files” means.

Liability, warranty and indemnity limits

Unlimited liability is unacceptable for a solo worker, and it appears in client paper more often than freelancers expect. You cannot insure an open-ended exposure, and one bad clause can put your savings at risk for a project fee that was modest.

Cap liability at a realistic multiple of the project fee — commonly the fee itself, sometimes a small multiple — and exclude indirect and consequential losses such as lost profit or lost business. The wording is short: “The freelancer’s total liability under this agreement is limited to the fees paid under it, and neither party is liable for indirect or consequential loss.”

For marketing, SEO and advertising work, add a no-guarantee-of-results sentence: “The freelancer does not guarantee specific rankings, traffic, conversion rates or revenue outcomes; search and advertising platforms are outside the freelancer’s control.” This is not pessimism; it is an accurate description of the work. It also keeps a bad quarter from becoming a refund demand.

Indemnity should run both ways and be limited. You indemnify the client for your own infringement or negligence; they indemnify you for the content and assets they supply. Unlimited one-way indemnity is a redline, not a negotiation.

Signing, storing and enforcing it in practice

An e-signature is fine. A signed PDF returned by email is fine. What matters is that both parties can produce the same document with a date on it. Use a simple e-sign tool or a signed PDF, keep a copy in cloud storage with the project files, and name the file so you can find it later — client, project, date.

Keep a plain-language version too. If the client is a small business owner, a one-page summary of the key terms — scope, price, revisions, payment dates, termination — reduces the chance of a dispute later, because the client actually read something. Attach the full contract behind it.

When an invoice goes unpaid, follow a sequence rather than improvising. Send a polite reminder on the due date. Send a firmer notice with the late fee applied after the grace period. Suspend work and state that you have done so. Send a final notice with a deadline and a copy of the contract clause. Then decide: small claims court is often the cheaper route for a modest invoice, because filing fees are low and you do not need a lawyer; a solicitor is usually only worth it when the sum is large or the client is disputing the contract itself.

The habits that prevent most of this are unglamorous: a written brief, a signed contract, an invoice with a due date, and a follow-up on the day. The freelancer habits that keep clients paying are mostly administrative, and they compound.

When the client insists on their own contract paper

Larger clients will send their own contract, and refusing outright rarely works. Read it, then redline the clauses that shift risk you cannot carry. Five clauses are worth the fight.

Clause	What client paper often says	Why it hurts a solo freelancer	Counter-edit to propose
IP assignment	All work becomes client property on creation	You lose leverage before final payment	Transfer on receipt of full payment
Liability	Unlimited, including consequential loss	One claim can exceed the whole fee	Cap at fees paid; exclude indirect loss
Termination	Client may terminate at any time, no fee	You absorb cancelled capacity	Pay for work done plus a kill fee
Payment	Net 60 or “on acceptance”	You fund the project and the definition	Net 14 from invoice; defined milestones
Indemnity	One-way, unlimited, includes client content	You carry risk for material you did not create	Mutual, limited, client warrants their assets

Phrase the counter-edit as a practical request, not a legal objection: “We can accept the IP assignment, but it needs to take effect on final payment, which is standard for independent contractors. Here is suggested wording.” Offer the sentence, not the argument. Most in-house reviewers accept a capped liability and a payment-conditional IP transfer because both are common.

If the client will not move on unlimited liability or a unilateral no-fee termination, that is information about how the project will go. Walking away from a bad contract is cheaper than enforcing a good one.

Checklist: what to confirm before you send the contract

• Both legal names and addresses are correct, including the entity that will pay.
• The brief is attached as an exhibit and referenced in the services clause.
• Deliverables are numbered, and exclusions are numbered separately.
• Revisions are counted, defined as consolidated rounds, and priced beyond the limit.
• A deposit is required before start, with milestone triggers named in plain terms.
• Payment terms are in days, with a late fee sentence and a silence clause.
• Ownership transfers on final payment; liability is capped; termination has a kill fee.

Frequently asked questions

Do I need a lawyer to write a freelance contract?

For standard small-business projects, no. A plain-language contract with clear scope, payment and ownership clauses is usually enough, and templates are widely available. Use a lawyer when the project value is high, the client is sending complex paper, or the work involves sensitive data or regulated claims.

Is an email agreement enforceable?

Often yes, but proving it is the problem. An email thread can establish that a deal existed, yet it rarely proves the revision limit, the payment date or the definition of done. A single signed document that references the brief removes the ambiguity and is far easier to rely on when a payment stalls.

How much should a deposit be?

Enough to matter. Many freelancers ask for a meaningful share of the project fee up front, with the balance tied to milestones. The exact figure depends on your cash flow and the client’s size; the principle is that the deposit covers your initial work and confirms the client is funded and serious.

Can I keep the copyright until I am paid?

Yes, if the contract says so. Make the transfer conditional on full payment and state that the client receives a licence to review the work in the meantime. This is common for independent contractors and is usually accepted once it is explained as a payment term rather than a restriction on use.

What if the client refuses to sign anything?

Treat that as a signal. Offer a one-page version covering scope, price, payment dates, revisions and ownership, and send it as a simple acceptance email if a signature is too much. If the client still refuses, decide whether the fee justifies the risk; often it does not.

What to do next

Open your last three projects and look for the moment money was lost: an extra round, a late invoice, a page nobody quoted. Then write the clause that would have prevented it, in one sentence, and add it to a master contract you reuse. Attach a brief to every quote, require a deposit, and put payment terms in days.

If you are still building your client base, the platforms can hold some of this for you — the freelancing sites that hold contracts and payment protection are a reasonable starting point, and Upwork is useful as a reference for how milestone wording looks when it is enforced by a platform. If you are freelancing alongside a job, the risk of an unbriefed project is higher because you have less time to absorb it; the guidance on starting freelance work alongside a job is worth reading before you take on a second client.

Finally, send the contract before the kickoff call, not after. The clause you never wrote is the one the client will interpret in their favour.

Disclosure: some links in this article are affiliate links. If you buy through them we may earn a commission at no extra cost to you.