Requirements Definition
Also known as: Statement of work, PWS, SOO, performance work statement, requirements documents
Your role here: Understand the SOW/PWS so your proposal answers exactly what is asked
At a Glance
- Phase
- 3 of 10 — the need becomes a written requirement
- Who leads it
- The program office / requiring activity, with the contracting officer
- What happens
- The need is written as an SOW, PWS, or SOO with specs and a delivery schedule
- You…
- Study the requirement documents — they become Section C of the solicitation
- Governing authority
- FAR Part 11 (Describing Agency Needs); FAR Subpart 37.6 (Performance-Based)
What It Is
Requirements definition is where the agency converts its need into the documents an offeror will actually be measured against. Under FAR Part 11 agencies must describe their needs in a manner that promotes full and open competition — favoring performance-oriented and commercial descriptions and restricting requirements to the agency's actual minimum needs. The core products are the work description: a Statement of Work (SOW) that spells out the tasks, a Performance Work Statement (PWS) that states the outcomes and measurable performance standards under the performance-based approach of FAR Subpart 37.6, or a Statement of Objectives (SOO) that states high-level goals and asks offerors to propose their own PWS. Alongside it come the specifications and standards, the deliverables and delivery/period-of-performance schedule, and any government-furnished property. These documents become Section C of the eventual solicitation, and the evaluation factors in Section M are written to test whether a proposal meets them — so reading and understanding the requirement is the foundation of a responsive, winning offer.
What Happens
- The requiring activity drafts the SOW, PWS, or SOO describing the work or outcomes.
- Specifications, standards, and applicable regulations are identified and, where possible, stated in performance terms.
- Deliverables, the delivery schedule, and the period of performance are set.
- Government-furnished property, security, and any special requirements are documented.
- The requirement package is finalized and folded into the solicitation as Section C (and related sections).
Key Activities
| Activity | What It Means |
|---|---|
| Write the SOW / PWS / SOO | The heart of the requirement. A PWS states measurable outcomes; an SOO asks you to propose your own approach — each changes how you write your technical proposal. |
| Set specifications and standards | FAR Part 11 favors performance and commercial standards limited to the government's minimum needs, which keeps competition open to capable small firms. |
| Fix the schedule and deliverables | The period of performance and deliverable list define what you are committing to and drive your staffing and price. |
| Identify special requirements | Security clearances, certifications, key personnel, and government-furnished property are set here and can be pass/fail gates in evaluation. |
What It Means for an SDVOSB
The requirement documents are the rulebook for the work, and reading them closely is where a disciplined SDVOSB pulls ahead. A PWS with measurable standards tells you exactly what the government will inspect and accept; an SOO invites you to show your expertise by proposing the approach. Either way, your technical proposal must answer the requirement point by point — unaddressed requirements become weaknesses or deficiencies in evaluation. Requirements definition is also where the limitations on subcontracting start to bite: read the scope and decide early how much of the work your firm will self-perform, because on a set-aside you (plus any similarly situated subcontractors) must perform at least the required percentage. If a specification looks unnecessarily restrictive of small-business competition, that is a point to raise with the contracting officer or the SBA procurement center representative before the solicitation closes.
What to Do in This Phase
- Read the SOW/PWS/SOO line by line and map every task and standard to a section of your proposal.
- Identify the deliverables, period of performance, and any key-personnel or clearance gates early.
- Decide your self-performance plan against the limitations on subcontracting before you price the work.
- Flag any unduly restrictive specification to the CO or the SBA procurement center representative during the question period.
Watch Out For
- Skimming the requirement and writing a generic proposal that does not track the actual SOW/PWS tasks and standards.
- Missing a mandatory qualification (a clearance, certification, or key-personnel requirement) that is a pass/fail gate.
- Building a delivery plan that quietly relies on more subcontracting than the limitations on subcontracting allow.
Run the Numbers
Frequently Asked
What is the difference between an SOW, a PWS, and an SOO?
All three describe the work, but they differ in who defines the 'how'. A Statement of Work (SOW) prescribes the specific tasks and how the work is to be performed. A Performance Work Statement (PWS), used in performance-based acquisition under FAR Subpart 37.6, states the required outcomes and measurable performance standards but leaves the method to the contractor. A Statement of Objectives (SOO) goes further and states only the high-level objectives, asking offerors to propose their own PWS and approach. The more the document leans toward outcomes (PWS) or objectives (SOO), the more your technical approach — and your expertise — becomes a discriminator.
Can I challenge a specification that seems to shut out small businesses?
Yes, through the proper channels and on time. If a specification or requirement appears unnecessarily restrictive of competition, you can raise it with the contracting officer during the solicitation's question-and-answer period, and you can ask the SBA procurement center representative to weigh in, since the PCR's job includes advocating for small-business participation. If the restriction is a genuine defect apparent on the face of the solicitation, a pre-award protest challenging the terms must generally be filed before the deadline for receipt of proposals — waiting until after award to complain about an obvious solicitation defect is usually too late.
Primary Sources
- FAR 11.002 — Policy (describing agency needs)
- FAR 11.101 — Order of precedence for requirements documents
- FAR 37.602 — Performance work statement
Plain-English reference, not legal advice. The phases of a federal acquisition are tailored to each buy, and the FAR is amended from time to time — always read the actual solicitation and confirm the applicable procedures with the contracting officer, and consult qualified counsel for your specific situation before relying on this.
Change log (1)
- LaunchedPublished the federal acquisition lifecycle phases reference covering the ten phases a federal contract moves through — acquisition planning (FAR Subpart 7.1), market research (FAR Part 10), requirements definition (FAR Part 11 / 37.6), the set-aside decision and the rule of two (FAR Subpart 19.5 / 19.1405 / 19.1406), the synopsis and solicitation (FAR Part 5 / Parts 12–15), proposal preparation and submission (FAR 15.208), evaluation and source selection (FAR Subpart 15.3), award and debriefing (FAR Subpart 15.5 / Part 33), contract administration (FAR Part 42), and contract closeout (FAR Subpart 4.8) — each with an at-a-glance quick-facts card, a what-happens list, a key-activities table, an SDVOSB-specific angle, a what-to-do checklist, watch-outs, FAQPage, Article, Dataset, and BreadcrumbList structured data, primary-source FAR citations, and cross-links into the glossary, how-to guides, FAQ, solicitation types, source-selection methods, roles, forms, clauses, protest forums, and the set-aside eligibility, size-standard, win-probability, price-to-win, limitations-on-subcontracting, and subcontracting-goal calculators.