There's a moment every freelancer dreads. A project you've poured weeks of work into stalls out. The client asks for "just a few more changes" that turn into a full redesign. Or the invoice comes due and the payments stop. When you ask what you agreed to, the answer is: nothing in writing.

A good freelance contract won't stop difficult clients from existing. But it will give you something far more valuable: clarity. Clarity about what you're delivering, when you'll get paid, what happens if things go sideways, and who owns the work when it's done. Most freelance disputes don't happen because people are dishonest — they happen because everyone remembered the conversation differently.

Here's what a contract that actually protects you needs to include.

The Scope of Work: Be Specific to the Point of Discomfort

Vague scope is the root cause of most freelance problems. "Design a website" sounds clear in a kickoff call. Three months later, you're on your sixth revision of the homepage and the client is asking why the e-commerce integration wasn't included in the original price.

Your scope of work section should describe deliverables so specifically that a stranger reading it would know exactly what's included — and what isn't. Good scope language looks like this:

  • Design of up to 5 unique page templates (Home, About, Services, Blog, Contact)
  • Up to 2 rounds of revisions per page template
  • Mobile-responsive layouts for all pages
  • Delivery as static HTML/CSS files; does not include CMS integration or backend development

That last bullet — the "does not include" — is often more important than what you do include. Explicitly calling out what's out of scope eliminates the "I thought that was part of it" conversation before it starts.

A useful rule of thumb: if you have to think about whether something is included, write it down. If it's clear it's not included, write that down too.

Payment Terms: More Than Just an Amount

Your contract should specify not just your rate, but every aspect of how and when you get paid:

  • The total amount — or your rate and the estimated hours/milestones if billing hourly or by phase
  • Deposit requirement — most freelancers require 25–50% upfront, especially for new clients
  • Payment schedule — upon milestone completion, on specific dates, or net-15/net-30 after invoice
  • Accepted payment methods — bank transfer, check, PayPal, etc.
  • Late payment fees — typically 1.5–2% per month on overdue balances
  • What happens if a payment is missed — work pauses, project is suspended, etc.

The deposit clause alone changes the dynamic of the relationship. A client who won't put any money down before work begins is a risk. A deposit aligns incentives: the client has skin in the game and you're not working for free while they "decide if they want to proceed."

Revision Limits: The Clause That Saves Your Sanity

Unlimited revisions sounds like a selling point. In practice, it's a liability. Without a cap, every round of feedback can restart the clock indefinitely. Some clients genuinely don't know what they want until they see it — and without a revision limit, your project has no end.

Be explicit: specify how many rounds of revisions are included in the price, and what happens when you exceed them. A common approach:

  • Two rounds of revisions are included in the project fee
  • Additional revision rounds are billed at $X/hour
  • A "revision" means changes requested within 5 business days of delivery; new feedback after that period constitutes a new revision round

The last point matters more than people realize. Without it, a client can drip feedback over weeks and claim it all counts as one revision.

Intellectual Property: Who Owns What, and When

By default in the US, the creator owns the work. Copyright vests with the author at the moment of creation. If you want the client to own the final work, that transfer has to be explicit in the contract.

Most freelance contracts use one of two approaches:

  1. Assignment — Full ownership of the final deliverable transfers to the client upon final payment. This is the most common approach for client work.
  2. License — You retain ownership but grant the client a license to use the work. This is more common for stock assets, photographs, or when you want to retain the right to show the work in your portfolio.

Two important additions here: First, ownership transfer (or the license taking effect) should be contingent on full payment. If the client hasn't paid, they don't own the work. This gives you real leverage. Second, specify whether you retain the right to display the work in your portfolio — most clients will agree to this, but get it in writing.

Scope Creep: The Change Order Clause

Scope creep is when a project gradually expands beyond what was originally agreed to, usually one small request at a time. "Can you just add a contact form?" "Can you also do the social media graphics?" "While you're at it, can you write the copy too?"

The change order clause is your defense. It should state that any work outside the defined scope requires a written change order — a brief document that describes the additional work, the additional cost, and requires the client's signature before you begin.

