Practical Tools
Business

Statement of Work Builder

Service provider

Saves automatically.

Client

Project details

Project overview

Scope of work (in scope)

Out of scope

Deliverables and acceptance criteria

Milestones

Payment schedule

Terms and conditions

A Statement of Work (SOW) is the most important document in a project relationship. It defines exactly what you will deliver, when, how it will be accepted, and what it costs. Build yours in minutes and download a professional PDF both parties can sign.

No signupRuns in your browserWorks offlineFormula explained belowGeneral information only
This produces a general-purpose statement of work template, not legal advice. It is not written for any specific jurisdiction, and contract terms and enforceability vary by location. Review it for your situation and have a professional check anything important before both parties sign.

How to use this tool

  1. 1Enter your details (the service provider) and the client details.
  2. 2Fill in the project title, start date, end date, and a brief project overview.
  3. 3Describe the full scope of work - what is included and what is explicitly excluded.
  4. 4Add deliverables with acceptance criteria so both parties know what 'done' means.
  5. 5Add a timeline with milestones and dates.
  6. 6Add the payment schedule (e.g. 50% on signing, 50% on delivery) and any standard terms. Download or print.

Example

Software agency SOW for a web app

Provider: Catalyst Digital. Client: NovaCare Health. Project: Patient Booking Portal. Scope: Design and build a responsive web booking system with email confirmations. Out of scope: Mobile app, payment processing. Deliverables: Wireframes (Week 2), Design mockups (Week 4), Tested build (Week 10). Acceptance: UAT sign-off from client. Payment: 30% on signing, 40% at build handoff, 30% on go-live.

Marketing consultant SOW

Provider: Reeves Strategy. Client: Peak Outdoors. Project: Brand and Content Strategy. Scope: Competitor analysis, brand positioning, content plan for 6 months. Out of scope: Content production, paid media. Deliverables: Research report (Week 2), Brand framework (Week 4), Content calendar (Week 6). Payment: 50% on signing, 50% on final delivery.

Common use cases

  • Freelancers and agencies defining the exact scope of a project before starting to prevent scope creep
  • Contractors submitting a formal SOW alongside a proposal to win a tender
  • Project managers documenting what their team will and will not deliver for a client
  • Consultants setting clear boundaries around an engagement to protect their time and fees
  • Any professional who needs a signed agreement on scope before starting billable work

Common mistakes

  • Vague scope statements - 'design and build the app' is not scope; specific features, platforms, and browsers should be listed.
  • No out-of-scope section - explicitly listing what is NOT included is as important as listing what is.
  • Acceptance criteria that cannot be measured - 'client is satisfied' is not acceptance criteria; 'UAT passes with fewer than 5 outstanding bugs' is.
  • Not linking payment milestones to deliverables - payment should be tied to completion of defined deliverables, not calendar dates.

Frequently asked questions

What is the difference between a proposal and a statement of work?

A proposal is a persuasion document used to win a project. A Statement of Work is a formal agreement document signed by both parties that governs the delivery. A proposal describes what you could do; an SOW is a contract for what you will do.

Is a Statement of Work legally binding?

When signed by both parties, an SOW is a binding contract. It is recommended to include it within or reference it from a master services agreement. For large or complex projects, have a lawyer review the terms. This tool generates a professional SOW document; it is not a substitute for legal advice.

What should an SOW acceptance criteria section include?

Acceptance criteria should be objective and measurable. For software: passes UAT with fewer than X open bugs. For design: client approves 2 revision rounds per deliverable. For research: report reviewed and approved within 5 business days. Avoid subjective criteria like 'client is satisfied' - these lead to disputes.

How should scope changes be handled after an SOW is signed?

Scope changes should be documented with a change order or variation agreement that both parties sign before the extra work begins. The SOW itself can reference this process. Include a clause stating that work not described in the SOW requires a signed change order before proceeding.

Does an SOW need to be reviewed by a lawyer?

For small standard projects, a well-written SOW generated here is typically sufficient protection. For large contracts, custom IP development, sensitive data handling, or regulated industries, have a lawyer review or draft the terms. This tool produces a professional SOW document - it is not a substitute for legal advice on complex commercial arrangements.

Are my details stored on a server?

No. Everything runs in your browser. Your personal details save in browser local storage for convenience.

Related tools

Related guides

Last updated