Template
Statement of Work (SOW)
The engagement-specific document. It states exactly what will be delivered, by when, for how much, on what assumptions, and how completion is judged.
One per assessment, implementation, automation build, migration or managed-services term.
pitrontech.com
1. Engagement summary
SOW reference: [SOW-YYYY-NNN]. Effective date: [date]. Governed by the Master Services Agreement dated [date].
Business objective: [the outcome the Client wants, expressed in business terms].
Engagement type: [Health Check / Assessment / Implementation / Automation build / Data migration / Managed service].
2. Scope of work
In scope: [numbered list of workstreams, systems, objects, integrations, reports and environments].
Explicitly out of scope: [items commonly assumed but not included, e.g. additional integrations, custom development, end-user training beyond the stated sessions, data beyond the stated objects].
3. Deliverables
[Deliverable 1 — description, format, acceptance owner]
[Deliverable 2 — description, format, acceptance owner]
Documentation set: solution summary, configuration record, integration notes and handover pack.
4. Approach and timeline
Phases: Discovery → Design → Build → Test → Deploy → Handover (adapt per engagement).
Indicative duration: [n] weeks from kick-off, subject to the assumptions and dependencies below.
Key dates: kick-off [date], design sign-off [date], UAT window [dates], go-live [date].
5. Assumptions and dependencies
Client provides system access and required licences before kick-off.
Named business owner is available for [n] hours per week.
Source data is provided in an agreed format and quality; remediation beyond [n] hours is a change request.
Third-party vendors respond within [n] working days where their involvement is required.
6. Commercials
Fee basis: [fixed fee of $X / day rate of $Y with an estimate of Z days / monthly retainer of $X].
Payment milestones: [e.g. 40% on signature, 40% on design sign-off, 20% on go-live].
Expenses: pre-approved only. Licences and subscriptions are purchased by the Client directly.
7. Acceptance criteria
Each deliverable is accepted when the stated criteria are demonstrated in the agreed environment.
The Client has [5] working days to accept or raise defects in writing; otherwise the deliverable is deemed accepted.
8. Governance
Weekly progress report and a [30] minute checkpoint call. RAID log maintained throughout.
Escalation path: delivery lead → engagement owner → [Client sponsor].
9. Signatures
Signed by the Client and the Consultant, each with name, position and date.
Complete the placeholders before use
Everything in square brackets is a placeholder — company details, dates, fees, notice periods, liability caps, jurisdiction and bank details. Have a qualified legal or accounting adviser review the completed document before you send it to a client.