← Back to shelf

Desk reference

Sources sought, RFIs, RFQs, RFPs, IFBs, and SOW/PWS/SOO

Instrument vocabulary from through the operative — before a single page of proposal is written.

1 / 3

Sources sought, RFI, RFQ, RFP, and IFB

notices and support market research and planning; responses are not offers when the Government does not presently intend to award. An requests a quotation (and, depending on its terms, sometimes an offer). An requests proposals in a negotiated acquisition. An requests sealed bids evaluated without . Classify the notice before staffing a response — wait for each document’s instructions before deciding whether the agency expects capability data, a quote, a proposal, or a bid.

Watch for

Don’t treat every posted notice as a solicitation capable of immediate award. An RFQ response is not automatically a binding offer unless the instrument makes it one. An IFB is not an invitation to negotiate after bid opening.

2 / 3

Uniform Contract Format Sections L and M

Under the Uniform Contract Format for negotiated acquisitions, contains instructions, conditions, and notices to offerors or respondents; contains evaluation factors for award. Crosswalk every L instruction to the associated M factor, while also tracing requirements and terms in Sections C, H, I, and J. Build the from the operative solicitation’s instruction and evaluation sections — after confirming or an alternate structure.

Watch for

Don’t assume L and M are universal labels for every FAR buy. Non-UCF packages (including many vehicle orders) use different sectioning — follow that document’s map, not muscle memory from Part 15 UCF.

3 / 3

SOW, PWS, and SOO

A () typically specifies tasks and how work is to be done. A () emphasizes and measurable performance standards. A () states overall objectives and leaves maximum flexibility for offerors to propose an approach — often including an offeror-developed PWS. Match solution depth to the requirements shape: method-heavy for many SOWs, metrics-heavy for PWS, offeror-architected for SOO.

Watch for

Don’t call every requirements attachment a “SOW” and assume that makes it one. A SOO is not a detailed Government PWS. The solicitation’s instructions control which artifact the offeror must submit.

Further reading