How do you write a freelance contract?

Short answer: a good freelance contract covers six things — what you will do, what you will be paid, when it is due, who owns the work, how either side can walk away, and what happens when something goes wrong. Everything else is decoration.

Most freelance disputes are not dramatic. Nobody is suing anyone over a $500 logo. They are quiet and corrosive: a client who keeps adding "one small thing," a payment that drifts from 15 days to 45, a project killed halfway with no compensation. A contract does not prevent bad clients from existing. It prevents misunderstandings from becoming conflicts, and it gives you a calm document to point at when memory gets fuzzy.

You do not need a lawyer to write a working contract. You need to be specific about the things people usually leave vague.

Start with scope, not signatures

The scope of work is the most important paragraph in the entire contract, and it is the one people rush through.

Describe exactly what you will deliver: the number of pages, the format, the features, the milestones. "Design a website" is a dispute waiting to happen. "Design a five-page marketing website including homepage, about, services, contact, and blog index, delivered as a Figma file with a responsive layout" is a contract.

Be equally specific about what is not included. If revisions are capped at two rounds, say so. If copywriting is not part of the design fee, say so. Every sentence you write here is one argument you will never have.

Money: rate, schedule, and the late-payment clause

Money terms need four answers: how much, how it is calculated, when it is paid, and what happens when it is not.

State your rate clearly — flat fee, hourly with a cap, or milestone-based. For projects over a few hundred dollars, split payment into milestones: a deposit before work starts (30 to 50 percent is standard and reasonable), the rest on delivery. A deposit does two jobs: it protects you from vanishing clients, and it filters out clients who were never serious.

Include a late-payment clause. Something like: invoices unpaid after 30 days accrue a fee of 1.5% per month, and work pauses until the account is current. You may never enforce it. Its value is psychological — a client who signs a late fee takes your invoice seriously from day one.

And specify how payment arrives: bank transfer, PayPal, Wise. Who pays the transaction fees? Say it in writing.

Deadlines that protect both sides

A contract should name the delivery date and, just as importantly, the client's obligations. Your deadline depends on their feedback arriving on time, their content being delivered, their approvals not taking three weeks.

Write it as a dependency: "Final delivery is due 14 days after the client approves the draft." That way a late client cannot blame you for a late project. Some freelancers add a clause that feedback arriving more than seven days late moves the delivery date by the same amount. It sounds fussy. It saves friendships.

Revisions: the clause that saves your sanity

Scope creep is the most common freelance complaint, and the revision clause is the cure.

Define a revision as a round of consolidated feedback — one round, one set of comments, one revision. Cap the included rounds at two or three, then state the price of additional rounds. When a client knows the fourth round costs $150, the third round suddenly becomes much more decisive.

This is not about nickel-and-diming. It is about making the cost of indecision visible. Clients who understand the economics of their own changes are better clients.

Who owns the work, and when

Intellectual property is the clause freelancers skip most and regret most.

The standard, fair arrangement: the client receives full ownership of the final deliverables upon final payment. Until payment is complete, ownership stays with you. That single sentence — "transfer of rights occurs upon receipt of final payment" — is your leverage for the last invoice.

Reserve a few things for yourself in writing: the right to show the work in your portfolio, the right to reuse your own processes and techniques, and the understanding that working files (source files, layered documents) may cost extra or be withheld. Many clients assume the source files are included. Many freelancers assume they are not. Write it down.

The exit clause: how to break up nicely

Every contract should describe how either party can end the relationship. Because sometimes they must.

A fair kill fee structure looks like this: the client may cancel at any time, but pays for all work completed plus a percentage of the remaining fee (25 to 50 percent is common) as compensation for the reserved time. You may also cancel with notice, delivering all work completed to date.

This clause feels pessimistic to write and is a relief to have. Projects die for blameless reasons — budgets get cut, strategies change, people leave. An exit clause turns a potential fight into a procedure.

The quiet clauses that matter

A few more lines, short and plain. Confidentiality: both sides keep each other's business information private. Independent contractor status: you are not an employee, which matters for tax and liability in most jurisdictions. Dispute resolution: name the governing law and prefer mediation before anything formal — it signals you are reasonable and makes the contract feel fair to sign.

Limitation of liability is worth one sentence: your total liability is capped at the fees paid under the agreement. No freelancer should carry unlimited liability for a $2,000 project.

Templates, tools, and the lawyer question

You do not need to draft from a blank page. Tools like Bonsai and HoneyBook include contract templates built for freelancers, and e-signature tools like DocuSign or HelloSign make signing painless. Many freelancer communities share battle-tested templates for free.

Do get a lawyer involved in two situations: when a client sends you their contract (read it carefully — their terms favor them by design), and when a project is large enough that a dispute would genuinely hurt you. For everything else, a clear plain-language contract you wrote yourself beats a vague one you downloaded and never customized.

How to send and sign without friction

A contract that sits unsent protects no one. The best contract process is the one that happens before the work starts, every time, without drama.

Send the contract with the proposal or quote, not after. Frame it as standard practice — "here is my standard agreement" — rather than as a reaction to distrust. Clients who are used to professional freelancers expect this; clients who resist a basic agreement are telling you something worth hearing before the project begins.

E-signature tools make this painless. DocuSign, HelloSign (Dropbox Sign), and the signing features built into Bonsai or HoneyBook let a client sign from a phone in under a minute. Never accept "we will sort out the paperwork later" for a project that has already started. Later is where paperwork goes to die.

What to do when a client breaks the contract

Most breaches are not malicious. A client misses a payment because their own client missed a payment. A project stalls because priorities shifted. Your contract gives you a script for these moments, and the script is calmer than your feelings.

Step one is the polite reminder, referencing the agreement: "Just a heads-up that per our agreement, the second milestone was due last Friday." Most late payments resolve here — the contract did its job by making the reminder factual rather than emotional.

Step two is the formal notice: a written email stating the breach, the clause it violates, and a deadline to fix it. Step three, which you will rarely reach, is stopping work. The contract's pause clause exists so that stopping work is an enforcement of terms, not a personal decision.

Actual legal action over freelance sums is rare because it is expensive for everyone. The contract's real power is earlier: it makes expectations explicit, which prevents most breaches, and it makes the few real ones easy to resolve with a pointed email. A freelancer with a contract and a paper trail almost never needs a courtroom.

The one-page version for small gigs

Not every project needs ten clauses. For a $200 article or a half-day of consulting, a full contract feels like overkill — and clients will tell you so.

The compromise is a short-form agreement: scope in one paragraph, fee and payment terms in a second, revision limit and IP transfer in a third, and a signature line. Five sentences can carry the essentials. The principle scales down even if the document does: what, how much, when, who owns it, how it ends.

What you should never do is skip the agreement entirely because the project is small. Small projects produce a surprising share of freelance disputes, precisely because both sides treat them casually. A one-page agreement takes ten minutes and removes the casualness.

A contract is not a weapon. It is a shared memory, signed while everyone is still happy. Write it clearly, keep it short, and send it before the work starts — because the best time to agree on the terms is when you least need them.