TLDR (Summary)
A freelance contract needs eight clauses: scope of work, payment terms, timeline, revision limits, intellectual property rights, confidentiality, termination and kill fee, and a signature block. Every clause should be specific enough that a dispute can be resolved by reading the document, not by arguing about what was "meant."
Freelancers who use contracts cut payment disputes by 73%, and new laws like New York's Freelance Isn't Free Act now require written contracts for engagements over $800. Contracts aren't optional paperwork anymore, they're income protection.
Why freelancers need written contracts
A written contract creates a legal reference point for every aspect of a freelance engagement: what gets delivered, when payment arrives, who owns the work, and what happens when something changes.
Without a contract, disputes become one person's word against another's. A client says the project included five blog posts. The freelancer remembers three. Without a written record, there's no way to settle the disagreement except negotiation, and negotiation always favors the person holding the money.
The financial cost of working without contracts
According to the Freelancers Union, 71% of freelancers have struggled to collect payment at least once in their career. A survey from GlobeNewsWire found that 59% of freelancers are owed $50,000 or more in unpaid invoices from late-paying clients. Those numbers shrink when written contracts define payment terms, late fees, and legal recourse before the work begins.
Contracts protect both sides
Contracts aren't just about protecting the freelancer. Clients benefit too. A clear scope of work prevents the freelancer from delivering less than expected. Defined revision limits prevent projects from running indefinitely. A payment schedule prevents the client from paying in full for unfinished work. The contract sets mutual expectations so both sides enter the project with the same understanding of what success looks like.
Legal requirements are expanding
New York's Freelance Isn't Free Act, effective in 2024, requires written contracts for any freelance engagement worth $800 or more within a 120-day period. The contract must include the scope of work, payment terms, and payment due date. California's Freelance Worker Protection Act followed with similar requirements for engagements over $250. More states are expected to pass similar legislation, making written contracts a legal requirement rather than a best practice.
Working without a contract means trusting that every client will honor verbal commitments, pay on time, and respect scope boundaries. The data shows most won't. A written contract converts trust into a documented agreement that holds up when the relationship doesn't.
The eight clauses every freelance contract needs
Every freelance contract should cover eight areas: scope, payment, timeline, revisions, intellectual property, confidentiality, termination, and signatures. Missing any single clause creates a gap that becomes a dispute when expectations don't match reality.
1. Scope of work
The scope clause lists every deliverable the client receives, with quantities, formats, and specifications. "Brand identity package" is not a scope clause. "3 logo concepts in AI, EPS, SVG, and PNG formats; color palette document with hex, RGB, and CMYK values; typography guide; brand guidelines PDF (20-30 pages)" is a scope clause. The scope should also state what falls outside the project: "copywriting, stock photography, website implementation, and print production are not included in this contract." Exclusions prevent the most common source of freelance disputes, which is work expanding beyond the original agreement without additional compensation.
2. Payment terms
Payment terms specify the total fee, the payment schedule, the method of payment, and the consequences of late payment. A standard structure: 50% deposit due upon signing, 50% due upon final delivery. For larger projects: 30% deposit, 40% on draft approval, 30% on final delivery. Late payment penalties should be stated clearly: "Invoices unpaid after 14 days incur a 1.5% monthly late fee." Payment method should also be specified: bank transfer, credit card, PayPal, or platform-specific (Stripe, etc.).
3. Timeline and milestones
The timeline clause sets the project start date, milestone dates, and final delivery date. Milestones break the project into phases that trigger review periods or partial payments. "Phase 1: Discovery (March 1-7). Phase 2: First draft (March 8-21). Phase 3: Revisions (March 22-28). Phase 4: Final delivery (March 29-31)." The timeline should also account for client delays: "If client feedback is not received within 5 business days of a milestone, the project timeline extends by the same number of days."
4. Revision limits
Revision clauses define how many rounds of changes are included in the project fee and what happens when additional revisions are requested. "Two rounds of revisions are included. Additional rounds are billed at $150 per round." The clause should define what counts as a revision (adjustments to existing work based on feedback) versus a new request (additional deliverables or significant direction changes that require a separate quote). Without this distinction, clients can rewrite the entire project through "revisions" and still consider the work within the original scope.
5. Intellectual property rights
The IP clause determines who owns the finished work. Two common approaches: full transfer (client owns everything upon final payment) or licensing (freelancer retains ownership, client gets a license to use the work for specific purposes). The safest default for freelancers: "All intellectual property rights transfer to the client upon receipt of final payment in full. Until final payment is received, the freelancer retains all rights to the work." Linking IP transfer to payment creates a financial incentive for clients to pay on time.
6. Confidentiality
The confidentiality clause protects sensitive information shared during the project: client business data, strategy documents, customer lists, and proprietary processes. A simple mutual clause works for most freelance engagements: "Both parties agree not to disclose confidential information shared during this engagement to any third party without written consent." The clause should define what counts as confidential (business plans, financial data, customer information) and what doesn't (publicly available information, the freelancer's general skills and techniques).
7. Termination and kill fee
The termination clause defines how either party can end the contract and what happens financially when they do. A standard clause: "Either party may terminate this contract with 7 days written notice. If the client terminates, the client pays for all work completed to date plus a kill fee of 20% of the remaining contract value. If the freelancer terminates, the freelancer delivers all work completed to date and refunds any prepaid amounts for undelivered work." Kill fees protect freelancers from clients who cancel mid-project after the freelancer has turned down other work to accommodate the timeline.
8. Signatures and dates
Both parties must sign and date the contract for it to be enforceable. Electronic signatures carry the same legal weight as handwritten signatures under the ESIGN Act (federal) and UETA (adopted by 49 states). The signature block should include the full legal name and business name of both parties, the date of signing, and a statement confirming that both parties have read and agree to the terms.
Each clause covers one specific aspect of the engagement. Together, the eight clauses create a document that answers every question before the work begins, so disputes get resolved by reading the contract instead of arguing about what was intended.
Structuring payment terms that protect freelancers
Payment terms are the most disputed section of any freelance contract, and the most important to get right because they directly determine when and whether the freelancer gets paid.
Deposit structures by project size
For projects under $5,000, a 50/50 split (50% deposit, 50% on delivery) is standard and protects against total non-payment. For projects between $5,000 and $15,000, a three-part split is standard: 30% deposit, 40% on draft approval, 30% on final delivery. For projects over $15,000, monthly milestone payments tied to specific deliverables keep cash flow steady throughout the engagement. The deposit should always be non-refundable and described as a project reservation fee that compensates the freelancer for blocking calendar time.
Late payment penalties
Late fees should be stated as a specific percentage applied monthly. "Invoices unpaid after 14 days incur a 1.5% monthly late fee on the outstanding balance" is enforceable in most jurisdictions. The late fee serves two purposes: it incentivizes timely payment, and it compensates the freelancer for the cost of carrying unpaid receivables. Some contracts also include a clause that pauses all work if an invoice remains unpaid after 30 days, which creates immediate business pressure for the client to resolve the payment.
Connecting payment triggers to deliverables
Tying payments to specific milestones rather than calendar dates ensures the freelancer gets paid as work completes. "Payment 2 of 3 is due within 5 business days of draft delivery" is clearer than "Payment 2 is due on April 15" because the trigger is the work itself, not an arbitrary date. When the contract links to a project management system that tracks milestones, both sides can see exactly when a payment trigger has been met. Plutio connects contract milestones to project tasks and invoicing, so a completed milestone can trigger an invoice automatically. For more on invoice structures and payment follow-ups, see our freelance invoicing guide.
Payment terms written with specific deposit amounts, enforceable late fees, and milestone-based triggers protect against the most common freelance payment problems: non-payment, late payment, and disputes over when payment is actually due.
Intellectual property clauses for freelancers
Intellectual property clauses determine who owns the work after the project ends, and getting this wrong can cost a freelancer ongoing revenue or leave a client without full rights to what they paid for.
Full transfer vs. licensing
Full IP transfer means the client owns the finished work outright and can use, modify, resell, or redistribute it without restriction. Licensing means the freelancer retains ownership and grants the client permission to use the work under specific conditions (specific platforms, specific time period, specific geography). Full transfer is standard for client-specific work like a custom logo, a branded website, or internal marketing materials. Licensing works for work with broader value, like stock photography, illustration portfolios, or reusable design templates.
The "payment-first" IP clause
The most protective IP clause for freelancers ties ownership transfer to payment: "All intellectual property rights in the deliverables shall transfer to the client upon receipt of final payment in full. Until such payment is received, the freelancer retains all rights." Linking IP to payment means a client who hasn't paid can't legally use the work, which creates a strong financial incentive to settle invoices promptly. Freelancers who transfer IP before receiving payment lose their strongest negotiating position in a payment dispute.
Portfolio rights
Most freelancers want to display completed work in their portfolio, but the IP transfer might technically prevent that. Including a portfolio license clause resolves the issue: "Upon completion of the project, the freelancer retains the right to display the work in their professional portfolio, on their website, and in marketing materials for the purpose of showcasing their skills and capabilities." The portfolio clause should be mutual: the freelancer can show the work, and the client can attribute the work to the freelancer in credits or case studies.
Pre-existing materials
Freelancers often bring pre-existing tools, templates, and frameworks into a project. An IP clause should exclude these from the transfer: "Pre-existing materials, including design templates, code libraries, and proprietary workflows, remain the property of the freelancer. The client receives a perpetual, non-exclusive license to use these materials as incorporated into the deliverables." Without this exclusion, a client could claim ownership of a design system the freelancer uses across multiple projects.
The IP clause is where freelancers most often give away more than they intended. Tying IP transfer to payment, retaining portfolio rights, and excluding pre-existing materials protects the freelancer's work and ongoing business while still giving the client full ownership of what they paid for.
Termination clauses and kill fees
Termination clauses define the exit terms for both sides, and kill fees compensate freelancers when clients cancel projects mid-delivery after the freelancer has already committed time and turned down other work.
Why termination clauses matter
Without a termination clause, a client can cancel a project at any point and argue they owe nothing for work not yet delivered. A freelancer who blocked three weeks of calendar time for a project that cancels after week one has lost two weeks of potential income. The termination clause converts that loss into a defined payment obligation.
Standard termination language
A balanced termination clause allows either party to exit with reasonable notice: "Either party may terminate this agreement with 7 days written notice. Upon termination by the client, the client shall pay for all work completed to date at the agreed project rate, plus a kill fee of 20% of the remaining contract value. Upon termination by the freelancer, the freelancer shall deliver all completed work to the client and refund any prepaid amounts for undelivered milestones." The 7-day notice period gives the freelancer time to wrap up deliverables in progress and the client time to plan for the transition.
Kill fee percentages
Kill fees typically range from 15% to 30% of the remaining contract value, with 20% being the most common. A $10,000 project cancelled after $4,000 of work has been completed would result in payment for the $4,000 of completed work plus a $1,200 kill fee (20% of the remaining $6,000). The kill fee covers the opportunity cost of the time the freelancer reserved for the project but can no longer bill to another client.
Material breach vs. convenience termination
The termination clause should distinguish between two scenarios. Convenience termination (the client changes direction or budget) triggers the kill fee. Material breach (one party fails to meet a core obligation, like non-payment or non-delivery) allows the other party to terminate without penalty. "If either party materially breaches this agreement and fails to cure the breach within 14 days of written notice, the non-breaching party may terminate immediately without kill fee obligation." Clear breach language prevents disputes over whether a cancellation was voluntary or caused by the other party's failure.
The termination clause is the clause freelancers skip most often and regret most frequently. Defining exit terms, kill fees, and breach conditions before the project starts protects income that would otherwise disappear when a client changes direction mid-project.
Contract red flags freelancers should watch for
Not every contract a client sends is fair. Some contracts contain clauses that strip freelancers of rights, delay payment indefinitely, or create one-sided obligations.
"Work for hire" without clear scope
A "work for hire" designation means the client owns everything the freelancer creates from the moment of creation, not upon payment. For freelancers, this removes the ability to retain IP rights until payment clears. If a client insists on work-for-hire terms, the freelancer should negotiate a higher rate and require full upfront payment to offset the loss of negotiating position.
Net-60 or net-90 payment terms
Large companies sometimes include payment terms of 60 or 90 days after invoice submission. For freelancers, that means completing a project in March and not getting paid until May or June. Long payment terms create cash flow gaps that force freelancers to finance their own work. Counter-offer with net-14 or net-30, and include a late fee clause to incentivize timely processing.
Unlimited revisions
A clause stating "revisions until client satisfaction" creates an open-ended obligation with no defined endpoint. Projects with unlimited revision clauses regularly exceed the original time estimate by 50-100% because there's no incentive for the client to combine feedback into one round or approve drafts. Replace with a specific revision count (two rounds is standard) and a per-round fee for additional changes.
Non-compete clauses
Some client contracts include non-compete clauses that prevent the freelancer from working with competing businesses for 6-12 months. For a freelancer specializing in one industry (healthcare, fintech, real estate), a non-compete effectively eliminates their client base. Non-compete clauses should either be removed entirely or compensated with a retainer fee for the exclusivity period.
"Client may terminate at any time without penalty"
One-sided termination clauses that let the client cancel without financial consequence leave freelancers exposed. If the contract allows the client to terminate without paying for completed work or a kill fee, the freelancer takes all the project risk. Every termination clause should be mutual and include payment for work completed to date.
Red flags in contracts are negotiation opportunities, not reasons to walk away. A client who pushes back on reasonable terms like defined revisions, fair payment timelines, and mutual termination rights is signaling how the project will go, and that signal is worth paying attention to.
E-signatures and getting contracts signed fast
Electronic signatures carry the same legal weight as handwritten signatures in the United States, the EU, and most of the developed world, so there's no reason for freelancers to print, sign, scan, and email PDF contracts in 2026.
Legal validity of e-signatures
In the US, the ESIGN Act (2000) and UETA (adopted by 49 states plus DC) establish that electronic signatures are legally binding for most business contracts. In the EU, the eIDAS regulation provides a similar framework. A freelance contract signed electronically through a platform like Plutio, DocuSign, or HelloSign is equally enforceable as a paper contract signed in person.
Speed matters for contract signing
The same urgency principle that applies to proposals applies to contracts: the faster a contract reaches the client, the faster it gets signed. When a proposal is accepted, the contract should follow within hours, not days. A delay between proposal acceptance and contract delivery opens a window where the client reconsiders, gets distracted, or starts talking to another freelancer. Sending the contract immediately after proposal acceptance maintains the momentum from the "yes" decision.
Connecting contracts to proposals and projects
When contracts live in the same system as proposals and projects, the workflow from "signed" to "started" happens without manual data transfer. Plutio's contract builder connects to proposals, so the scope and pricing carry forward automatically. A signed contract triggers the project setup, and the first milestone payment request goes out on the same day. No separate document, no re-entering scope details, no chasing signatures through email chains.
What to include in the signature block
The signature block should capture: full legal name of the freelancer, full legal name (and company name) of the client, date of signing, and a statement confirming agreement to the terms. Both parties should receive a signed copy automatically upon completion. Platforms that generate a signed PDF with a timestamp and audit trail provide the strongest legal documentation if the contract is ever disputed.
E-signatures eliminate the friction of getting contracts signed. The legal framework supports them, the tools make them instant, and the speed difference between a 5-minute e-signature and a 3-day print-sign-scan cycle directly affects how fast projects start and revenue flows.
Freelance contract checklist
A pre-send checklist for every freelance contract ensures no clause gets missed and no gap becomes a dispute.
Core clauses
- Scope of work: Every deliverable named with quantities, formats, and specifications
- Exclusions stated: What falls outside the project is explicitly listed
- Payment terms: Total fee, deposit amount, payment schedule, and payment method defined
- Late fee clause: Specific percentage and timeline (e.g., 1.5% monthly after 14 days)
- Timeline with milestones: Start date, phase dates, and final delivery date included
- Client delay clause: Timeline extends if client feedback is late
- Revision limits: Number of rounds included and per-round fee for additional rounds
- IP rights: Ownership transfer tied to final payment, portfolio rights retained
- Confidentiality: Mutual NDA covering business information shared during the engagement
- Termination clause: Notice period, kill fee percentage, and breach conditions defined
- Signature block: Full legal names, dates, and agreement statement for both parties
Before sending
- Scope matches the proposal: The contract scope mirrors what was accepted in the proposal, not a broader or narrower version
- Payment triggers are specific: Tied to deliverables or milestones, not arbitrary dates
- E-signature enabled: The client can sign digitally without printing or scanning
- Both parties receive copies: Automatic signed PDF delivery upon completion
After signing
- Project created from contract: Scope and milestones carry forward into the project management system. For project setup strategies, see our project management guide
- First invoice sent: Deposit invoice goes out the same day as contract signing. For invoice structures, see our invoicing guide
- Contract stored securely: A signed copy is accessible to both parties throughout the project for reference
Running this checklist before sending every contract catches the missing clauses that become expensive disputes later. The checklist takes 5 minutes. The disputes it prevents take weeks and cost thousands.
