Statement of Work (SOW)

Ready to Edit

STATEMENT OF WORK

SOW Number: [________________________________]
SOW Effective Date: [__/__/____]
Master Agreement Reference: [________________________________]
Master Agreement Date: [__/__/____]


TABLE OF CONTENTS

  1. Parties and Recitals
  2. Reference to Master Agreement
  3. Project Description
  4. Scope of Work
  5. Out-of-Scope Items
  6. Project Timeline and Schedule
  7. Roles and Responsibilities
  8. Staffing and Key Personnel
  9. Fees and Payment Schedule
  10. Expenses
  11. Change Order Process
  12. Acceptance Testing and Criteria
  13. Project Governance and Communication
  14. Warranties
  15. Term and Termination
  16. Signatures
  17. Appendices

1. PARTIES AND RECITALS

Client ("Client"):
Name: [________________________________]
Address: [________________________________]
City, State, ZIP: [________________________________]
Contact Person: [________________________________]
Email: [________________________________]
Phone: [________________________________]

Service Provider ("Provider"):
Name: [________________________________]
Address: [________________________________]
City, State, ZIP: [________________________________]
Contact Person: [________________________________]
Email: [________________________________]
Phone: [________________________________]

RECITALS

WHEREAS, Client and Provider have entered into that certain Master Services Agreement dated [__/__/____] (the "MSA" or "Master Agreement"); and

WHEREAS, Client desires to engage Provider to perform certain services as described in this Statement of Work, and Provider desires to perform such services, subject to the terms and conditions of the MSA and this SOW;

NOW, THEREFORE, in consideration of the mutual covenants and agreements contained herein and in the MSA, and for other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties agree as follows.


2. REFERENCE TO MASTER AGREEMENT

2.1 Incorporation. This SOW is entered into pursuant to and is governed by the terms of the MSA. All terms and conditions of the MSA are incorporated herein by reference as though fully set forth herein.

2.2 Order of Precedence. In the event of any conflict or inconsistency between the terms of this SOW and the MSA, the following order of precedence shall apply:

☐ The MSA shall control over this SOW
☐ This SOW shall control over the MSA with respect to the services described herein
☐ Other: [________________________________]

2.3 Defined Terms. Capitalized terms used but not defined in this SOW shall have the meanings assigned to them in the MSA. As used in this SOW, the following additional definitions apply:

  • "Acceptance Criteria" means the specific, measurable standards set forth in Section 12 against which each Deliverable shall be evaluated.
  • "Change Order" means a written amendment to this SOW executed in accordance with the Change Order Process in Section 11.
  • "Deliverable" means a tangible or intangible work product to be provided by Provider to Client as described in Section 4.
  • "Go-Live Date" means the date on which all Deliverables have been accepted and the project is deemed complete.
  • "Milestone" means a significant project event or completion of a Deliverable set forth in the Project Timeline.
  • "Project Manager" means the designated representative of each party responsible for day-to-day management of this SOW.

3. PROJECT DESCRIPTION

3.1 Project Name: [________________________________]

3.2 Project Overview: [________________________________]

3.3 Business Objectives:

# Objective Success Metric
1 [________________________________] [________________________________]
2 [________________________________] [________________________________]
3 [________________________________] [________________________________]
4 [________________________________] [________________________________]

3.4 Background and Context: [________________________________]


4. SCOPE OF WORK

4.1 Deliverables.

Provider shall deliver the following Deliverables in accordance with the Acceptance Criteria and timeline set forth in this SOW:

Deliverable # Description Milestone Due Date Acceptance Criteria
D-001 [________________________________] M-[____] [__/__/____] [________________________________]
D-002 [________________________________] M-[____] [__/__/____] [________________________________]
D-003 [________________________________] M-[____] [__/__/____] [________________________________]
D-004 [________________________________] M-[____] [__/__/____] [________________________________]
D-005 [________________________________] M-[____] [__/__/____] [________________________________]
D-006 [________________________________] M-[____] [__/__/____] [________________________________]

