What to Include in a Freelance Contract

Janis Hiestand
7/30/2026
A freelance contract is the document that separates professional work from a handshake. It defines what you will deliver, what you will be paid, who owns the work, and what happens when something goes wrong. Every clause exists because that specific thing has gone wrong for someone.
Most freelancers know they need a contract. The problem is not absence but incompleteness. A contract that covers scope and payment but ignores intellectual property, termination, or revision limits leaves gaps that only become visible during a dispute.
Scope of Work
The scope clause defines exactly what you will deliver. It is the most important section of the contract because it determines what the client can expect and what falls outside the agreement.
Be specific. "Logo design" is not a scope. "Primary logo, secondary logo mark, monochrome version, and brand usage guidelines document" is a scope. The more precise the deliverables, the easier it is to manage requests that fall outside them.
Equally important: state what is excluded. If the logo project does not include business card design, social media templates, or a brand book, say so. Exclusions prevent the most common freelance dispute: the client assuming something was included that was never discussed.
The freelance contractor proposal template includes a scope section that separates inclusions and exclusions. Using it as a starting point ensures you do not forget the boundaries.
Payment Terms
Define four things:
Total price or rate. Fixed project price, hourly rate, daily rate, or retainer. State the currency.
Payment schedule. When payments are due. A deposit on signing, milestone payments, or net-30 invoicing. For project work, requiring a deposit before starting filters out clients who are not serious and protects your cash flow.
Late payment terms. What happens when a payment is overdue. A standard clause: interest accrues at a defined rate after the due date, and work pauses until payment is received. This is not adversarial. It is a boundary that most professional clients respect.
Expenses. Whether expenses (stock images, software licenses, travel, printing) are included in the price or billed separately. If billed separately, define the approval threshold and the documentation required.
Intellectual Property
IP is where freelance contracts diverge most sharply from employment contracts. As a freelancer, you typically own the work you create until you assign it. The contract should define exactly when ownership transfers and what rights you retain.
The most common arrangement: intellectual property transfers to the client upon final payment. This protects the freelancer (no payment, no ownership transfer) and gives the client clean ownership once the engagement is paid for.
Some freelancers retain the right to use deliverables in their portfolio. If this matters to you, state it explicitly. If the work is confidential and the client needs to restrict portfolio use, that should also be stated.
Work-for-hire clauses, where the client owns the IP from the moment of creation, are standard in employment but unusual and unfavorable for freelancers. If a client insists on work-for-hire terms, the price should reflect the fact that you are giving up residual rights.
Revisions and Approval
Without a revision clause, projects can cycle indefinitely. Define:
- How many revision rounds are included (two to three is standard)
- What constitutes a revision versus a new request
- How additional revisions are priced (hourly or per round)
- How long the client has to provide feedback at each stage
- What happens if the client does not respond within the review period
A common default: feedback is due within five business days. If no feedback is received, the deliverable is deemed approved. This prevents projects from stalling in open-ended review cycles.
Timeline and Milestones
State the project timeline, including start date, milestones, and expected completion. Tie the timeline to client inputs: "The timeline assumes client feedback is provided within five business days of each deliverable. Delays in client-provided feedback will extend the timeline by an equivalent period."
This clause protects your schedule when the client is slow to respond. Without it, you absorb the delay while the client still expects the original deadline.
Termination
Every contract should define how the engagement ends early. This is the clause freelancers most commonly leave out, and the one they most commonly regret omitting.
Define:
Notice period. How much notice either party must give to terminate (7 to 14 days is typical for freelance engagements).
Kill fee. What compensation is owed if the client terminates mid-project. Common approaches: payment for all work completed to date, payment for the current milestone, or a fixed percentage of the remaining contract value.
Deliverable handoff. What happens to work in progress on termination. Does the client receive partially completed deliverables? Only if paid for?
IP on termination. Does IP transfer for the work completed and paid for, or does everything revert to the freelancer?
A contract without termination terms leaves the freelancer exposed. When a client cancels after three weeks of a six-week project, the freelancer needs a contractual basis for billing the work already done.
Confidentiality
If you will have access to the client's proprietary information, include a confidentiality clause. It does not need to be as detailed as a standalone NDA (for that, see how to write an NDA), but it should establish that you will not disclose or misuse the client's confidential information.
A mutual obligation is often appropriate: the freelancer protects the client's business information, and the client protects the freelancer's proprietary methods, pricing, and business operations.
Liability and Indemnification
Limit your liability to the total fees paid under the contract. This is standard practice and protects you from claims that exceed the value of the engagement.
An indemnification clause defines who is responsible for third-party claims. If you are building a website using content the client provides, the client should indemnify you against claims related to that content (copyright infringement, defamation, etc.).
Keep this section proportional to the engagement. A five-figure project does not need the same liability framework as an enterprise contract.
Independent Contractor Status
State explicitly that you are an independent contractor, not an employee. This protects both parties from misclassification issues. Include language confirming that you control how and when the work is performed, that you provide your own equipment, and that no employment relationship is created by the contract.
Governing Law and Disputes
Specify which jurisdiction's law governs the contract and how disputes are resolved. For small freelance engagements, specifying the freelancer's jurisdiction and requiring mediation before litigation is a reasonable default that avoids expensive legal proceedings.
Start From a Template
The freelance contractor proposal template and service agreement template on InkDraft include all of these clauses in a structure designed for freelance and solo engagements. Start from the closest match, adjust the terms to your specific situation, and the contract will cover the areas where freelancers most commonly get burned.
More from the blog
Client Onboarding After Signing: A Step-by-Step Process
What to do after a client signs the contract. A step-by-step onboarding process that sets expectations, collects what you need, and prevents the most common early-engagement failures.
How to Follow Up on a Proposal (Without Being Annoying)
When to follow up on a proposal, what to say, and how to read the silence. A step-by-step follow-up sequence that keeps deals moving without damaging the relationship.
How to Write a Scope of Work
A scope of work defines what will be delivered, when, and under what conditions. How to write one that prevents scope creep, protects both sides, and keeps the project on track.