Skip to content

How to Write a Scope of Work (With Example)

The scope of work is the part of a proposal that says exactly what you'll deliver, and just as importantly, what you won't. Get it right and most disagreements never happen. This guide covers the eight parts, with a complete example you can adapt.

Updated September 30, 2026

Scope of work vs proposal

A proposal persuades: it explains the problem, your approach and the price. A scope of work defines: it lists the deliverables, activities, dates and boundaries. For most freelance projects the scope lives inside the proposal as its own section. For larger projects, or when a client's legal team is involved, it's often a separate document attached to the contract.

The eight parts

  1. Objective: one or two sentences on what the project is for. It's the tiebreaker when a detail isn't covered elsewhere.
  2. Deliverables: the things the client receives, each countable or checkable.
  3. Activities: the work you'll do to produce them, such as workshops, research, concepts and revision rounds.
  4. Out of scope: what you won't do, named explicitly.
  5. Timeline and milestones: dates, plus what the client must provide before each one.
  6. Acceptance: how a milestone counts as approved, so work doesn't stay "almost done" forever.
  7. Assumptions and dependencies: what has to be true for the plan to hold.
  8. Changes: how requests outside the scope get handled.

Vague vs specific

The test for every line: could you and the client both point at it and agree whether it's done? A few rewrites:

A complete example

Here's a full scope of work for a brand identity project. The same structure works for web, content, video or consulting work. Swap the deliverables and activities.

Example scope of work
SCOPE OF WORK: Brand identity for Fern & Oak Interiors

1. OBJECTIVE
Create a visual identity that positions Fern & Oak as a premium residential interior studio, ready for the new website launching in [month] and for print materials at the [trade show] on [date].

2. DELIVERABLES
- Primary logo, secondary logo and icon mark, each in full colour, one colour and reversed
- Colour palette: up to 6 colours with HEX, RGB and CMYK values
- Typography: 2 typefaces (headings and body), with licensing notes
- Business card design (front and back), print-ready PDF
- Letterhead and email signature designs
- Brand guidelines: PDF, approximately 10-12 pages
- Final files in SVG, PNG and PDF, delivered via a shared folder

3. ACTIVITIES
- Kickoff workshop (90 minutes, video call)
- Research: review of 5 competitors and the client's reference images
- 3 initial logo concepts, presented on a call
- 2 rounds of refinement on the chosen concept
- Application of the chosen identity to the items above

4. OUT OF SCOPE
- Website design or development
- Photography, copywriting or naming
- Printing costs and supplier management
- Signage, vehicle graphics or packaging (can be quoted separately)
- Paid font licenses (client purchases directly; costs quoted before selection)

5. TIMELINE AND MILESTONES
Week 1: Kickoff workshop; client sends reference images and existing materials
Week 2: Logo concepts presented
Week 3: Round 1 feedback due within 3 business days; refinements delivered
Week 4: Round 2 feedback; logo approved
Week 5: Stationery and guidelines delivered; final files handed over

6. ACCEPTANCE
Each milestone is accepted when the client confirms in writing, or 5 business days after delivery if no changes are requested.

7. ASSUMPTIONS AND DEPENDENCIES
- The client names one decision-maker who attends the kickoff and approves each milestone
- Feedback at each round is consolidated into a single list
- If feedback arrives late, later milestones move by the same number of days

8. CHANGES
Requests outside section 2 or 3 will be quoted in writing (cost and timeline impact) and only started once approved.

The page counts, round counts and day counts above are examples. Set them to whatever you can actually deliver in the time you're pricing for.

Write the "out of scope" section on purpose

Good exclusions are the things this client is likely to assume are included. Think about the adjacent work: a logo client may expect a website, a website client may expect copywriting, a video client may expect music licensing. Name those, and offer to quote them separately so the list reads as helpful rather than defensive.

A change-request clause you can copy

Change request clause
Change requests: If you'd like to add or change anything outside the deliverables and activities listed above, I'll send a short written change note with the cost and any effect on the timeline. Work on the change starts once you approve the note. Small changes that take under [30 minutes] may be absorbed at my discretion, and I'll tell you when that happens so it doesn't become an unwritten expectation.

Signs your scope is too loose

When the scope changes mid-project

It will. That's normal, not a failure of the document. The scope's job is to make the change visible: when a request comes in, check it against the deliverables, and if it's new, send a change note before starting. Clients rarely mind paying for extra work they asked for. What causes friction is finding out afterwards.

Related