4.2 Services Description.

Provider shall perform the following services in connection with the Deliverables:

☐ Consulting and advisory services
☐ Software development and engineering
☐ System integration and configuration
☐ Data migration and conversion
☐ User training and knowledge transfer
☐ Documentation and technical writing
☐ Testing and quality assurance
☐ Project management
☐ Post-deployment support
☐ Other: [________________________________]

4.3 Service Standards. All services shall be performed in a professional, workmanlike manner in accordance with generally accepted industry standards and practices. Provider shall use commercially reasonable efforts to meet the deadlines set forth in this SOW. Pursuant to common law principles and UCC § 2-601, Deliverables must conform to the specifications and Acceptance Criteria described herein.


5. OUT-OF-SCOPE ITEMS

The following items are expressly excluded from the scope of this SOW. Any request to include out-of-scope items shall be handled through the Change Order Process in Section 11.

# Excluded Item Notes
1 [________________________________] [________________________________]
2 [________________________________] [________________________________]
3 [________________________________] [________________________________]
4 [________________________________] [________________________________]
5 [________________________________] [________________________________]

6. PROJECT TIMELINE AND SCHEDULE

6.1 Project Duration.

Start Date: [__/__/____]
Target Completion Date: [__/__/____]
Estimated Duration: [____] weeks/months

6.2 Milestone Schedule.

Milestone # Milestone Description Start Date End Date Duration Dependencies Status
M-001 Project Kickoff [__/__/____] [__/__/____] [____] days None ☐ Not Started
M-002 Requirements Gathering [__/__/____] [__/__/____] [____] days M-001 ☐ Not Started
M-003 Design Phase [__/__/____] [__/__/____] [____] days M-002 ☐ Not Started
M-004 Development/Build [__/__/____] [__/__/____] [____] days M-003 ☐ Not Started
M-005 Testing/QA [__/__/____] [__/__/____] [____] days M-004 ☐ Not Started
M-006 User Acceptance Testing [__/__/____] [__/__/____] [____] days M-005 ☐ Not Started
M-007 Deployment/Go-Live [__/__/____] [__/__/____] [____] days M-006 ☐ Not Started
M-008 Post-Launch Support [__/__/____] [__/__/____] [____] days M-007 ☐ Not Started

6.3 Gantt Chart Reference.

☐ A detailed Gantt chart is attached as Appendix A.
☐ The Gantt chart will be maintained in: [________________________________]
☐ Updates to the Gantt chart will be provided: ☐ Weekly ☐ Bi-weekly ☐ Monthly


7. ROLES AND RESPONSIBILITIES

7.1 Provider Responsibilities.

Role Responsibility
Provider Project Manager Overall project coordination, status reporting, escalation management
Technical Lead Architecture decisions, technical guidance, code reviews
Development Team Implementation of Deliverables per specifications
QA Lead Test planning, execution, defect tracking
[________________________________] [________________________________]

7.2 Client Responsibilities.

Role Responsibility
Client Project Manager Internal coordination, stakeholder management, approvals
Subject Matter Experts Requirements clarification, business rule validation
IT/Infrastructure Team System access, environment provisioning, network support
Executive Sponsor Escalation resolution, budget approval, strategic direction
[________________________________] [________________________________]

7.3 Joint Responsibilities.

  • Both parties shall participate in project governance meetings as described in Section 13.
  • Both parties shall use good-faith efforts to resolve issues promptly, consistent with the duty of good faith and fair dealing under Restatement (Second) of Contracts § 205.
  • Both parties shall maintain adequate records of project communications and decisions.

8. STAFFING AND KEY PERSONNEL

8.1 Key Personnel. Provider shall assign the following Key Personnel to this engagement:

Name Role Allocation (%) Start Date End Date
[________________________________] [________________________________] [____]% [__/__/____] [__/__/____]
[________________________________] [________________________________] [____]% [__/__/____] [__/__/____]
[________________________________] [________________________________] [____]% [__/__/____] [__/__/____]

