How to Write a Scope of Work (2026): 8 Parts, a Template and a Full Example

To write a scope of work, put eight parts on about one page: the objectives, the deliverables, what is in and out of scope, your assumptions, a timeline with milestones, the revision rounds, the acceptance criteria and the change process. Write the deliverables first, because every other part refers back to them. Draft it the same day as the discovery call, walk the client through it on a short call, and get a clear yes before any work starts.

The example scope of work in this guide is illustrative: the client, the numbers and the hourly rate are made up to show the method. This is general information, not legal advice; for a large contract, have a lawyer review the terms. Prices checked October 25, 2026 on each vendor’s own pricing page (PandaDoc’s on October 19), in US dollars and billed monthly unless noted.

Jump to the 8 parts, the copy-paste template, the full example, mistakes to avoid or the checklist.

What is a scope of work?

A scope of work pins down the job inside a client agreement: what you will deliver, by when, and what doesn’t count. It turns a conversation (“we’ll look at your operations”) into a list both sides can check (“six interviews, one process map, a report of up to fifteen pages, one workshop”).

Write one for any fixed-price job and for any project longer than a few weeks. Once a price is fixed, every unclear word becomes your cost.

Scope of work vs statement of work vs proposal

For freelancers and small teams, the scope usually lives inside the proposal as its scope section, so the client accepts one document. Our guide on how to write a business proposal covers the rest of that document: the problem, the options and the terms.

How to write a scope of work, step by step

Work in this order:

1. Your call notes. Write down the goal, the deadline and the client’s own words while the discovery call is fresh.
2. The deliverables. List what you will hand over first. Every other part refers back to this list.
3. The out list. Write what is not included while the “in” list is in front of you.
4. The dates. Milestones, sign-offs and the client’s own deadlines.
5. Review it together. Walk the client through it on a short call before they accept.

Draft it the same day as the call if you can. Questions on the review call are cheap; questions in week four are not. Keep a template, so no part gets skipped in a busy week.

The 8 parts of a scope of work

Each part answers a question the client would otherwise ask halfway through the project.

1. Objectives

One or two sentences on what the work is for and how you will both know it worked. Use the client’s words from the discovery call. “Improve operations” is too vague to finish; “find where orders stall” is something you can complete.

Keep the objective to results you control. You can deliver a plan; you can’t promise their shipping times. One objective is best, and three is the most a reader will remember.

2. Deliverables

The things you will hand over, each one something you can count. Write nouns, not verbs: “support” and “assist” can never be finished, while “a written report of up to fifteen pages” can. Add the format and the size: a PDF, a page limit, a 45-minute call.

If you can’t tell when a deliverable is done, it isn’t written clearly yet. For monthly work, cap the volume: hours, posts or calls each month. If the client supplies photos, copy or data, write that down too.

3. In scope and out of scope

List what is included, then just as clearly what isn’t. The out list does the heavy lifting: anything the client might assume comes free belongs on it.

• Consulting: new software setup, hiring and training, putting the fixes in place.
• Website: copywriting, hosting, stock photos.
• Brand identity: printing, signage, packaging.

If something could be read either way, decide which side it is on now. And remember that out of scope is not never: you can still offer it as a separate, optional add-on with its own price.

4. Assumptions and client responsibilities

Write down what has to be true for the plan to work and what you need from the client: access to their tools, content or data by a date, and one person who approves.

Then say that if an assumption breaks, the timeline or the price can change. That isn’t a threat; it shows where the plan depends on them. One decision-maker beats a committee.

5. Timeline and milestones

List milestones from kickoff to the final deliverable, with a sign-off at the big ones. Count in weeks from kickoff rather than calendar dates, so a late start moves every date together.

• Give each milestone a name, a date and the person who signs it off.
• Put dependencies in order: interviews before the map, the map before the report.
• Give the client’s part deadlines too, such as five business days to review a draft.
• Add a buffer week to anything longer than a month.

6. Revision rounds

