Scope
Define inputs, outputs, permitted use cases, excluded uses, and deliverables with measurable acceptance criteria.
A clear document aligns technical teams, legal counsel, and business owners on risk allocation, data handling, intellectual property, and compliance obligations, reducing disputes and operational uncertainty.
Teams and individuals involved in procurement, deployment, or oversight typically complete or sign the document.
Signatures come from authorized business officers, technical leads, procurement managers, and legal representatives depending on authority and internal approval thresholds.
| Field | Configuration |
|---|---|
| Authentication | Email link | SMS code optional | KBA for high-risk |
| Field logic | Conditional fields enabled for optional exhibits |
| Notifications | CC internal approvers; send reminders at set intervals |
| Integrations | Connect to CRM or document repository for versioning |
Use platforms that accept common file formats and capture robust audit information.
Define inputs, outputs, permitted use cases, excluded uses, and deliverables with measurable acceptance criteria.
Specify encryption, access controls, retention schedules, and data-subject rights handling for regulated data.
Clarify ownership of training data, models, and derived outputs and any license grant or assignment.
List benchmarks, evaluation methods, and remediation steps for underperformance or drift.
Allocate risk for model failures, data breaches, and third-party claims, with caps and insurance requirements.
Describe update processes, versioning, validation testing, and rollback procedures for model changes.
A manifest describing data sources, labeling standards, access restrictions, and any de-identification applied to training or test sets.
Technical description of architecture, version, hyperparameters, training process, and expected performance on validation tests.
Concrete test scripts and pass/fail criteria used to validate model behavior prior to production.
Detailed encryption, key management, vulnerability testing, and incident response obligations tied to the agreement.
A small portfolio firm formalized data access limits and acceptance tests to bound vendor work.
A real estate operator used a technology annex to require model explainability for tenant-screening tools.
Specify start date (MM/DD/YYYY) and contract term or renewal mechanics
Define time allowed for validation tests and acceptance, e.g., 30 days
State required notice period, e.g., within 72 hours for data breaches
Schedule audits or model reviews, e.g., quarterly or annually
Specify notice period for termination, e.g., 30–90 days
| 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 plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |