On this page
A scope of work describes the work itself: the tasks, the deliverables, the timeline and what is not included. A statement of work is the whole agreement for a project. It contains the scope of work, plus the objectives, payment terms, how finished work is accepted and how changes are handled. Both get shortened to SOW, which is where the confusion starts. If you already have a signed contract with the client, a scope of work attached to it is usually enough. If nothing is agreed yet about money, dates or sign-off, you need a full statement of work.
The difference between a scope of work and a statement of work matters most at the worst possible moment: when you and a client disagree about what was promised. One document says what you will do. The other says what you will do, what you will be paid, and what happens when the plan changes. As Asana puts it, both are often abbreviated as SoW, but they are not the same thing.
This guide covers how the two compare, how to decide which one you need, what goes in each, and two worked examples for the same small project, so you can see the scope of work sitting inside the statement of work. Both are part of the client delivery system in our map of business operations for a one-person business.
Scope of Work vs Statement of Work at a Glance
| Scope of work | Statement of work | |
|---|---|---|
| Answers | What will be done? | How will this whole project work? |
| Contains | Tasks, deliverables, timeline, exclusions | Objectives, the scope of work, schedule, payment, acceptance, changes, signatures |
| Stands alone? | Often a section inside a bigger document | A complete document, sometimes attached to a master contract |
| Legal weight | Binding when it is part of a signed agreement | Usually signed by both sides and treated as part of the contract |
| Size | Short: a focused list | Longer: it covers the whole project |
| Use it when | Terms are already agreed and you are defining the work | You are starting a project and nothing is agreed yet |
How to Decide Which One You Need
Four questions settle it for most projects:
- Is there already a signed contract with this client? If you work under a master agreement or a freelance contract that covers payment and legal terms, a scope of work for the new project is usually enough.
- Is anything about money still open? If the price, the deposit or the payment dates are not agreed in writing, you need a statement of work. A scope of work alone says nothing about when you get paid.
- Does anyone need to sign off the finished work? If a client has to approve deliverables before you invoice, the acceptance process belongs in a statement of work, so "done" means the same thing to both of you.
- Is the work internal? For a project inside your own business, or a task you are handing to a contractor you already work with, a scope of work is all you need.
Aziz's take: When in doubt, write the statement of work. The extra page about payment and sign-off takes twenty minutes, and it is the page you will reach for the first time a client says "I thought that was included".
What to Put in a Scope of Work
A scope of work only does its job if it is specific. NYU's contract guidelines name a lack of specificity as the most common problem, because a vague scope cannot settle a disagreement about what should have been delivered. Include:
- Deliverables, each with a task and an end product. Not "design a website" but "design six page layouts, delivered as Figma files".
- What is out of scope. Name at least three things you will not do. This is the line that prevents most arguments later.
- The timeline. A date or week for every deliverable, not just a final deadline.
- Revision limits. How many rounds of changes are included, and what happens after that.
- Assumptions. What the client must provide, and by when, for the timeline to hold.
What Are the Key Components of a Statement of Work?
A statement of work wraps the scope in everything else the project needs to run. For a small business project, that usually means:
- Background and objectives: why the project exists and what success looks like, in two or three sentences.
- The scope of work: everything in the section above.
- Schedule and milestones: the key dates, including the start date and when each stage is due.
- Price and payment terms: the total fee, the deposit and when each payment is due. Tying payments to milestones means you are never owed more than one stage of work.
- Acceptance criteria: how a deliverable is approved, by whom, and how long the client has to review it.
- Change process: how new requests are made, priced and approved before any work on them starts.
- Responsibilities and contacts: who decides on each side, and who supplies what.
- Signatures: both parties sign and date it.
Example of a Scope of Work
Here is a scope of work for a common small project: a freelance designer redesigning the website of a local bakery. First, the difference between a weak line and a usable one:
| Weak | Usable |
|---|---|
| Design a new website. | Design six page layouts (home, about, menu, catering, order, contact) for mobile and desktop, delivered as Figma files. |
| Revisions as needed. | Two rounds of revisions per page. Further rounds are billed at the hourly rate. |
| Launch in the spring. | Final files delivered by the end of week 6, provided content arrives by the end of week 1. |
The full scope of work, written that way:
- Deliverables: six page layouts for mobile and desktop as Figma files, a one-page style guide (colours, fonts, buttons) and an exported image pack for the developer.
- Out of scope: writing the copy, photography, a new logo, building or hosting the site, and connecting an online ordering system.
- Timeline: home page draft in week 2, remaining pages in week 4, final files in week 6.
- Revisions: two rounds per page, collected in one list per round.
- Assumptions: the bakery supplies all text and photos by the end of week 1 and returns feedback within three business days.
Example of a Statement of Work
The statement of work for the same project includes that scope of work word for word, then adds the parts that decide money and sign-off. The figures below are illustrative:
| Section | What it says for the bakery project |
|---|---|
| Objective | Replace the current site with one customers can use on a phone to see the menu and place catering enquiries. |
| Scope of work | As written above, including the out-of-scope list. |
| Schedule | Starts on the date the deposit is received. Final files at the end of week 6. |
| Fee and payments | $6,000 in total: $2,400 deposit before work starts, $1,800 when the home page is approved, $1,800 on delivery of final files. |
| Acceptance | Each stage is approved in writing by the owner. If there is no feedback within five business days, the stage counts as approved. |
| Changes | New pages or features are quoted in writing and approved before any work on them starts. |
| Contacts | The owner approves all work. The designer is the single point of contact. |
| Signatures | Both parties sign and date before the deposit is paid. |
Notice what the scope of work could not answer on its own: when the $6,000 is paid, what counts as approved, and what happens when the bakery asks for a seventh page. Those are the questions that turn a small project into a dispute, and they all live in the statement of work.
What Is a Project Scope?
In project management, the project scope is all the work needed to deliver the result, and nothing beyond it. A scope statement is the document that records it. In a client agreement, the scope of work is the client-facing version of the same idea: it turns "what this project includes" into a list both sides can check deliverables against.
That list is what you read out at a project kickoff, including the out-of-scope items, so everyone starts from the same picture.
What Is an SOW in Business?
In business, SOW usually means statement of work. Companies that hire the same agency or contractor often sign one master services agreement covering the legal terms once, then a separate SOW for each project. That way only the project-specific parts (scope, schedule, price, acceptance) are written each time.
Larger organizations use other names for similar documents. In US federal contracting, for example, an agency may issue a performance work statement (PWS) or a statement of objectives (SOO) instead, which describe the results required rather than every task.
Aziz's take: The out-of-scope list is the most valuable line in either document. Clients rarely argue about what you said you would do. They argue about what they assumed was included, and a written list of exclusions is the only thing that answers that politely. When a request does fall outside it, handling the scope conversation is far easier when you can point to the line.