Scope of Work Template — Deliverables, Timeline & Change Control
Prevent scope creep and project disputes with a detailed SOW that specifies every deliverable, sets clear acceptance criteria, and establishes a change management process.
Contract Template
1. Project Overview
Provides high-level project summary, identifies parties, and establishes version control for scope document revisions that may occur during project planning.
Project Name: [PROJECT NAME] Client: [CLIENT NAME] Provider: [YOUR NAME/COMPANY] Prepared By: [NAME] Date: [DATE] Version: [VERSION NUMBER] Project Summary: [2-3 SENTENCE DESCRIPTION OF THE PROJECT AND ITS GOALS]
2. Objectives
Defines project goals and success metrics that guide deliverable creation and provide measurable outcomes for project completion.
The objectives of this project are to: 1. [OBJECTIVE 1 - e.g., Redesign the company website to improve user experience] 2. [OBJECTIVE 2 - e.g., Increase mobile conversion rate by 25%] 3. [OBJECTIVE 3 - e.g., Establish brand consistency across digital touchpoints] Success Metrics: - [METRIC 1 - e.g., Page load time under 3 seconds] - [METRIC 2 - e.g., Mobile bounce rate below 40%]
3. Deliverables
Specifies every deliverable with detailed descriptions, formats, quantities, and acceptance criteria that define exactly what constitutes completion.
Provider will deliver the following: Deliverable 1: [NAME] - Description: [DETAILED DESCRIPTION] - Format: [FILE TYPE, DIMENSIONS, etc.] - Quantity: [NUMBER] - Acceptance Criteria: [WHAT MAKES IT COMPLETE] Deliverable 2: [NAME] - Description: [DETAILED DESCRIPTION] - Format: [FILE TYPE, DIMENSIONS, etc.] - Quantity: [NUMBER] - Acceptance Criteria: [WHAT MAKES IT COMPLETE] [CONTINUE FOR ALL DELIVERABLES]
4. Timeline & Milestones
Breaks project into phases with start/end dates, milestone deliverables, dependencies on client inputs, and assumptions about feedback timing that affect schedule.
Project Start Date: [DATE] Project End Date: [DATE] Phase 1: [PHASE NAME] - [START] to [END] - Milestone: [DESCRIPTION] - Deliverables: [LIST] - Dependencies: [WHAT'S NEEDED FROM CLIENT] Phase 2: [PHASE NAME] - [START] to [END] - Milestone: [DESCRIPTION] - Deliverables: [LIST] - Dependencies: [WHAT'S NEEDED FROM CLIENT] [CONTINUE FOR ALL PHASES] Note: Timeline assumes Client provides feedback within [X] business days at each milestone
5. Client Responsibilities
Lists all materials, access, content, and approvals clients must provide, with deadlines and consequences for delays that extend project timeline.
Client will provide the following: - [ITEM 1 - e.g., Brand guidelines and logo files] - [ITEM 2 - e.g., Access to existing website/systems] - [ITEM 3 - e.g., Written content/copy] - [ITEM 4 - e.g., Photography/imagery] - [ITEM 5 - e.g., Timely feedback at each milestone] Client will designate a single point of contact for approvals Primary Contact: [NAME], [EMAIL], [PHONE] Delays in Client responsibilities may extend project timeline
6. Assumptions
Documents project conditions assumed to be true, with provision that incorrect assumptions may require scope and pricing adjustments via change order.
This SOW assumes: - [ASSUMPTION 1 - e.g., Client has rights to all provided materials] - [ASSUMPTION 2 - e.g., Existing systems are functioning properly] - [ASSUMPTION 3 - e.g., Feedback will be consolidated from single source] - [ASSUMPTION 4 - e.g., Project will be completed in English only] If assumptions prove incorrect, scope and pricing may need adjustment
7. Out of Scope / Exclusions
Explicitly lists services, deliverables, and work NOT included in current scope, with note that excluded items can be added via change order at additional cost.
The following are NOT included in this SOW: - [EXCLUSION 1 - e.g., Copywriting/content creation] - [EXCLUSION 2 - e.g., Photography or stock image purchase] - [EXCLUSION 3 - e.g., Ongoing maintenance after launch] - [EXCLUSION 4 - e.g., Third-party integrations not specified] - [EXCLUSION 5 - e.g., Print materials] Excluded items can be added via Change Order at additional cost
8. Revisions & Approval Process
Defines included revision rounds per milestone, approval workflow requiring written sign-off before proceeding, and pricing for additional revisions beyond included rounds.
Included Revisions: - [X] rounds of revisions at each milestone - Revision round = one consolidated set of changes Approval Process: 1. Provider presents deliverable 2. Client reviews and provides consolidated feedback within [X] business days 3. Provider implements changes 4. Client approves or requests final revisions 5. Written approval required to proceed to next phase Additional revisions: $[AMOUNT] per round or $[RATE]/hour
9. Change Management
Establishes mandatory change order process requiring written approval with revised scope, timeline, and pricing before any scope changes can proceed.
Changes to this SOW must follow this process: 1. Client submits change request in writing 2. Provider assesses impact on timeline and budget 3. Provider issues Change Order with revised scope/cost 4. Client approves Change Order in writing 5. Work proceeds on approved changes No changes will be made without written Change Order approval Change Order approval may extend project timeline
10. Budget & Payment
Specifies total project investment, payment schedule tied to milestone completion, payment terms, and consequences for late payments that may pause project progress.
Total Project Investment: $[AMOUNT] Payment Schedule: - [X]% ($[AMOUNT]) - Due upon SOW approval - [X]% ($[AMOUNT]) - Due upon [MILESTONE 1] completion - [X]% ($[AMOUNT]) - Due upon final delivery Payment Terms: Net [X] days from invoice date Late payments may pause project progress
11. Approval
Executes the scope of work with dated signatures from client and provider, authorizing project work to begin and making the SOW legally binding.
Approval of this SOW authorizes Provider to begin work as described. Client Approval: _________________ Date: _________ Print Name: _________________ Title: _________________ Provider Approval: _________________ Date: _________ Print Name: _________________
Disclaimer: This template is provided for informational purposes only and does not constitute legal advice. We recommend having a qualified attorney review any contract before use to ensure it meets your specific needs and complies with applicable laws in your jurisdiction.
Pro Tips
- Be obsessively specific about deliverables—vagueness leads to disputes
- List exclusions prominently to set expectations
- Document all assumptions so everyone is working from the same understanding
- Tie payment milestones to deliverable approval, not dates
- Include a change management process BEFORE you need it
- Get written approval at each phase before moving forward
Key Features of This Contract
Acceptance Criteria Definition
Specifies exactly what "done" means for each deliverable—functional requirements, quality standards, format specifications, and approval conditions. Prevents disputes about whether work is complete and gives you clear benchmarks to meet. Clients can't claim deliverables are incomplete when they meet defined acceptance criteria, protecting you from endless revision requests.
Milestone-Based Payment Triggers
Links payment milestones to deliverable approval rather than calendar dates, ensuring you get paid when clients accept work, not when arbitrary deadlines pass. Each milestone has specific deliverables that must be approved before payment is due, creating clear payment gates that protect your cash flow and incentivize timely client feedback.
Assumption Documentation
Explicitly documents project assumptions (client-provided materials, system availability, single point of contact, etc.) that the scope is based on. When assumptions prove false, scope and pricing can be adjusted via change order. Prevents clients from changing project conditions without acknowledging impact on timeline and budget.
Change Order Requirement
Establishes mandatory change order process—all scope changes require written approval with revised timeline and pricing before work begins. Prevents scope creep disguised as "small additions" and ensures you're compensated for extra work. No verbal approvals or "just do this too" requests can proceed without formal change order.
Client Responsibility Checklist
Lists everything clients must provide (content, access, approvals, assets) with deadlines and consequences for delays. Makes client dependencies explicit and protects you from project delays caused by client inaction. Delays in client responsibilities extend project timeline without penalty to you.
Exclusion Prominence
Prominently lists what's NOT included in scope, preventing clients from assuming services are included when they're not. Common exclusions like ongoing maintenance, third-party integrations, or content creation are explicitly stated upfront. Makes it easy to point to exclusions when clients request out-of-scope work.
Frequently Asked Questions
What's the difference between a SOW and a contract?
A contract is the legal agreement covering terms, payment, liability, etc. A SOW details the actual work—deliverables, timeline, and requirements. Often the SOW is attached to or referenced by the contract.
How detailed should deliverables be?
As detailed as needed to prevent misunderstanding. "Website design" is too vague. "5-page website design including homepage, about, services, contact, and blog template, delivered as Figma files" is better.
What if the client doesn't know exactly what they want?
Start with a discovery phase. The SOW for discovery produces requirements that inform the SOW for the main project. Charge for discovery—it's real work.
How do I handle scope creep?
Point to the SOW. When clients request additions, say "That's not in our current scope. I can add it via change order for $X." Having a documented SOW gives you the leverage to have this conversation.
Related Contract Templates
Freelance Contract Template
A complete independent contractor agreement covering project scope, milestone payments, intellectual property assignment upon final payment, and kill fee provisions. Includes revision limits and late payment penalties that protect freelancers from scope creep and non-payment. Ensures you retain ownership of your work until every invoice is settled, giving you leverage to collect payment.
View TemplateDesign Contract Template
Designer-focused contract covering concept exploration phases, revision rounds per design stage, and ownership of unused concepts that remain your intellectual property. Includes file format specifications, source file licensing terms, and portfolio usage rights that let you showcase completed work. Protects against endless revision cycles and ensures you retain valuable unused concepts for future projects or other clients.
View TemplateConsulting Contract Template
Consulting agreement covering engagement scope, flexible billing structures (hourly, project-based, or retainer), and strong confidentiality protections for sensitive business information. Includes clear distinction between advisory services and implementation work, protecting consultants from scope creep into execution. Features non-solicitation clauses and independent contractor provisions that maintain consultant autonomy while protecting client interests.
View TemplateRetainer Agreement Template
Retainer agreement structuring monthly service allocation (hours or deliverables), rollover policies for unused capacity, and automatic renewal terms that create predictable recurring revenue. Includes service level commitments like response times and priority access, plus usage reporting requirements that keep clients informed. Features early termination fees during initial term and flexible overage billing for work beyond monthly allocation.
View TemplateManage Project Scope Effortlessly
Define project deliverables clearly, track milestone completion, and handle scope changes with automated approval workflows and change orders.