Statement of Work
STATEMENT OF WORK
SOW Number: [________________________________]
Effective Date: [__/__/____]
Master Agreement Reference: [________________________________] (if applicable)
PARTIES
CLIENT:
Name: [________________________________]
Address: [________________________________]
City, State, ZIP: [________________________________], Wisconsin [________]
Contact Person: [________________________________]
Email: [________________________________]
Phone: [________________________________]
SERVICE PROVIDER:
Name: [________________________________]
Address: [________________________________]
City, State, ZIP: [________________________________], Wisconsin [________]
Contact Person: [________________________________]
Email: [________________________________]
Phone: [________________________________]
1. PROJECT OVERVIEW
1.1 Project Name
[________________________________]
1.2 Project Description
[________________________________]
[________________________________]
[________________________________]
1.3 Project Objectives
The objectives of this project are:
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
1.4 Business Context
[________________________________]
[________________________________]
1.5 Success Criteria
The project shall be deemed successful upon achievement of the following criteria:
| Criterion | Measurement Method | Target |
|---|---|---|
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
2. SCOPE OF WORK
2.1 Services to Be Performed
Service Provider agrees to perform the following services:
Phase 1: [________________________________]
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
Phase 2: [________________________________]
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
Phase 3: [________________________________]
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
2.2 In-Scope Activities
The following activities are expressly included within the scope of this SOW:
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
2.3 Out-of-Scope Activities
The following activities are expressly excluded from this SOW:
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
2.4 Technical Requirements
| Requirement Category | Specification |
|---|---|
| [________________________________] | [________________________________] |
| [________________________________] | [________________________________] |
| [________________________________] | [________________________________] |
| [________________________________] | [________________________________] |
3. DELIVERABLES AND ACCEPTANCE CRITERIA
3.1 Project Deliverables
| Deliverable ID | Deliverable Description | Format | Due Date |
|---|---|---|---|
| D-001 | [________________________________] | [________] | [__/__/____] |
| D-002 | [________________________________] | [________] | [__/__/____] |
| D-003 | [________________________________] | [________] | [__/__/____] |
| D-004 | [________________________________] | [________] | [__/__/____] |
| D-005 | [________________________________] | [________] | [__/__/____] |
| D-006 | [________________________________] | [________] | [__/__/____] |
3.2 Acceptance Criteria
Each Deliverable shall be subject to the following acceptance criteria:
Deliverable D-001: [________________________________]
| Criterion | Requirement | Pass/Fail Standard |
|---|---|---|
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
Deliverable D-002: [________________________________]
| Criterion | Requirement | Pass/Fail Standard |
|---|---|---|
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
Deliverable D-003: [________________________________]
| Criterion | Requirement | Pass/Fail Standard |
|---|---|---|
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
3.3 Acceptance Process
3.3.1 Service Provider shall deliver each Deliverable to Client in accordance with the delivery schedule.
3.3.2 Client shall have [____] business days from receipt to review each Deliverable ("Review Period").
3.3.3 Client shall provide written notice of acceptance or rejection within the Review Period.
3.3.4 If Client rejects a Deliverable, Client shall provide detailed written explanation of deficiencies.
3.3.5 Service Provider shall have [____] business days to cure deficiencies and resubmit.
3.3.6 If Client fails to provide notice within the Review Period, the Deliverable shall be deemed accepted.
3.3.7 Final acceptance shall be documented using the Deliverable Acceptance Form attached as Exhibit A.
4. PROJECT TIMELINE AND MILESTONES
4.1 Project Duration
Project Start Date: [__/__/____]
Project End Date: [__/__/____]
Total Duration: [____] weeks / [____] months
4.2 Milestone Schedule
| Milestone ID | Milestone Description | Target Date | Dependencies | Payment Trigger |
|---|---|---|---|---|
| M-001 | Project Kickoff | [__/__/____] | None | ☐ Yes ☐ No |
| M-002 | Requirements Complete | [__/__/____] | M-001 | ☐ Yes ☐ No |
| M-003 | Design Approval | [__/__/____] | M-002 | ☐ Yes ☐ No |
| M-004 | Development Complete | [__/__/____] | M-003 | ☐ Yes ☐ No |
| M-005 | Testing Complete | [__/__/____] | M-004 | ☐ Yes ☐ No |
| M-006 | User Acceptance | [__/__/____] | M-005 | ☐ Yes ☐ No |
| M-007 | Go-Live | [__/__/____] | M-006 | ☐ Yes ☐ No |
| M-008 | Project Closure | [__/__/____] | M-007 | ☐ Yes ☐ No |
4.3 Detailed Project Schedule
| Phase | Activity | Start Date | End Date | Duration | Owner |
|---|---|---|---|---|---|
| 1 | [________________________________] | [__/__/____] | [__/__/____] | [____] days | [________] |
| 1 | [________________________________] | [__/__/____] | [__/__/____] | [____] days | [________] |
| 2 | [________________________________] | [__/__/____] | [__/__/____] | [____] days | [________] |
| 2 | [________________________________] | [__/__/____] | [__/__/____] | [____] days | [________] |
| 3 | [________________________________] | [__/__/____] | [__/__/____] | [____] days | [________] |
| 3 | [________________________________] | [__/__/____] | [__/__/____] | [____] days | [________] |
4.4 Schedule Change Provisions
Any changes to the milestone schedule must be documented in writing and approved by both parties through the Change Order Process described in Section 8.
5. RESOURCES AND STAFFING
5.1 Service Provider Personnel
| Role | Name | Responsibilities | Allocation (%) | Hourly Rate |
|---|---|---|---|---|
| Project Manager | [________________________________] | [________________________________] | [____]% | $[________] |
| Technical Lead | [________________________________] | [________________________________] | [____]% | $[________] |
| [________________________________] | [________________________________] | [________________________________] | [____]% | $[________] |
| [________________________________] | [________________________________] | [________________________________] | [____]% | $[________] |
| [________________________________] | [________________________________] | [________________________________] | [____]% | $[________] |
5.2 Client Personnel
| Role | Name | Responsibilities | Expected Time Commitment |
|---|---|---|---|
| Project Sponsor | [________________________________] | [________________________________] | [____] hours/week |
| Project Manager | [________________________________] | [________________________________] | [____] hours/week |
| Subject Matter Expert | [________________________________] | [________________________________] | [____] hours/week |
| [________________________________] | [________________________________] | [________________________________] | [____] hours/week |
5.3 Key Personnel Provisions
5.3.1 The following individuals are designated as Key Personnel:
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
5.3.2 Service Provider shall not remove or reassign Key Personnel without [____] days prior written notice to Client.
5.3.3 Client reserves the right to approve replacement personnel for Key Personnel positions.
5.3.4 Replacement personnel must possess substantially equivalent qualifications and experience.
5.4 Subcontractors
☐ Subcontractors are not permitted under this SOW.
☐ Subcontractors are permitted with prior written approval from Client.
Approved Subcontractors:
| Subcontractor Name | Services | Contact Information |
|---|---|---|
| [________________________________] | [________________________________] | [________________________________] |
| [________________________________] | [________________________________] | [________________________________] |
6. FEES AND PAYMENT SCHEDULE
6.1 Pricing Model
☐ Fixed Price: Total project fee of $[________________________________]
☐ Time and Materials: Hourly rates as specified in Section 5.1, not to exceed $[________________________________]
☐ Milestone-Based: Payments tied to milestone completion as specified below
☐ Hybrid: Combination of fixed price and time and materials as specified below
6.2 Fee Schedule
| Payment | Description | Amount | Due Date / Trigger |
|---|---|---|---|
| 1 | Project Initiation | $[________________________________] | Upon SOW execution |
| 2 | [________________________________] | $[________________________________] | [________________________________] |
| 3 | [________________________________] | $[________________________________] | [________________________________] |
| 4 | [________________________________] | $[________________________________] | [________________________________] |
| 5 | Final Payment | $[________________________________] | Upon final acceptance |
Total Contract Value: $[________________________________]
6.3 Expenses
☐ All expenses are included in the fees above.
☐ The following expenses are reimbursable at actual cost:
| Expense Category | Estimated Amount | Approval Required |
|---|---|---|
| Travel | $[________________________________] | ☐ Yes ☐ No |
| Equipment | $[________________________________] | ☐ Yes ☐ No |
| Software/Licenses | $[________________________________] | ☐ Yes ☐ No |
| [________________________________] | $[________________________________] | ☐ Yes ☐ No |
Maximum Reimbursable Expenses: $[________________________________]
6.4 Invoicing and Payment Terms
6.4.1 Service Provider shall submit invoices to:
[________________________________]
[________________________________]
Email: [________________________________]
6.4.2 Invoices shall include: SOW number, description of services performed, hours worked (if applicable), milestone achieved (if applicable), and supporting documentation.
6.4.3 Payment terms: Net [____] days from receipt of valid invoice.
6.4.4 Late payments shall accrue interest at [____]% per month (not to exceed the maximum rate permitted under Wisconsin law).
6.4.5 Client may dispute invoiced amounts in writing within [____] days of receipt. Undisputed amounts remain due per payment terms.
7. ASSUMPTIONS AND DEPENDENCIES
7.1 Project Assumptions
The following assumptions form the basis for this SOW. If any assumption proves incorrect, a Change Order may be required:
Client Assumptions:
☐ Client will provide timely access to all necessary systems, data, and personnel.
☐ Client will designate authorized decision-makers with authority to approve deliverables.
☐ Client will respond to Service Provider requests within [____] business days.
☐ Client facilities and infrastructure meet the following requirements: [________________________________]
☐ [________________________________]
☐ [________________________________]
Technical Assumptions:
☐ Existing systems are compatible with proposed solution architecture.
☐ Current data formats and quality are suitable for project requirements.
☐ [________________________________]
☐ [________________________________]
Resource Assumptions:
☐ Client personnel identified in Section 5.2 will be available as specified.
☐ Service Provider can access Client premises during normal business hours: [________________________________]
☐ [________________________________]
7.2 Dependencies
| Dependency ID | Description | Owner | Required By | Impact if Not Met |
|---|---|---|---|---|
| DEP-001 | [________________________________] | [________] | [__/__/____] | [________________________________] |
| DEP-002 | [________________________________] | [________] | [__/__/____] | [________________________________] |
| DEP-003 | [________________________________] | [________] | [__/__/____] | [________________________________] |
| DEP-004 | [________________________________] | [________] | [__/__/____] | [________________________________] |
| DEP-005 | [________________________________] | [________] | [__/__/____] | [________________________________] |
7.3 Client-Provided Items
Client shall provide the following items at no cost to Service Provider:
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
☐ [________________________________]
8. CHANGE ORDER PROCESS
8.1 Change Request Procedure
8.1.1 Either party may request changes to scope, schedule, or budget by submitting a written Change Request.
8.1.2 Change Requests shall be submitted to:
Client Change Request Contact: [________________________________]
Service Provider Change Request Contact: [________________________________]
8.1.3 Each Change Request shall include:
☐ Description of proposed change
☐ Reason for the change
☐ Impact on scope, schedule, and budget
☐ Alternatives considered
☐ Recommended approach
8.2 Change Request Evaluation
8.2.1 Service Provider shall evaluate each Change Request and provide a Change Impact Assessment within [____] business days.
8.2.2 The Change Impact Assessment shall include:
☐ Detailed description of work required
☐ Schedule impact (additions or reductions)
☐ Cost impact (additions or reductions)
☐ Resource requirements
☐ Risk implications
8.3 Change Order Approval
8.3.1 No work on a Change Request shall begin until a Change Order is executed by both parties.
8.3.2 Change Orders must be signed by authorized representatives:
Client Authorized Signatory: [________________________________]
Service Provider Authorized Signatory: [________________________________]
8.3.3 Emergency changes may be authorized verbally by the above signatories, followed by written confirmation within [____] business days.
8.4 Change Order Log
| CO Number | Description | Submitted | Approved | Schedule Impact | Cost Impact |
|---|---|---|---|---|---|
| CO-001 | [________________________________] | [__/__/____] | [__/__/____] | [____] days | $[________] |
| CO-002 | [________________________________] | [__/__/____] | [__/__/____] | [____] days | $[________] |
| CO-003 | [________________________________] | [__/__/____] | [__/__/____] | [____] days | $[________] |
9. RISK MANAGEMENT
9.1 Identified Risks
| Risk ID | 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 | [________________________________] | [________] |
| R-004 | [________________________________] | ☐ High ☐ Med ☐ Low | ☐ High ☐ Med ☐ Low | [________________________________] | [________] |
| R-005 | [________________________________] | ☐ High ☐ Med ☐ Low | ☐ High ☐ Med ☐ Low | [________________________________] | [________] |
9.2 Risk Monitoring
9.2.1 Risks shall be reviewed at each project status meeting.
9.2.2 New risks shall be documented and assessed within [____] business days of identification.
9.2.3 Risk status shall be reported in weekly/monthly project status reports.
9.3 Contingency
A contingency of [____]% of the total project value ($[________________________________]) is allocated for risk mitigation. Use of contingency funds requires written approval from both parties.
10. PROJECT GOVERNANCE
10.1 Project Organization
Executive Sponsor (Client): [________________________________]
Executive Sponsor (Service Provider): [________________________________]
Project Manager (Client): [________________________________]
Project Manager (Service Provider): [________________________________]
10.2 Decision-Making Authority
| Decision Type | Client Authority | Service Provider Authority |
|---|---|---|
| Scope Changes | [________________________________] | [________________________________] |
| Budget Changes (under $[____]) | [________________________________] | [________________________________] |
| Budget Changes (over $[____]) | [________________________________] | [________________________________] |
| Schedule Changes | [________________________________] | [________________________________] |
| Resource Changes | [________________________________] | [________________________________] |
| Technical Decisions | [________________________________] | [________________________________] |
10.3 Communication Plan
| Meeting Type | Frequency | Participants | Purpose |
|---|---|---|---|
| Status Meeting | [________________________________] | [________________________________] | Progress review and issue resolution |
| Steering Committee | [________________________________] | [________________________________] | Executive oversight and escalation |
| Technical Review | [________________________________] | [________________________________] | Technical decisions and architecture |
| [________________________________] | [________________________________] | [________________________________] | [________________________________] |
10.4 Reporting Requirements
Service Provider shall provide the following reports:
☐ Weekly Status Report: Progress, issues, risks, upcoming activities
☐ Monthly Executive Summary: High-level progress, budget status, key decisions needed
☐ Milestone Completion Report: Deliverable status and acceptance documentation
☐ [________________________________]
10.5 Escalation Procedure
| Level | Timeframe | Client Contact | Service Provider Contact |
|---|---|---|---|
| 1 - Project Manager | [____] days | [________________________________] | [________________________________] |
| 2 - Director/VP | [____] days | [________________________________] | [________________________________] |
| 3 - Executive | [____] days | [________________________________] | [________________________________] |
10.6 Issue Resolution
10.6.1 Issues shall be logged in a shared issue tracking system.
10.6.2 Each issue shall be assigned an owner and target resolution date.
10.6.3 Unresolved issues shall be escalated per Section 10.5.
11. WARRANTY
11.1 Warranty Period
Service Provider warrants all Deliverables for a period of [____] days / [____] months from the date of final acceptance ("Warranty Period").
11.2 Warranty Coverage
During the Warranty Period, Service Provider warrants that:
☐ All Deliverables shall conform to the specifications and acceptance criteria set forth in this SOW.
☐ All Deliverables shall be free from material defects in design and workmanship.
☐ Services shall be performed in a professional and workmanlike manner consistent with industry standards.
☐ All work shall comply with applicable laws and regulations.
☐ [________________________________]
11.3 Warranty Remedies
11.3.1 Client shall notify Service Provider in writing of any warranty claim within [____] business days of discovery.
11.3.2 Service Provider shall acknowledge receipt of warranty claim within [____] business days.
11.3.3 Service Provider shall, at its sole discretion:
☐ Repair the defective Deliverable; or
☐ Replace the defective Deliverable; or
☐ Re-perform the defective services.
11.3.4 Warranty repairs shall be completed within [____] business days of notification.
11.3.5 Warranty services shall be provided at no additional cost to Client.
11.4 Warranty Exclusions
This warranty does not cover defects caused by:
☐ Modifications made by Client or third parties without Service Provider's written consent
☐ Misuse, abuse, or negligence by Client
☐ Client's failure to follow documented procedures or specifications
☐ Hardware, software, or systems not provided by Service Provider
☐ Force majeure events
11.5 Extended Warranty
☐ Extended warranty is not available.
☐ Extended warranty is available for an additional fee of $[________________________________] per [____] months.
12. WISCONSIN GOVERNING LAW AND DISPUTE RESOLUTION
12.1 Choice of Law
This Statement of Work and any disputes arising hereunder shall be governed by and construed in accordance with the laws of the State of Wisconsin, without regard to its conflict of laws principles. To the extent applicable, this SOW shall be interpreted consistent with:
- Wisconsin Uniform Commercial Code (Wis. Stat. Chapters 401-411)
- Wisconsin Statute of Frauds (Wis. Stat. § 241.02)
- Wisconsin Uniform Electronic Transactions Act (Wis. Stat. §§ 137.11-137.26)
12.2 Venue and Jurisdiction
The parties consent to exclusive jurisdiction and venue in the state and federal courts located in [________________________________] County, Wisconsin for any legal action arising under this SOW.
12.3 Dispute Resolution
12.3.1 Negotiation: The parties shall first attempt to resolve any dispute through good faith negotiations between the Project Managers within [____] business days.
12.3.2 Escalation: If unresolved, the dispute shall be escalated to executive representatives who shall meet within [____] business days.
12.3.3 Mediation: If still unresolved, the parties agree to submit the dispute to non-binding mediation administered by [________________________________] before pursuing litigation.
☐ 12.3.4 Arbitration (Optional): In lieu of litigation, the parties may elect binding arbitration administered by the American Arbitration Association under its Commercial Arbitration Rules, with arbitration to take place in [________________________________], Wisconsin.
12.4 Continuation of Performance
During any dispute resolution process, both parties shall continue to perform their obligations under this SOW unless performance is the subject of the dispute.
12.5 Attorneys' Fees
In any action to enforce this SOW, the prevailing party shall be entitled to recover reasonable attorneys' fees and costs from the non-prevailing party.
13. DATA PROTECTION AND SECURITY
13.1 Confidential Information
All non-public information exchanged under this SOW shall be treated as confidential. Both parties shall implement reasonable safeguards to protect confidential information.
13.2 Data Breach Notification
In accordance with Wis. Stat. § 134.98, Service Provider shall notify Client within [____] hours of discovering any unauthorized acquisition of personal information of Wisconsin residents. Notification shall include:
☐ Description of the incident
☐ Types of personal information involved
☐ Steps taken to address the breach
☐ Contact information for inquiries
13.3 Data Handling Requirements
☐ Service Provider shall comply with Client's data security policies.
☐ All Client data shall be stored and processed within the United States.
☐ Service Provider shall encrypt all Client data in transit and at rest.
☐ Upon project completion, Service Provider shall return or destroy all Client data as directed.
14. ELECTRONIC SIGNATURES
14.1 Validity of Electronic Signatures
Pursuant to the Wisconsin Uniform Electronic Transactions Act (Wis. Stat. §§ 137.11-137.26), the parties agree that this SOW and any amendments, Change Orders, or other documents related hereto may be executed by electronic signature. Electronic signatures shall have the same legal effect as original handwritten signatures.
14.2 Electronic Record Retention
Records related to this SOW may be retained in electronic form in accordance with Wis. Stat. § 137.20, provided such records accurately reflect the information and remain accessible for later reference.
15. ADDITIONAL TERMS
15.1 Relationship to Master Agreement
☐ This SOW is governed by the Master Services Agreement dated [__/__/____] between the parties. In the event of conflict, the Master Agreement shall control unless this SOW expressly states otherwise.
☐ This SOW is a standalone agreement and constitutes the entire agreement between the parties with respect to the services described herein.
15.2 Order of Precedence
In the event of conflict among documents, the following order of precedence shall apply:
- Change Orders (in reverse chronological order)
- This Statement of Work
- Master Services Agreement (if applicable)
- Exhibits and Attachments
15.3 Insurance Requirements
Service Provider shall maintain the following insurance coverage:
| Coverage Type | Minimum Amount |
|---|---|
| Commercial General Liability | $[________________________________] |
| Professional Liability/E&O | $[________________________________] |
| Workers' Compensation | Statutory limits |
| Cyber Liability | $[________________________________] |
15.4 Compliance with Laws
Both parties shall comply with all applicable federal, state, and local laws and regulations, including but not limited to Wisconsin employment laws, tax laws, and licensing requirements.
EXHIBITS
☐ Exhibit A: Deliverable Acceptance Form
☐ Exhibit B: Change Order Form
☐ Exhibit C: Detailed Technical Specifications
☐ Exhibit D: Project Schedule (Gantt Chart)
☐ Exhibit E: Rate Card
☐ Exhibit F: [________________________________]
SIGNATURE BLOCK
By signing below, the parties agree to be bound by the terms and conditions of this Statement of Work.
CLIENT
Signature: [________________________________]
Printed Name: [________________________________]
Title: [________________________________]
Date: [__/__/____]
SERVICE PROVIDER
Signature: [________________________________]
Printed Name: [________________________________]
Title: [________________________________]
Date: [__/__/____]
ACKNOWLEDGMENT OF RECEIPT
Client Project Manager Acknowledgment:
I acknowledge receipt of this Statement of Work and confirm that I have the authority to commit Client resources as specified herein.
Signature: [________________________________]
Printed Name: [________________________________]
Date: [__/__/____]
Service Provider Project Manager Acknowledgment:
I acknowledge receipt of this Statement of Work and confirm that I have reviewed and understand all requirements, deliverables, and timelines specified herein.
Signature: [________________________________]
Printed Name: [________________________________]
Date: [__/__/____]
DISCLAIMER: This Statement of Work template is provided for informational purposes only and does not constitute legal advice. Wisconsin contract law has specific requirements that may affect the enforceability of this agreement. The parties are strongly encouraged to consult with attorneys licensed in Wisconsin to ensure compliance with all applicable laws and to tailor this document to their specific needs and circumstances.
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: February 2026