Scope of Work Template: How to Write One (With Examples and a Checklist)
Ask any freelancer or agency owner what causes the most stress in client projects, and "unclear expectations" will be near the top. The client thought the price included social media graphics. You thought it included only the website. Neither of you wrote it down, so now you are both unhappy.
A scope of work, often shortened to SOW, is the fix. It is a clear, written description of what will be done, by whom, by when and to what standard. In this guide you will learn what a scope of work is, what to put in it, how to word each part, and see a template you can copy and adapt.
What is a scope of work?
A scope of work is a document, or a section of a larger agreement, that defines the boundaries of a project. It lists the tasks, deliverables, timeline, roles and responsibilities, and states clearly what is not included. Think of it as the project's fence: everything inside is covered by the agreed price, and anything outside needs a new conversation.
You will hear "scope of work" and "statement of work" used interchangeably. Some organisations use "statement of work" for a longer document that also includes pricing and terms. For small projects, the difference is not important; clarity is. The SOW normally sits between the sale and the legal agreement: the business proposal introduces the plan, the SOW details it, and the service agreement makes it binding.
Why a scope of work matters
- Prevents scope creep. When extra requests arrive, you have a document to compare them to.
- Aligns expectations. Both sides read the same words before work starts.
- Makes pricing defensible. A client can see what they are paying for and why.
- Speeds up approvals. Clear acceptance criteria stop endless "one more tweak" loops.
- Helps if there is a dispute. A written scope is far stronger evidence than memory.
What to include in a scope of work
1. Project overview
Two or three sentences on the purpose and background: what the client wants to achieve and why this project exists. Keep it in plain language.
Sample: "Northfield Dental wants a new website to increase online appointment bookings and replace its outdated brochure site."
2. Objectives and success criteria
State what "done" and "successful" look like. Objectives should be as measurable as possible, but only include outcomes you can influence. "Publish a mobile-friendly booking page that lets patients request appointments in under two minutes" is better than "double the bookings."
3. Deliverables
This is the heart of the SOW. List each item the client will receive, with quantity, format and any relevant standard.
Sample: "Deliverable 1: five-page website (home, services, team, contact, booking) built on [platform]. Deliverable 2: two rounds of revisions. Deliverable 3: one 30-minute training session, recorded."
4. Tasks and activities
Outline the main work steps that lead to the deliverables: research, design, development, testing, launch. You do not need to list every micro-task. Group them into phases so the client can follow the process.
5. Out of scope
Every strong scope has an exclusions list. Write down anything the client might reasonably expect but that you are not including: copywriting, photography, hosting, ongoing maintenance, integrations, translation. This one section prevents many disagreements.
6. Timeline and milestones
Give a start date, milestone dates and a completion date. Link each milestone to a deliverable, and note the review time the client has at each stage. For example, "Client will provide feedback within three business days of each delivery."
7. Roles and responsibilities
Say who does what on both sides, including the client's decision maker and a single point of contact. List the client's obligations: content, logins, approvals, payments. If the client is late, the timeline must be able to move.
8. Assumptions and dependencies
Write down what you are assuming to be true: "Client will provide final text and images by [date]," "Existing website hosting remains available," "No more than two stakeholders review each stage." If an assumption fails, the scope may need adjusting.
9. Acceptance criteria and revisions
Explain how a deliverable is judged complete: it meets the description, passes agreed tests, and is approved in writing or considered accepted after a set number of days without feedback. State how many revision rounds are included and how additional ones are priced.
10. Change process
Explain how changes are handled: the client requests in writing, the provider estimates the impact on price and timeline, both approve before work begins. This turns "scope creep" into "paid change requests."
11. Fees and payment schedule
You can place pricing here or refer to the proposal or agreement. Either way, keep numbers consistent across all documents. When it is time to bill, use clean invoices as described in our guide to creating a professional invoice.
Keep scope, proposal and contract in sync. Contract & Proposal Generator Pro helps you produce matching documents for each client, so the wording you agree on stays consistent from offer to signature.
See the product Buy nowCopy-ready scope of work template
Replace the bracketed text with your own project details.
Scope of Work: [Project name]
Client: [Client name] · Provider: [Your name or company] · Date: [Date]
1. Overview. [Two or three sentences about the goal and background.]
2. Objectives. [Objective 1]; [Objective 2]; [Success measure].
3. Deliverables. [Deliverable, quantity, format]; [Deliverable, quantity, format]; [Number] rounds of revisions.
4. Work plan. Phase 1: [activities]. Phase 2: [activities]. Phase 3: [activities].
5. Out of scope. [Excluded item]; [Excluded item]; [Excluded item].
6. Timeline. Start: [date]. Milestone 1: [date]. Milestone 2: [date]. Completion: [date].
7. Responsibilities. Provider: [list]. Client: [list, with due dates].
8. Assumptions. [Assumption]; [Assumption].
9. Acceptance. Deliverables are accepted when [criteria]. Client has [number] business days to review.
10. Changes. Requests outside this scope will be quoted in writing and start after approval.
11. Fees. [Total or reference to agreement]. Payment schedule: [details].
Weak vs. strong scope wording
Small changes in wording make a big difference. Compare:
- Weak: "Design a logo." Strong: "Design one primary logo with three initial concepts, two rounds of revisions, and final files in SVG, PNG and PDF."
- Weak: "Write blog content." Strong: "Write four blog posts of 1,200 to 1,500 words each, including keyword research and one round of edits per post."
- Weak: "Ongoing support." Strong: "Up to five hours of support per month by email, with responses within two business days."
- Weak: "Unlimited revisions." Strong: "Two rounds of revisions. Additional rounds are billed at [rate] per hour."
The strong versions use numbers, formats and limits. If a sentence cannot be checked, it is probably too vague.
Scope of work mistakes to avoid
Writing vague verbs
Words like "support," "assist," "optimise" and "manage" can mean anything. Replace them with specific actions and outputs.
Skipping the out-of-scope list
What you leave unsaid, the client will assume is included. Say it out loud.
Ignoring client responsibilities
If your work depends on the client's content or decisions, write down when they are due and what happens if they are late.
Making it too long
A scope that nobody reads does not protect you. For most small projects, one to three pages is plenty.
Not updating it when things change
If the project changes direction, update the SOW in writing. The document should always reflect the current agreement. For more on handling this, see our guide on how to prevent scope creep as a freelancer.
How to write a scope of work in six steps
- Interview the client. Ask what success looks like, who approves work, what has been tried before and what constraints exist.
- List the deliverables. Write everything the client will actually receive.
- Break down the work. Identify the phases and estimate the time each requires.
- Define the fence. Write the out-of-scope list and the assumptions.
- Add the process. Timelines, approvals, revisions and change requests.
- Review together. Send it, walk through it on a short call if needed, and get written confirmation.
If you send many of these, a repeatable structure saves hours. Contract & Proposal Generator Pro is designed to help you keep your proposals and contracts, and the scope details inside them, consistent from project to project. For a look at the freelancer side of the paperwork, our freelance contract template guide and freelance proposal template pair well with this one.
Scope of work checklist
- Project overview and goal stated in plain language
- Measurable objectives you can actually influence
- Deliverables with quantity, format and standard
- Main phases of work
- Out-of-scope items listed
- Timeline with milestones and review periods
- Roles and client responsibilities with due dates
- Assumptions written down
- Acceptance criteria and included revisions
- Change process and payment terms
Frequently asked questions
What is a scope of work?
A scope of work is a document that describes the work to be done on a project, including deliverables, tasks, timeline, responsibilities and what is not included.
What is the difference between a scope of work and a statement of work?
The terms are often used interchangeably. A statement of work is sometimes a larger document that includes the scope plus terms, pricing and legal details.
How detailed should a scope of work be?
Detailed enough that both sides could tell whether an item was delivered or not, without listing every tiny task. Specific quantities, formats and acceptance criteria are the key.
Can the scope of work change during a project?
Yes, but changes should be agreed in writing, with any effect on price and timeline stated before the extra work begins.
Final thoughts
A good scope of work is short, specific and fair. It tells the client what they will get, tells you what you are responsible for, and gives both of you a calm way to handle changes. Write it before the work starts, keep it consistent with your proposal and contract, and update it in writing when things change.