Before a project begins, a client and service provider need one document that answers three questions: what gets delivered, by when, and for how much. Without it, you’re relying on email threads, verbal agreements, and assumptions.
That document is the statement of work.

What is a statement of work?

A statement of work (SOW) is a document that fully outlines a work agreement between two or more parties. It’s used at the start of any service-based engagement, including consulting, software development, marketing, construction, and government contracting, to align both sides before work begins.

An SOW establishes the work requirements, acceptance criteria, payment terms, and milestones that define a successful project.
Think of it as the single source of truth for a project: what gets done, by whom, by when, and for how much. It’s one of the first documents created before kickoff, and everything that follows traces back to it. When there’s a dispute about scope or payment, the SOW is the document both parties return to.

What does a statement of work include?

While no two SOWs are exactly the same, most cover the same core components.

Here’s what a standard SOW should contain.

Additionally, the statement of work outlines the goals, timelines, and criteria for the acceptance and closure of the project.

Here’s a closer look at what any basic standard of work should contain.

• Project overview and goals: A high-level summary of what the project will achieve and why the work is being commissioned. This section sets the context for all parties.

• Scope of work: Defines exactly what’s included in the engagement and, just as importantly, what is not. This is the most critical section for preventing scope creep down the line.
• Deliverables: The specific outputs the service provider will produce, with clear acceptance criteria for each. Vague deliverables are one of the most common sources of project disputes.
• Timeline and milestones: The project schedule broken into phases, with key dates and dependencies called out. This gives both parties a shared view of progress and accountability.
• Tasks and responsibilities: Specific actions assigned to teams or individuals, often with due dates and sequencing. This section makes clear who owns what and when.
• Timeline and milestones: The project schedule broken into phases, with key dates and dependencies called out. For complex projects, milestones may need to be completed in a specific order, and it’s worth building in scheduled check-ins that connect individual deliverables back to the broader organizational goal.
• Costs and payment schedule: A clear breakdown of approved labor, expenses, and how funds will be released, whether on a milestone basis or another schedule. Because most projects run over budget due to labor, materials, or unforeseen circumstances, this section should also define the conditions under which budget overages are acceptable and how they will be handled.
• Standards and requirements: Any regulatory, technical, or communication standards that apply to the engagement, including reporting formats, compliance requirements, or tools both parties agree to use.
• Signatures: The SOW becomes a binding document once both parties sign.

A well-structured SOW will also include a definitions section to clarify acronyms and technical terms, a clause covering ownership and usage rights for any work produced, and a process for handling decisions that cannot be resolved before the project starts. For more inspiration on structure and format, see our SOW templates and examples.

Types of statements of work

So far, we’ve covered all of the basic details that are common in statements of work. Everything listed in the previous section is commonly included in every contract SOW.

But how you write your document depends on which type of SOW you use. There are three basic types. We’ll cover each one in detail below.

1. Design/detail SOW

This type of SOW provides a detailed description of project goals, along with any tasks, to-dos, and requirements. The defined work is clear and precise, aimed at producing a very specific final product. Statements of work in this category are often the most specific.

Contractors are provided with a set of instructions, including which software to use, exact dimensions, final specifications, and clear start and end dates. This leaves very little room for autonomy on the part of the contractor.

While it’s not precisely a “paint-by-numbers” contract, this type of SOW leaves most of the control in the hands of the issuing organization. All the contractor must do is follow the provided instructions.

2. Level of effort SOW

Also known as a time-and-materials or unit-based SOW, this can include variable costs based on effort or the units required to complete a task.

Contractors typically work on an hourly basis and adhere to a set of guidelines and expectations for the service they perform.

If you require more of a particular service, the contractor simply works longer to fill that need. Additional units of effort (labor hours) generate additional costs.

In this scenario, the company still maintains a thorough level of control.

The statement of work is clearly outlined, and the contractor only needs to follow issued guidelines to perform the task as described.

3. Performance-based SOW

This type of SOW offers the greatest flexibility for the contractor because it’s based on performance and output largely supplied by the contractor.

A performance-based SOW lays out (often in broad detail) what is required for the project to be completed.

The documentation might include details on the period of performance and the metrics the company intends to use as part of its acceptance criteria.

However, most of the details regarding how to achieve that result are left to the contractor.

While the company still receives a high-quality product in the end, how the contractor chooses to accomplish that goal is beyond the company’s control, except for the initial guidelines set in the SOW.

Statement of work vs. scope of work: what’s the difference?

These two terms are often used interchangeably, but they’re not the same thing. A scope of work is one section within a statement of work. The SOW is the complete document; the scope of work is the part that describes what work will actually be performed.

An easy way to remember the difference is that the scope of work answers “what,” and the statement of work answers what, how, when, by whom, and for how much. If you hand someone a scope of work, they know what needs to be done. If you hand them a full SOW, they have everything they need to execute and hold both parties accountable.

Is a statement of work a contract?

An SOW is not a contract on its own. It is a project document that defines the work to be done, but it does not, by itself, create a legally binding relationship between parties. A contract is a legal agreement that governs how the parties work together, including liability, dispute resolution, confidentiality, and termination rights.

In practice, an SOW is usually incorporated into a contract or signed alongside a Master Service Agreement (MSA). When that happens, the SOW gains legal force as part of the broader agreement. Think of the MSA as the rulebook for the relationship and the SOW as the project-specific playbook that sits underneath it. If you want to understand what makes that broader agreement enforceable, see our guide on what makes a contract valid.

Learn more about an MSA vs. an SOW.

Ready to write one?

Once you know what an SOW is and what it needs to cover, writing one follows a structured process:

• Gather your project inputs
• Define the scope and deliverables
• Set the schedule and payment terms
• Establish acceptance criteria
• Get both parties to sign

Each of those steps has its own considerations worth getting right the first time.

If you want the full walkthrough, our guide on how to write a statement of work covers each step in detail with examples. Or, if you already know what you need and want to get started, go straight to the free SOW template.

Create better statements of work with PandaDoc

An SOW is an essential part of many business and government processes, but creating one can be difficult and tedious.

PandaDoc is an excellent solution if you’re looking to get the most out of your document workflow. Our platform makes it easy to create, send, and sign documents while keeping processes streamlined and parties engaged.

Sign up for a free 14-day trial and see how PandaDoc can level up your contracts, proposals, statements of work, and more.

Disclaimer

PandaDoc is not a law firm, or a substitute for an attorney or law firm. This page is not intended to and does not provide legal advice. Should you have legal questions on the validity of e-signatures or digital signatures and the enforceability thereof, please consult with an attorney or law firm. Use of PandaDocs services are governed by our Terms of Use and Privacy Policy.

Originally published October 24, 2022, updated April 30, 2026