How to Write a Scope of Work (Freelancer Guide + Example)

A freelancer in his early 30s highlighting a printed project outline at a coffee shop table next to his laptop and a cup of coffee

You’ve had a great discovery call, the client is excited, and they ask you to “send over the details.” This is the moment to learn how to write a scope of work. A scope of work is a short, plain-language document that spells out exactly what you’ll deliver, by when, how many revisions are included, and what’s not part of the deal. Write it well and you’ll avoid most of the arguments that sink freelance projects. Write it badly (or skip it) and you’ll end up doing two projects for the price of one.

This guide walks you through writing a scope of work as a solo freelancer: what goes in it, a step-by-step process, a sample you can adapt, and the mistakes that cost freelancers money.

What is a scope of work (and why freelancers need one)?

A scope of work (often shortened to SOW) describes the work itself: the goals, the deliverables, the tasks, the timeline, and the boundaries of the project. It answers one question for both you and your client: “What does ‘done’ look like?”

If you want the bigger-picture, business-side view of statements of work, including the different SOW types larger companies use, see our guide to SOW meaning in business. This post is the hands-on version: how you, a freelancer with a client waiting, actually sit down and write one.

Here’s why it’s worth the hour it takes:

  • It protects your time. Every request outside the scope becomes a conversation about a change, not an expectation.
  • It makes pricing easier. Once the deliverables are clear, your quote is just math.
  • It builds trust. Clients relax when they can see exactly what they’re paying for.
  • It gives you a finish line. Without one, projects quietly drift into “one more small thing” forever.

Scope of work vs. contract vs. proposal

These three get mixed up a lot. A proposal sells the project (“here’s how I’d solve your problem and what it costs”). A contract covers the legal relationship: payment terms, ownership, liability, termination. A scope of work defines the work. On small projects, the scope often lives inside the proposal or as a section of the contract. On bigger or ongoing projects, it’s usually its own document that the contract refers to. Either way, it should be in writing and agreed before you start. (For the legal side, see what to include in a freelance contract.)

What to include in a scope of work

A freelance scope of work doesn’t need to be 20 pages. Most solo projects fit on one or two. Here are the sections that matter:

  • Project overview: Two or three sentences on the client’s goal and why the project exists.
  • Deliverables: The specific things you’ll hand over, with quantities, formats and specs.
  • Tasks and process: The main steps you’ll take to produce the deliverables.
  • Timeline and milestones: Key dates, including when the client owes you feedback or assets.
  • Revisions: How many rounds are included, and what counts as a round.
  • Client responsibilities: What you need from them, and by when.
  • Out of scope: The things you are explicitly not doing.
  • Acceptance criteria: How you’ll both know a deliverable is finished.
  • Change requests: How new requests get quoted and approved.
  • Price and payment schedule: Total fee and when each payment is due (or a reference to the contract).

How to write a scope of work in 8 steps

1. Start with the client’s goal, not your task list

Before you write a single deliverable, write down what the client is trying to achieve in their words. “Launch a new website” is a task. “Get more consultation bookings from local businesses” is a goal. When the goal is on paper, it’s much easier to push back on requests that don’t serve it, and to suggest better options when they come up. Pull this straight from your notes; if you need help getting it on the call, our list of discovery call questions is a good starting point.

2. List every deliverable, with numbers

Vague deliverables are where scope creep is born. Compare these two:

  • Vague: “Blog content for the website.”
  • Clear: “Four blog posts, 1,200–1,500 words each, delivered as Google Docs, each with a meta description and two suggested images.”

Add quantities, lengths, formats, file types and sizes wherever you can. If you’re designing a logo, say how many initial concepts you’ll present. If you’re building a website, list the pages by name. A good test: could a stranger read the deliverables and know when you were done?

3. Break the work into phases and tasks

Group the work into phases that match how you actually work, for example: discovery, first draft, revisions, final delivery. Under each, list the main tasks. You don’t need a detailed project plan here. The point is to show the client the path from kickoff to delivery and to give you a reality check on how many hours it’ll really take. That hour estimate becomes the backbone of your price (see how to quote a freelance project).

4. Set a timeline that includes the client’s homework

Most freelance timelines slip because of the client, not the freelancer: late feedback, missing logins, content that never arrives. So put both sides on the timeline. For each milestone, note what you deliver and what the client owes you in return:

  • Week 1: You deliver the site map and wireframes. Client sends all page copy and brand files by Friday.
  • Week 2: Client returns consolidated feedback within 3 business days.

Then add one line that protects you: “If client feedback or materials arrive late, the timeline shifts by the same number of days.”

5. Define revisions so nobody has to guess

“Unlimited revisions” sounds generous and costs you dearly. Pick a number (two rounds is common for creative work) and define what a round means. A simple version: “One round of revisions is a single, consolidated set of feedback from the client, delivered at once. Additional rounds are billed at $X per round.” Also be clear that a revision changes what’s already been made. A new direction or a new deliverable is a change request, not a revision.

6. Write an “out of scope” list

This is the most useful section in any freelance scope of work, and the one most freelancers skip. Think about the requests you usually get mid-project and name them up front. For a web designer, that might be copywriting, stock photo purchases, hosting setup, SEO or ongoing maintenance. For a writer, it might be interviews, image sourcing or uploading posts to the CMS. Listing them isn’t unfriendly. It’s clarity, and it gives you a natural opening to offer those services as an add-on.

7. Agree on acceptance criteria and a change process

Acceptance criteria answer “when is this finished?” For example: “A deliverable is considered approved when the client confirms in writing, or 5 business days after delivery if no feedback is received.” That last clause keeps projects from sitting open for months.

