Freelance Contract Template: What to Include and a Copy-Paste Starting Point
Published · Updated
Why a Word doc contract keeps costing you money
Most freelancers start with a contract they found online, change the logo, and email it as a PDF. It works until a client asks for "just one more round" of revisions, or disappears after milestone one, or claims they never agreed to the payment schedule because the email thread got messy. A contract only earns its keep if it answers those disputes before they happen — and if the client actually signs it.
Below is what a freelance contract needs, a template you can copy into a doc right now, and the clauses people skip that cause the most damage later.
The clauses a freelance contract actually needs
| Clause | What it does | What happens if you skip it |
|---|---|---|
| Parties & effective date | Names the legal entities and when the agreement starts | Ambiguity over who's liable — you, or your LLC |
| Scope of work | Lists exactly what's included | Scope creep — "can you also just..." |
| Deliverables & format | Specifies file types, sizes, platforms | Client expects a Figma file, you send a PDF |
| Timeline & milestones | Dates tied to payments | Project drags with no leverage to push back |
| Payment terms | Amount, schedule, late fee, currency | Chasing invoices with no contractual late fee to cite |
| Revision limits | Number of rounds included | Unlimited unpaid revisions |
| Ownership & IP transfer | When rights transfer (usually on final payment) | Client uses your work before paying |
| Termination | How either side exits, and what's owed | Client vanishes mid-project, you're owed nothing on paper |
| Confidentiality | Protects both sides' information | Client shares your process with a competitor |
| Liability cap | Limits your exposure if something goes wrong | Uncapped liability for a $2,000 project |
| Governing law | Which jurisdiction applies to disputes | Expensive to enforce if it ever goes to court |
| Signatures | Makes it enforceable | It's not a contract, it's a proposal |
If your current template is missing more than two or three of these, it's not doing its job.
A freelance contract template you can use
This is a plain-language structure, not legal advice — for high-value or ongoing work, have a lawyer in your jurisdiction review it once and reuse the reviewed version.
FREELANCE SERVICES AGREEMENT
This Agreement is between [Your Name / Business Name] ("Freelancer")
and [Client Name / Company] ("Client"), effective [date].
1. SCOPE OF WORK
Freelancer will provide: [describe the work — e.g. "design and
development of a 5-page marketing website"]. Anything not listed here
is considered out of scope and will be quoted separately.
2. DELIVERABLES
Freelancer will deliver: [list files/formats, e.g. "final source files
in Figma, exported assets in PNG/SVG"].
3. TIMELINE
Project start: [date]
Milestone 1: [description] due [date]
Milestone 2: [description] due [date]
Final delivery: [date]
4. PAYMENT
Total fee: [amount/currency]
Payment schedule: [e.g. "50% deposit before work begins, 50% on
delivery"]
Late payments: [e.g. "1.5% per month on overdue balances"]
5. REVISIONS
This project includes [number] rounds of revisions. Additional
revisions are billed at [hourly rate].
6. OWNERSHIP
All rights to deliverables transfer to Client upon receipt of full
payment. Until then, all work remains the property of Freelancer.
7. TERMINATION
Either party may terminate with [number] days written notice. Client
will pay for all work completed up to the termination date.
8. CONFIDENTIALITY
Both parties agree not to disclose confidential information shared
during the course of this project.
9. LIABILITY
Freelancer's total liability under this Agreement will not exceed the
total fees paid by Client.
10. GOVERNING LAW
This Agreement is governed by the laws of [your jurisdiction].
Signed:
_______________________ _______________________
Freelancer Client
Date: ____________ Date: ____________
Adapt the bracketed sections to your work. A photographer's deliverables clause looks nothing like a developer's, but the skeleton holds.
The mistakes that show up in real disputes
No cap on revisions. "A few rounds of feedback" isn't a number. Write "2 rounds" or "10 hours of revision time," not an adjective.
IP transfer on signing instead of on payment. If ownership transfers when the contract is signed rather than when you're paid, a client can use your work and stop paying with no leverage left on your side.
No late fee written down. You can't charge one after the fact just because you're annoyed. It has to be in the contract before the invoice is late.
Sending it as a static PDF. A contract that lives in an email thread has no record of whether the client opened it, when they signed, or which version they signed. That matters if it's ever disputed.
Getting it actually signed
A template solves half the problem. The other half is getting a client to read and sign it without five email round-trips.
Frelvo doesn't ship a pre-built library of fill-in-the-blank contracts — what it gives you instead is a contract builder plus AI drafting, where you describe the project in a sentence or two and get a first draft to edit, and an e-signature flow built into the same client portal you already use for invoices and files. The client opens one link, sees the project, signs the contract, and can pay the deposit invoice on the same page. No separate e-signature tool, no PDF attachments, no "did you get my email."
E-signatures, invoicing and the client portal are on every Frelvo plan, including the free one — you don't need to upgrade just to send a signable contract.