Free SOW Template for US Companies (2026)

A Statement of Work turns an abstract engagement into something a court could read in five minutes and understand. The MSA describes the relationship. The SOW describes the project. This is a free SOW template walkthrough for US companies, with sample clause language for each of the eleven sections that matter. Use it as a starting point and have counsel review before signing on high-value engagements.

What goes in a SOW versus an MSA

The Master Services Agreement holds the stable terms. The Statement of Work holds the project-specific terms. The MSA is signed once. The SOW is signed for each project.

For a single short project, an integrated independent contractor agreement that bundles both works fine. Once you expect to engage the same contractor for multiple projects, the two-document structure pays off.

The eleven sections every SOW needs

1. Parties and reference to the MSA

This Statement of Work ("SOW") dated [Date] is entered into between
[Client Legal Name], a [State] [entity type] ("Client"),
and [Contractor Legal Name], a [country/state] [entity type or individual]
("Contractor"), and is governed by and incorporated into the Master Services
Agreement dated [MSA Date] between the parties (the "MSA"). In the event of
conflict between this SOW and the MSA, the MSA controls except where this
SOW expressly states otherwise.

Without the MSA reference, a court may treat the SOW as standalone with no IP, confidentiality, or indemnification terms.

2. Scope of work

Describe the work in concrete, testable terms. The phrase “and any other work as Client may reasonably request” is the single most common cause of scope disputes. Use the change-order process for anything outside the defined scope.

Contractor shall design, build, and deliver [project description] consisting
of the following components:

(a) [Component 1 with one-sentence definition]
(b) [Component 2 with one-sentence definition]
(c) [Component 3 with one-sentence definition]

The detailed technical specification is set forth in Annex A. Work outside
the scope described above shall be billable only if covered by an executed
Change Order under Section 7.

3. Deliverables and milestones

List deliverables as numbered items with delivery dates. Tie payment to deliverables, not to time. A common structure is a 20-30-30-20 payment split across four milestones.

Deliverable 1: [Description], due [Date], payment trigger [20%]
Deliverable 2: [Description], due [Date], payment trigger [30%]
Deliverable 3: [Description], due [Date], payment trigger [30%]
Deliverable 4: [Description], due [Date], payment trigger [20%]

Each Deliverable is subject to the Acceptance process in Section 4.

4. Acceptance criteria

This is the section that decides who wins a dispute. Write acceptance as testable conditions.

A Deliverable is accepted when (i) it conforms to the specification in Annex
A, (ii) it passes the acceptance tests listed in Annex B, and (iii) Client
confirms acceptance in writing within 10 business days of delivery. If
Client neither accepts nor delivers a written rejection within the review
window, the Deliverable is deemed accepted.

A rejection notice must specify the non-conformities in writing with
reference to the acceptance tests in Annex B. Contractor shall have 10
business days to cure rejected non-conformities at no additional cost. If
Contractor fails to cure within the cure period, Client may (a) accept the
Deliverable with a pro rata fee reduction, (b) require a further cure
period of equal length, or (c) terminate this SOW for material breach
under Section 10.

Three things matter here. Testable criteria (not “satisfactory”). A review window so the deliverable is not in limbo. A cure period so a small fix does not become a termination.

5. Payment terms

State the total fee, the schedule, the currency, the invoicing cadence, and the net terms.

Total fees for this SOW are USD [Amount], payable as follows:
- 20% on execution of this SOW
- 30% on Acceptance of Deliverable 2
- 30% on Acceptance of Deliverable 3
- 20% on Acceptance of Deliverable 4

Contractor shall invoice on completion of each milestone. Client shall pay
invoices within 30 days of receipt by [wire transfer / ACH / approved
payment platform] in USD. Contractor is responsible for any taxes,
withholdings, and currency-conversion costs in Contractor's jurisdiction.

For time-and-materials work, replace the schedule with an hourly rate, a not-to-exceed cap, a weekly or monthly invoicing cadence, and a timekeeping requirement.

6. Change orders

Any change to scope, deliverables, timeline, or fees requires a written
Change Order signed by both parties. No work outside this SOW shall be
billable unless covered by an executed Change Order. Email approval from
Client's authorized representative (named in Annex C) constitutes a
written signature for this section.

Without a change-order process, work just happens and disputes follow. Requiring physical signatures stalls async teams. Email approval from a named representative is the practical middle ground.

7. Intellectual property

All Work Product created by Contractor under this SOW shall be deemed
"work made for hire" as defined in 17 USC 101 to the maximum extent
permitted by law. To the extent any Work Product does not qualify as work
made for hire, Contractor hereby irrevocably assigns to Client all right,
title, and interest in such Work Product, including all copyrights,
patents, trade secrets, and other intellectual property rights, effective
upon creation. Contractor shall execute any further documents reasonably
necessary to perfect this assignment.

Contractor's pre-existing IP listed in Annex D is licensed to Client on a
non-exclusive, perpetual, royalty-free basis solely for use with the Work
Product.

