Five clauses every freelance contract needs

Most freelance disputes are not about bad work or bad clients. They are about two people who assumed they were agreeing to the same thing and discovered, weeks later, that they were not. A contract is the cheapest insurance against that outcome. It does not have to be long. It does have to cover five areas clearly.

This is a practical guide for independent contractors, designers, developers, writers, and consultants. It is not a template to copy and paste. It is a checklist for what needs to be written down before work begins.

1. Scope of work

Scope is where most freelance agreements fail, because scope is the part that feels boring compared to the creative work itself. Resist the urge to be vague. A good scope section describes three things:

• Deliverables. What, specifically, is being produced? "A new website" is not a deliverable. "A five-page responsive marketing site with a home page, about page, three feature pages, and a contact form, delivered as Next.js source code in a Git repository" is a deliverable.
• Revisions. How many rounds? What counts as a revision versus a new request? A common structure is two rounds of revisions included, with additional rounds billed at an hourly rate.
• Out of scope. It is almost more important to say what you are notdoing. Hosting, ongoing maintenance, content writing, SEO, and integrations with third-party systems are common items freelancers assume are excluded but clients assume are included.

A scope that fits on one page is usually good enough. A scope that would fit in a text message is not.

2. Payment terms

Getting paid is not automatic. Write down exactly when money changes hands and what happens if it doesn't.

• Amount and structure. Fixed fee, hourly, retainer, or milestone-based. For projects over a few thousand dollars, milestone billing protects both sides.
• Deposit. A non-refundable deposit — typically 25% to 50% of the total — before work begins. Clients who balk at a deposit are telling you something about how they will treat invoices later.
• Invoice schedule. When do you send invoices? When are they due? "Net 15" or "Net 30" is standard; anything longer should be compensated with a higher rate.
• Late fees. A flat late fee or a monthly percentage on overdue balances. Enforceability varies by jurisdiction, but the existence of the clause changes client behavior.
• Expenses. Are they billed separately? With a markup? With receipts required?

3. Intellectual property

This is the clause that matters most and the one freelancers think about least. Two questions have to be answered:

• Who owns the final deliverable? In most jurisdictions, the default under copyright law is that the creator owns their work. For the client to own the finished product, the contract must explicitly assign the rights — and most clients assume assignment is the deal.
• What about the tools, libraries, and background IP? If you reuse components you built for other clients, or open-source libraries, the contract should say the assignment only covers the custom work delivered, and you retain a license (or the underlying license flows through) for the reusable pieces.

A common structure: you keep ownership until final payment; on final payment, ownership of the delivered work transfers to the client; you retain a perpetual, non-exclusive right to use the work in your portfolio. Adjust for your field — photographers and designers usually negotiate broader portfolio rights than developers.

4. Termination

Projects end before they should. Sometimes the client runs out of money; sometimes the collaboration just does not work; sometimes you realize six weeks in that the scope was wrong. The contract should say what happens.

• Termination for convenience. Either party can end the engagement with written notice — typically 7 or 14 days. The client pays for work completed up to termination, plus any committed costs.
• Termination for cause. Either party can end the engagement immediately for material breach, non-payment, or similar serious issues, usually after a short cure period.
• Kill fee. For fixed-price projects, a minimum payment owed if the client terminates mid-project, so you are not left with half a deliverable and no compensation for the ramp-up.
• What happens to the work. If the project is terminated before final payment, do you hand over what exists? Or does ownership stay with you until paid in full? Be explicit.

5. Dispute resolution

Most disputes are resolved with a phone call and a discount. For the rest, the contract should say how disagreements are handled so you don't end up reading small claims court rules on a Tuesday morning.

• Informal resolution first. A clause requiring both parties to attempt to resolve disputes through direct discussion for 30 days before escalating. Cheap, and often sufficient.
• Mediation or arbitration. For larger engagements, binding arbitration can be faster and cheaper than court. For smaller engagements, it can be more expensive and is often skipped.
• Governing law and venue. Which state's law applies, and which court (or arbitration forum) hears the case. Usually the freelancer's home state, but this is negotiated.
• Attorneys' fees. A prevailing-party attorneys'-fees clause encourages reasonable behavior on both sides, since frivolous claims become expensive.

One more thing: signatures and timing

A contract that is not signed is a document, not a contract. Get signatures before work begins — ideally before the deposit is even invoiced. "I'll send it over next week" is how freelancers end up doing the first third of a project without an agreement in place and then quietly forgetting to circle back.

Five clauses, one page of scope, signatures before the first line of work. This is enough for most freelance engagements, and it is an enormous improvement over the handshake-plus-invoice pattern that so many independent workers rely on.

This article is for general information only and is not legal advice.