Then describe what happens when something new comes up: “Requests outside this scope will be quoted separately and started only after written approval.” That one sentence turns awkward conversations into routine ones. If a project has already started to drift, our playbook on how to handle scope creep covers how to reset it.

8. Review it together and get a signature

Don’t just email the document and hope. Walk the client through it on a short call, or at least ask them to read the deliverables and out-of-scope sections closely. This is where misunderstandings surface while they’re still cheap to fix. Then get it signed, or at least approved in writing (an email reply saying “Approved” is far better than nothing). If the client sends their own contract, check that it either includes your scope or refers to it as an attachment.

A simple scope of work example for freelancers

Here’s a sample for a small freelance web design project. Swap in your own details:

Project overview: Redesign the five-page website for Brightside Pilates to make it easier for new clients to book an intro class online.

Deliverables:

  • Site map and wireframes for 5 pages: Home, Classes, Instructors, Pricing, Contact
  • Visual design for all 5 pages (desktop and mobile)
  • Build in the client’s existing WordPress site using the current theme
  • Booking button linked to the client’s existing scheduling tool
  • One 30-minute training call on editing pages

Timeline:

  • Week 1: Wireframes delivered. Client provides copy, photos and logins.
  • Weeks 2–3: Designs delivered. Client feedback due within 3 business days.
  • Week 4: Build, testing and launch.

Revisions: Two rounds on wireframes and two rounds on designs. Additional rounds are $150 each.

Out of scope: Copywriting, photography, new booking software, SEO, hosting changes, ongoing maintenance and any pages beyond the five listed.

Acceptance: Each phase is approved by written confirmation, or automatically 5 business days after delivery without feedback.

Changes: New requests will be quoted separately and scheduled after written approval.

Fee: $4,800, paid 50% at signing, 25% on design approval and 25% at launch.

Notice how short it is. A clear one-page scope beats a long one that nobody reads.

Common scope of work mistakes to avoid

  • Using fuzzy words. “Some,” “a few,” “basic,” “as needed” and “etc.” all invite different interpretations. Replace them with numbers.
  • Leaving out client responsibilities. If your timeline depends on the client, say so in writing.
  • Promising outcomes you don’t control. “Increase sales by 30%” depends on things outside your work. Scope the deliverables, and describe goals as goals.
  • Skipping the out-of-scope list. If you don’t define the edges, the client will, usually mid-project.
  • Writing it after you start. A scope agreed in week three is a negotiation, not a plan.
  • Never updating it. If the project changes, update the scope (and the price) and get the change approved.

Turning a good scope of work into better clients

A clear scope does more than protect a single project. Clients who’ve worked with a freelancer who knows exactly what they’re delivering tend to come back, and they tend to refer others. It’s also a quiet signal that you run a real business. Once you’ve written a couple, save your best one as a template so the next one takes 20 minutes instead of two hours.

And if your pipeline needs more projects worth scoping, SolidGigs sends a curated list of the best freelance gigs to your inbox each week, so you can spend less time hunting and more time doing great work.

FAQ

Who should write the scope of work, the freelancer or the client?

Usually the freelancer. You know what the work involves, how long it takes and where the hidden effort is. The client provides the goals and requirements, and you turn those into specific deliverables. Larger clients sometimes send their own SOW. If they do, read it closely and suggest changes before you sign.

Is a scope of work legally binding?

On its own, a scope of work is a description of the work. It becomes binding when it’s part of, or referenced by, a signed contract or agreement. That’s why many freelancers attach the scope to their contract. Laws vary by location, so for high-value projects it’s worth having a lawyer review your contract template.

How detailed should a scope of work be?

Detailed enough that a stranger could tell when the project is finished. For most freelance projects that’s one to two pages: specific deliverables with quantities, a timeline, a revision limit and an out-of-scope list. Large or long projects may need more detail on phases and acceptance criteria.

What’s the difference between a scope of work and a statement of work?

People use them interchangeably, and both are shortened to SOW. Strictly speaking, the scope of work is the part that describes the work and deliverables, while a statement of work is a broader document that can also include pricing, terms and governance. For most freelancers, the distinction doesn’t matter much as long as the work is clearly defined and agreed.

What happens if the client wants something outside the scope?

Treat it as a change request. Thank them for the idea, explain that it’s outside the current scope, and send a short quote for the extra work with any effect on the timeline. Start only once they approve it in writing.

Conclusion

Knowing how to write a scope of work is one of the simplest ways to protect your time, price accurately and keep clients happy. Start with the client’s goal, list concrete deliverables, put both sides on the timeline, cap revisions, name what’s out of scope and get it approved before you begin. Do that, and “Can you just add one more thing?” becomes an easy, paid conversation instead of a headache.

One more thing...

You didn't start freelancing to spend hours every week searching through job boards. You started freelancing to do more work you enjoy! Here at SolidGigs, we want to help you spend less time hunting and more time doing work you love.

Our team of "Gig Hunters"—together with the power of A.I.—sends you high-quality leads every weekday on autopilot. You can learn more or sign up here. Happy Freelancing!

Aiko Tanaka

Aiko Tanaka

Aiko began her career as a traditional watercolorist in Kyoto before embracing digital art in her forties, demonstrating that it's never too late to master new skills. After two decades as an art director for major fashion magazines in Tokyo, she now works as a freelance digital artist specializing in subtle, atmospheric photo retouching and color grading. Her tutorials on creating natural-looking skin retouching and authentic vintage photo effects are highly regarded for their attention to detail and respect for photographic integrity. Aiko brings a traditionalist's eye to digital art, emphasizing the importance of understanding light, composition, and color theory as foundations for digital manipulation. In her spare time, she practices ikebana (Japanese flower arrangement) and sees strong parallels between this ancient art form and digital composition.

Leave a Comment

Your email address will not be published. Required fields are marked *