Freelance Contract Basics

A contract spells out what you’ll do, when you’ll get paid, and what happens if things go wrong. This guide covers what to include and how to keep it simple.

Many freelancers skip a contract for “small” jobs or trusted clients, only to run into scope creep, payment delays, or disagreements about ownership. A written agreement doesn’t have to be long or legalistic—it just needs to state scope, payment, and what happens when things change. Once both parties sign, you have a reference for the rest of the project.

We'll cover what a freelance contract typically includes, why it matters for protection and professionalism, and how to create and use one without overcomplicating things. For large or high-risk engagements, a lawyer review is wise; for most projects, a solid template plus project-specific edits is enough.

A freelance contract is a written agreement between you and a client. It usually covers scope of work, deliverables, timeline, payment terms, revisions, ownership of work, and how to end or change the project. It doesn’t have to be long—clear and signed is what matters.

Scope describes what you will deliver (e.g. “Logo design, up to 3 concepts, 2 rounds of revisions, final files in X formats”). Payment terms state the amount, when it’s due (e.g. 50% upfront, 50% on delivery), and how to pay. Revision limits prevent endless “small tweaks.” Ownership (work for hire vs. license) determines who can use the work and how. A change-order or out-of-scope clause says that work beyond the agreed scope is billed separately. Some contracts also address confidentiality, liability caps, and termination. You want to leave no ambiguity about what’s in, what’s out, and what happens when the client asks for more.

Contracts reduce misunderstandings and give you something to point to when scope creeps or payment is late. They also look professional and can protect your rights to use work in your portfolio or clarify that you’re not an employee.

Without a contract, “we agreed to a logo” can become “we thought the whole brand was included.” When payment is late, you have no written due date to point to. When the client wants to own everything including your process, you have no clause to fall back on. A contract also helps with client classification: in many places, a written agreement that specifies project-based work and no benefits supports your status as an independent contractor rather than an employee. Finally, clients often take you more seriously when you have a clear, professional agreement—it signals that you run a real business.

A designer uses a two-page contract: project description, number of rounds of revisions, payment schedule (50% upfront, 50% on delivery), timeline, and a clause that extra work is billed separately. When the client asked for a full rebrand instead of a logo, she referred to the scope and sent a change order for the additional work.

A developer’s contract includes: scope (e.g. “Landing page, 5 sections, CMS integration”), timeline (4 weeks from kickoff), payment (50% to start, 50% on launch), revision limit (2 rounds), and a clause that additional features are quoted separately. When the client requested a blog and contact form that weren’t in scope, he sent a short change order with hours and rate; the client approved and he added the work without eating into his margin.

Working without a contract. Vague scope (“design work” with no deliverables or limits). No payment schedule or late-payment terms. No mention of revisions or extra work. Signing a client’s contract without reading it or striking unfair terms.

Other mistakes: agreeing to “work for hire” or full assignment of rights without understanding that you may give up portfolio and reuse rights; not stating what happens if the project is cancelled (e.g. kill fee or payment for work done); and skipping a clause that you’re an independent contractor so the client doesn’t treat you as an employee for tax or benefit purposes. Also avoid verbal “we’ll figure it out” for key terms—get scope, price, and payment schedule in writing before you start.

Use a template and customize per project. Define deliverables and number of revision rounds. Include payment amount, due dates, and method. Add a clause that work beyond scope is extra. Both parties should sign; keep a copy. For big deals, a lawyer review is worth it.

Keep one master contract and duplicate it for each job; change only scope, price, dates, and client name. Send the contract with the proposal or right after the client says yes, and don’t start work until it’s signed. If the client sends their contract, read it for scope, payment, ownership, and liability; negotiate or strike clauses that are unfair (e.g. unlimited liability, assignment of all IP without portfolio rights). Store signed contracts in a folder or cloud so you can find them if a dispute arises.

A simple contract protects both sides. Get the basics in writing and adjust as you learn what causes disputes.

Include scope, payment terms, revision limits, and a clear statement that work beyond scope is extra. Both parties sign and keep a copy. When scope creeps, refer to the contract and issue a change order instead of doing free work. Update your template when you discover gaps (e.g. you add a kill-fee clause after a cancelled project). With a consistent contract habit, you’ll reduce disputes and look more professional to clients and partners.