What to Include in a Freelance Contract to Protect Yourself

You landed the client. You’re excited. And then you realize you have no contract — just a DM thread and a verbal “yeah, let’s do it.” Two weeks later: scope creep, late payment, and a disagreement about what “a few revisions” means. Every freelancer learns this lesson once. The smart ones learn it from other people’s stories instead of their own.

Here’s what to include in a freelance contract to protect yourself — the clauses that prevent the 90% of disputes that are actually predictable.

Why You Need a Contract (Even for Small Gigs)

“It’s just a $300 logo” — famous last words. Small gigs generate disputes at the same rate as big ones, and without a contract you have no leverage when things go sideways. A contract isn’t about distrust; it’s about clarity. Clients actually respect freelancers who use contracts — it signals professionalism. The FTC’s business guidance consistently emphasizes written agreements as basic business hygiene.

The Essential Clauses (Non-Negotiable)

1. Scope of Work (The Most Important Section)

Describe exactly what you’ll deliver, in specific terms: “Logo design: 3 initial concepts, 2 revision rounds, final files in AI, PNG, and SVG formats.” Vague scope (“design a logo”) invites infinite revisions. Specific scope lets you say “that’s outside our agreement — happy to quote it separately” without guilt.

2. Payment Terms

• Total fee and payment schedule: 50% upfront, 50% on delivery is the standard for project work. For projects over $2,000, consider thirds (start/milestone/delivery). Never start significant work with $0 down — the deposit filters out non-serious clients.
• Payment method and due dates: “Net 15” (due 15 days after invoice), not “whenever.”
• Late fees: 1.5% per month (18% annually) is standard and legal in most states. Include it — you’ll rarely enforce it, but its presence accelerates payment.
• Kill fee: if the client cancels mid-project, what do you keep? Typically the deposit plus payment for work completed. Without this clause, cancellations mean working for free.

3. Revisions and Change Requests

Define revision rounds explicitly (2–3 is standard) and state that additional revisions are billed at your hourly rate. Define what counts as a “revision” (tweaks to the agreed direction) versus a “new request” (a different direction entirely — billed separately). This single clause prevents the most common freelance dispute in existence.

4. Timeline and Deadlines

Your delivery date and the client’s responsibilities: “Final designs delivered within 10 business days of receiving all client materials and feedback.” Client delays are the #1 cause of missed deadlines — the contract should make clear the timeline depends on their responsiveness too.

5. Intellectual Property and Usage Rights

Who owns the work, and when? Standard freelance practice: you retain ownership until final payment is received, then rights transfer to the client. This is your ultimate leverage against non-payment — and it must be in writing. Also specify: can you show the work in your portfolio? (Get this in writing — “portfolio rights” disputes are depressingly common.) For licensed (not sold) work, define the license scope: where, how long, and in what media the client may use it.

6. Termination Clause

Either party can end the agreement with written notice (typically 7–14 days). Define what happens to payment and deliverables on termination: client pays for work completed through termination date; you deliver work completed to that point. Clean exits beat messy ones.

7. Confidentiality (When Relevant)

If you’ll see the client’s proprietary info, include a mutual NDA clause. Keep it reasonable in scope and duration (1–2 years typical).

Clauses Worth Adding

• Independent contractor status: clarifies you’re not an employee (tax and liability implications). One paragraph, important.
• Dispute resolution: mediation before litigation, in your county. Lawsuits are expensive for everyone; this clause encourages sanity.
• Non-solicitation (not non-compete): client won’t poach… actually for freelancers, the reverse matters: you won’t solicit the client’s clients. Keep it narrow and time-limited.
• Force majeure: neither party is liable for acts of God, pandemics, etc. Standard, include it.

Where to Get a Contract (Without a Lawyer… Initially)

• Free templates: the Freelancers Union contract template, AND CO’s free contract tool, Bonsai/HoneyBook templates. Start with these — they’re drafted by lawyers for exactly this purpose.
• Customize per project: fill in the specifics (scope, price, timeline) every time. A template with blanks is a starting point, not a finished contract.
• Lawyer review: $200–$400 for a lawyer to review your template once. Worth it when you’re doing consistent $2,000+ projects. Money well spent.
• E-signatures: DocuSign, HelloSign, or even a “reply ‘I agree'” email thread (legally binding in most contexts, though a real signature is cleaner).

Pair your contract with smart freelance pricing and tax planning and you’ve got the business fundamentals covered.

Frequently Asked Questions

Do I need a contract for work with friends and family?
Especially for friends and family. Money complicates relationships, and a contract prevents the misunderstandings that end friendships: scope, price, timeline, revisions — in writing, before starting. Frame it positively: “I do this for all my clients so we’re both clear.” Anyone offended by a simple contract is telling you something important about how the project would have gone.

What if a client refuses to sign a contract?
Walk away. A client who won’t sign a fair, standard contract is signaling one of three things: they plan to expand scope endlessly, they don’t intend to pay reliably, or they’re disorganized enough to be dangerous. None of those are clients you want. The contract conversation is also a client filter — good clients respect it, and the ones it scares off are the ones who’d have been problems.

Can I use the same contract template for every client?
The framework, yes — the specific terms (scope, price, timeline, deliverables) must be customized every time. A template with last client’s scope still in it is worse than no template; it creates confusion about what was actually agreed. Build a checklist ritual: new client → duplicate template → fill in all specifics → review → send. Five minutes of customization prevents the disputes the template exists to prevent.

Is an email agreement legally binding?
Generally yes — in most US jurisdictions, a clear email exchange showing offer, acceptance, and terms constitutes a binding contract. But “generally binding” and “practically useful” differ: a proper signed contract is clearer, more complete, and far more persuasive in a dispute. Use email agreements for tiny low-risk gigs if you must; use real contracts (with e-signature) for everything else. The formality is the point.

The Bottom Line

Every freelance contract needs: specific scope, payment terms with deposit + late fees + kill fee, defined revision rounds, mutual timeline responsibilities, IP transfer on final payment, and a termination clause. Start with a free Freelancers Union template, customize the specifics per project, and get a lawyer review once the stakes justify it. The contract doesn’t just protect you when things go wrong — it prevents most things from going wrong in the first place.