Statement of Work - Template
<Project Name>
<Project Cost Codes (if available) >
Prepared for:
<enter contractual partner at company name for the
statement of work>
Project Manager <name>
Version <document version number>
Date <dd/mm/yyyy>
Doc reference <insert link>
1.1 Revision History
Document
Author
Date Completed
Version Date Revised By Revisions Made
Tom Mills 1 Procurement Protagonist
1.2 Document Reviewers
Name Role Date reviewed Version
<enter name>
<enter name>
Note: subsequent document versions are subject to SME re-review
1.3 Document Approvers
Name Role Date approved Version
<enter name>
<enter name>
<enter name>
<enter name>
Note 1: Approvals can be obtained via Steering Committee meetings
Note 2: A record of approvals must be kept in the project folder
1.4 Document Distribution
Name Role Date circulated Version
<enter name>
<enter name>
2. Introduction
2.1 Purpose of Document
This Report is used during RFP as part of contract and also n planning (i.e. Discovery Phase) of the
project.. The document should:
● Document Vendor and Client agreement about scope and planning
● Generated on RFP phase as v1.0
● Updated and freeze at the end of Discovery / Planning Phase
3. Project Objectives & Success Criteria
3.1 Project Objectives
< Insert text referring what is documented as on Project charter (this chapter should be 1:1
aligned with sponsor expectation) >
3.2 Key Success Criteria
< Insert text referring what is documented as on Project charter (i.e. successful implementation
for key interfaces>
Tom Mills 2 Procurement Protagonist
3.3 Project Constraints
< Insert text referring what is documented as on Project charter (i.e. out of maintenance
date for legacy system) >
3.4 Project Dependencies
< Insert text referring what is documented as on Project charter (i.e. dependency on
another vendor delivery for interfaces) >
3.5 Project Assumptions
< Insert text referring what is documented as on Project charter (i.e. ROI assumption for
Change Request bucket) >
4. Project Scope
4.1 Requirements Traceability Matrix
< If there is a change between RFP to Planning Phase, insert / embed the latest respond
from supplier to SoW as appendix >
4.2 Scope Inclusion List
< Insert breakdown of each scope element that will not be delivered by this vendor >
Scope Item Review Date Comments
High level item.1 – Level.1
Breakdown item.1 – Level.2
Breakdown item.1 – Level.2
4.3 Scope Exclusion list
< Insert breakdown of each scope element which will not be delivered by this vendor >
Scope Item Review Date Comments
High level item.1 – Level.1
Breakdown item.1 – Level.2
Breakdown item.1 – Level.2
5. Solution Overview
< Insert one page summary of system, separate environments agreed on contract by this
vendor >
Tom Mills 3 Procurement Protagonist
6. Delivery Plan
< Insert duration and phases of project agreed on contract by this vendor >
Tom Mills 4 Procurement Protagonist
7. Project Deliverables
7.1 Vendor Deliverables
< Insert the documents or deliverables (i.e. tasks) that needs to be provided by vendor >
Deliverable Description Acceptance Criteria Sign off Required
by :
7.2 Client Deliverables
< Insert the documents or deliverables (i.e. tasks) that needs to be provided by client >
Deliverable Description Acceptance Criteria Sign off Required
by :
8. Project Team and Role Definitions
8.1 Vendor
< Insert the roles agreed with vendor for this project >
Role Name Area of Responsibility
8.2 Client
< Insert the roles agreed with client for this project >
Role Name Area of Responsibility
9. Project Planning
9.1 Project Planning Approach
< Insert the process to finalized detailed planning (i.e. Discovery Phase steps, solution
documentation approval by client) >
9.2 Warranty and Service Model for Project
< Insert the vendor statement to support post go-live / hypercare phase related activities
until project is closed (i.e. 4 weeks hypercare support included) >
Tom Mills 5 Procurement Protagonist
9.3 Payment Milestones
< Insert the procurement plan reference (i.e. remuneration sheet, chapter on the
contract) or breakdown of milestone payments >
9.4 Project Budget
< Insert project budget approved by stakeholders>
10. Project Management
10.1 Project Management Methodology
< Insert the methodology or framework applicable for this project >
10.2 Governance
< Insert Steering committee contacts from vendor and client side >
10.3 Main Contacts
< Insert main contacts (i.e. Project Managers) from vendor and client side >
10.3 Escalation
< Insert escalation contacts (1st and 2nd level) from vendor and client side >
10.4 Project Meetings
< Insert communication plan or meeting structure for project >
10.5 Project Tools
< Insert the tools (e.g Sharepoint, MS Teams) will be used for this project>
10.6 Monitoring and Controlling
< Describe the process for controls over project (e.g. using MS Project file as main plan
between vendor and client to be updated weekly) >
10.7 Risk Management
< Describe the process for risk management (i.e. common RAID log between client and
vendor) >
10.8 Change Management
< Describe the process for change management (e.g. Freeze of solution and Change
Request approval process) >
Tom Mills 6 Procurement Protagonist
10.9 Project Reporting
< Insert the reporting structure and template for team reporting (i.e. Stream lead) and
steerco / board reporting >
11. Testing
11.1 Overview
< Describe the scope of testing (i.e. penetration tests included / excluded) in the vendor
delivery , responsibilities of vendor and client on testing (i.e. Test Manager to be provided by
client, UAT Plan is with Test Manager..) >
Note : If there is a “Test Strategy” document agreed between vendor and supplier, then
the following sections can be ignored and testing strategy can be used as reference in the
statement of work
11.2 Testing Stages
< Describe high level stages (i.e. Unit Testing, QA testing, UAT) and >
Test Stage Description Included in this Project? Responsibility
<Stage Name> <Yes or no> <Vendor or Client>
11.3 Testing Stages
< Describe high level stages (i.e. Unit Testing, QA testing, UAT) >
Test Stage Description Included in this Project? Responsibility
<Stage Name> <Yes or no> <Vendor or Client>
11.4 Acceptance Criteria
< Describe solution acceptance criteria (e.g.%97 test cases successfully executed) >
12. Handover to Operations
< Describe the process for handing over of project to operations. If there a maintenance
contract for operations, it should be referred on this chapter. (i.e. After 4 weeks of warranty
period by project team, project will be handed over to operations and xx maintenance contract
will be applicable after this milestone >
13. List of Open Topics
< Add the list of open topics on RFP and / or Planning phase >
14. Appendixes
< Please insert the documents related to this statement of work (e.g. product document,
project plan file) >
Tom Mills 7 Procurement Protagonist
