← Back to Templates
Client Onboarding
Scope of Work Email Template
A scope of work document is the most effective tool for preventing scope creep — but only if the client actually reads and agrees to it before work begins. This email introduces the document clearly and creates a natural checkpoint for alignment before you're locked into a contract.
When to send
Send the scope of work before the contract — it's much easier to adjust terms at this stage. Once the contract is signed, changes require formal amendments.
The Template
Subject: Scope of Work: [Project Name] - Please Review
Hi [Client Name],
Attached is the scope of work for [project name], which summarizes everything we've discussed and agreed on before we get started.
It covers:
- Project objectives and deliverables
- What's included — and what's explicitly out of scope
- Timeline and milestones
- Revision policy
- Payment schedule
Please review it carefully and let me know if anything looks different from what you were expecting, or if you'd like to make any adjustments. Once we're both aligned, I'll send over the contract.
Happy to schedule a quick call to go through it together if that's easier.
Best,
[Your Name]
Tips for Getting This Right
- Explicitly list what's out of scope — this is the most important part of any scope document and the most commonly missed.
- Offer a call to review it. Clients who discuss the scope verbally have fewer surprises and disputes mid-project.
- Be specific about deliverables — 'a website' is not a deliverable. '5-page website with homepage, about, services, blog, and contact pages' is a deliverable.
- Include the revision policy clearly — how many rounds, what counts as a revision versus a new request.
- Don't start work until the client has acknowledged the scope in writing, even informally.
Common Mistakes to Avoid
- Skipping the scope of work and going straight to a contract — contracts are harder to negotiate. A scope of work is the right place to iron out expectations.
- Being vague about what's included — vague deliverables always expand in the client's mind.
- Not defining out-of-scope items — if you don't say what's not included, clients assume everything is.
- Sending it after the project has started — the scope needs to be agreed before work begins, not mid-project when there's already a dispute.
Frequently Asked Questions
Is a scope of work the same as a contract?
No. A scope of work defines what you're doing. A contract is the legal agreement that governs the entire relationship, including payment, IP, liability, and dispute resolution. The scope of work is often attached to or incorporated into the contract.
What if the client wants to change the scope mid-project?
Refer back to the agreed scope of work. Any changes outside the original scope should go through a formal change request, with a new quote and timeline. Your contract should include a clause for this.
How detailed should a scope of work be?
Detailed enough that there's no ambiguity about what you're delivering. If you can imagine a client asking 'does this include X?' about something, include it explicitly — either as in-scope or out-of-scope.
Do I need a scope of work for small projects?
For very small, simple, one-deliverable projects, a detailed contract may be sufficient. But for anything that takes more than a few hours or involves multiple deliverables, a scope of work is worth the 20 minutes it takes to write.