Say how many rounds are included and what an extra round costs. Then define a round: one set of written comments, sent together. Scattered notes over three weeks are not one round; they are ten.

Price extra rounds in the scope, so nobody negotiates later. A round changes the agreed draft; a new direction is a change request.

7. Acceptance criteria

What makes each deliverable done, in terms anyone can check. For the consulting example: the report covers all six interviews, and every recommended fix has an owner, a cost and a date. For a website: every page works on a phone, and the contact form sends.

Avoid “to the client’s satisfaction,” which never ends. Name the person who signs off, set a review window so a draft never waits weeks for comments, and say what sign-off unlocks, such as the final invoice.

8. Change process

New requests come in writing, you reply with a price and the time it adds, and nothing starts until the client approves. This one line is what stops scope creep, because it turns “could you just” into a decision.

Even a small change goes through the same four steps: the request, the price, the time, and a yes. Write your turnaround too, such as a price within two business days, and add approved changes as a new line or a new proposal.

Scope of work template

Copy this outline into your proposal or document and fill in each line.

Scope of work: [Project name] for [Client company], version [1.0], [date]

1. Objectives. [One or two sentences in the client’s words.] Done well means [a result you control].

2. Deliverables. [Deliverable 1, with format and size]. [Deliverable 2]. [Deliverable 3]. Client supplies: [content, data, access] by [date].

3. In scope: [items]. Out of scope: [items the client might assume are included]. Out-of-scope items can be quoted as separate, optional add-ons.

4. Assumptions. [Access or data] by [day]. [Meetings booked] in [week]. One approver for [Client company]: [name]. If an assumption changes, the timeline or price may change.

5. Timeline. Week [1]: [milestone]. Week [3]: [milestone] (sign-off: [name]). Week [5]: [milestone] (sign-off: [name]). Client reviews within [5] business days.

6. Revisions. [2] rounds of written comments on [deliverable] are included. A round is one set of comments sent together. Extra rounds are billed at [rate].

7. Acceptance criteria. [Deliverable] is complete when [checkable conditions]. Sign-off by [name] within [number] business days; sign-off releases [the final invoice].

8. Change process. New requests come in writing. We reply within [2] business days with the price and the time it adds. Work starts after you approve. Approved changes are added as a new line or a new proposal, and this scope gets a new version number.

Scope of work example: a consulting project

Here is the template filled in for an operations assessment. Cruz Logistics, the numbers and the $225 hourly rate are illustrative.

Project: Operations assessment for Cruz Logistics, version 1.0

1. Objectives. Find where orders stall, and plan the fixes for 3-day shipping. Done well: a plan the team agrees to.

2. Deliverables. 6 stakeholder interviews (45 minutes each). A process map, order to ship (PDF). A written report, up to 15 pages. A half-day on-site workshop in week 6.

3. In scope: the order desk and the warehouse; current tools as they are; written recommendations. Out of scope: new software setup; hiring or training; putting the fixes in place (available as a separate add-on).

4. Assumptions. Interviews booked in week 1. Order data export by day 5. One approver for the client.

5. Timeline. Week 1: kickoff and interviews. Week 3: process map (sign-off). Week 5: draft report (sign-off). Week 6: workshop. The client reviews within 5 business days.

6. Revisions. 2 rounds of written comments on the report are included. Extra rounds are billed at $225 an hour.

7. Acceptance criteria. The report covers all 6 interviews. Every fix has an owner, a cost and a date. The client’s comments are addressed.

8. Change process. Requests in writing. We reply with the cost and the time. Nothing starts until it is approved. Approved changes are added as a new line or a new proposal.

Eight short sections that a client can read in about two minutes.

How long should a scope of work be?

One page for most client projects. Longer projects need more detail in the deliverables and timeline, not more pages of legal-sounding words. Give the scope a version number: when it changes, the new version replaces the old one.

Scope of work mistakes to avoid

