MIL-HDBK-245 Preparation Of Statement Of Work SowThis handbook applies to the preparation of Statements of Work SOWs for projects and programs that have deliverables and /or services performed. It is written to implement the acquisition policies established in DODD 5000.1. It covers the preparation of SOWs which correlate to the acquisition such as DoDI 5000.2. This handbook is for SOWs in DoD solicitations and contracts and covers work requirements , in conjunction with applicable performance/design requirements contained in specifications, but also data deliverables contained in Contract Data Requirements Lists CDRLs. The Federal Acquisition Regulations FAR and Defense Federal Acquisition Regulation Supplements DFARS discuss the essentiality of the SOW for sound contracting. Ab offeror submits a proposal based on his perception of the Governments needs as defined in the RFP.

Pages 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16 - 17 - 18 - 19 - 20 - 21 - 22 - 23 - 24 - 25 - 26 - 27 - 28 - 29 - 30 - 31 - 32 - 33 - 34 - 35 - 36 - 37 - 38 - 39 - 40 - 41 - 42 - 43 - 44 - 45 - 46 - 47 - 48 - 49 - 50 - 51 - 52 - 53

MIL-HDBK-245D

3.6.2  SOW Section 2 - Applicable Documents.  Military handbooks, government instructions, service regulations, technical orders, and policy letters, as a type, are not written in language suitable for contract application.  In the event requirements of these documents must be included in a SOW, excerpts only should be used and should be made into either a clear task statement or a clear reference statement for guidance only, and not for contract compliance.  Any documents called out in Section 2 of the SOW should have the specific version referenced, i.e. by date or by revision letter.

The SOW writer should refer to DFARS 252.211-7000 with respect to referenced documents and begin with a zero base situation.   The requirement for any specification and standard should be justified before being placed in Section 2 of the SOW.  Therefore, Section 2 should not be

prepared until the draft of the requirements Section, Section 3, is complete.  Sections 2 and 3 are reciprocal.  Documents invoked by specific reference in Section 3 of the SOW must be identified and listed in Section 2.  When invoked in Section 3 of the SOW, the application should be tailored to invoke only those minimum requirements from the document which are absolutely necessary for program success as described in MIL-HDBK-248.  The applicability of each document listed in Section 2 of the SOW should be specified in Section 3 and identify only that portion needed to perform the work.  Improper document referencing (e.g., blanket imposition) was often a major cost driver since total compliance with a document listed in Section 2 of the SOW was implied unless Section 3 specified otherwise.

3.6.3  SOW Section 3 - Requirements.  Specific work tasks are called for in SOW Section 3 (see Appendix D).  These tasks, developed to satisfy program needs, are essentially the contractor work requirements.  Although the Source  Selection Evaluation Board (SSEB) is responsible for the examination of SOW requirements in order to eliminate nonessential requirements, such examinations may be accomplished by the functional technical groups during development of the SOW.  A well-written SOW has the following attributes:

a.  Specifies requirements clearly to permit the government and offerors to estimate the probable cost and the offeror to determine the levels of expertise, manpower, and other resources needed to accomplish the task.

b.  States the specific duties of the contractor in such a way that the contractor knows what is required and can complete all tasks to the satisfaction of the contract administration office.

c.  Written so specifically that there is no question of whether the contractor is obligated to perform specific tasks.

d.  References only the absolute minimum applicable specifications and standards needed. Selectively invokes documents only to the extent required to satisfy the existing requirements.

8