Template

Statement of Work Template for Implementations and Services

A statement of work template defines exactly what a vendor will deliver to a client: parties, background, scope, deliverables, what is out of scope, milestones with acceptance criteria, timeline, assumptions, change control, fees and sign-off. The SOW below works for software implementations, consulting and professional services engagements.

See pricing

Services lead marking scope and deliverables on a printed statement of work

onboardingcustomers.com/app/templates/sow SOW structure

Statement of work, Quillmere Freight Partners

Each section of the SOW becomes a specific part of the onboarding plan

1. Scope of servicesDispatch module, carrier portal, 3 depots Plan phases and tasks per depot
2. DeliverablesConfigured routing rules, data import, admin training Milestones with sign-off
3. Customer responsibilitiesDepot list, carrier contracts, IT contact Customer tasks in the portal
4. TimelineKickoff Oct 21, go-live Dec 5 Phase dates and go-live target
5. Acceptance criteriaTwo weeks of live dispatch without manual reroute Go-live checklist
6. Change controlWritten change request, priced separately Scope change log

Why the SOW decides how onboarding goes

Most disputes in a services engagement or a software implementation trace back to the statement of work. A deliverable that was described in one vague line. An integration that sales mentioned in a call but never wrote down. An acceptance step that nobody defined, so the client never formally accepts anything and the final invoice waits.

A good SOW template prevents those problems by forcing the right questions before signature. What exactly will be delivered? What will not? How does the client accept each milestone? What happens if they want something new halfway through? Who signs?

The SOW template below is written for B2B vendors: software companies running implementations, agencies, IT consultancies and professional services firms. It is long enough to be complete and short enough that a client will actually read it.

Out of scope is explicit

The template has its own section for what is not included. It is the cheapest protection against scope creep you will ever write.

Acceptance per milestone

Each milestone has an acceptance criterion and a review window, including what happens when the client does not respond.

Ready to become a plan

The structure maps directly onto phases, tasks and milestones, so the signed SOW turns into the onboarding plan without retyping.

The statement of work template

Copy the whole template and replace every bracketed placeholder. The example lines show the level of detail that works; delete them once you have your own.

Statement of work

Statement of Work [Number]
Under the [Master Services Agreement or Order Form] dated [Date]

1. Parties

Client: [Client name], [Client address], represented by [Name, title]
Vendor: [Vendor name], [Vendor address], represented by [Name, title]
Effective date: [Date]

2. Background and objectives

[Two or three sentences on why the client is buying this work and what result they expect. Example. Client is replacing its current scheduling tool across 14 dental clinics and wants all clinics booking patients in [Product name] by [Date].]

3. Scope of work

Vendor will perform the following services:

[Service 1. Example. Configure [Product name] for 14 locations, 3 user roles and the agreed appointment types]
[Service 2. Example. Migrate active patient records and future appointments from [Current system]]
[Service 3. Example. Connect [Product name] to the client billing system using the standard integration]
[Service 4. Example. Train up to 6 administrators and run one end-user session per location]

4. Deliverables

ID	Deliverable	Description	Acceptance criterion
D1	Project plan	Phased plan with dates, owners and milestones	Approved in writing by Client project lead
D2	Configuration	[Product] configured to the approved design	Walkthrough completed, design checklist signed
D3	Data migration	[Entities] imported from [System]	Client validates a sample of [50] records with no critical errors
D4	Integration	Connection to [System]	Agreed test cases pass in production
D5	Training	Admin and end-user sessions with recordings	Sessions delivered, recordings shared

5. Out of scope

The following are not included in this SOW and require a change request:

[Example. Migration of records older than [24] months]
[Example. Custom reports beyond the standard report library]
[Example. Integrations other than those listed in Section 3]
[Example. Training sessions beyond the number listed in Section 3]

6. Milestones and acceptance

Milestone	Deliverables	Target date
M1. Plan approved	D1	[Kickoff + 5 business days]
M2. Configuration accepted	D2	[Date]
M3. Data and integration accepted	D3, D4	[Date]
M4. Go-live	D5 and production use	[Date]

Client will review each deliverable within [5] business days of delivery and either accept it or list specific defects against the acceptance criterion. If Client does not respond within that window, the deliverable is considered accepted.

7. Timeline

Work starts on [Start date] with a kickoff meeting. Target go-live is [Date]. The timeline depends on Client meeting its responsibilities in Section 8.

8. Assumptions and client responsibilities

Client names a project lead with authority to approve deliverables within [5] business days of signature
Client provides admin access and data exports by [Date]
Data is provided in the import template supplied by Vendor
Client key users are available for testing during [Week range]
[Other assumption]

9. Change control

