Introduction
A scope of work (SOW) is the most important document in any freelance project. It defines exactly what you’ll deliver, when, and for how much. Without it, scope creep is inevitable — clients will ask for “one more thing” until you’ve done 3x the work for the same price.
This post gives you a SOW template and the strategy behind it.
What is a scope of work?
A SOW is a detailed description of:
- What you’ll deliver (specific deliverables)
- When you’ll deliver it (timeline with milestones)
- How much it costs (pricing and payment terms)
- What’s NOT included (explicit exclusions)
- How changes are handled (change request process)
It’s more detailed than a proposal and less legal than a contract. Think of it as the “project blueprint.”
The SOW template
═══════════════════════════════════════════
SCOPE OF WORK (SOW)
═══════════════════════════════════════════
Project: [Project Name]
Client: [Client Name]
Freelancer: [Your Name]
Date: [Date]
Version: 1.0
───────────────────────────────────────────
1. PROJECT OVERVIEW
───────────────────────────────────────────
[2-3 sentences: what the project is and the business goal]
Example: "Redesign the company website to improve mobile experience, reduce load time, and increase lead generation. The new site will be faster, modern, and optimized for search engines."
───────────────────────────────────────────
2. DELIVERABLES
───────────────────────────────────────────
### Included:
1. [Deliverable 1 — specific and measurable]
- [Sub-detail 1]
- [Sub-detail 2]
2. [Deliverable 2]
- [Sub-detail 1]
3. [Deliverable 3]
### NOT included (can be added as change orders):
- [Explicit exclusion 1 — e.g., "Content writing"]
- [Explicit exclusion 2 — e.g., "Logo design"]
- [Explicit exclusion 3 — e.g., "Ongoing maintenance"]
───────────────────────────────────────────
3. TIMELINE & MILESTONES
───────────────────────────────────────────
| Milestone | Date | Deliverable | Client Action |
|---|---|---|---|
| Kickoff | [Date] | Project start, requirements confirmed | Provide content, assets |
| Design | [Date] | Wireframes + design mockups | Review and approve |
| Development | [Date] | Working site on staging URL | Review and test |
| Revisions | [Date] | Revisions based on feedback | Provide feedback |
| Launch | [Date] | Live site + handover | Final approval + payment |
Total duration: [X] weeks
Timeline may extend if:
- Client delays feedback/content by more than 3 business days
- Scope changes are requested
- Force majeure events occur
───────────────────────────────────────────
4. PRICING & PAYMENT
───────────────────────────────────────────
Total project fee: ₹[Amount]
Payment schedule:
- 50% advance (₹[Amount]) — due before work begins
- 50% final (₹[Amount]) — due on project completion
Additional work: ₹[rate]/hour (billed in 30-minute increments)
Payment methods: UPI, bank transfer, Razorpay
Late payment: 2% per month interest after 15 days
───────────────────────────────────────────
5. REVISIONS
───────────────────────────────────────────
Included: [X] rounds of revisions per deliverable
A "revision" is: changes to existing work within the agreed scope.
A "new request" is: additional features, pages, or functionality not in the original scope.
Additional revisions: ₹[rate]/round
───────────────────────────────────────────
6. CHANGE REQUEST PROCESS
───────────────────────────────────────────
Any changes to scope must follow this process:
1. Client submits change request (email or form)
2. Freelancer provides impact assessment (time + cost)
3. Client approves in writing
4. Freelancer implements the change
5. Change is invoiced separately
No work on changes begins without written approval.
───────────────────────────────────────────
7. CLIENT RESPONSIBILITIES
───────────────────────────────────────────
The client agrees to:
- Provide content, images, and brand assets by [Date]
- Review deliverables within 3 business days
- Provide feedback in a single consolidated document
- Be available for 1 kickoff call and 1 review call
- Process payments per the agreed schedule
───────────────────────────────────────────
8. FREELANCER RESPONSIBILITIES
───────────────────────────────────────────
The freelancer agrees to:
- Deliver all agreed deliverables on time
- Communicate progress weekly
- Respond to client messages within 24 hours
- Provide [X] rounds of revisions
- Hand over all files and credentials on completion
───────────────────────────────────────────
9. ASSUMPTIONS
───────────────────────────────────────────
- Client will provide content in [format: Google Doc, Word, etc.]
- Client has existing hosting and domain (or will purchase)
- Client will handle legal/compliance requirements
- Third-party integrations (payment gateways, APIs) are client's responsibility to set up
───────────────────────────────────────────
10. SIGN-OFF
───────────────────────────────────────────
Freelancer: _________________ Date: _______
Client: _____________________ Date: _______
═══════════════════════════════════════════
Writing a good SOW
1. Be specific
❌ “Build a website” ✅ “Build a 5-page responsive website (Home, About, Services, Portfolio, Contact) with a contact form, Google Analytics, and basic SEO”
2. List exclusions explicitly
The “NOT included” section is more important than “Included.” Clients read what’s included; they don’t read what’s not. Make exclusions crystal clear.
3. Define “revision”
A revision is: changing the color of a button. A new request is: adding a new page. Define the difference.
4. Set client responsibilities
Clients delay projects by not providing content, feedback, or access. Make their responsibilities explicit with deadlines.
5. Include a change request process
No work on changes without written approval. This single clause prevents 90% of scope creep disputes.
SOW vs proposal vs contract
| Proposal | SOW | Contract | |
|---|---|---|---|
| Purpose | Pitch your services | Define project details | Legal agreement |
| When | Before client says yes | After client says yes | After client says yes |
| Length | 1-2 pages | 2-4 pages | 2-4 pages |
| Contains | Scope, price, timeline | Detailed scope, milestones, change process | Legal terms, IP, liability |
| Legal weight | Low | Medium | High |
Flow: Proposal → Client approves → SOW + Contract → Work begins
You can combine SOW and contract into one document for simplicity.
Common mistakes
- Vague deliverables — “website design” invites scope creep. “5-page responsive website with X, Y, Z” doesn’t.
- No exclusions — if you don’t list what’s NOT included, clients assume everything is.
- No change process — ad-hoc changes lead to disputes. Formalize it.
- No client responsibilities — clients delay projects by not providing content. Make them accountable.
- Not getting sign-off — an unsigned SOW is just a document. Get both signatures.
Key Concepts
- Scope of work (SOW) = detailed project blueprint
- Deliverable = specific output with clear definition
- Milestone = checkpoint with date and deliverable
- Change request = formal process for adding scope
- Exclusion = work explicitly NOT included
- Sign-off = both parties agree and sign
What to Try Next
- Write a freelance proposal that wins
- Handle scope creep professionally
- Create a freelance contract for legal protection
- Price your services with a proven framework
FAQ
SOW vs proposal — do I need both?
For small projects (under ₹25,000), a detailed proposal is enough. For larger projects, send a proposal first, then a SOW after approval. For ongoing retainers, a SOW is essential.
How detailed should the SOW be?
Detailed enough that there’s no ambiguity about what’s included. If a client could reasonably interpret “website design” as “including a blog, e-commerce, and a booking system,” your SOW isn’t detailed enough.
What if the client wants to change something mid-project?
That’s what the change request process is for. No work on changes without written approval and a quote. This protects both you (fair compensation) and the client (clear expectations). See Handle Scope Creep.