Description / Specifications / Statement of Work
Also known as: The SOW, PWS, SOO, or specification; the requirement
Your role here: Where you read exactly what the government wants
At a Glance
- Part
- Part I — The Schedule
- What it contains
- The SOW / PWS / SOO or specification — the actual work
- Forms it takes
- SOW (how), PWS (outcomes), SOO (objectives), or a spec
- You…
- Read it closely — it defines scope, and scope defines everything
- Governing authority
- FAR 15.204-2(c); FAR 11.101–11.106 (describing needs)
What It Is
Section C is where the government describes what it actually needs — the technical heart of the solicitation. Under FAR 15.204-2(c) it contains the description, specifications, or work statement: a Statement of Work (SOW) that prescribes how the work is done, a Performance Work Statement (PWS) that states the outcomes and lets the contractor propose the how, a Statement of Objectives (SOO) that gives only high-level goals and asks offerors to write the PWS, or a product specification. Everything else in the solicitation exists to buy, price, schedule, and administer whatever Section C describes. It defines the scope of the contract — the boundary between work you are paid to do and work that is 'out of scope' and therefore a change — so it is the section you read first and most carefully. A misread requirement in Section C leads to a bid that is priced wrong, a technical volume that answers the wrong question, or, after award, disputes about whether extra work is inside or outside the contract.
What’s In It
- The Statement of Work, Performance Work Statement, Statement of Objectives, or specification.
- The tasks, deliverables, and performance standards the contractor must meet.
- Applicable standards, references, and (in a PWS) the quality-assurance surveillance approach.
- The scope boundary — what is and is not included in the work.
- Often the definition of key terms and the government-furnished property or information.
What Goes Here
| Component | What It Means |
|---|---|
| SOW vs PWS vs SOO | A SOW tells you exactly how; a PWS states measurable outcomes and lets you choose the how; a SOO gives objectives and asks you to write the PWS yourself. Knowing which you have tells you how much of the solution you must design. |
| The scope boundary | Section C sets the line between in-scope work you are paid for and out-of-scope work that requires a modification. Read it to price correctly and to protect yourself from doing unpaid extra work later. |
| Performance standards | In a PWS the measurable standards (and any service-level metrics) are what your performance is judged against — and what feeds your CPARS past-performance rating. |
| Traceability to L and M | The requirements in Section C are what Section L asks you to address and what Section M evaluates. Map your proposal to Section C, tracked through L and M, or you will leave points on the table. |
What It Means for an SDVOSB
Section C is where an SDVOSB decides whether to bid at all. Read it against your real capabilities and past performance: if the SOW or PWS describes work you can genuinely self-perform to the degree the limitations on subcontracting require, it is a candidate; if the core of the scope is work you would have to subcontract out, the set-aside self-performance rules may make it a bad fit no matter how attractive the dollar value. During the market-research stage, a strong capability statement mapped to a draft Section C is also how you help the small business specialist and contracting officer justify an SDVOSB set-aside in the first place. After award, treat Section C as your shield: when a COR or program manager asks for work that is not in it, that is a potential out-of-scope change, and you should get a modification from the contracting officer before performing.
Watch Out For
- Skimming the SOW/PWS and pricing the wrong scope — the most expensive mistake in the whole solicitation.
- Missing the difference between a SOW, a PWS, and a SOO — a SOO expects you to write the work statement, which is a very different proposal effort.
- Ignoring the scope boundary — doing 'helpful' out-of-scope work on a COR's request without a modification means you may never be paid for it.
- Not tracing your proposal back to Section C through Sections L and M — evaluators score whether you addressed the requirement, not how hard you worked.
Run the Numbers
Frequently Asked
What is Section C of a solicitation?
Section C is the description, specifications, or statement of work part of a solicitation under FAR 15.204-2(c) — the technical heart that tells you what the government actually wants. It contains a Statement of Work (SOW), Performance Work Statement (PWS), Statement of Objectives (SOO), or a product specification. Section C defines the scope of the contract: the boundary between work you are paid to do and out-of-scope work that requires a modification. It is the section to read first, because everything else in the solicitation exists to buy, price, and administer what Section C describes.
What is the difference between a SOW, a PWS, and a SOO?
All three live in Section C. A Statement of Work (SOW) prescribes exactly how the work is to be done. A Performance Work Statement (PWS) states the required outcomes and measurable performance standards and lets the contractor propose how to achieve them (a performance-based approach under FAR Subpart 37.6). A Statement of Objectives (SOO) is the shortest — it gives only high-level objectives and asks offerors to write the PWS themselves as part of the proposal. Knowing which you have tells you how much of the solution you must design.
Primary Sources
- FAR 15.204-2 — Part I — The Schedule (Section C)
- FAR 11.101 — Order of precedence for requirements documents
- FAR Subpart 37.6 — Performance-based acquisition
Plain-English reference, not legal advice. The Uniform Contract Format is tailored by agencies, and the FAR sections that define it are amended from time to time — always read the actual solicitation and confirm each section against the official source before relying on it, and consult qualified counsel for your specific situation.
Change log (1)
- LaunchedPublished the federal solicitation sections reference covering the thirteen sections of the Uniform Contract Format under FAR 15.204 — Section A (the SF 33 / SF 1449 cover form), B (prices and CLINs), C (the statement of work / PWS / SOO), D (packaging and marking), E (inspection and acceptance), F (deliveries and period of performance), G (contract administration data and invoicing), H (special contract requirements), I (the FAR clauses, including the SDVOSB set-aside and limitations on subcontracting), J (the list of attachments and wage determinations), K (representations and certifications, where SDVOSB status is certified), L (instructions to offerors), and M (evaluation factors for award) — each with an at-a-glance quick-facts card, a what's-in-it list, a what-goes-here table, an SDVOSB-specific angle, watch-outs, FAQPage, Article, Dataset, and BreadcrumbList structured data, primary-source FAR citations, and cross-links into the glossary, how-to guides, forms, clauses, solicitation types, source-selection methods, FAQ, and the set-aside eligibility, win-probability, price-to-win, and limitations-on-subcontracting calculators.