Every freelancer has a story about the project that went wrong. The client who kept requesting changes until the scope doubled. The startup that disappeared after receiving the final deliverables without paying. The company that published your work under their name and then hired someone cheaper to maintain it.
The difference between freelancers who recover from these situations and those who absorb the loss almost always comes down to one thing: whether they had a contract.
A freelance contract is not a formality. It is the document that defines what you will deliver, what you will be paid, who owns the work, and what happens when something goes wrong. This guide walks through every section of a freelance contract, clause by clause, so you can create one that actually protects you.
Why Every Freelance Project Needs a Contract
Freelancing without a contract is working without a safety net. Here is what a well-drafted contract protects against:
Non-payment. A contract with clear payment terms, due dates, and late fees gives you legal standing to collect what you are owed. Without one, you are relying on the client's goodwill.
Scope creep. "Can you also just quickly..." is the sentence that turns a two-week project into a two-month one. A contract with a defined scope and change order process puts a boundary around what is included — and makes additional work a separate, paid engagement.
IP disputes. Who owns the logo, the codebase, the copy? Without a contract specifying IP ownership, the answer depends on jurisdiction-specific default rules that may not favor you.
Cancellation losses. If a client cancels after you have turned down other work to make room for their project, a kill fee clause ensures you are compensated for the opportunity cost.
The Anatomy of a Freelance Contract That Works
Section 1: Parties and Project Overview
Start with the basics. List the full legal names and addresses of both parties. If the client is a company, use the registered business name — not the name of the person you have been emailing.
Include a brief project overview: one to two sentences describing the nature of the engagement. This is not the scope of work — it is context. For example: "This agreement covers the design and development of a marketing website for [Client's Company]."
Section 2: Scope of Work
This is the most important section of your contract. A vague scope is the root cause of most freelance disputes.
For each deliverable, specify:
- What you will deliver (e.g., "5-page responsive marketing website")
- Format of the deliverable (e.g., "Figma design files and deployed Next.js application")
- Standards or requirements (e.g., "WCAG 2.1 AA compliant, loads under 3 seconds on mobile")
- Revision rounds included (e.g., "2 rounds of revisions per page design")
- What is not included (e.g., "Content writing, stock photography, and ongoing maintenance are not included in this scope")
The "not included" list is just as important as the deliverable list. It sets expectations and gives you a clear reference point when a client requests additional work.
Section 3: Timeline and Milestones
Break the project into phases with specific deadlines. For each milestone, specify:
- The deliverable or phase completion criteria
- The delivery date
- The client review period (e.g., "Client will provide feedback within 5 business days")
- The consequence of missed client deadlines (e.g., "Project timeline will shift by the number of days feedback is delayed")
Include a clause stating that final delivery dates are contingent on the client providing necessary materials (content, brand assets, access credentials) on time. If the client delays, your deadlines shift proportionally.
Section 4: Payment Terms
This section should leave no room for interpretation.
Fee structure. State the total project fee or hourly rate. If hourly, include an estimated range and a cap that requires client approval before exceeding.
Payment schedule. For project-based work, structure payments around milestones:
- 30–50% deposit before work begins (non-refundable after project kickoff)
- 25–35% at a defined midpoint milestone
- Remaining balance upon final delivery
Payment terms. Specify when payment is due (e.g., "Net 15 — payment due within 15 days of invoice date").
Late payment penalties. Include a late fee — typically 1.5 to 2 percent per month on overdue balances. Also specify that you may pause work if payment is more than a set number of days overdue.
Accepted methods. List the payment methods you accept (bank transfer, PayPal, etc.) and who pays any transaction fees.
Section 5: Intellectual Property
IP ownership is where freelancers most often get burned. Address these points explicitly:
Work product ownership. Specify that all work product created for the project becomes the client's property upon receipt of final payment. This is the standard arrangement — the client pays for the work and receives full ownership.
Pre-existing IP. If you are bringing existing tools, libraries, templates, or code to the project, list them and specify that you retain ownership. Grant the client a non-exclusive license to use these materials as part of the delivered work.
Portfolio rights. Reserve the right to display the work in your portfolio and on your website. Clients occasionally request confidentiality — if so, negotiate a time-limited restriction (e.g., "Freelancer may not display the work publicly for 6 months after delivery").
Conditional transfer. State that IP ownership does not transfer until the client has paid in full. If the client defaults on payment, you retain ownership of all work product.
Section 6: Revisions and Change Orders
Revisions are modifications to deliverables within the original scope. Specify how many rounds are included and what constitutes a "round" (e.g., "A revision round consists of one consolidated set of feedback from the client").
Change orders cover work outside the original scope. Require a written change order signed by both parties before beginning any additional work. The change order should specify the additional deliverables, the fee for the extra work, and the impact on the project timeline.
This distinction matters. Clients who request revision after revision are staying within scope (up to your limit). Clients who request entirely new features or deliverables are outside scope and should be billed separately.
Section 7: Cancellation and Kill Fee
Projects get cancelled. What matters is how the financial impact is handled.
Client cancellation. If the client cancels, they pay for all work completed to date plus a kill fee (typically 25 to 50 percent of the remaining project value). The deposit is non-refundable.
Freelancer cancellation. If you need to cancel, refund any payments received for work not yet delivered. Provide reasonable notice and, if possible, deliver any work in progress in a usable state.
The kill fee rationale. You turned down other projects to reserve time for this client. The kill fee compensates for that lost opportunity. Without it, a client can cancel mid-project and leave you with weeks of unbooked time.
Section 8: Confidentiality
If the project involves the client's proprietary information — business strategies, unreleased products, customer data — include a confidentiality clause. Specify what information is confidential, the duration of the obligation, and the standard exceptions (publicly available information, information you already knew, etc.).
Keep the confidentiality clause reasonable. An obligation lasting 2 to 3 years after project completion is standard. Indefinite obligations or overly broad definitions may discourage you from taking similar work in the future.
Section 9: Dispute Resolution
Specify how disputes will be resolved before they happen. A typical escalation:
- Good faith negotiation — the parties attempt to resolve the issue directly
- Mediation — a neutral mediator helps both parties reach a settlement
- Arbitration or litigation — binding resolution through an arbitrator or court
Mediation is significantly cheaper and faster than litigation. Requiring it as a first step saves both parties time and money.
Specify the governing law (which state's laws apply) and the jurisdiction (where disputes will be heard).
Section 10: Signatures
Both parties must sign and date the contract before work begins. Include signature lines with printed name, date, and title (if applicable). Digital signatures are legally valid in all 50 US states under the ESIGN Act and in most countries under their respective electronic signature laws.
Mistakes That Make Freelance Contracts Unenforceable
No written scope. "We discussed it on a call" is not a scope of work. If it is not written down, it does not exist.
Vague payment terms. "Payment upon completion" without defining what "completion" means invites disputes. Tie payments to specific, measurable milestones.
Missing IP clause. Default IP rules vary by jurisdiction and may not give you or the client what either party expects. Always specify ownership explicitly.
No late payment consequence. Without a late fee and a right to pause work, you have no leverage when a client delays payment.
Unlimited revisions. "Revisions until the client is satisfied" is an open-ended commitment. Cap revision rounds and define what each round includes.
Sending Your Contract With Confidence
The moment you send a contract to a client is the moment your working relationship becomes professional. A well-structured freelance contract tells the client that you take your work seriously, that you have clear boundaries, and that you have been through this process before.
Clients who push back on reasonable contract terms — payment schedules, revision limits, IP clauses — are signaling future problems. A contract does not just protect you legally. It filters for clients who respect professional boundaries.
Start every project with a signed contract. No exceptions.