TRUST ATLAS WORKSHEET
Change log
PCI DSS · Step 4 · Maintain scope and monitoring- Who prepares it
- Payments operations
- When to prepare it
- Ongoing
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Record ID
- REQ-022
- Event and date
- Verified access request received 2026-11-07 UTC
- Owner and target
- Privacy operations, internal review by 2026-11-23
- Decision and status
- Approved response, sent securely
- Completion evidence
- Case delivery record, 2026-11-24
- Follow-up
- None, approved by the reviewer
Gather first
- Case, change or communication records
- Required fields and timing
- Named case owner and authorized recipients
How to prepare it
- Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
- Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
- Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.
Review
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Handoff
Use the log at case reviews and provide a restricted copy only where the engagement requires it.