Guidance for the Development of Statement Of Objectives (SOO)


The Statement of Objectives (SOO) provides basic, top-level objectives of an acquisition and is provided in the request for proposal (RFP) in lieu of a government-written statement of work (SOW). It provides potential offerors the flexibility to develop cost-effective solutions and the opportunity to propose innovative alternatives meeting the objectives.


  1. The SOO should be compatible with the mission need statement, operational requirement document, program management directive, acquisition strategy, technical requirements documents or specifications, and the preliminary contract work breakdown structure (CWBS).
  2. The SOO should address product oriented goals as opposed to performance oriented requirements and should not exceed 4 pages as a goal.
  3. The SOO itself is typically appended to Part L of the RFP (Instructions, Conditions and Notices to Offerors). It does not become part of the contract.
  4. The SOO is used by the offerors to develop a SOW, Contract Work Breakdown Structure (CWBS) Integrated Master Plan (IMP), Integrated Master Schedule (IMS) and other documents required by the RFP. Section L should include instructions requiring all offerors to address all aspects of the SOO in their proposal.
  5. The SOO can be used for new training systems acquisition contracts or for modifications to existing training system acquisition contracts.
  6. The SOO can be used for both services and supply type contracts.


This document is intended for Integrated Product Teams (IPTs) to assist in identifying objectives that will be applicable to the acquisition of training systems. The document provides a suggested format to assist in organizing the objectives and a shopping list of generic objectives that can be used as applicable. The objectives listed here are meant to be demonstrative and are not all-inclusive, many programs are unique and will have objectives not identified here. As experience is gained with the use of the SOO document, more generic objectives will be added to this document.


The key to a successful SOO is the separation of requirements from objectives. Requirements should be identified in a separate document such as the Training System Requirements Document (TSRD), Training System Functional Description (TSFD), System Requirements Document (SRD), or Performance Specification.

Within these documents are identified conditions and constraints that must be incorporated into the training system program. This might include such things as where the training system must be located, details about the facility it will be in, the use of an existing visual system that must be incorporated, a required minimum student throughput, a required availability of the system, etc. The SOO approach allows contractors the maximum flexibility in their design approach, but there are almost always some conditions and constraints that must be accommodated in the design.

Suggested Format

Guidance and Generic Objectives for each Section

Last Update: 20 March 2013