Statement of Work
A statement of work is the single most important document for preventing scope creep — defining precisely what is included, what is not, and how changes are managed.
What is a Statement of Work?
A statement of work (SOW) is a project-specific document that defines the scope of services to be delivered, the deliverables the client will receive, the timeline, the fees, and the process for managing changes. It is typically attached to or governed by a master service agreement or agency agreement, which contains the general commercial terms.
For agencies, scope creep is the primary profitability killer. It occurs when clients expect more than what was agreed, and agencies deliver more than what was contracted — eroding margins and creating resentment on both sides. A well-drafted SOW is the primary defence: it creates a shared, written record of what done looks like, how revisions are handled, and what triggers an additional fee.
The best SOWs are specific without being rigid. They define deliverables clearly enough that disputes about quality and completeness are resolved by reference to the document, while allowing enough flexibility to accommodate reasonable evolution of the project.
When do you need a Statement of Work?
- ✓Before beginning any client project with a defined scope, timeline, and fee
- ✓When a master service agreement is in place and a new project is starting
- ✓When the scope of an existing project is being materially changed
- ✓When engaging subcontractors to perform part of a project under your primary contract
- ✓When a fixed-fee project includes specific deliverables and acceptance criteria
- ✓Before issuing any invoice for project work
Key provisions to include
Scope of Work
Detailed description of the services to be provided and what is specifically excluded from the engagement.
Deliverables
Specific outputs the client will receive, with description, format, and quality standards.
Timeline & Milestones
Project schedule with key milestone dates, dependencies, and the impact of client delays on delivery dates.
Fees & Payment Schedule
Project fee or rate, milestone-based payment schedule, and invoicing terms.
Change Request Process
How scope changes are identified, assessed, priced, and approved — the core scope creep defence.
Client Obligations
What the client must provide (briefs, approvals, access, content) for the agency to deliver on time.
Acceptance & Sign-Off
How deliverables are reviewed, approved, and formally accepted by the client.
Intellectual Property
When IP in deliverables transfers to the client and any conditions attached (e.g., receipt of full payment).
Common mistakes to avoid
Using vague deliverable descriptions like 'website' or 'campaign' without specifying the components, pages, or formats included
Not defining a change request process, meaning all client requests must be absorbed within the original fee
Failing to specify client obligations and the impact of client delays on your timeline and delivery obligations
Not tying IP transfer to final payment, giving clients the ability to withhold payment after receiving deliverables
Including too much legal boilerplate in the SOW instead of keeping it focused on the project specifics
Frequently asked questions
What is the difference between a statement of work and a service agreement?
A service agreement sets out the general commercial terms of the client relationship — payment terms, dispute resolution, IP ownership, and liability. A statement of work is project-specific and defines the particular scope, deliverables, and fees for a given engagement. Most agencies use a master service agreement once and then issue SOWs for each project.
How should I handle scope creep in a SOW?
The SOW should include a clearly defined change request process: when a client requests work outside the defined scope, you issue a change request that describes the additional work, the cost, and the impact on the timeline. The client approves or declines. No out-of-scope work begins until the change request is signed. This creates a documented record of agreed changes and prevents disputes about what was included.
Who owns the work created under a SOW?
This depends on your master service agreement or the IP clause in the SOW. Most agencies retain ownership of IP until final payment is received, at which point ownership transfers to the client. Some agencies license rather than assign IP. The SOW should reference the IP provisions clearly so both parties understand the position from the start.
Can I use the same SOW template for all clients?
Yes — a standard template adapted for each project is the best approach. The core structure (scope, deliverables, timeline, fees, change requests) is the same. The project-specific details (descriptions, dates, amounts) are filled in per engagement. The template ensures nothing is forgotten.
Related documents
Draft your Statement of Work in minutes
Try Neureson free for 3 days — no credit card required.
Start for free →