# NoticeKit AI Vendor Disclosure Packet Template

Use this template when a buyer, procurement reviewer, security reviewer, or counsel asks for a cleaner explanation of your AI vendor stack, what changed, whether notice is required, and where the proof lives. It is an operational handoff aid, not legal advice.

## 1. Packet Snapshot

| Field | Notes |
| --- | --- |
| Company |  |
| Product or workflow reviewed |  |
| Review owner |  |
| Packet date |  |
| Planned effective date |  |
| Review request source |  |
| Procurement, security, counsel, or renewal |  |

## 2. Current AI Vendor Stack

| Vendor | Purpose | Data categories | Region or transfer context | Status |
| --- | --- | --- | --- | --- |
|  |  |  |  | Active / Planned / Replacing / Removed |
|  |  |  |  |  |
|  |  |  |  |  |
|  |  |  |  |  |

## 3. What Changed

| Question | Notes |
| --- | --- |
| New vendor, replacement, region change, or scope expansion? |  |
| Why is the change happening? |  |
| Which product area is affected? |  |
| Which existing vendor or workflow is being replaced? |  |
| What customer or user data may be involved? |  |
| What still needs confirmation? |  |

## 4. Customer Scope And Notice Logic

| Segment | Accounts or contract class | DPA or agreement version | Notice required? | Notice window | Contact route |
| --- | --- | --- | --- | --- | --- |
|  |  |  | Yes / No / Review |  |  |
|  |  |  |  |  |  |
|  |  |  |  |  |  |

## 5. Reviewer Questions To Answer Fast

- Which vendors power the AI feature, hosting, analytics, support, auth, and billing flow?
- Which customers are actually affected by the vendor change?
- Does the public vendor list match the live production stack?
- Is direct customer notice required, or is the packet still waiting on contract review?
- Who owns send, objections, proof capture, and closeout?

## 6. Proof Trail

| Evidence item | Link or location | Owner | Complete? |
| --- | --- | --- | --- |
| Current public vendor page |  |  | [ ] |
| Updated draft vendor page |  |  | [ ] |
| Draft customer notice |  |  | [ ] |
| Archived screenshot or page capture |  |  | [ ] |
| Tracker row or internal ticket |  |  | [ ] |
| Security or procurement notes |  |  | [ ] |
| Open legal or privacy questions |  |  | [ ] |
| Final closeout note |  |  | [ ] |

## 7. Decision And Next Step

| Decision | Owner | Due date | Notes |
| --- | --- | --- | --- |
| Approve current packet |  |  |  |
| Revise vendor facts or customer scope |  |  |  |
| Draft or revise notice copy |  |  |  |
| Escalate to counsel or privacy advisor |  |  |  |
| Hold change until missing proof lands |  |  |  |

## 8. Handoff Summary

Use this short summary at the top of the review thread:

> We are reviewing one AI vendor change affecting `{{segment}}`. The packet below includes the current stack, the proposed change, notice timing, proof links, and the open questions that still need approval before the change goes live.