8.2 Replacement of Key Personnel. Provider shall not replace Key Personnel without prior written consent of Client, which consent shall not be unreasonably withheld. In the event Key Personnel become unavailable due to illness, resignation, or other circumstances beyond Provider's reasonable control, Provider shall:

(a) Notify Client within [____] business days;
(b) Propose a replacement of comparable skill and experience within [____] business days; and
(c) Ensure knowledge transfer from departing personnel to replacement personnel.

8.3 Subcontractors. Provider ☐ may ☐ may not use subcontractors to perform work under this SOW. If subcontractors are permitted, Provider shall remain fully responsible for all subcontractor performance and compliance with the terms of the MSA and this SOW.


9. FEES AND PAYMENT SCHEDULE

9.1 Compensation Model.

Fixed Fee: Total fixed fee of $[________________________________]
Time and Materials: At the rates set forth below, not to exceed $[________________________________]
Milestone-Based: As set forth in the payment schedule below
Hybrid: [________________________________]

9.2 Hourly/Daily Rates (if applicable).

Role Hourly Rate Daily Rate Estimated Hours
[________________________________] $[____] $[____] [____]
[________________________________] $[____] $[____] [____]
[________________________________] $[____] $[____] [____]

9.3 Milestone-Based Payment Schedule.

Payment # Milestone/Deliverable Amount ($) % of Total Due Upon Invoice Date
1 Project Kickoff / Mobilization $[________________________________] [____]% Execution of SOW [__/__/____]
2 Completion of Requirements $[________________________________] [____]% Client Acceptance [__/__/____]
3 Completion of Design $[________________________________] [____]% Client Acceptance [__/__/____]
4 Completion of Development $[________________________________] [____]% Client Acceptance [__/__/____]
5 Successful UAT $[________________________________] [____]% Client Acceptance [__/__/____]
6 Go-Live / Final Acceptance $[________________________________] [____]% Client Acceptance [__/__/____]
TOTAL $[________________________________] 100%

9.4 Payment Terms. All invoices are due and payable within [____] days of receipt. Late payments shall bear interest at the rate of [____]% per month or the maximum rate permitted by applicable law, whichever is less. Pursuant to UCC § 2-609, a party may demand adequate assurance of performance if reasonable grounds for insecurity arise regarding payment or delivery obligations.

9.5 Holdback. Client may withhold [____]% of each milestone payment as a holdback, to be released upon Final Acceptance of all Deliverables.


10. EXPENSES

10.1 Reimbursable Expenses. Client shall reimburse Provider for the following pre-approved expenses:

☐ Travel (airfare, ground transportation, lodging)
☐ Meals and per diem
☐ Equipment and materials
☐ Software licenses and tools
☐ Shipping and delivery costs
☐ Other: [________________________________]

10.2 Expense Limits.

  • Individual expenses exceeding $[________________________________] require prior written approval.
  • Total reimbursable expenses shall not exceed $[________________________________] without a Change Order.
  • All expenses must be documented with receipts and submitted within [____] days of incurrence.

10.3 Travel Policy. Provider shall comply with Client's travel and expense policy, a copy of which ☐ is attached as Appendix B ☐ has been provided separately ☐ will be provided upon request.


11. CHANGE ORDER PROCESS

11.1 Change Request Initiation. Either party may initiate a change to this SOW by submitting a written Change Request using the form below. No changes to scope, schedule, or fees shall be effective unless documented in a signed Change Order.

11.2 Change Request Form.

═══════════════════════════════════════════════════════════
                     CHANGE REQUEST FORM
═══════════════════════════════════════════════════════════

Change Request #: [________________________________]
Date Submitted: [__/__/____]
Submitted By: [________________________________]
Priority: ☐ Critical  ☐ High  ☐ Medium  ☐ Low

DESCRIPTION OF REQUESTED CHANGE:
[________________________________]

