Contracts
Scope of Work Template for Freelancers (Copy It, Fill It In)
By Aetisam · · 6 min read
The short answerA scope of work says exactly what you will deliver, what you will not, when, and how it gets approved and paid. Include specific deliverables, a separate list of exclusions, dated milestones, a revision limit, who approves, and payment terms. Write it before the work starts, then both sides can point at it.
You said yes on a call. The client said "great, so you will handle the website". You said "of course". Nobody wrote down what "the website" means. Six weeks later, it means the website, the blog, the email setup, a logo refresh, and "just a little help with the launch".
A scope of work (often shortened to SOW) is the fix. It is a plain document that says what you are delivering, what you are not, and how the project runs. It is the one page that turns "I thought you meant..." into "it says right here".
What is a scope of work?
A scope of work is a written description of a project: the deliverables, the timeline, the rules for changes, and the payment terms. It can sit inside your contract or be a separate page that the contract points to. Either way, it is the thing you both agreed to before any work began.
What should a scope of work include?
Freelancer guides from SelfEmployed.com, Taskade and Bonsai agree on the core sections. Exclusions and timeline assumptions get the most attention, because that is where projects go wrong.
- 1Project summaryTwo or three sentences on what the project is and why it exists, in the client’s own words if you can.
- 2DeliverablesA list of what you will hand over. Make each one specific and countable: pages, files, formats, and word counts, not just "website copy".
- 3ExclusionsA separate list of what is not included. Clients often assume nearby tasks are covered unless you say otherwise in writing.
- 4Timeline and milestonesDates for each stage, plus the assumptions behind them, such as "feedback within three business days".
- 5Revisions and approvalHow many rounds are included, who gives feedback, who signs off, and what "done" means.
- 6Payment termsThe total, the schedule, and what happens if an invoice is late. A deposit up front, payments at milestones, and a final payment on acceptance is a common structure.
- 7ChangesHow extra work gets requested, priced, and approved before it starts.
How specific should deliverables be?
Specific enough that a stranger could check whether you delivered them. One guide contrasts a vague "Website copy" with a line that gives page-by-page word counts and the delivery format. The second version leaves no room for "I expected more". The test is simple: can you count it, and can the client open it?
| Vague | Specific |
|---|---|
| Website copy | Copy for 5 pages (home, about, services, pricing, contact), up to 400 words each, as a shared document |
| Some design work | Two logo concepts, delivered as PNG and SVG |
| Social media help | Twelve social posts, delivered over four weeks |
| Ongoing support | Two 30-minute check-in calls, no support after delivery |
What is a good scope of work template?
Here is a short one you can copy. Replace everything in brackets. Keep the headings, because they are what stop the arguments later.
Project
Project: [name]. Client: [client]. Prepared by: [your name]. Date: [date].
Summary: [two or three sentences on what this project is for].
Deliverables
1. [Deliverable, quantity, format]
2. [Deliverable, quantity, format]
3. [Deliverable, quantity, format]
Not included
[Examples: copy not listed above, extra pages, post-launch support, rush timelines, stock images or fonts.]
Timeline
Kickoff: [date]. First draft: [date]. Final delivery: [date].
These dates assume the client sends feedback within [3] business days. Delays on the client’s side move the dates by the same amount.
Revisions and approval
[Two] rounds of revisions are included. A round is one consolidated set of feedback. [Name] gives feedback and has the final say.
Payment
Total: [amount]. [50%] on signing, [25%] at the first draft, [25%] on approval. Invoices are due within [14] days. Late invoices add [fee or interest as agreed].
Changes
Anything outside this document is quoted separately and starts only after written approval.
Agreement
Client: [name, date]. Freelancer: [name, date].
When should you write the scope of work?
Before you start, and before the first invoice. The best time is right after the client says yes, while everyone is still excited and nobody is annoyed. Send it as a short, friendly document and ask them to confirm it by replying "agreed". That one reply is more useful than a long email thread you will never be able to find again.
How do you keep the scope from drifting later?
Treat the document as living but controlled. When the client asks for something new, point to the section on changes, quote it, and wait for approval. Our guide to handling scope creep has the exact scripts. And if a request is simply a bad fit, how to say no to a client covers that too.
- Every deliverable can be counted and opened
- There is a clear "not included" list
- Dates are written with the assumptions behind them
- The revision limit and the approver are named
- Payment terms and the late fee are written down
- The client has replied "agreed"
What does a scope of work look like for different jobs?
The headings stay the same, but the details change with the work. Here is how the deliverables and exclusions might look for a few common freelance jobs.
- Writer: deliverables are the number of articles, word counts, and formats. Exclusions are image sourcing, publishing, and extra rounds of edits.
- Designer: deliverables are the number of concepts, files, and formats. Exclusions are printing, brand guidelines, and extra concepts.
- Developer: deliverables are the pages or features and the environments. Exclusions are hosting, content entry, and post-launch support.
- Consultant: deliverables are the sessions, reports, and recommendations. Exclusions are implementation and ongoing advice.
Whatever the job, the exclusions are where you earn your keep. If a task is not listed under deliverables, it is not included, and writing that sentence into the document is a kindness to both sides.
Questions people ask
A written description of a project that lists what will be delivered, what will not, the timeline, how revisions and approvals work, and how it will be paid. It protects both you and the client from misunderstandings.
A contract covers the legal terms of the relationship. A scope of work covers the details of the project itself. Many freelancers attach the scope to the contract so both live together.
As short as it can be while staying specific. For many small projects that is one to two pages. Bigger or riskier projects need more detail.
Yes. A separate "not included" section is one of the most useful parts, because clients often assume nearby tasks are covered unless you say otherwise.
Reuse the structure, not the details. Keep a template with the same headings, then fill in the specifics for each project. Never send a scope that was written for someone else.