How to Write a Freelance Contract

A contract is not a sign of distrust — it's the document that lets you and your client agree on what happens before anything goes wrong. The freelancers who get burned by scope creep, late payment, and ownership disputes are almost always the ones who skipped it. Here are the clauses that actually matter, in plain language.

Why Every Project Needs One

Most freelance disputes aren't caused by bad faith. They're caused by two people who sincerely remembered a verbal agreement differently. The client thought three rounds of revisions were included; you thought it was one. They assumed the source files came with the project; you assumed they were extra. A written contract doesn't just protect you legally — it forces both sides to make these assumptions explicit before money and deadlines are on the line. The conversation a good contract prompts is worth more than the document itself.

You don't need a lawyer to draft every agreement. A clear, plain-English contract that both parties sign by email is enforceable in most jurisdictions and covers the vast majority of freelance work. For large engagements or anything with significant legal exposure, have an attorney review your template once — then reuse it.

The Essential Clauses

Scope of work

The single most important clause. Describe exactly what you will deliver — the specific deliverables, formats, quantities, and any concrete specifications. Just as important, state what is not included. "Design of one landing page in Figma, delivered as a single desktop and mobile layout" is protective. "Website design" is an invitation to scope creep. The more precisely you define done, the harder it is for a project to quietly balloon.

Payment terms

State the price, the currency, the schedule, and the method. For projects, require a deposit upfront — 30–50% is standard — so you're never doing significant work with nothing secured. Specify when the balance is due (on delivery, net 15, net 30) and what counts as "delivered." For ongoing work, define the billing cycle. Vague payment terms are the leading cause of slow payment; precise ones give you a clear basis to chase an overdue invoice.

Late payment terms

Spell out what happens when an invoice goes unpaid: a late fee (commonly 1.5% per month on the outstanding balance) and the right to pause work until payment is received. You may rarely enforce the fee, but having it in writing changes client behavior and gives you leverage. A client who knows late payment has a defined cost pays on time more often.

Revisions

Define how many rounds of revisions the price includes, and what a "round" means. State your rate for additional revisions beyond that. Without this clause, "a few small tweaks" can stretch into weeks of unpaid back-and-forth. "Includes two rounds of revisions; additional rounds billed at [rate]/hour" ends that problem before it starts.

Kill fee / cancellation

Protect yourself against a client who cancels mid-project. A kill fee clause entitles you to keep the deposit and bill for work completed up to the cancellation point. Without it, a client can pull the plug after you've done 80% of the work and argue they owe nothing because there's no final deliverable. State clearly that work performed is payable whether or not the project is completed.

Intellectual property and ownership

Define who owns the work and when ownership transfers. The standard, and the one that most protects you: you retain ownership until final payment is received in full, at which point rights transfer to the client. This makes payment a precondition of ownership — a powerful incentive. Decide separately whether source files, working files, or licenses are included, and whether you retain the right to display the work in your portfolio.

Timeline and client responsibilities

Projects stall most often because the client is slow to provide feedback, content, or assets — then expects you to hit the original deadline anyway. Tie your timeline to their cooperation: state that deadlines assume timely delivery of what you need from them, and that delays on their side move your dates accordingly. This protects you from being blamed for slippage you didn't cause.

Clauses Worth Adding for Larger Work

Confidentiality — a mutual clause covering any sensitive information either party shares.
Limitation of liability — caps your financial exposure, typically at the total project fee, so a small project can't expose you to an outsized claim.
Independent contractor status — confirms you're a contractor, not an employee, which matters for taxes and benefits. (See the freelance taxes guide for why this distinction is important.)
Governing law — names which jurisdiction's law applies if there's ever a dispute.

Keep It Readable

A contract written in dense legalese that your client can't understand is worse than a plain one they can. The goal is shared clarity, not intimidation. Write each clause so a non-lawyer can read it and know exactly what they're agreeing to. Plain-language contracts get signed faster, generate fewer objections, and hold up just as well when both parties actually understood what they signed.

Make Signing Easy

The best contract is the one that gets signed before work starts. Use a simple e-signature tool so the client can sign in two minutes from their phone. Send the contract together with the deposit invoice, and make signing plus deposit the trigger that begins the work. Build this into your onboarding so it's automatic — never start a paid project on a handshake and a hopeful email thread.

Price the Work Before You Paper It

A contract locks in your price — so make sure the price is right first. Use the calculator to find the rate your finances actually require before you put a number in writing.

Calculate My Rate

This article is general information, not legal advice. Laws vary by jurisdiction — consult a qualified attorney for contracts involving significant value or risk.