guide

How to Write a Simple Freelance Contract (and Protect Yourself)

Published June 25, 2026

Disclosure: Some links below are affiliate links. If you sign up through them we may earn a commission at no extra cost to you. We only recommend tools we'd genuinely suggest to a friend. See our full disclosure.

This is not legal advice. It’s a plain-language checklist of what a simple freelance agreement usually covers, to help you avoid the most common problems. Contract law varies by country and by the type of work, so for high-value, complex, or IP-heavy projects, have a qualified lawyer in your area draft or review your agreement.

A winning proposal moves a client from “interested” to “yes.” The contract is what comes after the yes — the boring document that quietly prevents almost every freelance horror story: the client who keeps adding “small” requests, the invoice that goes unpaid for three months, the “I assumed that was included” argument. It’s cheap insurance, and most freelancers skip it until the first time they get burned. Here’s how to put one together without paying a lawyer for routine work.

Why a contract matters (even for small jobs, even for friends)

The jobs where freelancers skip the contract are exactly the jobs that go wrong. A clear agreement does three things:

You’re not being distrustful by asking for one. A professional client expects it; the ones who push back on a simple, fair agreement are often the ones who’d have caused the problems it prevents.

A contract can be simple

A freelance agreement doesn’t need pages of legalese to be useful. For most routine projects, a one- or two-page plain-language document — or even a structured email both parties agree to — covers what actually matters. The goal isn’t to sound like a law firm; it’s to write down, clearly, who does what, by when, for how much, and what happens if something changes. (For large budgets or valuable IP, that’s when you bring in a real lawyer.)

What a simple freelance agreement should cover

Work through these clauses. You won’t need every one on every job, but each exists because a real dispute happens when it’s missing.

1. The parties and the date. Your name/business and the client’s name/business, plus the date. Obvious, but it’s the anchor for everything else.

2. Scope — what’s included. The single most important clause. List the specific deliverables in plain language. Then add a short line: “Anything not listed above is out of scope and will be quoted separately.” That one sentence is your defense against scope creep.

3. Deliverables and format. What the client actually receives, and how — file types, number of pages, word counts, source files (or not). “A logo” causes arguments; “three logo concepts, one chosen design delivered as PNG, SVG, and editable source files” does not.

4. Timeline (and what it depends on). A realistic delivery window, stated as “X business days from kickoff” rather than a fixed calendar date you don’t control. Add that the timeline depends on the client providing inputs and feedback within an agreed window — otherwise their delays become your missed deadlines.

5. Price and exactly what it covers. The total (or rate), tied to the deliverables listed. Be explicit about whether tax is included. If you bill hourly, state the rate and your estimate, and how overages are handled.

6. Payment terms. This is where freelancers lose the most money. Spell out:

Always get money before you start. A deposit filters out non-serious clients and means you’re never fully exposed. The contract sets the terms; a clear invoice is how you actually collect on them. (Track what comes in and goes out so tax season isn’t a surprise.)

7. Revisions. State how many rounds of revisions are included (e.g. “two rounds”), and that additional rounds are billed at your hourly rate. Without this, “just one more tweak” runs forever.

8. Changes and out-of-scope requests. A short clause that new requests outside the agreed scope are handled as a separate, quoted change. This turns scope creep from an awkward conversation into a normal, expected process.

9. Cancellation / kill fee. What happens if the client pulls out partway. A common, fair approach: the deposit is non-refundable, and work completed beyond it is billed pro rata. This protects you from doing half a project for nothing.

10. Ownership of the work (and when it transfers). Be explicit: who owns the final deliverables, and that ownership transfers only on full payment. Until then, you retain the rights. This is one of your strongest levers for getting paid. Also state whether you can show the work in your portfolio.

11. Independent contractor status. A line confirming you’re an independent contractor, not an employee — you control how the work is done and are responsible for your own taxes. This keeps the relationship clear.

12. Confidentiality (if relevant). A brief mutual confidentiality line if either side will share sensitive information. Keep it proportionate to the job.

13. Liability. A simple clause limiting your liability to the amount paid for the project is common for small freelance work. For anything where mistakes could be costly, get professional advice rather than relying on a template line.

14. How both sides agree. A signature block, or — for smaller jobs — a clear “reply ‘I agree’ to accept these terms.” Either way you want a dated record that both people agreed to the same terms before work began.

Getting it signed without friction

You don’t need expensive software. Options, roughly in order of formality:

Whatever you use, send the agreement with your proposal acceptance (“reply ‘let’s go’ and I’ll send the agreement and deposit invoice”) so signing is the natural next step, not a separate hurdle. Keep a copy of the signed version. Once it’s signed and the deposit is paid, onboard the client — a warm welcome, everything you need gathered, and clear expectations — so the project starts smoothly.

Common mistakes

When to get a real lawyer

Templates are fine for routine, lower-value work. Bring in a qualified lawyer when the stakes rise: large budgets, ongoing retainers, valuable or licensed intellectual property, regulated industries, international clients with unclear jurisdiction, or any time the downside of a dispute would genuinely hurt. A one-time review of your standard agreement is money well spent if you freelance seriously.

The honest bottom line

A good freelance contract isn’t about distrust or legalese — it’s a clear, fair, written record of what you’ll deliver, by when, for how much, and what happens if things change. For routine work a simple one- or two-page agreement (or a well-structured email both parties accept) prevents the disputes that actually happen: scope creep, unpaid invoices, and “I thought that was included.” For anything high-stakes, get it reviewed by a professional. Either way, never start the work before the terms — and the deposit — are agreed.

Skip the blank page: my Freelancer’s Client Toolkit includes a plain-language agreement template alongside the proposal, onboarding, invoice, and polite payment-follow-up templates.

Keep reading

Frequently asked questions

Do I really need a contract for small freelance jobs?

A short written agreement is worth it even for small jobs, because the small jobs are where people skip it and then argue about scope, revisions, or payment. It doesn't have to be a long legal document — even a clear email both sides agree to puts the deliverables, price, and payment terms in writing, which is usually enough to prevent the common disputes. For high-value or complex work, have a lawyer review it.

Can a freelance contract just be an email?

In many places a clear written agreement that both parties accept can be binding, and a well-structured email that states the scope, price, timeline, and payment terms — and that the client replies to agree to — is far better than nothing. That said, contract law varies by country and situation, so for anything high-stakes, get a written agreement reviewed by a professional in your jurisdiction. Treat the email approach as a sensible minimum, not legal certainty.

What should a simple freelance contract include?

At minimum: who's involved, the scope (exactly what's included and what isn't), deliverables and format, the timeline and what it depends on, the price, payment terms (deposit and due dates), how many revisions are included, what happens if the client cancels, who owns the finished work and when, and a way for both sides to agree. Those clauses cover the disputes that actually happen.

How do I get a freelance contract signed?

A free e-signature tool is the cleanest option, but a typed name and date in a replied-to email, or a clear 'I agree to the above' reply, is commonly treated as acceptance for smaller jobs. The important part is a dated record that both people agreed to the same terms before work starts — keep a copy.

Is this legal advice?

No. This is a plain-language checklist of what a simple freelance agreement usually covers, written to help you avoid the common problems. Laws differ by country and by the type of work, so for anything significant — large budgets, valuable intellectual property, regulated industries — have a qualified lawyer in your jurisdiction draft or review your contract.