Definition
Scope of work translates a vague engagement ('redesign our website') into specific, verifiable deliverables ('design five landing pages, migrate the existing blog, deliver assets in Figma'). It is the most important section of a proposal and the biggest source of disputes when missing or vague.
Good scope statements use verb-plus-object sentences, name the deliverable explicitly, quantify what is included (number of revisions, length of documents, number of participants), and include an out-of-scope list to prevent creep.
Why it matters
Vague scope is the leading cause of project disputes, late payments, and unhappy client relationships. Clear scope protects both sides — the buyer knows exactly what they will get, and the supplier knows exactly what they have committed to deliver.
Where this appears in your tools
The Proposal Builder has a dedicated scope section. The scope of work template page shows a full skeleton with included, not-included, assumptions, and change-control sections.
Example
A 'website redesign' is acted on at week 8 by a buyer who expects copywriting included; the supplier had assumed it was excluded. With a written scope ('design and front-end development of 5 pages, copy provided by the client'), this dispute does not happen.
Common confusion
Scope and timeline are not the same thing. Scope is what; timeline is when. A change to scope almost always changes the timeline; a change to timeline does not always change scope. Track them in separate sections.