REASON/JUSTIFICATION:
[________________________________]

IMPACT ASSESSMENT:
  Scope Impact: [________________________________]
  Schedule Impact: [____] days added/reduced
  Cost Impact: $[________________________________] increase/decrease
  Resource Impact: [________________________________]
  Risk Impact: [________________________________]

PROPOSED IMPLEMENTATION APPROACH:
[________________________________]

AFFECTED DELIVERABLES:
[________________________________]

REQUESTED BY:
Name: [________________________________]
Signature: [________________________________]
Date: [__/__/____]

APPROVED/REJECTED BY:
Name: [________________________________]
Signature: [________________________________]
Date: [__/__/____]
Decision: ☐ Approved  ☐ Rejected  ☐ Deferred
Comments: [________________________________]
═══════════════════════════════════════════════════════════

11.3 Evaluation Period. Provider shall evaluate each Change Request and deliver a written impact assessment within [____] business days of receipt. The impact assessment shall include effects on schedule, cost, resources, and risk.

11.4 Approval Authority.

Change Impact Client Approver Provider Approver
Cost < $[____] Project Manager Project Manager
Cost $[____] - $[____] [________________________________] [________________________________]
Cost > $[____] Executive Sponsor [________________________________]
Schedule impact > [____] days Executive Sponsor [________________________________]

11.5 Modification Requirements. Consistent with UCC § 2-209, modifications to this SOW require mutual written agreement. No oral modifications shall be enforceable. Each Change Order, once executed by both parties, shall be deemed an amendment to this SOW.


12. ACCEPTANCE TESTING AND CRITERIA

12.1 Acceptance Process. Upon delivery of each Deliverable, the following acceptance process shall apply:

(a) Provider shall deliver the Deliverable along with a Delivery Notice to Client.
(b) Client shall have [____] business days (the "Review Period") to evaluate the Deliverable against the Acceptance Criteria.
(c) Client shall provide written notice of acceptance or rejection within the Review Period.
(d) If Client fails to provide written notice within the Review Period, the Deliverable shall be deemed ☐ accepted ☐ not accepted.

12.2 Rejection and Cure.

(a) If Client rejects a Deliverable, Client shall provide a written description of all deficiencies.
(b) Provider shall have [____] business days to cure the identified deficiencies at no additional cost.
(c) Upon redelivery, Client shall have [____] business days for a second review.
(d) If the Deliverable fails acceptance after [____] cure cycles, Client may:

  • ☐ Extend the cure period by mutual agreement
  • ☐ Terminate this SOW for cause
  • ☐ Accept the Deliverable with an equitable price adjustment
  • ☐ Engage a third party to complete the Deliverable at Provider's expense

12.3 Acceptance Criteria Matrix.

Deliverable Criteria Category Specific Criteria Pass/Fail Standard
D-001 Functionality [________________________________] [________________________________]
D-001 Performance [________________________________] [________________________________]
D-001 Documentation [________________________________] [________________________________]
D-002 Functionality [________________________________] [________________________________]
D-002 Performance [________________________________] [________________________________]

12.4 Final Acceptance. Final Acceptance shall occur when all Deliverables have been individually accepted and Client has confirmed in writing that the project as a whole meets the business objectives stated in Section 3.3. Under UCC § 2-601, Client retains the right to reject non-conforming Deliverables in whole or in part.


13. PROJECT GOVERNANCE AND COMMUNICATION

13.1 Steering Committee. The parties shall establish a project steering committee composed of:

Member Organization Role
[________________________________] Client Executive Sponsor
[________________________________] Client Project Manager
[________________________________] Provider Account Executive
[________________________________] Provider Project Manager

13.2 Meeting Schedule.

Meeting Type Frequency Participants Format
Status Meeting ☐ Weekly ☐ Bi-weekly Project Managers, Leads ☐ In-person ☐ Virtual
Steering Committee ☐ Monthly ☐ Bi-weekly Steering Committee ☐ In-person ☐ Virtual
Technical Review ☐ Weekly ☐ As needed Technical Leads ☐ In-person ☐ Virtual
Risk Review ☐ Monthly ☐ Quarterly Project Managers ☐ In-person ☐ Virtual

