Freelance scope of work template
Say exactly what's in and what's out. A scope of work document that heads off "can you just also..." before it starts.
Example: a filled-in scope of work
Scope of Work
Brand Refresh: Scope of Work
- Effective
- July 1, 2026
- Project
- Brand Refresh
Between
Whitfield Creative
Sana Whitfield
And
Nomad Coffee Co.
Priya Nair
Included
3- Logo suite (primary, secondary, icon mark)
- Packaging design for 3 SKUs
- Brand guidelines document
Excluded
3- Website design or development
- Photography or stock image licensing
- Print production and vendor coordination
Whitfield Creative
Signature and date
Nomad Coffee Co.
Signature and date
The 10 components of a solid scope of work document
1. Project summary: one paragraph on what's being built and why. 2. Included deliverables: the specific items you're handing over (pages, features, files), not a vague category. 3. Excluded items: what's explicitly not covered, so nothing gets assumed in. 4. Milestones and dates: the phases the work moves through and when each is due. 5. Roles and responsibilities: what you own versus what the client needs to provide (copy, assets, approvals) and by when. 6. Revision limits: how many rounds of feedback are included before extra rounds cost extra. 7. Acceptance criteria: how "done" gets confirmed for each deliverable, so sign-off isn't a moving target. 8. Assumptions and dependencies: anything the estimate relies on (existing brand assets, a working API, timely client feedback) that would change scope if it's wrong. 9. Change process: how additions get priced and approved once work has started, usually a pointer to a separate change request. 10. Payment tie-in: which milestones trigger which invoices, so scope and billing stay linked. Most disputes trace back to a missing item 3, 6, or 9: the pieces that only matter once something goes off-plan.
What should a scope of work explicitly exclude, not just include?
The excluded list is what actually prevents scope creep: an included list alone just describes the project, but "excluded: additional page templates beyond the 5 listed, content writing, stock photo licensing, hosting setup" is what you point to when a client asks for one more thing. Freelancers under-invest in the excluded section because it feels adversarial to write down what you won't do before the project starts, but it's the opposite: it's what lets you say yes to add-ons as a paid change request instead of an awkward argument about whether it was "basically included." Common categories worth excluding explicitly even when they seem obvious: revisions beyond an agreed count, content/copywriting if you're doing design or dev, third-party costs (stock assets, plugins, hosting), and post-launch support beyond a stated window.
Scope of work or proposal first: what's the right order?
Proposal first, scope of work second: the proposal wins the engagement and sets a rough shape of the work and price; the scope of work document then locks in the specifics once the client has said yes, before any work starts. Sending a scope of work before the client has committed is wasted detail: you're writing precise included/excluded line items for a deal that might not close. Sending vague scope after the proposal, on the other hand, is what causes the disputes the whole document exists to prevent. If a project is small enough that proposal and scope would be nearly identical, it's fine to merge them into one document. The sequencing matters more for larger engagements where scope takes real drafting time you don't want to spend twice.
Frequently asked questions
- How is this different from a proposal?
- A proposal sells the work; a scope of work document defines exactly what's included and excluded once the client has said yes.
- Does it prevent scope creep?
- That's the point: explicit "included" and "excluded" line items give you something to point to when a client asks for "just one more thing."
- Can I attach it to an existing project?
- Yes, link it to a client and it sits alongside their invoices and agreements.
