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

FOREWORD

1. This handbook is approved for use by all Departments and Agencies of the

Department of Defense.

2. This handbook is for guidance only and cannot be cited as a requirement in any DoD contract.  Contractors may, at their option, utilize this document for guidance in preparing responses to Government requests for proposals.

3. This handbook provides guidance to enable personnel to create a completed contract Statement Of Work (SOW) applicable to any material acquisition life-cycle phase.  It also covers the SOW preparation for non-personal services contracts.

4. Modern weapon systems have traditionally contained many more specifications and greater detailed SOWs than those of the past.  Contrast the Army Signal Corps SOW for the Wright Brothers' heavier-than-air flying machine in 1908 to the Air Force SOW for the Advanced Tactical Fighter in 1986.  Requirements in the 1908 SOW (e.g., be easily taken apart for transport in Army wagons and be capable of being reassembled for operation in an hour, carry 350 pounds for 125 miles, and maintain 40 miles per hours in still air) and other contract conditions were specified on one page.  The requirements section in the 1986 SOW for the Air Force Advanced Tactical Fighter is 85 pages long with 300 paragraphs of requirements.  Today's SOWs are much more complex requiring greater attention to detail.

5. The handbook is organized so that the SOW writer after reviewing Section 3, General Description, can proceed to that portion of Section 4, Detailed Requirements, that pertains to the type of SOW required.  Each portion of Section 4 has detailed instructions on the specific requirements for each type of SOW tailored to specific needs.  The specific instructions provide techniques for defining task elements, and a method for organizing these elements into a comprehensive SOW. Sample outlines and significant DO's and DONT's are provided.

6. The tendency of SOW writers is to include requirements which belong in other parts of a government contract.  Contract requirements should be specified in Sections A - M and should not be restated in other parts of the contract. Quantitative technical requirements should be specified in the specification and not be restated in other parts of the contract.  Work requirements should be specified in the SOW, and all data requirements for delivery, format, and content should be in the Contract Data Requirements List (CDRL) in conjunction with the appropriate Data Item Description (DID) respectively, with none of the requirements restated in other parts of the contract.  Redundancy invites conflict.

7.  This handbook provides guidance, following DoD direction, that will enable SOW writers to rely on commercial contracting practices.  The new SOW will specify what tasks need to be accomplished but leave "how to" accomplish those tasks up to the contractor.

ii