13.3 Status Reporting. Provider shall deliver written status reports to Client on a [☐ weekly ☐ bi-weekly ☐ monthly] basis, including:

  • Progress against milestones and deliverables
  • Budget utilization and forecasts
  • Risk and issue log updates
  • Change request status
  • Upcoming activities and resource needs

13.4 Escalation Process.

Level Timeframe Client Escalation Provider Escalation
Level 1 0-[____] business days Project Manager Project Manager
Level 2 [____]-[____] business days [________________________________] [________________________________]
Level 3 [____]+ business days Executive Sponsor [________________________________]

13.5 Communication Tools.

☐ Email
☐ Project management platform: [________________________________]
☐ Document repository: [________________________________]
☐ Instant messaging: [________________________________]
☐ Video conferencing: [________________________________]


14. WARRANTIES

14.1 Deliverable Warranty. Provider warrants that each Deliverable shall:

(a) Conform to the specifications and Acceptance Criteria set forth in this SOW;
(b) Be free from material defects in design, workmanship, and functionality;
(c) Perform substantially in accordance with any accompanying documentation; and
(d) Not infringe any third-party intellectual property rights.

14.2 Warranty Period. The warranty period for each Deliverable shall be [____] days following Final Acceptance (the "Warranty Period").

14.3 Warranty Remedies. During the Warranty Period, Provider shall, at no additional cost to Client:

(a) Correct any Deliverable that fails to conform to the warranties in Section 14.1;
(b) Respond to warranty claims within [____] business hours; and
(c) Provide a corrected version within [____] business days of notification.

14.4 Services Warranty. Provider warrants that all services shall be performed in a professional and workmanlike manner by qualified personnel with the requisite skill, training, and experience.

14.5 Disclaimer. EXCEPT AS EXPRESSLY SET FORTH IN THIS SOW AND THE MSA, PROVIDER MAKES NO OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE UNDER UCC § 2-314 AND § 2-315.


15. TERM AND TERMINATION

15.1 SOW Term. This SOW shall commence on the SOW Effective Date and continue until the earlier of:

(a) Final Acceptance of all Deliverables;
(b) The Target Completion Date, unless extended by Change Order; or
(c) Earlier termination in accordance with this Section 15 or the MSA.

15.2 Termination for Convenience. Client may terminate this SOW for convenience upon [____] days' prior written notice to Provider. In the event of termination for convenience, Client shall pay Provider for:

(a) All Deliverables accepted prior to the termination date;
(b) All work-in-progress at the applicable rates through the termination date; and
(c) Reasonable, documented wind-down costs.

15.3 Termination for Cause. Either party may terminate this SOW for cause if the other party:

(a) Materially breaches this SOW or the MSA and fails to cure such breach within [____] days of written notice; or
(b) Becomes insolvent, files for bankruptcy, or has a receiver appointed for its assets.

15.4 Wind-Down Obligations. Upon termination or expiration, Provider shall:

(a) Deliver all completed and in-progress Deliverables and work product to Client;
(b) Provide reasonable transition assistance for a period of [____] days;
(c) Return or destroy all Client Confidential Information; and
(d) Provide a final accounting of all fees, expenses, and outstanding amounts.

15.5 Survival. The following provisions shall survive termination or expiration: Sections 2, 9 (to the extent of amounts owing), 14 (for the Warranty Period), and any other provisions which by their nature should survive.


16. SIGNATURES

IN WITNESS WHEREOF, the parties have executed this Statement of Work as of the SOW Effective Date.

CLIENT:

Signature: [________________________________]
Print Name: [________________________________]
Title: [________________________________]
Date: [__/__/____]

PROVIDER:

Signature: [________________________________]
Print Name: [________________________________]
Title: [________________________________]
Date: [__/__/____]


