Subprocessor evidence log template for SaaS teams
Use this when you need a compact record of what changed, who approved it, when notice went out, and where the proof lives.
This page helps you record evidence for a notice workflow. It does not decide whether a specific notice is required or sufficient under your agreements.
When to use this log
An evidence log is useful whenever a SaaS team adds a subprocessor, changes a service purpose, updates a processing region, or needs to show how the customer notice process was handled.
It is most useful after the notice is sent, when the team still needs to track objections, approvals, and page proof in one place.
Fields to capture
- Vendor name and public website.
- Service purpose and data categories.
- Customer segment or agreement source.
- Notice date and planned effective date.
- Objection deadline and notice window.
- Internal owner and reviewer.
- Status: draft, sent, waiting, objected, resolved, or closed.
- Proof link for the notice, page update, or archived copy.
Evidence log template
| Field | Example | Why it matters |
|---|---|---|
| Vendor | Acme Email Cloud | Identifies the third party that was added or changed. |
| Notice date | 2026-04-21 | Starts the customer notice window. |
| Objection deadline | 2026-05-21 | Shows when the review period closes. |
| Proof link | Archived email or screenshot | Lets the team answer customer or counsel questions later. |
Suggested log entry
Change: Added {{vendor_name}} as a subprocessor for {{service_purpose}}.
Affected segment: {{affected_customer_segment}}
Notice sent: {{notice_date}} via {{notice_method}}
Deadline: {{objection_deadline}}
Proof: {{proof_link}}
Status: {{status}}
Evidence to keep before closing
Close the record only after the team has saved the proof needed to explain the decision later.
- Final notice copy and recipient segment.
- Timestamp, sender, and delivery channel.
- Updated subprocessor page snapshot or archive.
- Objections received and their resolution notes.
- Internal approval note from privacy, legal, security, or leadership.
Common mistakes
Storing proof in too many places
Evidence gets lost when the page archive, sent email, and approval note are scattered across unrelated tools.
Leaving the status ambiguous
A log should show whether the change is still waiting, already closed, or still blocked by an objection.
Tracking only the vendor name
Teams often need the purpose, data categories, and customer segment to answer procurement questions later.
Closing before proof is saved
Archive the notice and page snapshot before the objection window closes so you do not have to recreate the record later.
Need the editable files?
NoticeKit Starter includes an evidence log, objection-window tracker, notice variants, and a subprocessor list template for one change.