Free Statement of Work Template

What's in a Statement of Work

A Statement of Work covers sixteen sections in the standard order. The first six describe the engagement; the next ten govern the contract.

1. Project Overview. Two to four sentences. Business context, what the engagement is delivering.
2. Scope — In-Scope Activities. What the Vendor will perform.
3. Out of Scope. What the Vendor will not perform; any addition triggers Section 11 (Change Order).
4. Deliverables. Table — ID, deliverable, due date, acceptance criteria.
5. Timeline and Milestones. Table — milestone IDs and target dates.
6. Pricing and Payment. Fee model (fixed-fee or T&M), total fee, milestone-based payment schedule.
7. Acceptance Criteria. Default 10-business-day review window with silence-equals-acceptance.
8. Confidentiality. Either incorporates by reference an existing MSA or NDA, or operates as a standalone clause for the duration of the SOW plus three years.
9. Intellectual Property. Work-for-hire on deliverables; license-back of the Vendor's pre-existing tools and methodologies.
10. Warranties. Workmanlike-manner warranty plus a 30-day deliverable conformance warranty. All other warranties expressly disclaimed.
11. Change Order Process. Written agreement before changed work begins.
12. Term and Termination. Termination for convenience on 30 days' notice; termination for cause with a 15-day cure period.
13. Limitation of Liability. No indirect or consequential damages; aggregate cap at 12 months of fees.
14. Governing Law and Dispute Resolution. Choice of law, good-faith discussion period, exclusive jurisdiction.
15. Miscellaneous. Severability, integration, independent contractor, counterparts, electronic signatures.
16. Authorization. Two-column signature block.

SOW vs. Scope of Work — explained

The two terms collide because they share the same acronym. The distinction worth knowing is structural rather than semantic.

• Statement of Work. The full contract. Includes the scope, deliverables, timeline, fees, change-order process, IP, warranties, termination, governing law, and signatures. In US federal contracting (FAR Part 37, DoD MIL-HDBK-245), the Statement of Work is the master artifact for service contracts.
• Scope of Work. The narrower section or standalone document focused on the work itself — what gets done, when, and how acceptance is judged. In federal contracting it lives inside the Statement of Work as one section. In commercial work, especially construction and consulting, people often call the whole document a Scope of Work and skip the broader contract framing.

Practical guidance: if you have an existing Master Services Agreement that covers IP, warranties, and termination, you usually only need a Scope of Work template that attaches to the MSA and describes the work. If you do not have an MSA, this Statement of Work template is the better starting point because it bundles the project terms and legal framing into one document.

Commercial vs. federal Statements of Work

The template defaults to commercial — consulting, software, and professional-services engagements between two private parties. Federal Statements of Work follow a different path: FAR Part 37 (Service Contracting) and DoD MIL-HDBK-245 (Preparation of Statement of Work) prescribe a fixed ten-section structure, mandatory clauses (FAR flow-downs covering IP, termination for the convenience of the government, labor standards, accessibility), and a separate document called the Contract Data Requirements List (CDRL, DD Form 1423) for deliverables.

The structural overlap is meaningful — both formats cover scope, deliverables, period of performance, acceptance, and special requirements — but the federal version has compliance requirements that a commercial template cannot satisfy. If you are responding to a federal RFP or working under a prime-contractor flow-down, do not adapt this template; start from the FAR-compliant resources at acquisition.gov and have the document reviewed by federal-contracting counsel.

SOW vs. MSA — when each applies

A Master Services Agreement (MSA) is a long-form framework contract that two parties sign once and reuse across multiple engagements. It covers the legal terms — IP, warranties, indemnification, termination, governing law, dispute resolution — that don't change project-by-project.

An SOW is the project-by-project document that names the scope, deliverables, timeline, and fee, and incorporates the MSA's legal terms by reference. Two parties with an active MSA can execute multiple SOWs in parallel, each governing a single engagement, without renegotiating the legal terms each time.

Practical rule: if you and the counterparty expect to do more than one engagement together, sign an MSA once and execute SOWs against it. If this is a single engagement, the standalone Statement of Work template on this page is sufficient — it includes the legal terms inline. The template's cover block has a field for referencing an existing MSA, which causes Sections 8 (Confidentiality), 13 (Limitation of Liability), and 14 (Governing Law) to defer to the MSA's terms.

How to write a Statement of Work

1. Fill the cover block. Project name, SOW ID, effective date, version, the underlying MSA reference (if any), and the parties' details.
2. Write the project overview in two to four sentences. Business context, what the engagement is delivering.
3. Write the in-scope and out-of-scope lists. Specific activities, not vague capabilities. The cardinal rule: if it isn't listed, it isn't in scope.
4. Name the deliverables in a table. Each deliverable is a specific artifact in a specific format with specific acceptance criteria.
5. Set the milestone schedule and tie payment to milestones. The default in the template is 30/40/30 across three milestones with Net-15 payment terms after acceptance.
6. Choose the IP model. Work-for-hire (Client owns deliverables) is the default. The template also licenses back the Vendor's pre-existing tools and methodologies for use of the deliverables.
7. Set the warranty period. 30 days post-acceptance is standard for software and consulting. Construction warranties run longer.
8. Set the termination terms. 30 days' notice for convenience and 15 days' cure for cause is the commercial default.
9. Set governing law. Choose a state where enforcement actually has to happen — usually the Client's headquarters state or a neutral commercial state like Delaware or New York.
10. Sign. Two-column signature block. Electronic signatures are valid per Section 15.4.

Common pitfalls

1. Vague acceptance. Acceptance criteria like “Client satisfaction” or “quality work” are unenforceable. Use observable behaviors — “7 consecutive clean pipeline days,” “design memo approved by Project Sponsor.”
2. No change-order process. Without one, every scope discussion becomes a contract dispute. The template's Section 11 makes the bar low (a written email exchange is enough) but the form mandatory.
3. Missing IP clause. Without explicit assignment, copyright defaults to the author (the Vendor) for most deliverables. The Client thinks they own the work; they do not. The template's Section 9 fixes this.
4. Implied warranties unaddressed. Most US states imply warranties of merchantability and fitness for purpose. If the SOW does not disclaim them, they apply by default. The template's Section 10 disclaims everything except the express workmanlike-manner and conformance warranties.
5. No liability cap. Without a cap, the Vendor is exposed to potentially unlimited damages from any breach. Standard practice is to cap at 12 months of fees for direct damages and exclude indirect damages entirely.
6. No termination-for-convenience clause. Without it, the Client cannot stop the engagement without alleging breach. The template's Section 12 lets either party walk on 30 days' notice.
7. Choice of law in a state neither party operates in. Looks neutral, but enforcing the SOW means filing in that state's courts. Choose a state where one of the parties operates, or accept Delaware/New York as the commercial default.

What is inside the template

The download is a zip containing two files:

• statement-of-work-blank.docx — the full template with [BRACKETED PLACEHOLDERS] for parties, project, scope, deliverables, milestones, fee, and signatures.
• statement-of-work-example.docx — the same template filled with a software-consulting example: Acme Corporation hires Widget Industries Inc. to migrate three legacy data systems into a Snowflake warehouse, with three milestones, four deliverables, a 200K USD fixed fee, and Delaware governing law.

Both files render in Cambria on US letter-size pages with 1.5-inch margins. They open cleanly in Microsoft Word, Google Docs, Apple Pages, and LibreOffice. A short footer on every page repeats the disclaimer that this is a template, not legal advice.