Scope of Work Template

Professional Scope of Work Template

Define project success clearly with a detailed SOW covering deliverables, timeline, acceptance criteria, and change management.

Contract Template

1. Project Overview

High-level summary of the project.

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

What the project will achieve.

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

Specific items that will be delivered.

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

Project schedule and key dates.

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

What the client needs to provide.

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

Conditions assumed to be true for this scope.

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

What is NOT included.

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

How feedback and changes are handled.

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

Process for handling scope changes.

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

Project cost and payment terms.

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

Sign-off on the scope of work.

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

Detailed Deliverables

Comprehensive sections for listing every project deliverable.

Timeline & Milestones

Clear project phases with dates and dependencies.

Acceptance Criteria

Defines what "done" looks like for each deliverable.

Assumptions

Documents project assumptions to prevent misunderstandings.

Exclusions

Explicitly states what's NOT included to prevent scope creep.

Change Process

Defines how scope changes will be handled.

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

Manage Project Scope Effortlessly

AgencyPro helps you define scope, track deliverables, and manage changes with built-in approval workflows.