Modèle de périmètre de travail
A clean SOW template that reduces ambiguity—deliverables, milestones, assumptions, acceptance criteria, and what happens when priorities change. Two versions: plain-English and formal.
What You'll Get
- Plain-English version — Conversational tone for clients who prefer straightforward language
- Formal version — Professional language for enterprise clients or legal requirements
- Deliverables table — Clear listing of what's being delivered
- Assumptions & dependencies — What needs to be true for this to work
- Out of scope section — Explicit exclusions to prevent misunderstandings
- Change process section — How to handle scope changes
Download the Template
Get the scope of work template in PDF format.
No email required. Free to use and share.
Defining "Out of Scope" (With Examples)
The most important part of your SOW is what's NOT included. Be explicit:
Website Redesign Example
In scope: Homepage, About, Services, Contact page designs (4 pages total)
Out of scope: Blog template, e-commerce functionality, copywriting, photography, SEO optimization, hosting setup, content migration
Brand Identity Example
In scope: Logo (primary + icon), color palette, typography selection, basic brand guidelines (10 pages)
Out of scope: Brand strategy/positioning, tagline development, extended guidelines, business card design, website design, social media templates
Marketing Campaign Example
In scope: Campaign strategy, 3 ad concepts, 1 landing page design, campaign setup in ad platform
Out of scope: Ongoing optimization, ad spend management, landing page development, copywriting beyond headlines, A/B testing beyond initial setup
How Change Requests Connect
Your SOW should explain what happens when scope needs to change:
"Changes to this scope will be documented using a Change Request Form. The client will receive impact assessment (time, cost, timeline) and must approve before work proceeds. Minor clarifications within the spirit of this scope require no formal change request."
Link to your Change Request Form in the SOW.
How to Use This Template
- 1
Start with the discovery call notes
Use information from your Creative Brief or discovery to populate the SOW.
- 2
Fill in deliverables first
Be specific: "5-page website" not "website redesign." Include quantities, formats, and specs.
- 3
Write the out-of-scope section
Think about what the client might assume is included but isn't. List those things explicitly.
- 4
Document assumptions
"Client will provide copy by X date." "Assumes access to Y platform." If these aren't met, scope changes.
- 5
Review with the client
Walk through the SOW together. Don't just send it—discuss it to ensure alignment.
Common Mistakes & How to Avoid Them
Being vague about deliverables
"Logo design" is vague. "Primary logo + icon variant, delivered in AI, EPS, PNG, SVG formats" is specific.
Skipping the out-of-scope section
If you don't say what's excluded, clients will assume it's included. Always have explicit exclusions.
Not defining acceptance criteria
"Approved by client" is subjective. "Client provides written approval within 5 business days" is measurable.
Ignoring dependencies
If you need client content, API access, or third-party assets, list them. Timeline delays from missing dependencies aren't your fault if documented.
How to Run This in Corcava
- Attach SOW to the deal/project — Keep documentation connected to the work
- Create project milestones from deliverables — Turn SOW items into trackable tasks
- Share via client portal — Client can access and reference the SOW anytime
- Track changes with version history — See how scope evolved over the project
Maps to: Projects, Documents, Client Portal features
Frequently Asked Questions
What's the difference between an SOW and a proposal?
A proposal is a sales document—it sells the work and includes pricing, timeline, and why you're the right fit. An SOW is a project document—it defines exactly what will be delivered. The proposal may include an SOW section, or the SOW may be a separate document signed after the proposal is accepted.
Should the SOW include pricing?
It can, but doesn't have to. Some agencies include pricing in the SOW for simplicity. Others keep pricing in a separate agreement or invoice schedule. The key is that scope and price are clearly connected somewhere.
How detailed should deliverables be?
Detailed enough that both parties would reach the same conclusion about what's included. "Website" is too vague. "5-page marketing website including homepage, about, services, blog index, and contact page, responsive design, delivered as HTML/CSS" is clear.
When should I use the formal vs plain-English version?
Use formal for enterprise clients, procurement processes, or when legal review is involved. Use plain-English for startups, small businesses, and clients who value straightforward communication. When in doubt, ask what they prefer.
How do I handle scope that's hard to define upfront?
Use phases. Phase 1 can be discovery/scoping with a fixed price. Phase 2 is the actual work with scope defined after Phase 1 is complete. This protects both parties when requirements are unclear.
Should the client sign the SOW?
Yes, ideally. A signature indicates agreement. If formal signatures aren't practical, at minimum get explicit written confirmation: "Reply to this email with 'approved' to confirm you agree to this scope."