---
tool_id: WACK-TOOL-0026
concept_id: WACK-CONCEPT-0012
playbook_content_id: WACK-CONTENT-0106
status: draft
technical_review: pending
artifact_type: working_worksheet
---

# Year-End PCI Readiness Countdown

> Work backward from the real acceptance date before reduced availability turns ordinary questions into January blockers.

**Expected output:** A dependency-aware countdown with last responsible dates, owner coverage, evidence and review milestones, exception paths, and reopen triggers.  
**Working time:** 90 minutes  
**Derived from:** WACK-CONTENT-0106

## Working context

Organization / environment: __________________________________________  
Facilitator / owner: __________________________________________________  
Participants: _________________________________________________________  
Date: ____________________  Review trigger or next date: ______________

## 01 / Find — Start with the real finish line

Work backward from the date the compliance-accepting entity needs the completed package.

- [ ] **What review, correction, approval, and processing time must exist before that date?**

  Notes: ________________________________________________

- [ ] **Which recurring, change-triggered, remediation, or evidence-refresh clocks mature during reduced availability?**

  Notes: ________________________________________________

## 02 / Map — Build the countdown

Give every remaining claim and deliverable a last responsible date.

- [ ] **Which owner, delegate, input, output, and external dependency does each item require?**

  Notes: ________________________________________________

- [ ] **Which provider, ASV, tester, assessor, or approver lead time constrains the schedule?**

  Notes: ________________________________________________

## 03 / Explain — Separate the clocks

Keep authoritative obligations, entity dates, assessment milestones, and preferences distinct.

- [ ] **What makes each date binding, and who owns it?**

  Notes: ________________________________________________

- [ ] **What is the honest disposition if the date or underlying control window is missed?**

  Notes: ________________________________________________

## 04 / Reduce — Clear the fragile joins

Resolve work that consumes scarce people before availability narrows.

- [ ] **Which scope, provider, evidence, and exception questions can close now?**

  Notes: ________________________________________________

- [ ] **Which duplicate approval, oversized claim, or unnecessary handoff can be removed?**

  Notes: ________________________________________________

## 05 / Prove — Run the landing-zone review

Demonstrate a coherent baseline and an explicit path for change.

- [ ] **Does every material claim have an owner, delegate, evidence contract, review path, and exception path?**

  Notes: ________________________________________________

- [ ] **Which changes or new facts reopen the baseline, and who can act during the slowdown?**

  Notes: ________________________________________________

## Completion check

- [ ] The real acceptance date and each last responsible date are explicit.
- [ ] Every critical role has named availability or delegated coverage.
- [ ] Recurring obligations remain tied to their actual windows.
- [ ] The landing zone has a governed change and reopening path.

## Decision and next action

Decision: _____________________________________________________________  
Owner: __________________________  Due date: ___________________________  
Evidence or artifact location: ________________________________________

---

_Working practitioner worksheet pending technical review. It does not determine PCI DSS compliance, replace the standard, or replace instructions from an assessor or compliance-accepting entity. The Cluster of Wack is an independent resource and is not affiliated with or endorsed by PCI SSC._