Statement of Work (SOW)

A Statement of Work (SOW) is the contractual document that defines the specific tasks, deliverables, timeline, and milestones a recipient must complete under a sponsored research contract, industry-funded research agreement, or subaward. It is usually drafted as a discrete exhibit or attachment — “Exhibit A: Statement of Work” — and incorporated by reference into the governing agreement, so that changes to the work itself are made by amending the SOW rather than renegotiating the whole contract.

What a SOW specifies

A well-drafted research SOW typically covers:

• Scope and objectives — the boundaries of the work to be performed, stated in operational terms.
• Tasks — the discrete units of work, often numbered (Task 1, Task 2…) and sometimes broken into subtasks.
• Deliverables — the tangible outputs tied to each task: reports, datasets, prototypes, assay results, software, or other work product.
• Timeline and period of performance — start and end dates for the overall effort and, often, for individual tasks.
• Milestones — checkpoints (which may also gate payment tranches) marking task completion or go/no-go decision points.
• Reporting requirements — the frequency and format of progress reporting tied to the SOW’s task structure.

In U.S. federal contracting specifically, statements of work are addressed within the Federal Acquisition Regulation (FAR) — most directly FAR Part 37 (service contracting) for the drafting standard that requirements be stated in clear, specific, measurable terms, with FAR Part 35 governing research and development contracting more broadly. A federal SOW for an R&D contract typically frames tasks around research objectives, methodology, and expected deliverables such as reports, datasets, or prototypes, rather than the fixed-quantity production tasks typical of a services or supply contract.

SOW vs. Specific Aims: contract, not narrative

Research administrators frequently field the question of how a SOW differs from a grant proposal’s Specific Aims (or Research Strategy) section, because both documents describe “what the researcher is going to do.” The distinction is legal, not just stylistic:

• A Specific Aims page is persuasive scientific writing. It argues the rationale, hypotheses, and significance of proposed research to a funding agency or peer-review panel, and its purpose is to win the award on scientific merit. It is not itself a binding performance obligation — a funder does not sue an investigator for failing to fully achieve Aim 2.
• A SOW is a binding contractual specification. Its tasks and deliverables are what the parties monitor performance against, and in a true contract (as opposed to a grant), failure to deliver can trigger contractual remedies — withheld payment, cure notices, or termination for default — not just a progress-report conversation.

This distinction tracks the underlying instrument. Research funded through a grant or cooperative agreement is typically scoped by Specific Aims or a similarly narrative research plan; research funded through a procurement contract, an industry-sponsored research agreement, or a subaward that flows down prime-contract terms is typically scoped by a SOW. (For a broader look at how these instruments differ, see Grant vs. Contract vs. Cooperative Agreement.) Some awards use both: a federal cooperative agreement may reference the applicant’s Specific Aims for scientific framing while a separate SOW-like task schedule governs reporting and milestone deliverables, particularly on multi-site or milestone-driven mechanisms.

Where SOWs show up in research administration

Research administrators encounter SOWs most often in:

• Industry-sponsored research agreements, where the sponsor’s legal and technical teams negotiate SOW language directly with the institution, often iteratively, before the agreement is executed.
• Subaward agreements (see how subaward negotiation works), where the subrecipient’s SOW is incorporated per the pass-through entity’s obligations under 2 CFR 200.331/200.332 and becomes the basis for monitoring subrecipient performance.
• Federal procurement contracts (as distinct from grants or cooperative agreements), where FAR-based SOW or Performance Work Statement (PWS) language governs the entire relationship.
• Amendments and change orders, where scope creep or redirected research is formally handled by amending the SOW rather than the base agreement — a discipline that keeps contract administration auditable.

Because a SOW carries contractual weight, research offices typically route SOW language through both the scientific PI (for technical accuracy and feasibility) and sponsored-programs or contracts staff (for enforceability, IP, and reporting-obligation review) before execution — unlike a Specific Aims page, which is primarily a scientific-writing exercise reviewed by the PI and mentors.