A proposal scope of work that holds up has four parts. What's included, with quantities and frequency. What's not included. How many revision rounds you'll do. And what happens when the client asks for more. Most client disputes don't start at delivery. They start with a proposal that left room for interpretation.
Take "Website redesign." You know exactly what you meant. The client reads the same two words and pictures new copy, new photos, a blog and a year of updates.
Spelling it out isn't red tape. It protects both of you.
What are the four parts of a solid scope of work?
1. What's included?
Length isn't the goal. Removing ambiguity is.
Weak: "Website design and development."
Strong: "Design and build of a six-page marketing site: Home, About, Services, two case studies and Contact. Includes moving existing copy, basic on-page SEO setup, and two rounds of revisions per page."
2. What's not included?
This is the section most freelancers and small teams skip, and the one that prevents the most arguments later. Listing exclusions isn't defensive. It's how professionals write scopes.
For the website above, you might list: new copywriting, photography and stock image licenses, hosting and domain fees, and maintenance after launch (available as a separate monthly retainer). Every line here is a future argument that never happens.
3. How many revisions are included?
Open-ended revisions are the fastest route to scope creep. Put a number on it:
"This scope includes up to two rounds of revisions per deliverable. Additional rounds are billed at $[rate]/hour."
A client acting in good faith will respect a line this clear.
4. How are extra requests handled?
"Any request outside the scope above is treated as a change order. Before starting, I'll send a short add-on proposal with the description, timeline and price."
This one paragraph protects your margin. Without it, the client asks for "one small thing," you do it to keep the peace, and at the end of the project you've worked far more hours than you sold.
What does a complete scope of work look like?
- Included: every deliverable with quantity, format and frequency.
- Not included: the items clients in your field most often assume are part of the deal.
- Revisions: rounds per deliverable, with the rate for extra rounds.
- Timeline: start and delivery dates, or a clear trigger for when the clock starts (for example, the deposit and the kickoff call).
- Proposal expiration: how long the price and dates are valid.
- Change orders: anything outside the scope gets quoted separately before work starts.
In Nepfy, writing the scope means filling in the template's Scope section or describing the project in Write with AI, instead of starting from a blank page. Either way, price and timeline go in exactly as you typed them, and sections without input are born hidden. Review the scope in the editor before you publish. See how a proposal is created.
What should you check before you send it?
- Every deliverable has a quantity, format and frequency.
- There's an explicit "not included" list.
- The number of revision rounds is written down.
- The timeline has a clear start trigger.
- The file formats and handoff method are specified.
- There's a change-order clause for anything outside the agreed work.
A clear scope is worth more than any clause you add after a dispute. When the client knows exactly what they bought and you know exactly what you owe, the project starts on trust instead of assumptions. A vague scope is also one of the proposal mistakes that costs the most deals.
Frequently asked questions
Is a scope of work the same as a proposal?
No. The scope of work is one section of the proposal. The proposal also covers the problem, your approach, timeline, investment and next step. On larger projects, the scope often becomes a standalone SOW attached to the contract.
Do I really need to list what's not included?
Yes. What's obvious to you is rarely obvious to the client. List the items that most often turn into "I thought that was included" in your line of work.
What do I do when a client asks for extra work mid-project?
Point to the change-order clause and send a short add-on proposal with scope, timeline and price before you start. Doing it for free once sets the expectation for every request after that.
With Nepfy, the Minimal template already has a Scope section, and the proposal goes out as a live page. You see when the client opened it and how far they read, without having to ask.
Start free: 14 days of Pro, no credit card.
