| Purpose | Explain the strategy and goals of the project. |
| Background | Give context to the project. |
| Technical Environment | Details of the technical environment including platforms, infrastructure, systems and facilities that are relevant to the work. |
| Scope of Work | A detailed list of functional and non-functional requirements. This may include a work breakdown structure that outlines activities, dependencies and milestones. The scope of work may also reference various requirements documents such as use cases, business rules, diagrams and mockups. |
| Special Requirements | Any requirements you have that relate to the performance of the vendor such as the requirement that the vendor provide certain tools, locations and infrastructure. |
| Location of Work | State the location of work and requirements that the vendor be physically present at a particular site or work offsite from their own facilities. |
| Period of Performance | Any requirements you have that relate to schedule such as a business calendar and daily work schedule. |
| Schedule | A project schedule or list of key dates such as due dates for deliverables. |
| Standards | A list of standards and principles that must be followed such as a style guide for a user interface, quality standard or security principles. |
| Deliverables | A list of everything the supplier will deliver. |
| Acceptance Criteria | Specifications of how work will be measured, validated and accepted. This may be listed at the deliverable level and may reference details at the requirement level such as test cases. |
| Commercial Terms | Commercial terms such as the type of contract and a payment schedule. Keep in mind that a statement of work is often attached to a full contract and legal terms need not be stated in detail. The commercial terms in the statement of work typically reflect the terms required by business units and project teams. |