Either party may request a change to scope, timeline or deliverables in writing. Vendor will respond within [5] business days with the impact on fees and dates. No change is binding until both parties sign the change request. Work on a change starts only after signature.

10. Fees and payment

Fee type: [Fixed fee or time and materials]
Total: [Amount and currency]
Payment schedule: [Example. 40 percent on signature, 30 percent on M2, 30 percent on M4]
Payment terms: as set in the [Master Services Agreement]

11. Sign-off

	Client	Vendor
Name	[Name]	[Name]
Title	[Title]	[Title]
Signature
Date

This template is a practical structure, not legal advice. Have your counsel review it together with your master agreement.

A sample statement of work, line by line

The example lines in the template come from a fictional engagement. Atlas Dental Group buys a practice management system for 14 clinics. Here is why each choice in their statement of work example matters.

Background names a date and a number. "All clinics booking in the new system by March 1" is a goal both sides can check. "Modernize scheduling" is not.
Training has a limit. "Up to 6 administrators and one session per location" means the 15th clinic Atlas opens next year is a new piece of work, not an unpaid extension.
Data migration has a cut-off. Records older than 24 months are out of scope. When Atlas asks for ten years of history, the answer is a change request with a price.
Acceptance has a deadline. The five-day review window stops a milestone from staying open for a month because the approver is on holiday.

Consulting and professional services statement of work templates

For a consulting statement of work template, keep the same eleven sections and change what goes inside Deliverables. Advisory work produces reports, workshops, recommendations and roadmaps. Each still needs an acceptance criterion: a report is accepted when the client has reviewed the draft and one round of comments has been addressed.

For a professional services statement of work template with time and materials billing, add a rate table to Fees and a monthly cap. Keep the out of scope section anyway. Even when the client pays by the hour, a list of what is not included protects the timeline.

Services firms can see how the full flow runs after signature on the professional services client onboarding page.

Paste the finished SOW and get the onboarding plan

The SOW is the most precise description of what you sold. It should not sit as a PDF while someone rebuilds the plan by hand in a spreadsheet.

In OnboardingCustomers you paste the signed statement of work, and the AI onboarding plan reads it. Deliverables become phases and tasks, milestones keep their acceptance criteria, client responsibilities from Section 8 become customer tasks with owners, and the target go-live sets the dates. Anything the document leaves unclear is flagged for your team to confirm at kickoff.

The client then works through their part in a branded portal, and each milestone acceptance is recorded with a name and a timestamp. For larger rollouts, compare the result with our implementation plan template.

onboardingcustomers.com/app/onboardings/184 Owner: Ingrid Halvorsen

Northwind Logistics, Growth rollout

Go-live Nov 15, 32 days left

On track

Closed-won Oct 1
Kickoff Oct 6
Discovery Oct 13
Configuration Oct 27
Training Nov 7
Go-live Nov 15

Discovery, 5 tasksSide

Confirm data fields to import Customer
Share current carrier contracts Customer
Map warehouse codes to locations Vendor
Review user roles with IT lead Vendor
Approve configuration workbook 2 days late Customer

Keep exploring

AI onboarding plan Paste the signed SOW and get the project plan. Implementation plan template The plan you build from this SOW. Professional services onboarding How services firms run onboarding.

Frequently asked questions

Still deciding? Write to [email protected] and a person on our team answers.

What is a statement of work?

A statement of work, or SOW, is the document that describes the work a vendor will do for a client under a master agreement or contract. It sets scope, deliverables, timeline, acceptance criteria and fees, so both sides agree on what done means before the work starts.

What is the difference between a SOW and a contract?

The contract or master services agreement sets the legal terms such as liability, confidentiality and payment terms. The SOW sits under it and describes one specific piece of work. A client can have one master agreement and many SOWs.

How detailed should a SOW template be?

Detailed enough that someone who was not on the calls before signing can deliver the work. Every deliverable should have an acceptance criterion and every assumption should be written down. If a sentence could be read two ways, rewrite it.

Is this a consulting statement of work template too?

Yes. The structure works for consulting and professional services statements of work. For pure advisory work, replace configuration deliverables with reports, workshops and recommendations, and keep the acceptance and change control sections.

Is this template legal advice?

No. It is a practical structure for describing work. Have your own counsel review the SOW together with your master agreement before you use it with clients.

What happens after the SOW is signed?

The SOW becomes the onboarding or implementation plan. In OnboardingCustomers you paste the finished SOW and get a phased plan with milestones and customer tasks, ready to share in a portal.

Paste your finished SOW and get the plan

OnboardingCustomers reads the SOW, builds the phased onboarding plan with milestones and customer tasks, and opens a portal for your client.

Compare plans

Generate my onboarding plan