A scope of work is not a task list — it's a boundary document. Its job is to name what's included, what's excluded, how many rounds of revisions the client gets, and what happens (and what it costs) when they ask for something outside that. Get those four parts on paper before work starts, and most scope creep never happens, because there's a written line to point to instead of an argument to have.
What a scope of work actually has to do
A scope of work exists to answer one question later, mid-project, when the client asks for "just one small thing": is this in, or is this extra? If the document doesn't answer that clearly, you'll end up negotiating scope in real time, under pressure, usually while also trying to keep the relationship friendly. Write the boundary now, while everyone is calm and nothing is at stake yet.
The difference between a scope of work and a proposal
A proposal sells the engagement — it covers the problem, your approach, your price, and why you're the right person. A scope of work is narrower and more mechanical: it lists exactly what will be built, in what quantity, with what limits. Some freelancers write it as a section inside the proposal; others attach it as a separate one-page document referenced by the contract. Either works, as long as it exists somewhere both sides sign off on.
The four parts of a scope that holds up
Deliverables, named specifically
Don't write "a website." Write the actual pages and components: "Homepage, About, Services (3 sub-pages), Contact, and a blog template — 7 templates total, built responsively for desktop, tablet, and mobile." Specific counts are what let you say, later, "the scope was 7 templates; this is template 8" instead of arguing about intent.
Revision rounds, with a number
Every deliverable phase should have a stated number of revision rounds — commonly two for a brochure site, sometimes three for a larger rebuild. Define what a "round" means too: one round is one consolidated set of feedback per page or section, not an open-ended back-and-forth.
What's explicitly out of scope
List what's not included, even if it seems obvious: copywriting, photography and image licensing, SEO strategy beyond basic on-page setup, e-commerce app integrations, translations, ongoing maintenance after launch. If it's not written as excluded, clients reasonably assume it might be included.
What triggers a change order and how it's priced
State the rule plainly: any request beyond the listed deliverables or revision rounds becomes a change order, priced at your hourly or day rate, approved in writing before you start it. This is the single sentence that ends most scope disputes before they start, because it turns "can you also..." into a two-line email instead of a fight.
Common scope-of-work mistakes that cause disputes
"Unlimited revisions" and other vague promises
"Unlimited revisions" sounds generous in a sales conversation and becomes the reason a project runs three months over schedule. If you want to signal flexibility, say "we'll work together until you're happy with the design direction, within two structured revision rounds" — flexible in tone, bounded in practice.
No definition of "done" for a page or section
Disputes often aren't about the big things — they're about whether a page is "finished" when the client keeps adjusting word choice or button color a week after approving it. Define done as: client has reviewed the page against the agreed revision round and approved it in writing (an email or a checked box works). Once approved, further changes are a new round or a change order, not a continuation of the same one.
A short example scope section
Here's wording you can copy into a proposal or a standalone scope document today:
SCOPE OF WORK — [Client Name] Website Project
DELIVERABLES:
- 6 page templates: Home, About, Services, Portfolio,
Contact, Blog listing
- Responsive design for desktop, tablet, and mobile
- One (1) content migration pass from existing site
REVISIONS:
- Two (2) rounds of revisions per page template
- One round = one consolidated round of feedback,
delivered in a single document or call
OUT OF SCOPE (not included):
- Copywriting or content editing beyond migration
- Stock photography purchase or licensing
- Custom app integrations (booking, e-commerce, etc.)
- SEO strategy beyond basic on-page title/meta setup
- Post-launch maintenance or hosting
CHANGE ORDERS:
Any request outside the deliverables or revision rounds
above will be quoted separately at $95/hour and requires
written approval before work begins.
Adjust the page count, revision count, and rate to your own work, but keep all four sections — deliverables, revisions, exclusions, change orders. A scope missing any one of them is the part that gets exploited, usually without anyone meaning to.
Where the scope of work lives — inside the proposal or as a separate doc
Either placement works, but for most solo freelancers and small studios, putting the scope inside the proposal — as its own clearly labeled section, right after pricing — is simpler to manage than a separate document, because there's only one file for the client to sign and reference. If your projects are larger or your contract is handled by a separate legal document, a standalone scope-of-work attachment referenced by both the proposal and the contract works too. What matters is that it exists in writing and both sides have agreed to it before work starts. If you'd rather not build that section from a blank page each time, a proposal framework with the scope section built in is what The Web Design Proposal Kit provides.
FAQ
Do I need a lawyer to write this? No. A scope of work is a business document, not a legal contract — it defines the work, not the legal terms (those live in your contract or terms of service). Plain, specific language is more useful here than legal phrasing.
What if the client wants changes mid-project that aren't in scope? Point to the change-order clause, quote the additional work at your stated rate, and get written approval before starting it. This is normal and, if the scope is written clearly, rarely causes friction — clients generally accept that new requests cost more.
How detailed should the scope be for a 5-page brochure site vs. a 20-page rebuild? The structure stays the same size — deliverables, revisions, exclusions, change orders — but a 20-page rebuild needs more specificity inside "deliverables": which pages have unique layouts versus reuse a template, whether there's a content migration for all 20 pages or a subset, and whether stakeholder review happens per-section or all at once. More pages means more places for ambiguity to hide, so be more specific, not more brief.
Writing a scope of work is mostly a discipline of naming things before they become arguments. See The Web Design Proposal Kit ($29) if you want that structure — deliverables, revisions, exclusions, and change orders — already laid out, so you can fill in the details for your next project instead of starting from a blank page.