In practice, you don't need formal paperwork for a $50 addition. But having the clause in the contract means you can point to it when a client insists that the extra work "should be covered." It resets the conversation from "why are you being difficult" to "here's what we both agreed to."

Project Timeline and Client Responsibilities

Contracts typically focus on what the freelancer will do. But the timeline often depends just as much on the client. If they take three weeks to approve a draft, the final deadline moves — or should.

Include language that:

  • States the estimated project timeline and any key milestone dates
  • Specifies how many business days the client has to provide feedback at each stage
  • Makes clear that delays caused by late client feedback extend the project timeline accordingly
  • Addresses what happens if the project stalls due to client inaction for more than X weeks (you're within your rights to treat the project as complete and invoice accordingly)

This last point is worth highlighting. Projects that drag on indefinitely are expensive — you're holding capacity, answering questions, and staying mentally engaged with something you can't close out. The "abandonment" clause lets you declare the project complete and collect payment if the client goes dark.

Termination: What Happens If It All Falls Apart

Sometimes projects end before they're finished. You need a termination clause that's fair to both sides:

  • Termination for convenience — Either party can end the project with reasonable notice (typically 7–14 days). If the client terminates, they pay for all work completed to date plus a kill fee (often 25% of the remaining project value).
  • Termination for cause — If one party materially breaches the contract (the client doesn't pay, you don't deliver), the other party can terminate immediately. Define what constitutes a breach.

The kill fee is the most important element here. Without it, a client can terminate the moment you've done 80% of the work and owe you nothing beyond what's been invoiced. A kill fee means there's a cost to changing their mind.

Confidentiality and Non-Disclosure

Many clients will ask you to sign their NDA. That's fine — most are reasonable. But your contract should also include confidentiality provisions that protect you. Specifically:

  • You agree not to share the client's confidential business information
  • The client agrees not to share your proprietary processes, rates, or terms with third parties
  • Both parties agree on what counts as "confidential" (typically anything marked as such, or anything a reasonable person would consider sensitive)

This is also where you clarify your right to discuss the project publicly — including in your portfolio, case studies, or as a reference. Get explicit permission in writing, even if the client says "of course, no problem" verbally.

Dispute Resolution: How You'll Handle Disagreements

Nobody signs a contract expecting to use the dispute resolution clause. But it's one of the most important ones to have. At minimum, specify:

  • Governing law — Which state's laws apply to the contract
  • Jurisdiction — Where disputes would be heard (typically your state)
  • Resolution process — Many freelancers prefer mandatory mediation before arbitration, which keeps disputes out of court

For most freelance projects, you'll never need this clause. But specifying your home state as the governing jurisdiction means that if a dispute does arise, you're not flying to the client's city to resolve it.

Getting Signatures: Make It Easy

A contract that exists only on your computer provides zero protection. You need a signed copy before work begins.

The easiest approach today is e-signature software. DocuSign, HelloSign (now Dropbox Sign), and PandaDoc all allow you to send a contract and get a legally binding signature without anyone printing a piece of paper. Clients can sign on their phone in under a minute, which removes the friction that makes people procrastinate.

Never start work without a signed contract. Not even "just the first part." Not even for a client you've worked with before. The one time you skip it will be the one time you needed it.

Building Your Template

You don't need a lawyer to draft your first freelance contract — though having one review it is worthwhile if you're doing high-value work. Start with a reputable template (the Freelancers Union and AIGA both publish solid ones), customize it to your services, and run it by any long-term clients for their input before you lock it in.

Over time, your contract becomes a living document. Each project teaches you something new about what needs to be clearer. Add the clause you wish you'd had. Remove the language that caused confusion. In a few years, you'll have a contract that's been field-tested in dozens of real projects — and that's more valuable than anything a lawyer drafts from scratch.

The goal isn't to turn every client relationship into an adversarial legal exercise. It's to have a shared document that both of you can point to when memory fails and expectations diverge. A good contract doesn't prevent trust — it makes trust possible by removing ambiguity.