I'm working on a couple of federal IT services proposals, specifically for NAICS 541519, and I've noticed some RFPs include a Statement of Objectives (SOO) while others have a Performance Work Statement (PWS). One recent solicitation for a software development effort had a SOO, giving us a lot of room to propose solutions. Another, for O&M services, came with a detailed PWS that felt very prescriptive. I understand both describe the work, but how does the choice between a SOO and a PWS impact my strategy for writing the technical volume? What are the key differences I should be looking for when I see one versus the other?
What is the difference between a Statement of Objectives (SOO) and a Performance Work Statement (PWS)?
Ask a question1 answer
A Performance Work Statement (PWS) describes the work in terms of required results, not how the work is to be performed, whereas a Statement of Objectives (SOO) provides the basic top-level objectives of the acquisition, allowing the contractor to propose the how, what, and where. The main difference for your technical volume strategy is the level of detail the government provides and, consequently, the level of detail you need to provide in your proposal. With a PWS, the government has already defined the outcomes and often outlines key performance indicators, so your technical volume will focus on demonstrating your ability to meet those specific requirements efficiently and effectively. For a SOO, your firm has more latitude to innovate and propose unique solutions to meet the stated objectives, requiring a more comprehensive and creative approach in your technical volume to articulate your proposed methodology and approach.