How to Write a Freelance Contract That Actually Gets You Paid (+ Free Template)

Most freelance contracts you'll find online have one of two problems: they're either three lines of "I'll do X for $Y, payable on delivery" (which protects nothing), or they're 14-page legal templates copy-pasted from an agency that has lawyers on retainer (which no client will sign and you'll never enforce).

This guide is the middle path. It's the freelance contract structure used by successful independent designers, developers, writers, and consultants — the people who routinely close five-figure projects and rarely chase payments. The whole document is two to three pages. It covers the eight clauses that actually matter when things go wrong. And it's written in plain English, not legalese, so clients sign it without forwarding to their lawyer for a week of "review."

By the end, you'll have a copy-paste template you can adapt to your business in ten minutes, and the judgment to know which clauses to fight for and which to let slide.

Why a Freelance Contract Matters (Even for Small Projects)

The freelancers who get burned almost always say the same thing afterward: "We had a verbal agreement, I trusted them, the project was small." Three months later they're owed $4,200, the client has gone silent, and there's no document anywhere that proves what was agreed.

A freelance contract does four things that nothing else does:

• It locks the scope. When the client emails you on Day 14 asking for "just one more page," your contract is the reference point. Without it, every "small addition" becomes a negotiation about whether it was implied in the original ask.
• It fixes the payment terms in writing. Verbal "we'll pay you when the project is done" turns into "actually, our accounts payable runs Net 60" the moment the invoice arrives. A signed contract that says "50% deposit upfront, 50% on delivery, Net 15" is enforceable.
• It assigns IP ownership clearly. By default, in most jurisdictions, the creator of a work owns it until they assign rights — but clients almost universally assume they own what they paid for. The contract specifies which is true for this engagement.
• It gives you a graceful exit. Termination clauses define what happens if either side wants to walk away, who owes what, and which deliverables transfer. Without one, an early breakup turns into a fight.

Even for a $500 logo project, a one-page contract takes ten minutes to send and prevents the worst-case loss. Above $2,000, working without a contract is malpractice on yourself.

The Eight Clauses Every Freelance Contract Needs

Skip the boilerplate. These are the clauses that earn their place by actually mattering in disputes. If your contract has these eight, you have a contract. If it's missing any of them, you have a wish list.

1. The Parties and the Project

