A Statement of Work is the contract document that defines the scope, deliverables, schedule, price, and acceptance process for a single engagement under a parent agreement. Executed SOWs drawn from institutional procurement records name an approver for every deliverable, state how long that approver has to review it, state what silence means, and state what a rejection triggers; a generic template typically carries a Deliverables section with a due date and nothing further. This guide examines five public-record SOWs, a federal task order, a NATO framework agreement, a state-agency call-center contract, a state IT template, and a university consulting engagement, and identifies the clauses a template leaves out.
A Statement of Work is the contract instrument that specifies the work to be performed on a single engagement: its scope, deliverables, schedule, price, personnel, and the process by which each deliverable is accepted. A blank template supplies section headings and bracketed placeholders; what it commonly omits are the clauses that resolve a later disagreement over whether a deliverable was completed, when the client considers it unfinished and the consultant considers it delivered.
Executed SOWs, the kind institutions negotiated, signed, and operated under, show what those clauses look like in practice. Five are examined here, all drawn from public procurement or public-institution records: a Department of Homeland Security compliance-support task order, a NATO framework agreement for an enterprise software rollout, a Texas state agency's call-center contract with Accenture, the Commonwealth of Virginia's standing SOW template, and a Deloitte consulting engagement with a public university. Each was written for a different register of client and a different scale of engagement. Together they show the same handful of structural moves, repeated at every scale, that a downloaded template almost never includes.
Five real SOWs, five registers
Before comparing clauses, it helps to see how differently these five documents are built. The register a SOW is written in, not just its content, tells a reader what kind of engagement it governs.
| Source | Register | What it governs |
|---|---|---|
| DHS S&T OCIO | Federal task-order narrative | Information Assurance Compliance Support Services, a labor-category-driven support contract inside DHS's Science and Technology Directorate. |
| NATO NSPA | Framework outline-agreement, multi-annex | A multi-year SAP S/4HANA consultancy arrangement that spawns individual task-order SOWs over its term. |
| Accenture / Texas Workforce Commission | Commercial schedule-based | An on-call staffing and call-center services contract, expanded during the pandemic unemployment surge. |
| Virginia VITA | Fill-in-the-blank consulting template | The Commonwealth's standing SOW template, issued as Attachment A to its Master Services Agreement for any qualifying vendor engagement. |
| Deloitte / University of Cincinnati | Commercial schedule-based, MSA-anchored | A CampusConnect systems-implementation engagement under a standing consulting Master Service Agreement. |
The federal task order: DHS's compliance-support SOW
DHS's Office of the Chief Information Officer issued a Statement of Work in 2022 (RFQ 70RSAT22Q00000040, Attachment I) to support the Information Assurance Compliance function inside its Science and Technology Directorate. Its scope statement is two sentences: "The scope of work is to support the Information Assurance Compliance function within S&T OCIO. This contract is limited to S&T staffing only." The first sentence describes the work; the second states a boundary, a limitation a template typically omits.
The requirements section is a list of bulleted "shall" statements, one obligation per bullet, each independently checkable, for example: "Conducting vulnerability assessments and penetration testing... Respond to vulnerability issues within 5 Calendar days of occurrence." A bundled paragraph mixing three obligations is unauditable later, because nobody can tell which part was missed. A bulleted, single-obligation "shall" statement can be graded pass or fail on its own.
The personnel section adds a gate most compliance-consulting SOWs never need but every government one does: no unescorted access to a facility or system before a favorable suitability determination, with named rules for limited escorted access in the gap, and 14 days' advance notice before a named Key Person can be swapped out, with the replacement required to hold qualifications equal to or better than the person leaving.
The framework agreement: NATO's SAP S/4HANA consultancy SOW
The NATO Support and Procurement Agency's 2021 Statement of Work for SAP S/4HANA consultancy services, released to bidders inside a competitive tender and marked NATO UNCLASSIFIED, is built for a different problem: a multi-year outline agreement that will spawn many individual task-order SOWs, not one project with one end date. The core document is short. Nearly all of its content lives in six numbered annexes carrying the staffing tables, pricing tables, and reference worksheets that a bidder has to submit.
Two disciplines stand out. First, a stated interpretation key up front: "'Shall' statements are contractually binding. 'Should' and 'may' statements are non-mandatory provisions. 'Will' statements are non-mandatory, or imply intent... or are future tense." Without that key, a sentence like "the Contractor should provide weekly reports" is unenforceable, and nobody notices until the reports stop. Second, a seniority-tiered staffing table (Senior vs. Junior, cross-tabbed by years of platform experience, years of adjacent experience, education, and certification) plus a security-clearance phasing schedule requiring 6 of 50 proposed consultants to already hold NATO Secret clearance at bid time, with the rest phased in against named milestone dates. A framework agreement this size cannot leave staffing quality to a one-line resume requirement.
The enterprise commercial contract: Accenture and the Texas Workforce Commission
Accenture State Healthcare Services' on-call Master Services Agreement and SOW Number One with the Texas Workforce Commission, a Texas Public Information Act record, staffed and ran unemployment call-center operations during the 2020 surge. Two of its mechanics are transferable to engagements of any scale.
The first is a hard ceiling stated regardless of how the work is billed: "shall not exceed $7,000,000.00... [Vendor] shall have no obligation to perform services that would generate invoice amounts in excess of this amount absent an amendment." Most of that contract is billed on staffed hourly rates, not fixed price, but the Not-to-Exceed cap applies anyway, as a drafting discipline independent of the billing method. The cap bounds total billing on a staffing arrangement that is otherwise open-ended.
The second is a defined Service Level table with real numerator/denominator math: Average Handle Time (talk plus hold plus after-call work, divided by calls handled, target 10 minutes or less), CSR Occupancy Rate (handle time divided by paid staff time excluding training, target 65 percent or higher), and Average Speed of Answer (total queue wait time divided by calls answered, target 30 minutes or less), each with a measurement window and a ramp-up grace period before it starts binding. A Service Level carries no enforcement weight unless a financial consequence attaches to it; this contract ties each metric to a credit schedule, and pairs the billable headcount with a stated supervision ratio (one Team Lead per 25 agents, billed separately).
The state template: Virginia's VITA SOW
The Commonwealth of Virginia's VITA Statement of Work Template (Attachment A to its Master Services Agreement, Contract No. VA-160720-TEMP) is the fill-in-the-blank register, meant to stand up a new engagement without a prior contract vehicle to hang off of. Two of its mechanics are worth copying into any consulting SOW.
First, the order-of-precedence clause is stated plainly instead of left implied: "no term of this SOW may conflict with or undermine the integrity of the terms and conditions of the MSA." The parent agreement controls, and the template says so in one sentence rather than leaving the relationship to be argued later. Second, its Key Personnel table pins a committed period, not just a named role: 24 months per Key Personnel assignment, the clause that stops a vendor from rotating a named lead off the account the week after signature. VITA also embeds a reusable, one-page Deliverable Acceptance Receipt, a form with three checkboxes (Accepted, Rejected, Conditionally Accepted) attached to every deliverable, rather than re-litigating the acceptance mechanic in prose each time.
The university engagement: Deloitte and the University of Cincinnati
Deloitte Consulting's 2020 Master Service Agreement and CampusConnect Statement of Work No. 1 with the University of Cincinnati, a public-university procurement record, is the cleanest worked example of two mechanics most consulting SOWs never state out loud.
The first is what silence means. Most SOWs leave this implied. Deloitte/UC's does not: "approval of a Deliverable shall be deemed given by Client if Client has not delivered... a notice of Deficiencies... prior to the expiration of any period for Client review... or if Client uses the Deliverable in production." That is a deliberate, pro-vendor default (silence equals acceptance), stated as a rule rather than left as an assumption either side could argue about later. A SOW does not have to pick this direction, but it has to pick one and say so.
The second is the change-control sentence that does more work than any other clause in the document: nothing except a signed Change Order varies the Statement of Work. Emails, status-meeting comments, and verbal discussion do not. Without that sentence, a project-status remark becomes a contested "verbal agreement" months later. The MSA also states that terminating this SOW has no effect on any other SOW running under it, which matters the moment a client has more than one active engagement with the same firm, and carries a Data Security Rider (restricted-data categories named, breach reporting inside one day of discovery, data return or destruction confirmed in writing on termination) that a generic confidentiality clause in the MSA does not cover on its own.
What every real SOW does that a template skips
Read across all five, the same handful of structural moves reappear, at every scale from a two-page federal task order to a six-annex framework agreement.
- A stated order of precedence. Every SOW here names its parent agreement and states, in one sentence, which document wins if they conflict.
- A scope boundary, not just a scope description. DHS's two-sentence scope and the fill-in template's "anything not addressed here is out of scope" both turn a scope argument into a change-order conversation instead of a dispute.
- Single-obligation "shall" statements. One bullet, one requirement, independently checkable, with the "shall/should/may/will" key stated up front when the drafters mix modal verbs.
- A four-part acceptance mechanic on every deliverable. Who approves, how long they have, what silence means, and what a rejection triggers, stated for each deliverable, not assumed.
- A Not-to-Exceed cap, even on fixed-price work. Accenture/TWC states one regardless of billing method; an uncapped time-and-materials SOW places no ceiling on total billing.
- A change-order-only clause. Nothing varies the SOW except a signed Change Order, stated explicitly, not left to be inferred from a meeting.
- A named committed period for Key Personnel on any engagement where the client is buying a specific person's expertise, not just a headcount.
Each of these is a genericized, register-independent pattern; none of them depends on contract size to apply. A short BSA/AML gap-analysis engagement carries the same need for the acceptance mechanic and the change-order clause as a federal task order does. See how a gap analysis is structured for what that specific deliverable looks like when it shows up in a SOW's Deliverables table.
Reading an executed SOW before drafting one
Three attributes are worth locating in any real SOW before its structure is borrowed.
1. The register of the document
A federal task-order narrative, a multi-annex framework agreement, a commercial schedule-based contract, and a fill-in-the-blank template are structurally different documents. A NATO-scale evidence annex copied into a two-month fixed-fee engagement adds friction without adding protection. The register is matched to the engagement first.
2. The completeness of the acceptance mechanic
A complete mechanic answers all four questions: who approves, how long they have, what silence means, and what a rejection triggers. Where any of the four is absent, the document carries the same gap as a generic template.
3. The clauses that vary the scope
The change-management clause governs this. Where it does not state that only a signed change order amends the SOW, the scope remains variable regardless of how detailed the Deliverables table is.
A BaaS fintech's compliance consulting engagement, for instance, often needs an independent-testing deliverable named in the SOW's Attachment II with its own acceptance mechanic; see the third-pillar guide for what that deliverable is actually testing, and the sponsor-bank oversight guide for how the underlying responsibility is allocated between a bank and its fintech partner before a consultant is ever engaged.
Primary sources
- U.S. Department of Homeland Security, Science and Technology Directorate, Office of the Chief Information Officer, Information Assurance Compliance Support Services, RFQ 70RSAT22Q00000040, Attachment I (Statement of Work), 2022. Federal solicitation records of this kind are searchable through SAM.gov, the federal government's System for Award Management.
- NATO Support and Procurement Agency (NSPA), Statement of Work for SAP S/4HANA Consultancy Services, with Annexes 1–6, 2021, marked NATO UNCLASSIFIED and released within a competitive tender. See NSPA Procurement.
- Accenture State Healthcare Services LLC / Texas Workforce Commission, On-Call Master Services Agreement and SOW Number One, 2020. Available under the Texas Public Information Act, Texas Government Code Chapter 552; request records through TWC Open Records Requests.
- Commonwealth of Virginia, Virginia Information Technologies Agency (VITA), Statement of Work Template, Attachment A to the VITA Master Services Agreement, Contract No. VA-160720-TEMP, 2016. See VITA Procurement Forms and Policies.
- Deloitte Consulting LLP / University of Cincinnati, Master Service Agreement and CampusConnect Statement of Work No. 1, 2020, a public-university procurement record. Request through the university's Public Records Office.