Sample artifact
Sample AIVER Approval Pack
This is a public sample showing the type of buyer-controlled approval record ChaseDesk creates. It is not a certification, legal opinion, audit, or security assessment.
Review ID: AIVER-2026-0147
Boundary: ChaseDesk structures vendor evidence and review records. The enterprise remains the decision-maker.
VendorExample Support Agent Vendor
Lifecycle eventRenewal + production expansion
Decision statusConditional approval pending evidence
Next review90 days after production rollout
Executive approval summary
The vendor may proceed only if open evidence conditions are resolved or accepted by the buyer’s relevant approval owners. Data retention, model-provider training terms, and escalation monitoring remain open.
Claim-versus-evidence map
| Vendor claim | Evidence submitted | Status | Owner | Approval consequence |
|---|---|---|---|---|
| No training on buyer customer data | Privacy policy + DPA excerpt | Needs review | Privacy | Contract clause required |
| Human escalation for high-risk issues | Escalation workflow | Missing SLA | CX | Condition before rollout |
| SOC 2 available | SOC 2 report | Provided | Security | Scope review required |
| Incident process exists | Incident-response policy | Review | Security / CX | Customer-impact notice unclear |
Open approval conditions
| Condition | Required owner | Required before |
|---|---|---|
| Confirm model-provider training and retention terms. | AI Governance / Privacy | Signature |
| Attach support escalation SLA and fallback process. | Enterprise CX | Production rollout |
| Confirm SOC 2 report scope covers the relevant product and subprocessors. | Security | Signature |
Required contract notes
Approval should be conditioned on evidence submission, Review ID attachment, re-review on material model, data-use, incident, subcontractor, jurisdiction, or deployment-scope change, and renewal review before expiry.
Back to ChaseDesk