QA and Testing Engagement Statement of Work Template

Count everything. A deliverable a client cannot count is a deliverable a client can expand.

1. 2.1A test strategy and test plan for the web application and its iOS and Android apps.
2. 2.2Up to 350 manual test cases covering the modules listed in Schedule A.
3. 2.3Up to 120 automated end-to-end tests with Playwright for web and Maestro for mobile, integrated into the client's CI.
4. 2.4Up to 4 full regression cycles and 8 smoke test cycles during the engagement.
5. 2.5Defect reports in the client's Jira with reproduction steps, evidence and severity.
6. 2.6A weekly quality report and a final test summary report.

Name what the engagement does not include. These are the lines your PMs will cite most often.

1. 3.1Performance, load, security and penetration testing.
2. 3.2Accessibility audits beyond automated checks.
3. 3.3Fixing defects in application code.
4. 3.4Testing on platforms, browsers or devices not in Schedule B.
5. 3.5Test data creation beyond the seed data sets agreed in the test plan.

The test plan includes one revision round. Test cases may be revised when requirements change, within the case cap. Rewriting automated tests because of UI changes made after the test was accepted counts against the change budget.

Acceptance needs a measurable test and a window. Without both, delivery never formally ends.

1. 5.1Test cases and automated tests are accepted after client review in each sprint.
2. 5.2Automated tests pass reliably (flake rate under 2% over 20 runs) on the client's CI.
3. 5.3Regression cycles are complete when every in-scope case has a recorded result.

Tie each dependency to a date so a late input has a known effect on the schedule.

1. 6.1Stable test environments and test accounts are available during cycles.
2. 6.2Builds arrive at agreed times. Late builds move the cycle, not the scope.
3. 6.3The client's team triages defects within two business days.

Extra cycles, new modules, platforms or test types, and test maintenance beyond the agreed budget are changes. The QA lead estimates hours and cost and notes timeline impact within two business days.