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

and/or data delivery requirements, a data item description number listed on the

CDRL may be cross-referenced in the SOW.

·   Specify technical proposal criteria or evaluation factors.

·   Establish a delivery schedule.  (May include significant milestones for clarity.)

·   Specify design control parameters or the performance of hardware because these items should be covered in a specification.

·   Impose on the contractor a Government format when a contractor format is acceptable.

·   Overspecify.  Specify only what is required and let the contractor establish the best method to fulfill the requirement.

·   Invoke in-house management instructions.

·   Use the SOW to establish or amend a specification.

·   Invoke handbooks, service regulations, technical orders, or any other document not specifically written according to DoD standards.  (Non-government documents excluded.)

3.6.5  Title Page and Table of Contents.  All SOWs should have a title page or cover that shows the SOW title, preparation date, procurement request number or contract number, revision number, date, and identity of the preparing organization (see Figure 3). A table of contents should be used when the SOW exceeds five pages (see Figure 4).

3.6.6  Paragraph Numbering and Identification.  Each paragraph and subparagraph should be numbered consecutively within each SOW Section using a period to separate the number representing each sublevel.  Paragraph numbering should be limited to the third sublevel, if possible, as shown in the following example for SOW Section 3:

Paragraph breakdowns should be kept to that level necessary to clearly define required contractor tasks.  Only one task should be provided in a numbered paragraph or sub paragraph to facilitate costing, referencing and tailoring of tasks.  Each paragraph and sub-paragraph should be titled.

10