What should I include in a freelance contract to protect myself? Every freelancer learns this lesson eventually — ideally from an article, not from a client who vanished owing $3,000. A contract isn’t about distrust; it’s about clarity. The clients worth having respect it; the ones who refuse to sign are telling you exactly who they are. Here’s every clause that matters, in plain English.

You don’t need a lawyer to start — a clear written agreement (even an email summarizing terms that the client confirms) beats a handshake every time. But for projects over $1,000 or ongoing relationships, a proper contract template (Bonsai, AND CO, or your local freelancer union’s template) is worth the small cost.

The Non-Negotiable Clauses

  1. Scope of work — in detail. Exactly what you’ll deliver, in what format, how many revisions (state a number: ‘two rounds of revisions included’), and what’s NOT included. Scope creep is the #1 freelancer profit-killer, and this clause is the cure.
  2. Payment terms: total fee (or rate), payment schedule (50% upfront for new clients — non-negotiable in my book), due dates, late fees (1.5%/month is standard), and what happens on non-payment (work pauses; IP doesn’t transfer — see below).
  3. Timeline: start date, milestones, delivery dates — and what happens when the CLIENT delays (feedback due within X days; delays push the timeline accordingly). Client-caused delays are the silent killer of freelance schedules.
  4. Intellectual property transfer: specify WHEN ownership transfers — ‘upon final payment’ is the freelancer-protective standard. This means non-paying clients don’t own the work. Also clarify portfolio rights (you can show the work publicly unless NDA’d).
  5. Termination: either party can end with X days’ written notice; client pays for work completed to date (kill fee: 25-50% if cancelled mid-project).
  6. Revisions and approvals: how many rounds, who approves, response timeframes. ‘Unlimited revisions’ is a trap — never agree to it.

Clauses People Skip (Then Regret)

  • Late payment consequences: beyond fees — ‘work product remains contractor’s property until paid in full’ is your leverage. Also: you may pause all work (including other projects for the same client) on overdue invoices.
  • Confidentiality (mutual): protects both sides’ business info. Keep it reasonable in scope and duration (1-2 years, not forever).
  • Non-solicitation vs. non-compete: non-competes are increasingly unenforceable and often overreaching — push back on broad ones. A narrow non-solicitation (won’t poach their clients for 12 months) is more reasonable.
  • Dispute resolution: specify mediation before litigation, and your home jurisdiction. A $2,000 dispute isn’t worth flying across the country to litigate.
  • Liability cap: limit your liability to the contract value (‘liability capped at fees paid’). Without this, a theoretical error could expose you to unlimited damages.
  • Independent contractor status: states you’re a contractor, not an employee (tax clarity, and some clients require it for their own compliance).

What Should I Include in a Freelance Contract to Protect Myself? Red Flags in THEIR Contracts

When clients send their own paperwork, watch for: IP transfer before payment (never — payment first, always), unlimited liability or indemnification (you’re insuring their business — cap it), broad non-competes (‘won’t work in marketing for 2 years’ — absurd; negotiate to narrow or remove), net-90 payment terms (you’re financing their business — push for net-15/30), and ‘work for hire’ language combined with low pay (work-for-hire means they own everything including your process — price accordingly or decline). Big-company vendor agreements are written by their lawyers for their benefit — redline confidently; they expect it.

Making Contracts Painless (The System)

The reason freelancers skip contracts is friction — so remove it. Keep a template with blanks for scope/fee/timeline (15 minutes to customize per project). Send it with the proposal, not after the handshake — ‘here’s the agreement covering what we discussed’ is normal business, not confrontation. Use e-signature (HelloSign, DocuSign, or Bonsai’s built-in) — no printing, no scanning, no excuses. And for tiny projects under $200 with trusted repeat clients, at minimum get the scope/fee/timeline confirmed in an email they reply ‘agreed’ to. Something in writing, always.

Pair the contract with good business hygiene: pricing your work properly so the contract protects worthwhile rates, finding clients who respect professionalism, and accounting software that tracks who’s paid. The contract is one piece of a professional practice — the piece that makes all the others enforceable.

What to Do When a Client Won't Sign

It happens: great project, client balks at the contract. Don’t panic and don’t cave — diagnose first. Common reasons and responses: ‘Our legal needs to review it’ (fine — send a clean PDF, offer a 15-minute call with their counsel; 90% sign after review), ‘We’ve never used contracts’ (red flag tinged yellow — explain it’s standard protection for both sides, offer your simplest one-page version), ‘Just trust me’ (red flag burning red — the clients who most resist paperwork are statistically the ones who cause payment problems).

The fallback ladder when they won’t sign the full contract: (1) your short-form agreement (one page: scope, fee, timeline, payment terms), (2) confirmed email terms (‘Per our discussion: [scope] for [fee], 50% upfront, balance on delivery. Reply ‘agreed’ to confirm.’) — legally meaningful in most jurisdictions, (3) for tiny repeat work with trusted clients, the email confirmation alone. What you never do: start work on a large project with zero written terms because the client seemed nice. Niceness isn’t a payment mechanism.

And know your walk-away point: a client who refuses ANY written terms on a $2,000+ project is telling you about their payment practices. Thank them, decline politely, and fill the slot with someone professional. The Freelancers Union offers free contract templates and has campaigned for freelance payment protection laws — their resources are the industry standard for a reason.

The Bottom Line

What should you include in a freelance contract to protect yourself? Detailed scope with revision limits, 50%-upfront payment terms with late fees, IP transfer upon final payment (not before), termination with kill fee, liability capped at contract value, and mutual confidentiality. Use a template, e-sign everything, never do ‘unlimited revisions,’ and read client-drafted contracts for IP grabs and absurd non-competes. The contract doesn’t signal distrust — it signals you’re a professional. Professionals get paid.