How to Write a Scope of Work: Free SOW Template + Guide

What Is a Scope of Work?

A scope of work (SOW) is a document that defines exactly what will be done, by whom, by when, and for how much. It is the most important single document in any service-based project — because everything that goes wrong in a project can usually be traced back to an unclear or missing scope.

Think of it as the contract for a specific project. If you have a master service agreement with a client, the SOW is the project-level attachment that specifies each engagement's deliverables, timeline, and cost.

SOW vs Statement of Work vs Project Brief

A scope of work and statement of work are often used interchangeably. The SOW is more specific and operational — it is what gets signed and followed, not what gets pitched.

The 8 Sections Every SOW Must Have

1. Project Overview

A brief (2–3 sentence) description of what the project is and what problem it solves. Example: "This project covers the design and development of a 5-page marketing website for [Client Name] to replace their existing site and improve lead generation."

2. Scope of Work (Deliverables)

The most critical section. List every deliverable — what it is, what format it will be in, and what "done" looks like. Be painfully specific:

• ✅ "Five responsive web pages designed in Figma: Home, About, Services, Blog (template), Contact"
• ❌ "Website design"

3. Out of Scope

Explicitly state what is NOT included. This is as important as what is included. Example: "This scope does not include copywriting, photography, SEO optimization, CMS setup, or hosting configuration." Every item not listed here is a potential scope creep argument.

4. Timeline and Milestones

Include: project start date, key milestone dates (e.g. wireframes due, first review, final delivery), and the expected end date. A table format works well here.

5. Responsibilities

Who does what. Specify the client's responsibilities too — content provision, approvals, access to existing systems, stakeholder availability for reviews. Missed client responsibilities are the most common cause of timeline slippage.

6. Fees and Payment Schedule

Total project fee, payment milestones, and due dates. Example: "£5,000 total. 25% on signing, 25% on wireframe approval, 50% on final delivery." Include your hourly rate for additional work and your change order process.

7. Revision and Approval Process

Number of revision rounds included, the turnaround time for each review cycle, how revisions are submitted (email, comments on a shared doc, a specific platform), and what counts as "approval" (written email confirmation).

8. Terms and Conditions

Intellectual property (who owns the work on full payment), confidentiality, termination conditions, governing law. This section is often covered by a master service agreement — if so, reference it here rather than repeating it.

SOW Example — Web Design Project

Project: Marketing website redesign for Acme Ltd
Deliverables: 5 responsive pages (Figma → HTML/CSS), 1 blog template, mobile and desktop variants
Out of Scope: Copywriting, photography, SEO, hosting, CMS integration
Timeline: Start 2 Aug → Wireframes 15 Aug → First review 1 Sep → Launch 15 Sep
Client Responsibilities: All copy and images by 10 Aug; 48-hour turnaround on review feedback
Fee: £8,000 — 30% on signing, 30% on wireframe approval, 40% on launch
Revisions: Two rounds of revisions per milestone included; additional revisions at £100/hour
IP: Full ownership transfers to client on receipt of final payment

SOW Mistakes That Cause Scope Creep

• Vague deliverables ("design the website" not "design 5 specific pages")
• No "out of scope" section — clients assume everything is included
• Missing client responsibilities — no deadline for client to provide content
• Unlimited revisions — never include these; they are a career-ending trap
• No change order process — verbal changes have no paper trail

How to Handle Changes After the SOW Is Signed

Use a change order — a brief written document that both parties sign, describing the new work and the additional fee. Even a one-sentence email that says "Can you add X?" followed by your "Yes, that's an additional £500, shall I proceed?" (replied to with "Yes, go ahead") constitutes a change order. Always document it.

Frequently Asked Questions

Is a scope of work the same as a contract?

Not exactly. A full contract includes payment terms, governing law, dispute resolution, and IP clauses. A SOW typically focuses on deliverables and timelines. For best protection, have both: a master service agreement (for standard terms) and a SOW for each project.

How long should a scope of work be?

1–3 pages for typical freelance projects. Large enterprise projects may run 10–20 pages. If you need more than 3 pages for a small project, you are either overly detailed or the project is more complex than initially scoped.

Who writes the scope of work?

Either party can initiate it. It is in your interest as the contractor to write the first draft — the party that writes the document controls the framing. Share it with the client for review and agreement before signing.

What is a change order?

A change order is an amendment to the signed SOW that documents a new request, the additional cost, and both parties' agreement. It protects you from doing additional work without additional pay, and protects the client from being surprised by additional invoices.

Can I use a scope of work template?

Yes — a template gives you the structure so nothing is forgotten. Customize every section entirely for each project; a template is a scaffold, not a finished document.