AUXO INSIGHTS

 

We are excited to share insights and expert perspectives on navigating the intricate world of government acquisition! Our greatest passion is growing the government business base by making the processes and nuances of the government market more transparent. Whether you're a seasoned professional or just stepping into this realm, our aim is to equip you with the knowledge and strategies needed to excel. Stay tuned for thought-provoking discussions, practical tips, and best practices that will empower you to navigate the complexities of government procurement with confidence and success.

Have blog ideas or questions? Share with us in comments or via our contact form!  

 

What’s the difference between SOW, SOO, and PWS?

haley yeagley Jun 07, 2024

A lot of people use the terms Statement of Work (SOW), Statement of Objective (SOO), and Performance Work Statement (PWS) interchangeably, but they’re actually three different documents meant to serve different purposes. 

To better understand the rest of this discussion, here are some details about each: 

Statement of Work

  • Specific description of work to be accomplished
  • Not specifically discussed in the FAR but guidance can be found in MIL-HDBK-245E
  • Typically included as an attachment to a contract
  • Should specify in clear, concise, and understandable terms what work will be accomplished by the contractor in developing or producing the goods or services 
  • Should be prepared to satisfy particular requirements and define what is required in specific, quantitative terms
  • Standard format includes: Scope, Applicable Documents, Acronyms and Definitions, and Requirements however, it’s typically up to the PM or requirements owner what format and content is needed

Statement of Objective 

  • FAR 2.101 “a Government prepared document incorporated into the solicitation that states the overall performance objectives. It is used in solicitations when the Government intends to provide the maximum flexibility to each offeror to propose an innovative approach.” 
  • Top-level objectives, proposed scope of work, and includes performance metrics, desired outcomes, and measures
  • Should be included in a solicitation and used to prepare/refine a SOW
  • Can be used in advance of a PWS
  • Should be replaced in the contract with the SOW at contract award
  • SOO’s typically contain top level information including purpose, scope, period, place of performance or term, background, performance objectives, and any operating constraints

Performance Work Statement (PWS)

  • FAR 2.101 “a statement of work for performance-based acquisitions that describes the required results in clear, specific and objective terms with measurable outcomes.” 
  • Used for performance-based acquisition and focused on intended results, not processes
  • Should be written in such a manner that it’s focused on required results and not how the work is to be accomplished providing Contractor’s flexibility to determine “how”
  • Enables assessment of Contractor work against measurable standards
  • Like a SOO, typically used as part of a solicitation so that contractors know what standards to propose to

If you’ve worked with or within government acquisitions for any length of time like I have, there are a few things that likely jumped out at you in these descriptions.

If the government is supposed to be writing all three of these documents, then why was I, the contractor, asked to write it? 

 

This is a fair question, and I don’t have a good answer for you. Just know that it is not uncommon for an RFP to request a Contractor’s best attempt at a SOW. Then it’s negotiated, edited, and/or re-worked by both parties during contract negotiations.

Of note, asking a Contractor to write their own SOW is common in sole source environments or on direct sales. However, if the USG did this in a competitive environment, it would be an OCI issue and the company that wrote the SOW for them would likely be unallowed to compete for the subsequent award.

How do I know which one to expect?

The only thing you can be sure of is that a SOW in some form or fashion will be included in the contract. Otherwise, which documents you see during your contracting process are entirely up to the USG. It all depends on how they want Contractors to respond to a solicitation. For a Contractor, it’s just important to know the difference between all three documents so when you see them, you know their purpose. 

Why would the government use one type of document over another?

What type of document you see will depend entirely on what the USG is looking for from Contractors in response to a solicitation. Sometimes, the USG might not know exactly what they’re looking for or what they need. So, they’ll put out a top-level SOO in a solicitation and see how industry responds. From there, they’ll refine their requirements or needs and write a PWS to be included in a formal RFP. 

Alternatively, if the USG knows what they need but they’re more indifferent to “how” it’s provided, they may just go straight to a PWS in the solicitation. 

-------

Moral of the story, the Contractor does not determine the type of requirements document that the Government will use in an acquisition. However, it is beneficial for you to understand the purpose of each and when you’re likely to see them. Additionally, now you know that these are not interchangeable, these are three distinct documents, and should be referenced and discussed as such. 

Let us know your thoughts or questions!

Keep moving forward, 

Categories