Freelance Contract Templates: What to Include and What to Skip

A freelance contract exists for one purpose: to make sure both you and the client know exactly what's going to happen. What you'll deliver. When you'll deliver it. How much the client will pay. What happens if things go wrong. That's it. A contract that does those four things clearly is a good contract. A contract that doesn't — regardless of how many pages it has — is a liability.

Most freelancers fall into one of two camps. They either use no contract at all (terrifying) or they use a 15-page legal document they found online that includes clauses about force majeure, arbitration venues, and indemnification — none of which they understand (also terrifying, but in a different way).

The sweet spot is a contract that's comprehensive enough to protect both parties and simple enough that both parties actually read it. Here's what that looks like.

The Essential Clauses: What Every Contract Needs

1. Scope of Work

This is the most important clause in the entire contract. If you get nothing else right, get this right.

What to include:

• Specific deliverables listed individually (not "website design" but "Design and development of a 6-page marketing website including: Homepage, About, Services, Portfolio, Blog, Contact")
• Specifications for each deliverable where relevant (file formats, dimensions, responsive breakpoints, supported browsers, page count, word count)
• Number of revision rounds included
• What constitutes a "revision" vs. a "change in direction"

What to skip:

• Detailed process descriptions (that's for the project brief, not the contract)
• Technical specifications that might change during the project (reference a separate technical spec document instead)

The golden rule: If there's a disagreement later about what was included, can this clause settle it? If yes, it's specific enough. If not, it needs more detail.

2. Payment Terms

Clear payment terms prevent more disputes than any other clause.

What to include:

Total project fee: The full amount the client will pay.

Payment schedule: When each payment is due. Common structures:

• 50% deposit, 50% on completion
• 33% deposit, 33% at midpoint, 34% on completion
• 100% upfront (common for smaller projects under $5,000)

Payment method: How you accept payment — bank transfer, credit card, PayPal, Stripe. Include your payment details or a link to your invoicing system.

Payment deadline: "Payment is due within [X] days of invoice date." Net 15 is standard. Net 30 is acceptable for larger companies. Never agree to Net 60 unless the project fee justifies the cash flow impact.

Late payment terms: "Invoices unpaid after [X] days will incur a late fee of [1.5%] per month on the outstanding balance." Also consider: "Work will be paused on accounts more than [14] days overdue."

The deposit clause: "A deposit of [50%] of the total project fee is required before work begins. The deposit is non-refundable but is applied toward the total project fee."

3. Timeline

What to include:

Project start date: Tied to deposit receipt, not the contract signing date. "The project will commence within [5] business days of deposit receipt."

Milestone dates: Major deliverable dates tied to specific deliverables. "Design concepts will be presented by [date]. Development will be completed by [date]."

Final delivery date: When the project is expected to be complete — with a condition. "The estimated completion date of [date] is contingent on the client providing timely feedback and assets per the agreed schedule."

Timeline shift clause: "Delays in client feedback, asset delivery, or approvals will shift the project timeline by an equivalent period." This protects you when the client takes three weeks to review something and then complains the project is behind schedule.

4. Revisions and Change Orders

This clause prevents the single most common source of freelancer-client conflict: scope creep.

What to include:

Revision rounds: "This project includes [2] rounds of revisions per deliverable. A revision round consists of feedback provided in a single consolidated document, addressed within the existing project direction."

Change in direction: "A change in direction — defined as feedback that fundamentally alters the approved concept or requires starting a phase over — is not a revision. Changes in direction will be scoped and quoted separately as additional work."

Change order process: "Any work outside the defined scope requires a written change order signed by both parties before work begins. Change orders will include the additional scope, cost, and timeline impact."

Additional revisions: "Revision rounds beyond those included in the scope will be billed at [$X] per round."

5. Intellectual Property and Ownership

Who owns the work? This must be crystal clear.

The standard approach (recommended):

"Upon receipt of full and final payment, all intellectual property rights to the deliverables described in the Scope of Work transfer to the Client. Until final payment is received, all intellectual property rights remain with the Freelancer."

What this means: You own the work until they pay for it. Once they've paid in full, it's theirs. This is simple, fair, and protects both parties.

Portfolio rights: "The Freelancer retains the right to display the completed work in their portfolio, website, and marketing materials, unless otherwise agreed in writing."

Most clients have no issue with this. If a client requires confidentiality (rare but it happens), negotiate a higher fee to compensate for the marketing value you're giving up.

Pre-existing materials: "The Freelancer retains ownership of all pre-existing tools, frameworks, code libraries, and methodologies used in the creation of the deliverables." This protects your reusable assets — the code libraries, design systems, and frameworks you've built over time that you bring to every project.

6. Termination (Kill Clause)

Sometimes projects need to end early. A clear termination clause makes this clean instead of ugly.

What to include:

"Either party may terminate this agreement with [14] days written notice. In the event of termination:

• The Client will pay for all work completed up to the termination date.
• The non-refundable deposit is retained by the Freelancer.
• Completed deliverables will be transferred to the Client upon payment of all outstanding amounts.
• Work in progress may be delivered at the Freelancer's discretion."

Why this matters: Without a kill clause, you're either stuck in a project that's gone sideways or walking away from money you've earned. The kill clause gives both parties a clean exit.

7. Confidentiality

A basic confidentiality clause protects sensitive business information both ways.

"Both parties agree to keep confidential any proprietary information shared during the course of this project, including but not limited to business strategies, financial information, customer data, and trade secrets. This obligation survives the termination of this agreement."

Keep it simple and mutual. Both parties have information they don't want shared. A mutual clause is fairer and more professional than a one-sided NDA.

8. Liability Limitation

This clause caps your financial exposure if something goes wrong.

"The Freelancer's total liability under this agreement shall not exceed the total fees paid by the Client for the project. The Freelancer is not liable for any indirect, incidental, or consequential damages."

What this means in plain language: If your work somehow causes the client a problem, the maximum they can claim from you is the amount they paid you. They can't sue you for $500,000 in "lost revenue" from a $5,000 website project.

This clause is essential. Don't skip it. Don't sign a contract without it.

Clauses to Skip (or Simplify)

Force Majeure (Usually Unnecessary)

The boilerplate force majeure clause about earthquakes, pandemics, and acts of God is overkill for most freelance contracts. A simple sentence is sufficient: "Neither party is liable for delays caused by circumstances beyond their reasonable control."

Detailed Dispute Resolution Procedures

Complex arbitration clauses, mediation requirements, and jurisdiction specifications are appropriate for six-figure enterprise contracts. For a $10,000 freelance project, they add pages without adding value. A simple clause is sufficient: "Any disputes will be resolved through good-faith negotiation. If negotiation fails, disputes will be handled in [your jurisdiction]."

Non-Compete Clauses

Clients sometimes try to include clauses preventing you from working with their competitors. Push back on this firmly. You're a freelancer — your livelihood depends on being able to work with multiple clients, including competitors. If the client insists, charge a premium that compensates for the restricted market.

Warranty Clauses Beyond Reasonable Scope

Some client contracts include warranties like "the deliverables will be free of defects for 12 months." This is unreasonable for most creative and development work. A reasonable warranty is: "The Freelancer warrants that the deliverables will conform to the agreed specifications at the time of delivery. Any defects identified within [30] days of delivery will be corrected at no additional cost."

Contract Delivery and Signing

Use E-Signatures

Paper contracts that need to be printed, signed, scanned, and emailed back are a relic. Use an e-signature tool (DocuSign, PandaDoc, HelloSign) for instant, legally binding signatures. The faster the contract gets signed, the faster you start earning.

Walk the Client Through Key Clauses

Don't just send the contract and hope the client reads it. On a brief call or in a cover email, highlight the key clauses: scope, payment terms, revisions, and termination. This prevents "I didn't realize that was in there" conversations later.

Keep a Signed Copy

Store every signed contract in a dedicated folder (your Google Drive or Notion workspace). You need to be able to access it quickly if a dispute arises. A contract you can't find is almost as useless as a contract you never signed.

When to Use a Lawyer

For most standard freelance projects, a well-crafted template covers you. But some situations warrant legal review:

• Projects over $25,000 — the stakes are high enough to justify legal costs
• Equity or revenue-share agreements — these are fundamentally different from service contracts
• Clients with their own contracts — always have a lawyer review a client's contract before signing
• International clients — cross-border contracts have jurisdiction implications
• Contracts with unusual clauses — anything you don't understand, have reviewed

A lawyer's review costs $300-$1,000 and can save you tens of thousands in disputes.

The Contract Conversation: Setting the Tone

How you introduce the contract sets expectations for the entire relationship.

Don't say: "Here's the contract — I need you to sign it before we start." Do say: "I've put together our project agreement. It covers the scope we discussed, payment terms, and our process for handling revisions and changes. Take a look and let me know if you have questions."

Frame the contract as a tool for clarity, not a weapon. Both parties benefit from clear terms. The contract isn't adversarial — it's the foundation of a professional relationship.

Key Takeaways

1. Eight essential clauses: scope, payment, timeline, revisions, IP, termination, confidentiality, and liability. Cover these and you're protected.
2. The scope clause is the most important. Make it specific enough to settle any disagreement about what was included.
3. Payment terms should be non-negotiable. Deposit before work starts. Late fees for overdue invoices. Work pauses for significantly overdue accounts.
4. IP transfers on final payment. You own the work until they've paid for it.
5. Skip the legal bloat. Force majeure paragraphs, complex arbitration, and excessive warranties add pages without adding protection.
6. Use e-signatures. Fast signing means faster project start.
7. Invest in legal review for high-stakes situations. Projects over $25K, equity deals, and client-provided contracts all warrant a lawyer's eyes.