SCOPE OF WORK

(SOW)
[PROJECT NAME]

Company Logo Goes Here

Revision 0.1

TABLE

OF

CONTENTS

Purpose............................................................................................................2
Revision History...............................................................................................2
Introduction/Background.................................................................................3
Scope of Work/Scope Statement......................................................................3
Period of Performance......................................................................................3
Key Project Activities........................................................................................3
Schedule/Milestones........................................................................................4
Project Approach & Resource Plan...................................................................4
Acceptance Criteria.........................................................................................5

Purpose
The Statement of Work (SOW) is a document that describes the scope of work
required to complete a specific project. It is a formal document and must be agreed
upon by all parties involved. In order to be effective, the SOW must contain an
appropriate level of detail so all parties clearly understand what work is required,
the duration of the work involved, what the deliverables are, and what is
acceptable.

Revision History
Revision
Date

Versio
n

Changes

INTRODUCTION/BACKGROUND
This section should provide a general description of the project as well as highlight
the projects background and what is to be gained by the project.

SCOPE

OF WORK/SCOPE STATEMENT
This section should provide a brief statement of what you expect to accomplish as a
result of this scope of work. This section should highlight what is and is not
included in the scope of the project in broader terms.

PERIOD

OF PERFORMANCE
This section should define the time period over which the project will occur. The
timeframe for the project can be pre-determined or based on a completion date to
coincide with some external requirement.

KEY PROJECT ACTIVITIES

This section should include a description of the actual tasks which the project will
require. This should include what tasks need to be completed in order for successful
completion of this project/contract. As with all other portions of the SOW, every
effort should be made to include as much detail as possible.

Project Initiation/Planning:
Design Phase:
Build Phase:
Testing:
Implementation Phase:
Transition and Close:

SCHEDULE/MILESTONES
This section should define the schedule of deliverables and milestones for this
project. It is imperative that all milestones, tasks, and schedule information are as
accurate as possible.
The below list an example of these milestones:

Milestones
RFP/SOW Release
Vendor Selection
Vendor Negotiation
Business/Functional Requirement
Design
Build/Unit Test
Integration Testing
System Testing
UAT
Cut-over
Project Completion Review
Project Closure/Archives Complete

End Date
January 2, 20xx
February 1-28,
20xx
March 1, 20xx
March 2, 20xx
August 31, 20xx
November 30, 20xx
December 31, 20xx
February 20, 20xx
February 25, 20xx
February 25, 20xx
February 25, 20xx
March 3, 20xx

PROJECT APPROACH & RESOURCE PLAN

This section will have an overview of how the work will be executed against and
what the identified resources are for the particular project. An outline of the team
roles and responsibilities should be included.

ACCEPTANCE CRITERIA
This section defines how the business will accept the deliverables resulting from this
SOW. The acceptance of deliverables must be clearly defined and understood by all
parties.

Executive Sponsor:
[Name]

[Title]

[Date]

[Name]

[Title]

[Date]

[Name]

[Title]

[Date]

[Name]

[Title]

[Date]

Stakeholders: