A scope of work (SOW) is only as strong as its specificity. Vague deliverables like "website design" are an open invitation for scope creep. Here's how to write one that holds up.
The anatomy of a bulletproof SOW
Every scope of work should include: a project title and description, a list of specific deliverables, the number of revision rounds included per deliverable, the total price, a timeline, and a change order clause.
Be specific about deliverables
Bad: "Website design." Good: "Design of 5 pages: Home, About, Services, Portfolio, Contact. Each page includes desktop and mobile layouts. 2 rounds of design revisions included per page."
Bad: "Logo design." Good: "Primary logo in horizontal and stacked formats, provided in SVG, PNG, and PDF. 3 initial concepts, 2 rounds of revisions on the selected concept."
Include revision limits
This is where most freelancers fail. Without a stated limit, clients assume unlimited revisions are included. State the number explicitly for each deliverable, and describe what happens when the limit is reached — typically a change order process.
Get it signed
A scope document without a signature is a suggestion, not an agreement. Use ScopePilot to generate a signable link that captures the client's name, email, timestamp, and IP address — creating an audit trail you can reference if things go sideways.
The change order clause
Include a sentence like: "Any work outside this scope of work will require a separate change order with its own pricing and approval." This single sentence gives you permission to charge for additional work.