← 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]
Business and Vendor Versions
The template above is written for a freelancer sending a scope to a client. Scopes of work move in other directions too — out to vendors and suppliers for quotation, back and forth for clarification, and sometimes they don't exist yet at all. These three cover those cases.
Subject: Scope of Work for Quotation: [Project / Part Name] – Response by [Date]
Hi [Vendor Contact Name],
Attached is the scope of work for [project / component / package], which we'd like you to quote against. Please treat the attached as the basis for your quotation; if anything in it can't be met as written, flag it rather than quoting to a different assumption.
The key points:
- Deliverables and quantities: [summary]
- Specifications and standards: see Section [X]
- Required delivery / completion date: [date]
- Payment milestones we're proposing: [e.g. 30% on PO, 40% on FAT, 30% on delivery]
- Items explicitly excluded from this scope: see Section [X]
Please send your quotation, lead time, and any exceptions or clarifications by [date]. If it would help, I'm happy to set up a call with our [engineering / operations] team before then.
Regards,
[Your Name]
[Title, Company]
Subject: Clarification Needed: [Project Name] Scope of Work
Hi [Name],
Thank you for the scope of work for [project name]. Before we confirm pricing and schedule, we need clarification on a few points so that we're quoting against the same assumptions you are:
1. [Item] — the scope says "[quoted text]". Does this include [specific question]?
2. [Item] — who is responsible for [materials / access / approvals / permits]?
3. Acceptance — what is the sign-off process, and who on your side approves each deliverable?
Once these are confirmed, we'll send an updated quotation within [X] business days. Any point that changes the scope will be reflected in the revised document so the final version is the single reference for both teams.
Regards,
[Your Name]
Subject: [Project Name] – Proposed Scope of Work for Your Approval
Hi [Name],
You mentioned there isn't a written scope of work for [project name] yet. Rather than start on assumptions, I've drafted one based on our conversation so far — it's attached for your review.
It sets out:
- What will be delivered, and what's explicitly not included
- The timeline and the materials or access we'll need from your side
- How changes outside this scope will be handled
- The payment schedule
If it needs approval from someone else on your side — for example [Name / Title] — please forward it to them directly, or let me know who should sign off and I'll send it to them. Work will begin once it's approved in writing; a reply to this email confirming approval is enough.
Best,
[Your Name]
Two things make the difference in all three. First, name the exclusions — in a vendor quote an unlisted item becomes a change order later, and in a client scope it becomes an argument. Second, name the approver. Scopes stall most often not on content but because nobody said who signs off, which is why the third template asks the question outright instead of guessing. For tiered offers, see how to draw the scope lines between tiers; to build the document itself, use the scope of work generator.
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.
How do I send a scope of work to a vendor for a quote?
Attach the scope, ask the vendor to quote against it exactly as written, and ask them to flag any point they can't meet rather than quoting to a different assumption. Give a response date, state the payment milestones you're proposing, and list the exclusions explicitly. Without that last part, anything the vendor assumed was included becomes a change order after the purchase order is issued.
What if there's no scope of work yet?
Offer to draft one from what's already been discussed, send it for approval, and don't start until it's approved in writing — a reply email confirming approval is enough. If the person you're talking to can't approve it themselves, ask who can and send it to them directly. Starting work before a scope exists is how most projects end up in a dispute about what was agreed.
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.