Statement of Work (SOW) - Arizona
STATEMENT OF WORK — ARIZONA
SOW Number: [________________________________]
SOW Effective Date: [__/__/____]
Master Agreement Reference: [________________________________]
Master Agreement Date: [__/__/____]
TABLE OF CONTENTS
- Parties and Recitals
- Reference to Master Agreement
- Project Description
- Scope of Work
- Out-of-Scope Items
- Project Timeline and Schedule
- Roles and Responsibilities
- Staffing and Key Personnel
- Fees and Payment Schedule
- Expenses
- Change Order Process
- Acceptance Testing and Criteria
- Project Governance and Communication
- Warranties
- Term and Termination
- Arizona-Specific Provisions
- Signatures
- Appendices
1. PARTIES AND RECITALS
Client ("Client"):
Name: [________________________________]
Address: [________________________________]
City, State, ZIP: [________________________________]
Arizona Business Entity Number (if applicable): [________________________________]
Contact Person: [________________________________]
Email: [________________________________]
Phone: [________________________________]
Service Provider ("Provider"):
Name: [________________________________]
Address: [________________________________]
City, State, ZIP: [________________________________]
Arizona Business Entity Number (if applicable): [________________________________]
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;
WHEREAS, the parties acknowledge that this SOW shall be governed by Arizona law, including the Arizona Revised Statutes, Title 44 (Trade and Commerce);
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.
2.2 Order of Precedence. In the event of any conflict between this SOW and the MSA:
☐ 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. Additional definitions:
- "Acceptance Criteria" means the specific, measurable standards against which each Deliverable shall be evaluated.
- "Change Order" means a written amendment executed per the Change Order Process in Section 11.
- "Deliverable" means a tangible or intangible work product to be provided by Provider as described in Section 4.
- "Go-Live Date" means the date on which all Deliverables have been accepted.
- "Milestone" means a significant project event or completion point set forth in the Project Timeline.
- "Project Manager" means the designated representative of each party for day-to-day management.
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.
| 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.
☐ 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 consistent with generally accepted industry standards. Provider shall exercise commercially reasonable efforts to meet the deadlines herein. Deliverables must conform to the specifications and Acceptance Criteria set forth in this SOW, consistent with Arizona UCC provisions under ARS § 44-1201 et seq.
5. OUT-OF-SCOPE ITEMS
The following items are expressly excluded. 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 # | 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.
☐ A detailed Gantt chart is attached as Appendix A.
☐ Updates 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 |
| Executive Sponsor | Escalation resolution, budget approval |
| [________________________________] | [________________________________] |
7.3 Joint Responsibilities. Both parties shall participate in governance meetings (Section 13) and use good-faith efforts to resolve issues promptly, consistent with the duty of good faith under ARS § 44-1267 and Restatement (Second) of Contracts § 205.
8. STAFFING AND KEY PERSONNEL
8.1 Key Personnel.
| 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 (not unreasonably withheld). If Key Personnel become unavailable, Provider shall:
(a) Notify Client within [____] business days;
(b) Propose a comparable replacement within [____] business days; and
(c) Ensure knowledge transfer to replacement personnel.
8.3 Subcontractors. Provider ☐ may ☐ may not use subcontractors. Provider remains fully responsible for all subcontractor performance.
9. FEES AND PAYMENT SCHEDULE
9.1 Compensation Model.
☐ Fixed Fee: $[________________________________]
☐ Time and Materials: Not to exceed $[________________________________]
☐ Milestone-Based: Per payment schedule below
☐ Hybrid: [________________________________]
9.2 Rates (if applicable).
| Role | Hourly Rate | Daily Rate | Estimated Hours |
|---|---|---|---|
| [________________________________] | $[____] | $[____] | [____] |
| [________________________________] | $[____] | $[____] | [____] |
| [________________________________] | $[____] | $[____] | [____] |
9.3 Milestone Payment Schedule.
| Payment # | Milestone/Deliverable | Amount ($) | % of Total | Due Upon | Invoice Date |
|---|---|---|---|---|---|
| 1 | Project Kickoff | $[________________________________] | [____]% | SOW Execution | [__/__/____] |
| 2 | Requirements Complete | $[________________________________] | [____]% | Client Acceptance | [__/__/____] |
| 3 | Design Complete | $[________________________________] | [____]% | Client Acceptance | [__/__/____] |
| 4 | Development Complete | $[________________________________] | [____]% | Client Acceptance | [__/__/____] |
| 5 | UAT Successful | $[________________________________] | [____]% | Client Acceptance | [__/__/____] |
| 6 | Go-Live / Final Acceptance | $[________________________________] | [____]% | Client Acceptance | [__/__/____] |
| TOTAL | $[________________________________] | 100% |
9.4 Payment Terms. Invoices are due within [____] days of receipt. Late payments bear interest at [____]% per month or the maximum permitted under Arizona law, whichever is less. Pursuant to ARS § 47-2609, a party may demand adequate assurance of performance if reasonable grounds for insecurity arise.
9.5 Holdback. Client may withhold [____]% of each milestone payment, released upon Final Acceptance.
10. EXPENSES
10.1 Reimbursable Expenses.
☐ Travel (airfare, ground transportation, lodging)
☐ Meals and per diem
☐ Equipment and materials
☐ Software licenses and tools
☐ Shipping and delivery
☐ Other: [________________________________]
10.2 Expense Limits. Individual expenses over $[________________________________] require prior approval. Total reimbursable expenses shall not exceed $[________________________________].
10.3 Travel Policy. Provider shall comply with Client's travel policy ☐ attached as Appendix B ☐ provided separately.
11. CHANGE ORDER PROCESS
11.1 Change Request Initiation. Either party may submit a written Change Request. No scope, schedule, or fee changes are effective without 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: $[________________________________]
Resource Impact: [________________________________]
Risk Impact: [________________________________]
AFFECTED DELIVERABLES:
[________________________________]
REQUESTED BY:
Signature: [________________________________] Date: [__/__/____]
APPROVED/REJECTED BY:
Signature: [________________________________] Date: [__/__/____]
Decision: ☐ Approved ☐ Rejected ☐ Deferred
═══════════════════════════════════════════════════════════
11.3 Evaluation Period. Provider shall deliver a written impact assessment within [____] business days.
11.4 Approval Authority.
| Change Impact | Client Approver | Provider Approver |
|---|---|---|
| Cost < $[____] | Project Manager | Project Manager |
| Cost $[____] - $[____] | [________________________________] | [________________________________] |
| Cost > $[____] | Executive Sponsor | [________________________________] |
11.5 Modification Requirements. Consistent with UCC § 2-209 (as adopted in Arizona), modifications require mutual written agreement. No oral modifications are enforceable. This provision is supported by Arizona's statute of frauds under ARS § 44-101, which requires written evidence for agreements not performable within one year.
12. ACCEPTANCE TESTING AND CRITERIA
12.1 Acceptance Process.
(a) Provider delivers Deliverable with a Delivery Notice.
(b) Client has [____] business days to evaluate against Acceptance Criteria.
(c) Client provides written acceptance or rejection.
(d) If no notice within the Review Period, the Deliverable is deemed ☐ accepted ☐ not accepted.
12.2 Rejection and Cure.
(a) Client provides written deficiency description upon rejection.
(b) Provider has [____] business days to cure at no additional cost.
(c) Client has [____] business days for second review.
(d) After [____] cure cycles, Client may:
☐ Extend the cure period
☐ Terminate this SOW for cause
☐ Accept with equitable price adjustment
☐ Engage a third party at Provider's expense
12.3 Acceptance Criteria Matrix.
| Deliverable | Category | Criteria | Pass/Fail Standard |
|---|---|---|---|
| D-001 | Functionality | [________________________________] | [________________________________] |
| D-001 | Performance | [________________________________] | [________________________________] |
| D-002 | Functionality | [________________________________] | [________________________________] |
| D-002 | Performance | [________________________________] | [________________________________] |
12.4 Final Acceptance. Final Acceptance occurs when all Deliverables are individually accepted and Client confirms the project meets business objectives in Section 3.3.
13. PROJECT GOVERNANCE AND COMMUNICATION
13.1 Steering Committee.
| 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 | ☐ In-person ☐ Virtual |
| Steering Committee | ☐ Monthly ☐ Bi-weekly | Full Committee | ☐ In-person ☐ Virtual |
| Technical Review | ☐ Weekly ☐ As needed | Technical Leads | ☐ In-person ☐ Virtual |
13.3 Status Reports. Provider shall deliver written status reports [☐ weekly ☐ bi-weekly ☐ monthly] covering progress, budget, risks, and upcoming activities.
13.4 Escalation Process.
| Level | Timeframe | Client Contact | Provider Contact |
|---|---|---|---|
| Level 1 | 0-[____] business days | Project Manager | Project Manager |
| Level 2 | [____]-[____] business days | [________________________________] | [________________________________] |
| Level 3 | [____]+ business days | Executive Sponsor | [________________________________] |
14. WARRANTIES
14.1 Deliverable Warranty. Provider warrants each Deliverable shall:
(a) Conform to specifications and Acceptance Criteria;
(b) Be free from material defects;
(c) Perform substantially in accordance with documentation; and
(d) Not infringe third-party intellectual property rights.
14.2 Warranty Period. [____] days following Final Acceptance.
14.3 Warranty Remedies. During the Warranty Period, Provider shall correct non-conforming Deliverables at no additional cost, responding within [____] business hours.
14.4 Services Warranty. All services shall be performed in a professional and workmanlike manner by qualified personnel.
14.5 Disclaimer. EXCEPT AS EXPRESSLY SET FORTH HEREIN AND IN THE MSA, PROVIDER DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE UNDER ARS § 44-1314 AND § 44-1315.
15. TERM AND TERMINATION
15.1 Term. This SOW commences on the SOW Effective Date and continues until Final Acceptance, the Target Completion Date, or earlier termination.
15.2 Termination for Convenience. Client may terminate upon [____] days' written notice. Client shall pay for accepted Deliverables, work-in-progress, and reasonable wind-down costs.
15.3 Termination for Cause. Either party may terminate if the other materially breaches and fails to cure within [____] days of notice, or becomes insolvent.
15.4 Wind-Down. Upon termination, Provider shall deliver all work product, provide transition assistance for [____] days, return Client Confidential Information, and provide final accounting.
15.5 Survival. Sections 2, 9 (amounts owing), 14, 16, and any provisions that by nature should survive.
16. ARIZONA-SPECIFIC PROVISIONS
16.1 Governing Law. This SOW shall be governed by the laws of the State of Arizona without regard to conflict-of-laws principles. All disputes shall be subject to the exclusive jurisdiction of the state and federal courts located in [________________________________] County, Arizona.
16.2 Statute of Frauds. Pursuant to ARS § 44-101, agreements not performable within one year require a writing signed by the party to be charged. This SOW satisfies that requirement.
16.3 Attorney Fees. Pursuant to ARS § 12-341.01, in any action arising out of a contract, the court may award the successful party reasonable attorney fees. The prevailing party in any action to enforce this SOW shall be entitled to recover reasonable attorney fees and costs.
16.4 Electronic Transactions. This SOW may be executed electronically in accordance with the Arizona Uniform Electronic Transactions Act (ARS § 44-2901 et seq.), and electronic signatures shall have the same legal effect as original signatures.
16.5 Good Faith. All performance under this SOW shall be governed by the obligation of good faith as required by ARS § 44-1267 and Arizona common law.
16.6 Transaction Privilege Tax. Provider is responsible for payment of any Arizona Transaction Privilege Tax (TPT) applicable to the services performed under this SOW. Provider shall separately state any applicable TPT on each invoice. Client shall provide a valid TPT exemption certificate if applicable.
16.7 Contractor Registration. If applicable, Provider represents that it is properly licensed and registered with the Arizona Registrar of Contractors and holds all licenses required to perform the services described herein.
17. 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: [__/__/____]
18. APPENDICES
Appendix A: Technical Specifications
| Specification | Requirement | Notes |
|---|---|---|
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
Appendix B: Assumptions
| # | Assumption | Impact if Invalid |
|---|---|---|
| 1 | [________________________________] | [________________________________] |
| 2 | [________________________________] | [________________________________] |
| 3 | [________________________________] | [________________________________] |
| 4 | [________________________________] | [________________________________] |
Appendix C: Dependencies
| # | Dependency | Owner | Required By | Status |
|---|---|---|---|---|
| 1 | [________________________________] | ☐ Client ☐ Provider | [__/__/____] | ☐ Open ☐ Resolved |
| 2 | [________________________________] | ☐ Client ☐ Provider | [__/__/____] | ☐ Open ☐ Resolved |
| 3 | [________________________________] | ☐ Client ☐ Provider | [__/__/____] | ☐ Open ☐ Resolved |
Appendix D: Risk Register
| Risk # | Description | Probability | Impact | Mitigation | Owner |
|---|---|---|---|---|---|
| R-001 | [________________________________] | ☐ High ☐ Med ☐ Low | ☐ High ☐ Med ☐ Low | [________________________________] | [________________________________] |
| R-002 | [________________________________] | ☐ High ☐ Med ☐ Low | ☐ High ☐ Med ☐ Low | [________________________________] | [________________________________] |
SOURCES AND REFERENCES
- Arizona Revised Statutes, Title 44 — Trade and Commerce
- ARS § 44-101 (Statute of Frauds)
- ARS § 44-1201 et seq. (Arizona UCC — Sales)
- ARS § 44-1267 (Good Faith Obligation)
- ARS § 44-2901 et seq. (Uniform Electronic Transactions Act)
- ARS § 12-341.01 (Attorney Fees in Contract Actions)
- Uniform Commercial Code, Article 2 — UCC Article 2
- Restatement (Second) of Contracts § 205
This template is for informational purposes only and does not constitute legal advice. Consult a licensed Arizona attorney before using 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