Login

Fillable Printable Statement of Work Guide

Fillable Printable Statement of Work Guide

Statement of Work Guide

Statement of Work Guide

GUIDETO PREPARING A
STATEMENT OFWORK
State of Arizona
State ProcurementOffice
ABBREVIATED GUIDELINE FOR
PREPARING A STATEMENT OF WORK
A statement of work (SOW) is a narrativedescription of a contract’s goals/agenda. It is also
a valuable project management tool. The SOW is the key in the evaluation of proposals
received and contractor selection. After awardof a contract, the SOW becomes the standard
against which the State of Arizona (State) willmeasure a contractor’s performance. It
should set measurable limits as to what the State can demand and whata contractor must
perform in order tobe compensated. An SOW should include thefollowing sections:
I. Introduction/Background
II. Objectives
III. Scope
IV. Task Identification
V. Time Frames and Deliverables
The statement of work (SOW) describes the framework within which acontractor is
expected to operate — thatis, the work to be performed and/or the results tobe achieved).
The SOW normally consists of six sections:
I. Introduction/Background
II. Objectives
III. Scope
IV. Task Identification
V. Time Frames and Deliverables
INTRODUCTION/BACKGROUND
__This section identifies the need for this particular work, cites the contract’s goals,
describes the location of the work, and identifies how the contract workfits intothe
State’s mission and goals.
__This section should consist of no more than three to four paragraphs.
OBJECTIVES
__These are well-defined statements of the results to be achievedin order for the overall
mission of the work tobe accomplished.
__The objectives should be quantifiable criteria that must be met for the work tobe
considered successful.
SCOPE OF WORK
__This section brieflystates what the scope of work does and does not cover. The scope of
work paragraph should be limited to whatis necessary to convey the intent of the
contract.
__Itincludes an outline of theextent of the work, a briefoverview of the steps of the
project, a brief descriptionof the methodology to be used, and a description of the
location of the work.
TASK IDENTIFICATION
__Tasks are activities and milestones that need to be completed to accomplish the contract
objectives. Tasks can bestructured bymilestones, deliverables, or processes.
__Include the following in this section:
__A clear delineation of responsibilities
__A detailed description of each work element
__The approach or methodology
__Timelines anddeliverable requirements with each task description
__State support in terms of equipment,staffing, computers, software, or
subcontractors, as applicable
__A clear description of any specific equipment or software compatibility requirements
__Identification ofdocumentation that must be followed or used as guidelines
__Clear instruction of contract phasing or sequencing, if necessary
TIME FRAMESAND DELIVERABLES
__Specify time frames as they apply tocompletion of tasks, milestones, and/or completion
of the entire contract.
__State what the contractor is responsible fordelivering during the course of the workand
at the end of the project,as applicable.
__Deliverables should:
__Be specific
__Have clear instructions regarding their submission
__Clearly define themanner in which the State will determine if theyare acceptable
PREPARING A STATEMENT OF WORK
The SOW describes thebasic framework withinwhich a contractor is expected to operate,
that is, the work to be performedand/or the results tobe achieved. It shouldinclude
information on the relationship to the programit supports anda summary of the statutory
and regulatory requirements that pertain to the work. The SOW is intended to act as a
baseline for resolvingquestions of interpretation about the scope of thework in the final,
negotiated contract. It is intended to supplement, rather than to duplicate a contract. An
SOW should clearlyreflect what the State expects the contractor to accomplish. Themore
specifically tasks are delineated; the more accurately the cost of a proposed contract can be
estimated. Poorly draftedSOWs can lead toconfusion aboutexpected performance,
unnecessary disputes or litigation, cost overruns, delays, or deteriorating relations between
the public and private sectors.
The objectives of a well-defined SOW will
1. Provide precise andclear definition of all deliverable items
2. Employ cost-effectivecontracting measures
3. Establish contract requirements
4. Provide clear guidelines for both the State and the contractor
5. Provide criteria bywhich to inspect and accept deliverables
6. Develop performance standards for thecontracting parties
7. Provide for uniform technical requirements
8. Ensure consistent quality output
9. Provide for and promote safety
10. Assure that the contractor can be compensated on time and fully for acceptable
deliverables
11. Develop realistictime frames, tasks, and deliverables
The components of an SOW are described in the next section. In general,a well-prepared
SOW should provide answers to the followingsummary questions:
__Why — (Introduction/Background)
__Where, What If— (Scope of Work)
__How — (Tasks Identification)
__Who — Responsibilities of the parties (Task Identification)
__When — Time frames, deadlines (Timeframesand Deliverables)
__What — Outputs, deliverables (Timeframesand Deliverables)
I. INTRODUCTION/BACKGROUND
The introduction explains how this contract fitsinto the State’smissionand goals and
describes the location of the work. The introductionprovides a brief historical description
of events leading to the current need(s) and setsthe stage for the subsequent explanation of
what the State requires in terms of performance. The background section defines why the
contract is being pursued and theparticular need of the State.
The introduction should be no more than three or fourparagraphs and shouldprovide the
following information:
__The need for thisparticular work, including a description of events leading to this need
— that is, why the contract is being pursued and the particular need ofthe State — and
a description of how the work relates to other on-going or future work at the State or in
conjunction with other governmental entities or non-profit organizations.
__The contract’s goalsand the relationship of the contract goals as they relate to the State’s
project/program goals.
__A description of how the work relates tothe State’s missions andpriorities.
__The legal basis for the statement of work — referencinglegislation, legal requirements,
or State policy.
__Key terms that will be referenced throughout the statement of work, e.g., minimum
flows and levels, Indian River Lagoon, and surface water improvementand
management, as well asa general description of the work location.
__Include any additional backgroundinformation that would be useful in understanding
the nature of the proposedcontract.
II. OBJECTIVES
Objectives are well-defined statements of the results to be achievedin order for the overall
mission of the work tobe accomplished. In other words, work objectives are the
quantifiable criteria thatmust be met for the work to be considered successful. This section
must communicate a concise description of work objectives and how those objectives
interrelate.
The following acronymcan be used to remember the essentials that characterize a
statement of objectives. A work objective mustbeSMART:
Specific
Measurable
Attainable
Realistic
Time-limited
Following are examples of contract objectives:
1. The objective of this study is to obtain information defining the relationship between parameters
X, Y, and Z.
2. The objective is to develop and implement a cost-effective project control system that would track
and measure theperformanceof projects with respect to their schedule and budget, by December
31, 2001.
3. The objective of this work is to develop training materials in the areaof Managing Teams and to
train supervisory personnel by December30, 2001.
4. The objective of this contract is toprocure120 10-mile-range radiounits foruse in government
vehicles.
5. The purpose of this work is to develop, mail, analyze, and interpret the results from a
questionnaire/survey to 10,000 residences to measure the residentsperception regarding the
quality of the water inthe city of Palatka.
6. The objective of this work is to undertake a feasibility study to determine thetechnical and
economical feasibility ofa 4-day workweek by December 31, 2001.
III. SCOPE OF WORK
Since the amount of work involved is directly connected to the contract’s scope, scope
management is arguably the single most importantcontract management activityin terms
of achieving time and cost targets.
The scope of workis a small part of the overallSOW. The scope section brieflystates what
the SOW does and does not cover. The scope paragraphdefines the breadth and limitations
of the workto be performed — not how to do it. The informationcontained in the scope
should be limited to onlywhat is necessary to convey the intent of the contract. For
instance; the following elements should be inthe Task section andnot in the Scope section:
1. Directions to the contractor to perform work tasks
2. Contract specifications or data requirements
3. Detailed description of deliverable products
Consideration of the contract’s scope is an important step in developingthe contract
documents. The scopesection of the SOW will be used to determine whether additional
work is “in or out” of scope. Out-of-scope requirements require aseparate contract action.
The scope section should include the following:
__An outline of the extent of the work envisioned
__A brief overview of the steps, tasks, and/or phases of the project
__A brief description of the approach or methodology to beused
__A brief description of the locationof the work. Adetailed legal description of the
property may be required and, in somecases, itwill be necessary to include a map
showing more detailed site location(s)
__Any pivotal decisionpoints following completion of a task or phase (e.g., ‘stop/go.’ Is it
cost effective? Was the result of the initial study successful? Does the State have the
appropriate authority, e.g. permits, easements?).
__Identification ofwork thatis not encompassed in the scope and which may need
clarification. Examplesof this are:
1. Contractor providessample collection; State provideslab.
2. State provides pumps; contractor installs pumps.
3. Should contractor encounter hazardous waste on the project site, the State will be responsible
for removal and any remediation necessary.
IV. TASK IDENTIFICATION
Tasks are the activitiesand milestones that need to be completed to accomplish the contract
objectives. Tasks are anarrative description of the spectrum of servicesto be rendered or
work to be performed. Tasks can be structured by milestones, deliverables, or processes.
Clear definition of the tasks is a must in orderto reduce scopecreep. Following are some
specific guidelines andexamples:
__Define the range of contractor activities, beginning the following tasks with the phrase
“All work required to…”:
1. Design, sampleand test
2. Develop, manufacture, and field test
3. Test and evaluate
4. Collect and analyze
__Define all detailedtechnical requirements thatare required in the delivered product or
service.
__Categorize requirements (reporting, documentation, survey, design,etc.):
1. The survey shall includea minimum of10,000 households.
2. Analysis shall be made to determine the statistical relationship betweenX, Y, and Z, etc.
3. The radio shall operate in the temperaturerange of –20 to +60 degreescentigrade.
__Use a standardformatting system, for example, Construction Specifications Institute
(CSI), Engineers Joint Contract Documents Committee (EJCDC), etc., if applicable. If not,
the followingitems shouldbe considered inpreparing thissection:
1. Tasks (subtasks/project specific details, define themajor tasks in such a way that the sequence
allows for progressmeasurement and easily measured task costs)
2. Design Details, permits, etc.
3. Quality Assurance/ Control(e.g., QAPP, CIAP,EPA study)
1. A growth or change inyour project which happens while you’re developing thestatement of
work. It typically involves adding ormodifying featuresas the design evolves.
2. The migration of a project froma budget, schedule, or defined plan to a slowly expanding
sourceofconflict, confusion, and additional costs.
3. A term architectsand engineersuse for the tendency of projects to grow, expand, or swell
beyond theoriginal intent.
__Scope Creep
Login to HandyPDF
Tips: Editig or filling the file you need via PC is much more easier!
By logging in, you indicate that you have read and agree our Terms and Privacy Policy.