Every freelancer learns the hard way at some point, usually when a client doesn’t pay their third payment or says that the “final” design needs 14 more rounds of changes. A good contract does more than just keep you safe legally. Before a single product changes hands, it sets the tone for the whole working relationship.
It takes these things to make a deal that stands.
The Scope of Work: Where Most Contracts Fall Apart?
Vague scope language is the #1 source of freelance disputes. “Design a website” means something completely different to you and your client unless you specify it.
A proper scope clause should define:
- Exactly what you’re delivering (number of pages, file formats, word count, revision rounds).
- What’s explicitly not included (e.g., “copywriting is not part of this agreement”).
- The medium, platform, or use case.
Real-world example: A UX designer contracted to “redesign the app interface” delivered new screens, but the client expected a full clickable prototype and developer handoff files in Figma.
Nothing illegal happened. Nothing was even unethical. It was just unspecified. The designer ended up doing 3 extra weeks of work unpaid to preserve the relationship.
Scope creep doesn’t announce itself. It accumulates. Your contract should define the ceiling, not just the floor.
Payment Terms That Actually Get You Paid
Most freelancers underengineer this section. “Net 30” is not a payment policy; it’s a starting negotiation that clients will quietly ignore.
What to include:
- Deposit amount (typically 25–50% upfront for projects over $500)
- Milestone payment schedule for larger projects
- Invoice due date (Net 7 or Net 14, not Net 30). The longer the window, the more likely the payment disappears.
- Late fees: a standard rate is 1.5% per month on the outstanding balance
- Accepted payment methods
- What happens to the work-in-progress if the payment lapses
One often-skipped clause: a kill fee. If a client cancels a project midway, you’re entitled to compensation for time already invested. A kill fee of 25–50% of the remaining contract value is industry standard, and it needs to be written in verbal agreements, as this never survives a dispute.
Intellectual Property: Who Owns What, and When
Default copyright law assigns ownership of creative work to the person who made it — not the person who paid for it. That means without a clear IP clause, you technically own the logo, the code, and the article you wrote.
Most clients don’t know this, and most freelancers don’t explain it. This creates confusion and sometimes litigation.
Three common IP structures:
Work-for-hire / Full transfer: Client owns everything upon final payment. This is standard for most commissioned work. Use language like: “Upon receipt of full payment, Contractor assigns all intellectual property rights to Client.”
License only: You retain copyright and grant the client a license to use the work. This is common for stock photography, software components, or situations where you plan to reuse assets. Specify whether the license is exclusive or non-exclusive, and what territory/duration it covers.
Retained rights: You keep the rights to show the work in your portfolio, case studies, and self-promotion. Add this even in full-transfer contracts. Clients sometimes try to restrict this after the fact.
If you’re a developer, address third-party libraries, open-source components, and pre-existing code specifically. Work-for-hire language applied to open-source code creates legal inconsistencies that most lawyers will charge you $500/hour to sort out.
Revision Rounds: Define Them Before You Need Them
“Unlimited revisions” is a phrase no experienced freelancer ever includes twice. A single project with unlimited revisions can stretch from a 2-week timeline to a 4-month ordeal.
Specify the number of revision rounds included in the price, what constitutes a revision (minor changes) versus a new direction (scope change), and your rate for additional rounds beyond the included limit.
A practical structure for design or writing projects:
| Revision Type | Included | Rate for Extras |
|---|---|---|
| Minor copy edits or small adjustments | 2 rounds | $X per round |
| Structural or directional changes | 1 round | $Y per hour |
| New concept or complete restart | Not included | Quoted separately |
This table should live in your contract. It eliminates 80% of revision-related arguments.
Timeline and Delivery Terms
A timeline isn’t just about protecting your schedule; it’s about establishing mutual accountability.
Your contract should specify:
- Project start date (often tied to deposit receipt)
- Key milestone dates with deliverable descriptions
- Final delivery date
- What happens if the client delays providing feedback or materials (“Client understands that delays in providing required materials may extend the delivery timeline accordingly”)
That last point matters. A client who takes 3 weeks to respond to a draft can’t reasonably hold you to the original deadline. The contract should say so explicitly.
Confidentiality and Non-Disclosure
If you’re working with sensitive business information, financial data, product roadmaps, or internal processes, include a basic NDA clause or a reference to a standalone NDA.
Even if the work isn’t sensitive, confidentiality clauses reassure clients and signal professionalism. Keep it proportional: a small business owner hiring you to write blog posts doesn’t need the same NDA as a Series B startup sharing investor decks.
Standard language covers: not sharing proprietary information with third parties, not using the client’s data for your own purposes, and the duration of the obligation (typically 2–3 years).
Termination Clause: The One Most People Skip
Every contract needs a clean exit mechanism for both parties.
Cover these scenarios:
- Client terminates early: Client pays for all work completed plus the kill fee.
- You terminate: You deliver completed work to date, refund unused portions of the deposit, and give reasonable notice (typically 14 days).
- Termination for cause: Either party can terminate immediately if the other materially breaches the contract and fails to cure the breach within a specified period (5–10 business days is typical).
Without a termination clause, disputes about cancellation turn into legal gray areas where the only winner is whoever has a better lawyer.
Dispute Resolution
Most freelance contracts include a boilerplate arbitration clause, which is fine.
But consider adding:
- Which state/jurisdiction’s laws govern the agreement?
- Whether disputes go to binding arbitration or mediation first.
- A small claims carve-out (disputes under $X can bypass arbitration).
The American Arbitration Association publishes standard arbitration clauses that are widely recognized and free to use as a template.
Limitation of Liability
This clause protects you if the work you deliver somehow contributes to a client’s loss. Say you build an e-commerce site and a bug causes checkout to fail for 48 hours without a liability cap; theoretically, the client could sue you for lost revenue.
A standard clause limits your liability to the total amount paid under the contract. This is normal, expected, and defensible.
Common Mistakes to Avoid
Using a generic template without customizing it. Templates are starting points, not finished contracts. A logo design contract and a software development contract need very different scopes and IP language.
Not dating revisions. If you negotiate changes to a contract via email and don’t issue an amended signed version, you have conflicting documents. Always generate a clean amended contract when terms change.
Forgetting to specify payment triggers. “Upon project completion” is vague. What triggers the completion of client approval, file delivery, and publication? Tie payment to a concrete, observable event.
Leaving out your own protections while focusing on the client’s. Contracts aren’t just client protections. Your portfolio rights, your ability to terminate, your late fee rights, these need to be in there too.
FAQ
Do I need a lawyer to write my freelance contract?
Not necessarily for straightforward projects. Many freelancers use well-structured templates from platforms like AND CO or the Graphic Artists Guild’s Handbook of Pricing and Ethical Standards, which has been the industry reference since the 1970s. For large projects — say, $10K+ or work involving sensitive IP, a one-time legal review from a contracts attorney is worth the $200–400 investment.
What if a client refuses to sign a contract?
That’s important information. Most professional clients understand that contracts are standard. A client who resists signing is often a client who plans to push boundaries later. You can soften it by explaining that contracts protect both parties, but if they still refuse, factor that risk into your decision to take the project.
Can I use one contract for all my clients?
You can use one base template, but scope, pricing, and IP terms need to be customized per project. A single-use licensing clause appropriate for a software module doesn’t make sense for a ghostwriting engagement. The structure can be standard; the details can’t be.
What’s the difference between a contract and a statement of work?
A contract establishes the legal relationship, rights, and obligations. A Statement of Work (SOW) describes the specific deliverables, timelines, and technical details for a given project. For ongoing relationships, you might have one master contract with individual SOWs attached per project. For one-off work, a single contract that includes both is common.
What if I’m working internationally?
Specify which country’s laws govern the agreement, and consider including a currency clause to avoid ambiguity on exchange rates. Cross-border enforcement is complicated, but having a written governing law clause at least establishes a starting point.