1. Vague verbs. “Support,” “assist” and “help with” have no finish line. Write the noun you hand over.
2. No out-of-scope list. Without it, every assumption the client makes is a free extra.
3. Unlimited revisions. Cap the rounds and define what one round is.
4. No dates for the client’s part. Your timeline depends on their reviews and content, so give those dates too.
5. Copying last project’s scope. Old details, old names and old numbers slip through. Rewrite the objectives and deliverables every time.
6. Leaving the scope in an email thread. Put it in the document the client accepts, not in a reply three messages down.

Where to write your scope of work

A Word or Google document works for your first few projects. Proposal software adds a link the client accepts, a record of the yes, and reusable sections:

Sources, prices checked October 25, 2026 (PandaDoc October 19, 2026): Workspace369 pricing, PandaDoc pricing, Proposify pricing and Better Proposals pricing. Yearly billing lowers each price. PandaDoc and Proposify suit sales teams sending many documents.

Writing a scope of work in a Workspace369 proposal

Our #1 pick is Workspace369. The scope goes into the proposal the client accepts, so the scope and the price live in one document.

• Write the scope as proposal sections. Add a Deliverables section, list what is included, then add a “Not included” line, and highlight the section so it stands out. Objectives, Timeline and Terms are built-in sections you add the same way.
• The client accepts it through a link. Clients review, accept and sign proposals through a public link, on every plan.
• The yes and the deposit are one step, on every plan. With Stripe connected, you send the proposal from the editor, the client opens the link, accepts and signs, and pays the deposit.
• Then set the work up as a project. The project holds the budget you priced, a task for each deliverable, and progress as each one gets done. Link the accepted proposal to the project, so the scope sits next to the work.

Proposals and projects start on Cadet, $29 a month (1 seat, no project cap). Deposit on acceptance and time tracking are on every plan. Voyager, $74 a month (2 seats, extra seats $10), adds texting and calls. Specialist is $149 a month (10 seats). Cadet through Commander start with a 14-day free trial (card required). See proposals in Workspace369 or follow one client job from proposal to paid invoice in our Workspace369 walkthrough.

Scope of work checklist

Before the client accepts:

• The objective is in the client’s words and limited to results you control.
• Every deliverable is a noun you can count, with a format and a size.
• The out list names everything the client might assume is free.
• Assumptions have dates, and one approver is named.
• Milestones count in weeks from kickoff, with sign-offs and the client’s review window.
• Revision rounds are capped, a round is defined, and extra rounds have a price.
• Acceptance criteria are checkable, with a named person who signs off.
• Changes come in writing, get a price and a time, and start after approval.
• It fits on about one page, has a version number, and sits in the document the client accepts.

To compare proposal tools on one real project before you commit, use our trial checklist.

To run this on one real client, start the Workspace369 14-day free trial.

Frequently asked questions

What should a scope of work include?

Eight parts: objectives, deliverables, what is in and out of scope, assumptions, a timeline with milestones and sign-offs, revision rounds, acceptance criteria and a change process. For most client projects they fit on one page.

What is the difference between a scope of work and a statement of work?

A scope of work describes the job: what you deliver, when, and what is out. A statement of work usually wraps that scope together with the price and the terms. Freelancers and small teams often put both inside one proposal.

Does a scope of work include pricing?

Often not. The price usually sits in the proposal or the contract, and the scope says what that price buys. Do price extra revision rounds in the scope, so nobody negotiates them later.

How long should a scope of work be?

About one page for most client projects, written in plain words. Bigger projects need more detail in the deliverables and timeline, not longer legal-sounding sections.

What is the difference between a scope of work and a proposal?

A proposal persuades: the problem, the options and the price. A scope of work defines what is delivered, when, and what is excluded. In small businesses the scope is usually a section of the proposal.

How do you handle changes to a scope of work?

Through the change process in the scope itself: the client asks in writing, you reply with the price and the time it adds, and work starts after they approve. Add the approved change as a new line or a new proposal and update the scope’s version number.