How to write a scope of work: a plain guide for solo freelancers
A scope of work says what you will deliver, what you will not, by when and for how much. That is the whole idea. It is not a contract and it is not a proposal, though it often sits inside one. It is the page both of you can point to when someone asks, “wasn’t that included?”
- 1Start from the goalOne sentence, in the client’s words.
- 2List deliverablesThings they can hold, not activities.
- 3Write “not included”The things clients assume.
- 4Set dates and roundsIncluding the client’s side.
- 5Add the change ruleExtras are quoted first.
You can write a good one in about twenty minutes. This guide shows you how.
A note before we start: this is practical guidance, not legal advice. For anything high-risk or high-value, ask a solicitor to look over your terms.
Why it matters when you work alone
When you work alone, nobody else remembers what was agreed. There is no colleague to say “that was in the quote”. If the scope is vague, the gaps fill with unpaid hours, which is how scope creep starts.
A clear scope protects you, and it protects the client too. They know what they are buying, what they need to provide and what happens when they want something extra.
What to put in it
Keep it to one or two pages. Include:
- The goal, in one sentence. What the client wants to achieve, in their words.
- Deliverables. The things they will receive.
- What is not included. The things they might assume, but will not get.
- What you need from them. Content, logins, feedback, sign-off.
- Timeline and milestones. Dates, or at least an order and rough durations.
- Revision rounds. How many, and what counts as one.
- Price and payment. The total, and when each part is due.
- How changes are handled. What happens when they ask for something new.
Write it in five steps
1. Start from the client’s goal
Not “build a website”. Something like “give customers a clear way to book a first appointment online”. The goal tells you what matters, and it gives you a reasonable way to judge a later request: does it serve the goal, or is it something new?
2. List deliverables as things they can hold
Write nouns, not activities. “Five designed pages: Home, About, Services, Pricing, Contact” is a deliverable. “Work on the design” is an activity, and activities have no end.
3. Write the “not included” list
This is the most useful part and the one most people skip. Think of what clients usually assume: copywriting, photography, extra pages, content migration, ongoing support after launch. Name them, kindly and clearly.
4. Set dates and review rounds
Say how many rounds of changes are included, and who is responsible for each stage. Include the client’s side: if feedback is late, the dates move. Say that in the scope, not after the fact.
5. Add the change rule
One short paragraph. Anything outside the scope is quoted separately, and work on it starts once it is agreed. This is what turns an awkward conversation into a routine one.
A short example
This is a fictional example.
Project: Brochure website for a local physiotherapy practice
Goal: Help new patients find the practice and book a first appointment online.
Deliverables: A five-page WordPress website (Home, About, Treatments, Prices, Contact); a booking form that emails the practice; the site working on phones and tablets; basic search setup (page titles and descriptions).
Not included: Copywriting (the client supplies text), photography, a blog, online payments, ongoing support after the 14-day launch period.
From the client: All text and images by [date]; logins for the domain; feedback within three working days of each review.
Timeline: Design for review in week 2, build for review in week 4, launch in week 5.
Revisions: Two rounds of changes on design, one on the finished build.
Price: [amount], half to start, half on launch.
Changes: Anything outside this list is quoted separately before work begins.
That is about 150 words. Nobody gets lost in it.
Mistakes to avoid
- “Unlimited” anything. Unlimited revisions, unlimited pages, unlimited support. Put a number on it.
- Deliverables written as activities. If there is no clear finish, there is no clear scope.
- No client responsibilities. Most delays come from waiting. Say who owes what.
- No sign-off. Get a plain “yes, that’s what we agreed” by email before you start. It takes ten seconds.
Keeping the scope alive
A scope only works if you look at it again. At the end of each stage, read it against what you have done and what the client has asked for. This is the habit that stops creep early, and it is the sort of routine work that slips when you are busy with several projects (see running several client projects alone).
It is also the sort of thing your project manager is for. Agenc’s project manager keeps each project checked against its plan and brings you only what needs your decision.
If that sounds useful, you can join the early-access waitlist from the form at the foot of this page.
Questions
What is the difference between a scope of work and a statement of work?
In practice the terms overlap. A statement of work is usually the more formal document, often with legal terms. A scope of work is the simple description of what is and is not being delivered. For most solo freelancers, a clear scope inside a proposal is enough.
How long should it be?
One or two pages. If the client will not read it, it is too long.
Do I need a lawyer?
For small, low-risk projects, many freelancers write their own. For anything large or high-risk, ask a solicitor to check your terms.
What if the client changes their mind?
Use the change rule. Say yes, name it as a change, and give the price and timing. Our post on scope creep has a reply you can adapt.