17. APPENDICES

Appendix A: Technical Specifications

Specification Requirement Notes
[________________________________] [________________________________] [________________________________]
[________________________________] [________________________________] [________________________________]
[________________________________] [________________________________] [________________________________]

Appendix B: Assumptions

The following assumptions underlie this SOW. If any assumption proves incorrect, the parties shall use the Change Order Process to address any resulting impact.

# Assumption Impact if Invalid
1 [________________________________] [________________________________]
2 [________________________________] [________________________________]
3 [________________________________] [________________________________]
4 [________________________________] [________________________________]
5 [________________________________] [________________________________]

Appendix C: Dependencies

# Dependency Owner Required By Status
1 [________________________________] ☐ Client ☐ Provider [__/__/____] ☐ Open ☐ Resolved
2 [________________________________] ☐ Client ☐ Provider [__/__/____] ☐ Open ☐ Resolved
3 [________________________________] ☐ Client ☐ Provider [__/__/____] ☐ Open ☐ Resolved
4 [________________________________] ☐ Client ☐ Provider [__/__/____] ☐ Open ☐ Resolved

Appendix D: Risk Register

Risk # Description Probability Impact Mitigation Strategy Owner
R-001 [________________________________] ☐ High ☐ Med ☐ Low ☐ High ☐ Med ☐ Low [________________________________] [________________________________]
R-002 [________________________________] ☐ High ☐ Med ☐ Low ☐ High ☐ Med ☐ Low [________________________________] [________________________________]
R-003 [________________________________] ☐ High ☐ Med ☐ Low ☐ High ☐ Med ☐ Low [________________________________] [________________________________]

SOURCES AND REFERENCES

  • Uniform Commercial Code, Article 2 (Sales) — UCC Article 2, Legal Information Institute
  • Restatement (Second) of Contracts §§ 205, 261 — American Law Institute
  • UCC § 2-204 (Formation in General)
  • UCC § 2-209 (Modification, Rescission and Waiver)
  • UCC § 2-302 (Unconscionable Contract or Clause)
  • UCC § 2-314 (Implied Warranty: Merchantability)
  • UCC § 2-315 (Implied Warranty: Fitness for Particular Purpose)
  • UCC § 2-601 (Buyer's Rights on Improper Delivery)
  • UCC § 2-609 (Right to Adequate Assurance of Performance)
  • UCC § 2-615 (Excuse by Failure of Presupposed Conditions)

This template is for informational purposes only and does not constitute legal advice. Consult a qualified attorney licensed in your jurisdiction before using this document.

Ezel AI
Hi! Need help customizing this document? I can tailor every section to your specific case in minutes.
AI Legal Assistant
Ezel AI
Hi! Need help customizing this document? I can tailor every section to your specific case in minutes.

Insert Image

Insert Table

Watch Ezel in action (sample case)

All changes saved
Save
Export
Export as DOCX
Export as PDF
Generating PDF...
statement_of_work_universal.pdf
Ready to export as PDF or Word
AI is editing...
Chat
Review

Customize this document with Ezel

  • Deep Legal Knowledge
    Understands case law, statutes, and legal doctrine.
  • Court-Ready Formatting
    Proper captions, certificates of service, and local rule compliance.
  • AI-Powered Editing on Your Timeline
    Edit as many times as you need. Tailor every section to your specific case.
  • Export as PDF & Word
    Download your finished document in professional PDF or DOCX format, ready to file or send.
Secure checkout via Stripe
Need to customize this document?

About This Template

A contract is a written record of what two or more parties agreed to and what happens if someone does not follow through. Clear language, defined terms, and clean signature blocks keep disputes small and enforceable. The most common mistakes in contracts come from vague promises, missing details about timing or payment, and skipping standard protective clauses like governing law and dispute resolution.

Important Notice

This template is provided for informational purposes. It is not legal advice. We recommend having an attorney review any legal document before signing, especially for high-value or complex matters.

Last updated: April 2026