A statement of work template is a formal procurement document that provides a narrative description of the products, services, or results to be delivered under a contract or work package. According to the Project Management Institute (PMI), the statement of work (SOW) is a key procurement document in PMBOK 8 used to define the scope of work that a vendor or contractor must deliver, establishing the foundation for the contract and the basis for vendor performance evaluation. A well-written SOW prevents the most common source of contract disputes: differing interpretations of what was agreed.

What is a Statement of Work?

A statement of work template is a structured document that describes the work scope, deliverables, timeline, location, applicable standards, and acceptance criteria for work performed by an external party. In PMBOK 8, the SOW is referenced in the Procurement Performance Domain as the document that defines exactly what the performing organization is contracting to deliver. The SOW transforms internal WBS work packages into an externally facing, contractually binding description of scope — forming the technical basis of the contract alongside the terms and conditions.

What's Included in This Statement of Work Template?

• Scope of Work Description - A detailed narrative of the work to be performed, written from the perspective of what the contractor must deliver, not just what the buyer needs internally.
• Deliverables List - A specific, enumerated list of all deliverables the contractor must produce, with enough detail to enable unambiguous acceptance or rejection at delivery.
• Performance Requirements and Standards - The technical standards, regulatory requirements, quality specifications, and performance benchmarks the deliverables must meet.
• Period of Performance - The start date, end date, and any phased delivery schedule for the work, including key milestone dates that anchor the project schedule.
• Place of Performance - Where the work will be performed — on-site at the buyer's location, at the contractor's facility, or remotely — including any travel requirements and associated constraints.
• Applicable Documents and Standards - References to all documents, standards, specifications, and regulations that the contractor must comply with in performing the work.
• Acceptance Criteria - The specific, measurable criteria that the buyer will use to evaluate and accept each deliverable, including any inspection, testing, or review processes.
• Buyer-Furnished Items - Any data, equipment, facilities, access, or materials that the buyer will provide to the contractor to enable performance of the work.

How to Use This Statement of Work Template (PMBOK 8)

1. Write the SOW from the contractor's perspective - The SOW describes what the contractor must do, not what the buyer wants to achieve. Describe the work in terms of actions, outputs, and standards — not organizational goals or business objectives.
2. Make acceptance criteria explicit and measurable - Vague acceptance criteria like "to the buyer's satisfaction" are the most common cause of contract disputes. Define exactly what will be inspected, tested, or reviewed, and what constitutes pass/fail.
3. Include all applicable documents by reference - Do not repeat technical specifications in the SOW body. Reference them by document number and version. This keeps the SOW readable while ensuring all requirements are contractually binding.
4. Define the boundary of work explicitly - State clearly what is outside the contractor's scope. Anything not explicitly excluded may be claimed as in-scope by the contractor or assumed as in-scope by the buyer, creating disputes at delivery.
5. Have technical and legal subject matter experts review the SOW - The SOW must be technically accurate (reviewed by the project team) and legally sound (reviewed by contracts or legal counsel) before being issued to potential contractors.
6. Update the SOW when scope changes are approved - Any approved change to the contracted scope must be reflected in a formal contract modification to the SOW. Verbal or informal scope changes create unauthorized work.

When to Create This Document (PMBOK 8)

The statement of work is created during the Plan Sourcing Strategy process, after the make-or-buy decision confirms that work will be contracted externally. In PMBOK 8, the SOW is developed as part of the procurement documents package before vendor solicitation begins — it must be complete before an RFP or RFQ can be issued. The SOW becomes part of the executed contract and remains the binding scope reference throughout the contract period.

Related Templates

• Sourcing Strategy Plan Template
• Request for Proposal Template
• Request for Quotation Template
• WBS Dictionary Template
• Scope Baseline Template

Complete Guide & Filled-In Example

Get the most out of this template with the two companion resources below:

• Download the Filled-In Example - Project Phoenix - See exactly how this document was completed for a real $72K website launch project.