State who the contract is between (your legal name or business name, and the client's legal entity name — not just "Sarah" but "Sarah Chen of Greenleaf Marketing LLC"), the date, and a one-paragraph plain-English description of what's being built. The description doesn't need to be exhaustive — that comes in the scope clause — but it should be specific enough that a stranger reading the contract could tell what the project is.

Example: "This agreement covers the design and front-end implementation of a 5-page marketing website for Greenleaf Marketing LLC, including homepage, services page, case study index, individual case study template, and contact page."

2. Scope of Work (the Most Important Clause)

This is where 80% of freelance disputes are won or lost. Be specific to the point of feeling pedantic. List every deliverable, every round of revisions included, every meeting type, and explicitly what is not included.

A strong scope clause has three parts:

• Deliverables: a numbered list of every concrete output. "Homepage Figma design (desktop + mobile)" — not "website design."
• Revision rounds: how many rounds of feedback are included per deliverable. Two is a sane default. Beyond that, you bill hourly at a stated rate.
• Exclusions: the things clients commonly assume are included but aren't. Copywriting. Hosting setup. Post-launch maintenance. SEO. CMS training. Stock photo licensing fees. List them.

The exclusions list is the unsung hero of freelance contracts. It prevents the conversation where a client says "obviously the design includes the copy" and you say "no, the contract says copywriting is excluded and quoted separately at $X."

3. Timeline and Milestones

Give a start date, a target completion date, and intermediate milestones if the project is longer than three weeks. Critically, include a client-dependency clause: timeline assumes the client provides feedback within X business days, content within Y business days, and so on. If they're late, the timeline extends day-for-day.

Without this clause, a client who sits on your design for three weeks then asks why the launch date slipped will blame you. With it, you have a documented reason and (if you've structured payment by milestone) a defensible position on partial billing.

4. Payment Terms

This is the second most-fought-over clause after scope. Spell out:

• Total fee (or hourly rate + estimated hours)
• Payment schedule: deposit, milestone payments, final payment. For projects over $2,000, a 30–50% deposit is industry standard and not negotiable for most freelancers.
• Payment terms: Net 15 is a strong default for invoices. Net 30 is acceptable for established clients. Net 60+ is a financial cost to you and should be reflected in your rate.
• Late fees: 1.5% per month on overdue balances is standard and enforceable in most jurisdictions. Even if you never charge it, having it documented changes how clients prioritize your invoice.
• Accepted payment methods: bank transfer, Wise, PayPal, Stripe — whatever you accept. If you don't accept checks, say so explicitly, because someone will mail one.
• Currency: obvious but easy to forget on international projects.

For deeper guidance on which payment terms to use when, see our guide to invoice payment terms (Net 15, Net 30, Net 60) — it covers the cash-flow trade-offs in detail.

5. Intellectual Property Rights

This clause does two things: it specifies when IP transfers (almost always: upon final payment), and it specifies what transfers (the final deliverables vs. all working files, source files, intermediate drafts).

A clean default for most service work:

"Upon receipt of full payment, Client receives a perpetual, worldwide, royalty-free license to use the final deliverables for their business purposes. Freelancer retains ownership of all source files, working files, and methodologies, and may use anonymized versions of the work in their portfolio."

If the client demands full IP assignment (common for branding work and custom software), price it higher — you're giving up the ability to reuse foundational work. Some freelancers charge a 25–50% premium for full IP transfer.

6. Revisions and Change Requests

You already capped revision rounds in the scope clause. This clause handles what happens beyond that.

Two common structures:

• Hourly overage: "Additional revisions beyond the included rounds will be billed at $X/hour, with a written estimate provided before work begins."
• Change-request fee: "Material changes to the project scope require a written change request and may incur an additional fee of $X or a renegotiation of the timeline."

Use whichever fits your billing model. The point is to have a documented mechanism so "just one more thing" requests are met with a process, not a free favor.

7. Termination Clause

What happens if the client wants to cancel halfway through? What happens if you do? The termination clause defines:

• Notice period: typically 7–14 days written notice.
• Kill fee: the client pays for all work completed to date plus a percentage of remaining unbilled work (commonly 25–50%). This compensates you for the opportunity cost of having blocked time for their project.
• Deliverables on termination: what the client receives in exchange for the kill fee. Usually: all completed work in its current state, no further revisions.
• Non-refundable deposit: explicitly state that the upfront deposit is non-refundable. Without this, a client who cancels on Day 3 may demand it back.

8. Independent Contractor Status

A short paragraph confirming that you are an independent contractor, not an employee. You're responsible for your own taxes, insurance, and equipment. The client has no obligation to provide benefits, withhold taxes, or treat you as staff. This protects both parties from misclassification claims, which are surprisingly common and surprisingly expensive.

The Optional Clauses (Use Judgment)

These aren't required for most projects, but they're worth including when relevant:

• Confidentiality / NDA: if you'll see sensitive business information. Two-paragraph mutual NDAs are sufficient for 95% of cases.
• Non-solicitation: the client agrees not to hire your subcontractors directly for X months. Relevant if you bring in collaborators.
• Indemnification: each party agrees to cover damages caused by their own breach. Boilerplate but worth including for projects above $10,000.
• Limitation of liability: caps your maximum liability at the contract value. Essential for any project where a mistake could cause damages above your project fee.
• Governing law / jurisdiction: which state or country's laws apply, and where disputes would be heard. Default to your home jurisdiction.
• Force majeure: neither party is liable for delays caused by events outside their control. Worth including in any contract with a hard deadline.

Red-Flag Clauses to Refuse

Sometimes a client will send back your contract with edits — or insist you sign theirs. Watch for these:

• Unlimited revisions. No professional services work this way. Cap them.
• Payment on "client satisfaction." Satisfaction is subjective and unenforceable. Payment must trigger on delivery of specified deliverables.
• Net 90 or longer without a premium. Long payment terms are a hidden discount. Reprice or refuse.
• Full IP assignment with no premium. If they want everything, they pay for everything.
• Indemnification of the client without a mutual provision. One-way indemnification is a trap.
• Non-competes that survive after the project. A 6-month industry non-compete on a $3,000 project is a deal-breaker.
• Mandatory arbitration in a jurisdiction you can't afford to travel to. If the client's "neutral arbiter" is across the country, you can't realistically enforce anything.

You're allowed to push back on all of these. Most clients added them because their lawyer said to, not because they care. If they're inflexible on a red-flag clause, ask why — sometimes there's a real reason, but more often they'll concede when asked directly.

Copy-Paste Freelance Contract Template

Here's a complete two-page contract you can adapt. Replace the bracketed sections with your specifics. This is a starting point — for projects over $10,000 or in regulated industries (health, finance, legal), have a lawyer review your standard agreement once.

FREELANCE SERVICES AGREEMENT

This Agreement is made on [DATE] between:

Freelancer: [Your full legal or business name], located at [your address]
Client: [Client full legal entity name], located at [client address]

1. PROJECT OVERVIEW
Freelancer agrees to provide the following services to Client:
[One-paragraph plain-English description of the project]

2. SCOPE OF WORK
Deliverables:
- [Deliverable 1, specific]
- [Deliverable 2, specific]
- [Deliverable 3, specific]

Revisions included: [2] rounds per deliverable.

Explicitly excluded from this scope: [copywriting / hosting / SEO / etc.]
Additional services may be added via written change request at [$X/hour].

3. TIMELINE
Start date: [date]
Target completion: [date]
Milestones:
- [Date]: [milestone deliverable]
- [Date]: [milestone deliverable]

Timeline assumes Client provides feedback within [3] business days of each request and required content/assets within [5] business days of project start. Client delays will extend the timeline day-for-day.

4. FEES AND PAYMENT
Total project fee: [$X,XXX] (in [USD/EUR/GBP])

Payment schedule:
- [50%] deposit due upon contract signing, before work begins
- [50%] balance due upon delivery of final deliverables

Payment terms: Net 15 from invoice date.
Late fees: 1.5% per month on any balance outstanding after the due date.
Accepted payment methods: bank transfer, [PayPal/Wise/Stripe].
The deposit is non-refundable.

5. INTELLECTUAL PROPERTY
Upon receipt of full payment, Client receives a perpetual, worldwide, royalty-free license to use the final deliverables for their business purposes. Freelancer retains ownership of all source files, working files, and methodologies, and may use anonymized versions of the work in their portfolio.

6. TERMINATION
Either party may terminate this Agreement with [14] days written notice.

On termination by Client: Client pays for all work completed to date plus a [25%] kill fee on remaining unbilled scope. Client receives all completed work in its current state.

On termination by Freelancer for non-payment: Freelancer retains all work product and any deposits paid until outstanding balances are settled.

The deposit is non-refundable in all termination scenarios.

7. INDEPENDENT CONTRACTOR
Freelancer is an independent contractor, not an employee of Client. Freelancer is responsible for their own taxes, insurance, and equipment.

8. CONFIDENTIALITY
Both parties agree to keep confidential any non-public business information shared during the engagement, for a period of [2] years after the project ends.

9. LIMITATION OF LIABILITY
Freelancer's total liability under this Agreement shall not exceed the total fees paid by Client. Neither party shall be liable for indirect, consequential, or punitive damages.

10. GOVERNING LAW
This Agreement is governed by the laws of [your state/country], and any disputes shall be resolved in the courts of [your city/region].

Agreed and accepted:

_______________________     _______________________
Freelancer (date)            Client (date)

How to Get Clients to Actually Sign It

A contract no one signs is worthless. Three tactics that consistently get signatures:

• Send it before the proposal feels "final." Don't treat the contract as a separate step that happens after agreement. Send it with your proposal, framed as "here's how I work — happy to adjust any clause that doesn't fit." This normalizes signing.
• Use e-signature software. DocuSign, HelloSign, PandaDoc, or even a free tool like Dropbox Sign reduces the friction from "print, sign, scan, email" to two clicks. Sign-completion rates roughly double.
• Tie work-start to signature, not the other way around. "I'll get started as soon as the contract is signed and the deposit lands" is a firm but professional position. Working in advance of signature is how freelancers get burned.

If a client is dragging on signing, ask politely what's holding it up. Often they have one specific concern (an IP clause, a timeline question) that takes five minutes to resolve. Generic "I'll get to it" replies usually mean the project is cooling and you're better off knowing now.

Contract vs. Proposal vs. Statement of Work

These three documents often get conflated. They serve different purposes:

• Proposal: a sales document. It pitches your approach, your qualifications, and your price. It's not binding and rarely signed.
• Contract: the legal agreement. It defines rights, obligations, and remedies. Signed by both parties.
• Statement of Work (SOW): a project-specific addendum to a master contract. Common when you have an ongoing relationship and run multiple projects under one umbrella agreement.

For most freelance engagements, a single contract that contains both the legal terms and the specific scope is sufficient — no separate proposal or SOW required. Larger client relationships (especially with enterprises) often want a master services agreement plus SOWs per project, so the legal terms are negotiated once and reused.

The Contract-Plus-Invoice Workflow

The contract sets the terms; the invoice triggers the money. Together they're the engine of a freelance business that actually gets paid. Once your contract is signed and the deposit invoice is issued, the structure of the engagement runs itself:

1. Signed contract on Day 0
2. Deposit invoice issued same day (Net 15)
3. Deposit lands → work begins
4. Milestones hit → milestone invoices issued (Net 15)
5. Final delivery → final invoice issued (Net 15)
6. Final payment lands → IP transfers per contract

This rhythm — contract first, then a series of structured invoices — is what separates predictable freelance income from chaotic "remember to send the invoice" patterns. InvoiceAgent handles the invoice side: describe each milestone in plain English ("50% deposit for Greenleaf website project, Net 15") and you have a professional PDF in under a minute, with payment terms and late-fee language that match what's in your contract.

Write the contract once, reuse it for every project (with the specifics swapped in), and you've eliminated the single biggest source of freelance disputes. The first contract takes an afternoon. Every contract after that takes ten minutes. The compounding return on that one afternoon of work is the difference between freelancing as a side hustle and freelancing as a real business.

Related Reading

• Invoice Payment Terms Explained: Net 15, Net 30, Net 60 (And When to Use Each)
• 5 Polite but Firm Email Templates to Chase Late Payments
• How to Handle Clients Who Don't Pay (Without Burning Bridges)
• Best Practices for Setting Up Recurring Invoices