Freelance Scope of Work (SOW) Example: What to Include So You Don't Work for Free

A Scope of Work (SOW) is the single most important section in any freelance contract. Without one, you're promising "whatever the client needs" at the original price. With one, you have a legally defensible boundary that says: this is exactly what you're paying for, and anything else costs more.

Here is a real freelance Scope of Work example, broken down section by section, with the exact language you can adapt. We'll also cover the three traps that turn a good SOW into a free-work machine — and how to avoid each one.

---

What Is a Scope of Work in a Freelance Contract?

A Scope of Work is a detailed description of the deliverables, tasks, timelines, and exclusions in a project. It lives inside your Service Agreement or Statement of Work and serves as the reference point if a client later claims you promised something you didn't.

A strong SOW answers four questions:

• What are you delivering?
• When will it be delivered?
• What is explicitly NOT included?
• How many revisions are covered?

If your SOW doesn't answer all four, the client's assumptions will fill the gaps — and you'll eat the cost.

---

Freelance Scope of Work Example (Full Template)

Below is a real-world SOW for a website design project. Every section includes the clause language and an explanation of why it's written that way.

1. Project Overview

Project: Redesign of [Client Name]'s company website (5 pages) Engagement Type: Fixed-fee project Total Fee: $3,500 Timeline: 6 weeks from signed contract and deposit

Why it works: Naming the engagement type (fixed-fee vs. hourly) upfront prevents confusion later. A fixed-fee SOW needs tighter boundaries than an hourly one, because you absorb the risk of extra work.

2. Specific Deliverables

Designer will deliver the following:

• 5 custom web pages designed in Figma (Home, About, Services, Portfolio, Contact)
• Mobile-responsive layout for all 5 pages
• One round of revisions per page
• Final handoff: Figma file + exported PNG assets

Designer will NOT provide:

• Copywriting or content creation
• Stock photography or illustration
• Logo design or branding
• SEO keyword research or implementation
• CMS integration or development (separate contract)

Why it works: The "will NOT provide" list is the most profitable paragraph in your contract. Clients often assume design includes copy, photos, logos, and development. Spelling out exclusions turns "Can you just throw in…?" into a paid change order.

3. Timeline & Milestones

Milestone	Due Date	Deliverable
Kickoff & brief	Week 1	Client provides brand guide, content, and feedback preferences
Wireframes	Week 2	5 wireframes for client review
Design mockups	Week 3-4	First draft of all 5 pages
Revision round	Week 5	One round of changes
Final delivery	Week 6	Figma file + assets

Why it works: Tying milestones to client dependencies ("Client provides brand guide") protects you. If the client is late delivering materials, the timeline shifts — and you're not penalized for their delay.

4. Revision & Change Order Process

This SOW includes one round of revisions per deliverable. Additional revisions or changes outside the scope defined above will be billed at $85/hour with a 2-hour minimum. Any change that adds a new page, feature, or deliverable requires a signed Change Order before work begins.

Why it works: "One round of revisions" is specific. "Reasonable revisions" is a blank check. Also note the change order requirement — never start extra work on a verbal "yeah just add it." Get it in writing.

5. Completion Criteria

Project is considered complete when:

• All deliverables have been delivered to client
• Client has confirmed acceptance in writing (email is sufficient)
• Final payment has been received

After delivery, designer is not obligated to make further changes unless covered by a new SOW and fee.

Why it works: Define "done." Otherwise, a client can request tweaks months later, claiming the project was never finished.

---

3 Scope Creep Traps (and How Your SOW Kills Them)

Trap 1: "Can you just add one more page?"

A single extra page doesn't feel like a big ask. But if you say yes once, you've established that scope is negotiable by request.

Fix: Your SOW says "5 pages." Any additional page requires a Change Order and additional fee. Point to the contract — politely — every time.

Trap 2: "I assumed revisions were unlimited."

Clients who don't know design often need 4, 5, or 6 rounds to get comfortable. If you didn't cap revisions, you're working those extra rounds for free.

Fix: Your SOW caps revisions at one round per deliverable. For more, they pay the hourly rate. This also incentivizes the client to consolidate feedback instead of trickling it in.

Trap 3: "The project changed direction, but the price shouldn't."

A mid-project pivot — new features, different audience, rebranding — is a new project, not a continuation of the old one.

Fix: Your SOW includes a clause stating that material changes to the project scope require a new or amended SOW. No free pivots.

For more detail on how to handle scope creep in your contract, see our guide: What Is a Scope Creep Clause? How to Write One That Protects Your Freelance Business.

---

Scope of Work vs. Statement of Work: What's the Difference?

These terms are often used interchangeably, but there's a practical difference:

Scope of Work (SOW)	Statement of Work (SoW)
A section within a contract that defines deliverables	A standalone document attached to a contract
Best for smaller, shorter projects	Best for large, multi-phase projects
Lives inside the Service Agreement	Exists as an exhibit or appendix

For a longer comparison, read: Scope of Work vs Statement of Work: What Freelancers Need to Know.

The short version: If your project fits on one page, write your SOW directly into the contract. If it's a 6-month engagement with phases, use a separate Statement of Work document that you can update per phase.

---

How to Write Your Own Scope of Work (Quick Checklist)

Use this checklist before you send any freelance contract:

• Deliverables are listed as specific, countable items (not "design work" but "5 web pages")
• Exclusions are listed explicitly (what you WON'T do)
• Timeline includes client dependencies ("Client will provide X by Y date")
• Revision limit is stated numerically ("one round")
• Change order process is defined
• Completion criteria is clear
• Fee matches the scope (if scope changes, fee changes)

---

The One-Question Test for Your SOW

Before you send a contract, ask yourself:

If a client asked for everything in this SOW twice, would I still make money?

If the answer is no, your scope is too vague or your fee is too low. A good SOW protects you from working for free — but only if the numbers work at the start.

---

Get the Contract Language You Need

Writing a solid Scope of Work from scratch takes time. The clauses above — revision caps, change orders, exclusions, completion criteria — are all pre-written in the Contracts Kit template library.

Each template includes plain-English explanations of every clause so you know why it's there and how to customize it for your specific project.

Browse the contract templates

---

Disclaimer: This article provides general information and does not constitute legal advice. Contract templates are tools, not a substitute for consultation with a licensed attorney regarding your specific situation.