The two-step language (work made for hire plus express assignment) matters because under 17 USC 101 (https://www.law.cornell.edu/uscode/text/17/101), work made for hire for an independent contractor applies only to nine narrow categories (collective works, motion pictures, translations, supplementary works, compilations, instructional texts, tests, answer materials, atlases). Most software and product work falls outside those categories. The fallback assignment is what actually transfers ownership. Under 17 USC 204 (https://www.law.cornell.edu/uscode/text/17/204), the assignment must be in writing and signed by the assignor.

8. Confidentiality

The MSA usually carries the master confidentiality clause. The SOW restates it for clarity.

Contractor shall treat all non-public information disclosed by Client in
connection with this SOW as Confidential Information under the terms of
the MSA. The confidentiality obligation survives termination of this SOW
for a period of 5 years.

9. Termination

This SOW commences on the Effective Date and continues until Acceptance of
the final Deliverable or [End Date], whichever is earlier. Either party
may terminate this SOW for cause on 15 days written notice for an uncured
material breach. Client may terminate this SOW for convenience on 30 days
written notice. On termination, Client shall pay for accepted work through
the termination date plus a wind-down fee not to exceed USD [Amount].
Contractor shall deliver all work-in-progress within 5 business days of
termination.

Without termination for convenience, the client is locked in even when priorities change. The wind-down fee compensates the contractor for stopping mid-stream.

10. Governing law and dispute resolution

This SOW is governed by the laws of the State of [Delaware/California/New
York], without regard to its conflict-of-laws principles. Any dispute
arising under this SOW shall be resolved by binding arbitration administered
by the American Arbitration Association under its Commercial Arbitration
Rules, with the seat in [City, State]. The parties consent to the
non-exclusive jurisdiction of the state and federal courts located in
[County, State] for any matter not subject to arbitration.

State the seat, the rules, and the forum. Silence creates uncertainty that costs more than the dispute itself.

11. Signatures and electronic execution

This SOW may be executed in counterparts, each of which is an original.
Electronic signatures are valid and have the same force and effect as
manual signatures under the federal ESIGN Act (15 USC 7001) and applicable
state UETA statutes. The parties consent to do business electronically.

The ESIGN Act consent language (https://www.law.cornell.edu/uscode/text/15/7001) is required for ESIGN to apply. Standard e-signature platforms handle the consent flow automatically.

US-specific concerns

Classification

The IRS examines behavioral control, financial control, and the relationship of the parties under common-law rules (https://www.irs.gov/businesses/small-businesses-self-employed/independent-contractor-self-employed-or-employee). A SOW that supports contractor status has deliverable-based scope, contractor-controlled hours and tools, contractor risk on fixed-fee work, a right to subcontract subject to confidentiality, no employee benefits or exclusivity, and a term tied to the project. A SOW that reads like a job description is a misclassification risk.

Tax forms

For US contractors, collect Form W-9 before the first payment and issue Form 1099-NEC at year end if payments exceed the IRS threshold. For non-US contractors, collect Form W-8BEN (individuals) or W-8BEN-E (entities) before the first payment. Services performed outside the US by a non-US person are generally foreign-source income and not reportable on Form 1099 or 1042-S. See IRS guidance on reporting payments to independent contractors (https://www.irs.gov/businesses/small-businesses-self-employed/reporting-payments-to-independent-contractors).

State-specific issues

California, New York, and Massachusetts have stricter classification tests than the federal common-law test. The California ABC test (Labor Code Section 2775) is the strictest. If your contractor performs work for California residents from outside California, the SOW should explicitly disclaim California work and the contractor should not be a California resident. For California-specific compliance, see our guide on AB5 contractor compliance.

Common SOW failure modes

• Vague acceptance criteria. “Satisfactory to Client” is not a standard. Write acceptance as a test plan with pass conditions.
• No change-order process. Every email becomes a potential billable hour or a potential dispute.
• Missing IP assignment. A SOW that relies only on work-made-for-hire is exposed because most contractor work does not qualify under 17 USC 101.
• Silent on subcontracting. State whether subcontracting is allowed and require flow-down of IP and confidentiality to subcontractors.
• No termination for convenience. Without it, you are locked into a project that may no longer make sense.
• Unclear FX terms. Spell out the source rate (wire date, invoice date, central bank rate). For volatile currencies, invoice in USD.
• Open-ended timelines. “Within a reasonable time” is not a delivery date. Commit to a date or a date range.

When to use this SOW versus when to escalate

This template works for engagements under USD 250k where scope is reasonably defined and the contractor is a known counterparty. Above that threshold, or for novel work, or for engagements with regulated data, have outside counsel draft a bespoke SOW. The cost of two hours of legal review is dwarfed by the cost of a single acceptance dispute.

Get a country-aware version

This template is a starting point. The real version depends on the contractor’s country (moral rights in France and Germany, Copyright Act 1957 in India, GDPR if EU data is involved), the work product (software, design, content), and the payment rails (ACH, wire, multi-currency). Manually adjusting a template for each of these dimensions is where mistakes happen.

Omnivoo Contract Management generates a country-aware SOW in minutes. You answer a short set of questions about the engagement and the platform produces a SOW with the right IP language for the contractor’s jurisdiction, the right tax form collection (W-9, W-8BEN, W-8BEN-E), e-signature under ESIGN and eIDAS, KYC on the contractor, and payment rails built in. The SOW is flat USD 49 per contract with payment transaction fees passed through at cost.

For comparison of when to use a SOW versus a standalone independent contractor agreement, see our MSA vs SOW guide. For a deeper IP treatment, see contractor IP assignment across US, India, and EU jurisdictions. To skip the manual drafting entirely, Omnivoo Contract Management handles it.

If you remember three things

1. The MSA holds the stable terms. The SOW holds the project-specific terms. Always reference the MSA from the SOW.
2. Acceptance criteria are testable conditions, not adjectives. Write them like a test plan with a review window and a cure period.
3. Work made for hire under 17 USC 101 does not cover most contractor work. Add an explicit IP assignment under 17 USC 204.

Use Omnivoo Contract Management at /solutions/contract-management to generate a country-aware SOW in minutes, with e-sign, KYC, and payment all included for USD 49 flat.