Scope of Testing
Define included modules, environments, test data, supported browsers/devices, and excluded items to avoid scope creep.
A written agreement reduces ambiguity about acceptance criteria, limits rework, and protects intellectual property and confidential test data.
This agreement is used by product owners, vendors, development teams, and procurement officers to manage acceptance testing and delivery risk.
Use formal sign-off and traceable evidence to avoid disputes over test results and payment triggers.
Typically responsible for coordinating test execution, documenting results, and certifying that acceptance criteria were met. The QA manager should have authority to attach test reports and sign off on behalf of the client or product owner.
An authorized representative of the software vendor or developer who can accept contractual obligations, commit to remediation timelines, and bind the vendor to warranty and support commitments described in the agreement.
Define included modules, environments, test data, supported browsers/devices, and excluded items to avoid scope creep.
Specify pass/fail thresholds, severity levels for defects, and objective metrics required for formal acceptance.
Set timelines for test execution, evidence submission, defect triage, and re-test cycles with clear milestones.
Describe defect fix SLAs, regression testing responsibilities, and dispute resolution for contested defect status.
Protect test data and preserve ownership or license terms for code, test artifacts, and derived results.
Limit damages, define warranty periods post-acceptance, and allocate risk for third-party dependencies.
| Field | Configuration |
|---|---|
| Document Format | PDF or DOCX with embedded test plan attachments. |
| Signer Order | Sequence: QA sign-off, vendor remediation, final executive approval. |
| Authentication | Email link or two-factor authentication for higher assurance. |
| Reminders | Automatic reminders every 3–7 days until sign-off. |
Choose a platform that supports legal eSignature standards, secure storage, and integrations needed by your workflow.
Ensure the platform retains an auditable certificate of completion and supports export in common archival formats.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies | Varies | Varies |
Start date for obligations and warranty counting
Dates when acceptance tests must be executed
Time allowed for fixes after defect report
Deadline for issuing final sign-off or rejection
Date when vendor warranties lapse
Vendor delivers software and test artifacts for QA review.
Client runs agreed tests and documents results within the test window.
Vendor fixes defects per SLAs; client verifies fixes.
Designated approver signs acceptance and payment triggers occur.
A mid-market SaaS vendor delivers a release with a defined test suite and environment credentials.
An enterprise vendor supplies an integration with payment systems and provides acceptance scripts.