The problem with most freelance contract templates isn’t that they’re wrong. It’s that they’re generic, borrowed from agency agreements written for a different context, or lifted from legal blogs that prioritize comprehensiveness over usability. The result is a contract template with 12 sections, half of which don’t apply to your work, and language so formal that clients hesitate to sign.
What follows is the structure of a contract that works: one that covers what matters, uses language a client can understand, and closes projects cleanly.
The Header
Before the clauses, the contract needs to identify who it’s between and when it takes effect.
The header should include:
- Your full legal name (or business name if you operate as one)
- The client’s full legal name (individual or company)
- The company name and address, if applicable
- The effective date, the date both parties sign, not the project start date
This sounds obvious. But contracts signed by “Sarah J” from “the design studio”, without legal names and entity types, create enforcement problems. If you ever need to take the matter to small claims or send a formal demand, you need to know exactly who you contracted with.
Section 1: Scope of Work
The scope section is the most important part of the contract and the one most likely to cause a dispute if written vaguely.
What the language should say:
“The Freelancer agrees to provide the following services: [specific list of deliverables, formats, and quantities]. The following are expressly excluded from this agreement: [specific exclusions].”
The deliverable list should be specific enough that both parties could independently review it and agree on whether each item was delivered. “Logo design” is not a deliverable. “Primary logo in three color variants (full color, monochrome, reversed white), delivered as AI, EPS, PNG, and SVG files” is a deliverable.
Exclusions matter as much as inclusions. If you’re writing copy but not managing SEO, state it. If you’re designing the interface but not writing production code, state it. The “not included” list is where scope disputes get resolved before they start.
For projects with phases, scope each phase separately. If phase two depends on client approval of phase one, state that explicitly.
Section 2: Timeline
The timeline section states when work will be delivered and what the client is responsible for to keep things on schedule.
What the language should say:
“Work will be delivered according to the following schedule: [milestones and dates]. This schedule assumes timely client feedback and approvals. Delays caused by late feedback or approvals will extend the timeline by an equivalent period.”
The second sentence is the one freelancers omit and later regret. If a client takes three weeks to provide feedback on a milestone, the project doesn’t end on the original date. The contract should reflect that. Without it, you’re holding yourself to a deadline you can’t control.
Also specify when client deliverables are due, if the project requires them: brand assets, copy, access credentials, reference materials. If the client is supposed to provide copy by a certain date and doesn’t, that affects your timeline. The contract should say so.
Section 3: Fees and Payment
Payment terms need four components: the total amount, the schedule, the due dates, and the consequences of late payment.
What the language should say:
“The total fee for services described in Section 1 is [amount]. Payment is due as follows: [50% / deposit amount] due upon signing this agreement, [remaining amount] due within [14] days of final delivery. Invoices unpaid after [30] days will accrue interest at [1.5%] per month. Final deliverables will be released upon receipt of full payment.”
The final sentence, deliverables released on full payment, is the one most freelancers don’t include and should. It’s industry-standard for creative work. Clients who understand the business expect it. Clients who push back on it are telling you something.
If you’re billing hourly rather than by project, the payment clause should state the hourly rate, estimated hours, how overages are handled, and how often invoices are issued (weekly, bi-weekly, at project end).
Section 4: Revisions
The revision clause prevents endless rounds of changes by defining what’s included and what costs extra.
What the language should say:
“The quoted fee includes [two] rounds of revisions per deliverable. A round of revisions is defined as one set of consolidated feedback submitted within [ten] days of receiving the deliverable. Additional revision rounds are available at [hourly rate] per hour, invoiced separately. Revisions requested after final approval constitute a new project and will be quoted separately.”
The word “consolidated” is doing important work here. It means all feedback from all stakeholders on the client’s side, collected into a single document, submitted once. It prevents the drip of “one more thing” emails that extend projects without triggering the revision cap.
Define the difference between a revision and a change of scope. Refinement of the agreed concept is a revision. A new direction, new requirements, or substantial changes to the brief are scope changes, they require a separate quote, not a revision round.
Section 5: Intellectual Property
The IP clause determines who owns the work when the project is complete.
What the language should say (full transfer):
“Upon receipt of full payment, the Freelancer assigns all intellectual property rights in the final deliverables to the Client. Prior to full payment, all rights remain with the Freelancer.”
The “prior to full payment” sentence is the enforcement mechanism. Without it, a client could take delivery, refuse to pay, and argue they already own the work. With it, ownership transfers only when the financial obligation is complete.
If you want to retain rights in underlying components, source files, frameworks, fonts, code libraries you use across projects, state that explicitly:
“The Client receives a perpetual, non-exclusive license to use the final deliverables. The Freelancer retains ownership of all underlying tools, frameworks, and methodologies used in creating the deliverables.”
For work that will be used commercially at scale, brand assets, software, licensed photography, the IP clause should be specific about the scope of use. Unlimited commercial use, perpetual and worldwide, is different from limited use for a specific campaign.
Section 6: Kill Fee
The kill fee clause covers project cancellation after work has begun.
What the language should say:
“In the event the Client cancels this project after signing this agreement, the following cancellation fees apply:
- Cancellation before work begins: [25]% of total project fee
- Cancellation after Phase 1 delivery: [50]% of total project fee
- Cancellation after Phase 2 delivery: [75]% of total project fee
- Cancellation after final delivery: [100]% of total project fee
Cancellation fees are due within [14] days of written notice of cancellation.”
Tailor the tiers to how your projects actually flow. If you work in two phases, you need two tiers plus the pre-start tier. If your projects have four milestones, build four tiers.
The kill fee clause is separate from the termination clause. Termination covers how either party ends the engagement (process and notice). The kill fee covers what it costs the client to cancel. How to write a freelance contract termination clause covers both the notice period language and how to structure kill fee tiers.
Section 7: Confidentiality
The confidentiality clause restricts both parties from sharing the other’s sensitive information.
What the language should say:
“Both parties agree to keep confidential any proprietary information shared during this engagement, including but not limited to business strategies, financial data, unreleased products, and client lists. This obligation survives termination of this agreement for [two] years. Each party retains the right to display completed deliverables in their portfolio unless otherwise agreed in writing.”
The final sentence is the portfolio carve-out. Without it, you technically need client permission to show your work, permission that can be slow to arrive, inconsistently granted, or disappear entirely if your contact leaves the company.
If you’re doing work with genuinely sensitive information (healthcare data, financial systems, competitive intelligence), the confidentiality clause should be more detailed and specific. For most creative or consulting work, the language above is sufficient.
Section 8: Termination
The termination clause covers how either party exits the engagement and what happens financially when they do.
What the language should say:
“Either party may terminate this agreement with [14] days written notice. Upon termination, the Client will pay for all work completed up to the date of termination, calculated as a pro-rated portion of the total project fee based on work completed. The cancellation fees in Section 6 apply to client-initiated terminations.”
The termination clause and the kill fee clause work together. Termination defines the process and notice period; the kill fee defines the financial consequences for client-initiated cancellation. Make sure they’re cross-referenced in the contract so there’s no ambiguity about which applies when.
Section 9: Governing Law
For domestic clients, a governing law clause specifies which jurisdiction’s law applies in the event of a dispute. For international clients, it’s essential.
What the language should say:
“This agreement is governed by the laws of [your jurisdiction]. Any disputes arising from this agreement will be resolved in the courts of [your jurisdiction].”
Without this clause, an international client could argue that the contract is governed by their country’s law, which may differ significantly from yours on IP, payment enforcement, and contractor rights. Choose your home jurisdiction and state it clearly.
What to Leave Out
Most freelance contracts contain clauses that look professional but add friction without protection. Non-compete clauses are frequently unenforceable for independent contractors. Arbitration clauses are increasingly difficult to enforce at freelance contract values. Limitation of liability clauses work in some jurisdictions and are overridden by courts in others.
If you understand why a clause is in your contract and what it protects against, keep it. If you copied it from a template without knowing what it does, remove it. Shorter contracts close faster and are more likely to be read before signing.
A complete contract covering the nine sections above fits comfortably on two pages. That’s the version that gets signed, understood, and honored. The clauses that genuinely protect you in a freelance contract are the same ones described here, specific, plain-language, and tailored to how your projects actually work. Before sending your contract, run it through the freelance contract checklist to confirm nothing essential is missing.