Free Statement of Work (SOW) Template
By the CrewDriven team · 10 min read · Updated May 15, 2026
A Statement of Work protects you when a project slides, when a client asks for something that was not in the original brief, and when the relationship ends and somebody asks "what exactly did we agree?" Use this template as the starting point — copy it, paste your specifics, send it. It is the same structure agencies have been using for two decades; the language below is what makes it actually work.
Get the free SOW template
Drop your email and we will unlock the editable Google Doc instantly. Make a copy to your Drive and you are ready to send.
No spam — we will only email you occasional agency-operations tips. Unsubscribe anytime.
What is a Statement of Work?
A Statement of Work — SOW — is the document that turns a vague conversation about a project into a concrete agreement. It sits between the master services agreement (the legal frame for the entire client relationship) and the day-to-day invoices and timesheets. The MSA says "here is how we work together"; the SOW says "here is what we are doing right now, for how much, by when." Every serious project should have one. Even a four-week sprint with a long-time client benefits from a one-page SOW — because the moment scope moves, someone needs a document to point at.
A good SOW is not a legal weapon. It is a shared definition of "done." When the client thinks the project includes three rounds of revisions and you thought two, the SOW settles it. When the project plan slips because the client took six weeks to send brand assets, the SOW shows where the timeline reset. The act of writing it forces a conversation about scope, deliverables, and money that often does not happen otherwise — and it is much cheaper to have that conversation in week one than in week eight.
10 essential sections every SOW needs
- 1
Project overview
Two or three sentences naming the client, the project, the business objective, and the rough shape of the engagement. This is the elevator pitch that orients anyone who reads the document later — including your own team six months from now. Avoid jargon; write it so a non-specialist could understand what you are about to build.
- 2
Scope of work
A specific list of what is in scope and — equally important — what is out of scope. "Design and build a five-page marketing website" is in scope. "Ongoing content updates after launch" is out of scope. The out-of-scope list is what saves you when the client asks for a tenth page two weeks before launch. List both; do not assume the absence of mention is enough.
- 3
Deliverables
Tangible artifacts the client receives. "Figma file with finalized designs," "deployed website on client domain," "training documentation PDF." Be specific about format and quantity. "Five hero illustrations as PNG and SVG at 2x resolution" beats "illustrations" every time, because the second version is an argument waiting to happen.
- 4
Timeline & milestones
Key dates with deliverable checkpoints. Discovery complete by date X, design review by date Y, beta launch by date Z. Include a note about what causes the timeline to shift — typically "client review windows" and "asset delivery from client" — so neither side is surprised when a missed deadline on their end pushes the launch.
- 5
Payment terms
Total project fee, payment schedule, accepted payment methods, currency, late payment terms. A common structure for project work is 40% on signature, 30% at midpoint milestone, 30% on delivery. For ongoing engagements, monthly retainer terms. State whether expenses are billed separately and what the limit is.
- 6
Acceptance criteria
How the client formally accepts deliverables. Usually: written approval via email within X business days of delivery, with deemed acceptance if no objection by the deadline. Without this clause, deliverables hang in approval limbo and you cannot bill the milestone. Define the review window — five business days is standard — and what happens if it lapses.
- 7
Change request process
How scope changes are handled mid-project. Standard language: any change to scope, deliverables, or timeline requires a written change order signed by both parties, which may include adjustments to fees and timeline. This single clause prevents most of the "but I thought that was included" arguments by giving you a formal mechanism to say "happy to add that — here is the change order."
- 8
Confidentiality
Both parties protect the other's confidential information. Most MSAs already cover this in detail, in which case the SOW just references the MSA. If you do not have an MSA, include a short confidentiality clause inline: each party keeps the other's non-public business information confidential, with usual carve-outs for legally required disclosure and information already in the public domain.
- 9
Termination clause
How either party can end the engagement. Typical: either party may terminate for material breach with 30 days written notice and opportunity to cure; either party may terminate for convenience with 30 days notice, with the client paying for work completed and committed-to costs through the termination date. This protects you from clients who walk away at week six of a twelve-week project.
- 10
Signatures
Both parties sign and date. Electronic signatures via DocuSign, HelloSign, or even Google Docs signature blocks are legally binding in most jurisdictions. Make sure the signatory on the client side has authority to commit the company — getting the marketing director's signature does not bind the company if procurement was supposed to approve.
What a real SOW looks like
A short, working example. Use this structure for your next engagement and replace the placeholder language with your specifics.
STATEMENT OF WORK
SOW #001 — Effective Date: [DATE]
Between
[Your Company LLC] ("Provider")
[Client Inc.] ("Client")
1. Project Overview
Provider will design and develop a five-page marketing website for Client, including content management capability, basic SEO setup, and analytics integration. The project supports Client's Q3 2026 product launch.
2. Scope of Work
In scope:
- Visual design for five pages (home, about, product, pricing, contact)
- Frontend development in Client's preferred stack
- CMS integration for two editable content blocks per page
- Two rounds of design revisions and one round of post-launch refinements
Out of scope:
- Brand identity work (logo, brand guidelines)
- Ongoing content updates after launch
- Custom illustrations beyond stock imagery and Client-supplied assets
3. Deliverables
- Figma file with finalized designs for all five pages
- Deployed website on Client domain
- Brief admin training (one 60-minute session)
4. Timeline & Milestones
- Week 1–2: Discovery, sitemap, wireframes
- Week 3–4: Visual design, two rounds of revisions
- Week 5–7: Development and CMS integration
- Week 8: QA, launch, admin training
5. Payment Terms
Total project fee: $24,000 USD. Payment schedule: 40% on signature ($9,600), 30% at design approval ($7,200), 30% on launch ($7,200). Invoices are Net 14. Late payments accrue interest at 1.5% per month.
6. Acceptance Criteria
Each deliverable is accepted upon written approval from Client within five business days of submission. If Client does not provide written feedback within five business days, the deliverable is deemed accepted.
7. Change Requests
Any change to scope, deliverables, or timeline requires a written change order signed by both parties. Change orders may include adjustments to fees and timeline.
8. Termination
Either party may terminate this SOW for material breach with 30 days written notice. Either party may terminate for convenience with 30 days notice; Client pays for work completed through the termination date.
9. Signatures
For Provider: _______________________ Date: ___________
For Client: _______________________ Date: ___________
How to send and track SOWs in CrewDriven
A signed SOW is the start, not the end. The numbers in the document — total fee, milestone payments, late-payment terms — become invoices, payment trackers, and cash-flow forecasts. The deliverables become work assignments for your team. The timeline becomes a project plan. Without a system that connects the SOW to the operations, the document gets filed and the team still works from memory.
CrewDriven turns SOW commitments into operational reality. The total project fee becomes a billable expectation against the client record. Milestone payments become scheduled invoices. The team members assigned to deliverables show up on the project with their cost and bill rates set. The project P&L view shows revenue against actual costs as the work happens — not after the project is delivered and you finally have time to look. You can create your workspace now and start tracking your next SOW against real numbers, or see how project profitability works for the deeper version on per-project margin.
Frequently asked questions
- What is the difference between a SOW and a contract?
- A contract — usually a Master Services Agreement (MSA) — is the legal frame for the whole client relationship: confidentiality, IP ownership, liability limits, governing law. A Statement of Work sits underneath it and defines a specific engagement: scope, deliverables, timeline, fees. One MSA, many SOWs. For small projects without an MSA, the SOW can include the essential legal terms inline.
- Do I need a SOW for small projects?
- Yes — even a one-page SOW. The discipline of writing it down forces the scope conversation that catches misunderstandings before they become disputes. A two-paragraph SOW for a $2,000 logo project is fine; a thirty-page novel for a $200,000 build is overkill. Scale the document to the engagement.
- Can I use this template for retainer work?
- Yes, with adjustments. For retainers, replace "Timeline & Milestones" with "Retainer Period and Renewal Terms," replace the milestone payment schedule with monthly billing, and add a section on scope limits per month (typically hours or deliverable units). Keep change request, acceptance, and termination clauses; they are even more important on ongoing relationships.
- What happens if scope changes mid-project?
- Use the change order process defined in the SOW. Write the new request, estimate the additional fee and timeline impact, send it to the client for signature. Do not start the new work until the change order is signed. This is the single biggest discipline that separates agencies that earn change-order revenue from agencies that quietly absorb scope creep.
- Can clients sign SOWs electronically?
- Yes — in the US (ESIGN Act), EU (eIDAS), UK, Canada, Australia, and most other jurisdictions, electronic signatures via DocuSign, HelloSign, Adobe Sign, or even Google Docs signature blocks are legally binding for commercial agreements. A few specific document types (wills, certain real-estate transfers) require wet signatures; SOWs do not.
Track your SOW commitments in CrewDriven
Turn signed SOWs into real project P&L. Multi-currency, per-assignment rates, free during launch.