Statement of objectives (SOO)

FAR 37.602(c) lets an agency issue a SOO in place of a PWS; offerors then write their own PWS inside the proposal, and the winner's version becomes part of the contract. The format is loose, but a SOO usually gives the purpose, scope, period and place of performance, background, operating constraints and objectives in a few pages. It is common in IT, research and development, and other work where the agency wants industry to shape the solution rather than price a fixed recipe.

What to check: how Section L wants the proposed PWS structured and how Section M will score it, the constraints that cannot be traded away (security, data, transition), and the risk that your PWS promises more than your price volume covers. A SOO rewards firms that know the mission and punishes a copy of the incumbent's approach.

What it is not: a statement of work. The government is asking what you would do, not telling you what to do.