A scope of work (SOW) is a document that defines exactly what you will deliver, when you will deliver it, and what falls outside the agreed engagement. For freelancers, it is the most important section of any proposal or contract because it draws the line between what the client is paying for and what they are not.
How it works
The SOW typically lives inside a broader proposal or contract. It gets written during the sales phase, before work begins. Both sides review it, agree on the details, and sign off.
A strong scope of work covers these elements:
| Section | What it defines |
|---|---|
| Project overview | A brief summary of goals and context |
| Deliverables | The specific, tangible outputs you will produce |
| Timeline and milestones | When each deliverable or phase is due |
| Revision rounds | How many rounds of feedback are included |
| Out of scope | What is explicitly not included |
| Assumptions | Conditions that must be true for the project to proceed as planned |
| Acceptance criteria | How the client will approve each deliverable |
The “out of scope” section is just as important as the deliverables list. It gives you a clear reference when scope creep starts.
For a walkthrough of how the SOW fits into a complete proposal, see our freelance proposal guide.
Why it matters for freelancers
Without a scope of work, you and your client are operating on assumptions. They assume the price covers “whatever we need.” You assume it covers what you discussed on the call. Those assumptions diverge quickly, leading to unpaid extra work and strained relationships.
A clear SOW protects you in three ways:
It prevents scope creep. When a client asks for something not in the SOW, you can say, “That is outside our agreed scope — here is what it would cost as a change order.” Our scope creep clause guide covers the contract language to include.
It sets expectations. Clients who see a detailed deliverables list and timeline know exactly what they are getting and when.
It defines “done.” The SOW establishes acceptance criteria so both sides know when work is complete, preventing endless revision loops.
Example
You are a freelance brand designer creating a visual identity for a startup:
Deliverables:
- Logo design (3 initial concepts, 2 revision rounds on chosen direction)
- Color palette (primary and secondary colors with hex codes)
- Typography selection (2 typefaces with usage guidelines)
- Brand guidelines PDF (20-25 pages)
Out of scope:
- Business card or stationery design
- Social media templates
- Website design or development
Timeline:
- Week 1-2: Strategy and research
- Week 3-4: Logo concepts
- Week 5: Revisions and color/type selection
- Week 6: Brand guidelines document
This level of detail takes 30 minutes to write and can save dozens of hours of uncompensated work.
Common mistakes
Being too vague on deliverables. “Website design” is not a deliverable — it is a category. “Homepage design, 4 interior page templates, and a responsive mobile layout” is a deliverable set.
Skipping the “out of scope” section. If you do not explicitly state what is excluded, clients will assume it is included.
Not including revision limits. “Unlimited revisions” means the project never ends. Two to three rounds per deliverable is standard. After that, additional revisions are billed as a change order. See our change order template for how to handle this.
Writing the SOW after the project starts. The SOW should be agreed upon before any work begins. Writing it retroactively means you have already lost the ability to set boundaries.
FAQ
What is the difference between a scope of work and a statement of work? In freelancing, the terms are used interchangeably. Technically, a “statement of work” is a broader document that may include legal terms and payment schedules alongside scope. A “scope of work” focuses on deliverables, tasks, and boundaries. For most freelance projects, a single document covers both.
How detailed should my scope of work be? Detailed enough that a stranger could understand what you are delivering, what you are not, and when it is due. A $500 project might need a half-page SOW. A $20,000 engagement might need several pages. Scale the detail to match project complexity.
Should the scope of work include pricing? The SOW typically focuses on what you will do, not what it costs. Pricing usually appears in the broader proposal alongside the SOW. That said, if combining scope and pricing into one document works for your workflow, do it. GetPaidFirst bundles scope, pricing, and payment terms into a single proposal so your client sees everything in one place.