---
tool_id: WACK-TOOL-0008
concept_id: WACK-CONCEPT-0017
playbook_content_id: WACK-CONTENT-0057
status: draft
technical_review: pending
artifact_type: working_worksheet
---

# Representative Sample Storyboard

> Put population completeness and meaningful variation before evidence convenience.

**Expected output:** A population snapshot and variant analysis ready to support the assessor’s sampling methodology.  
**Working time:** 45 minutes  
**Derived from:** WACK-CONTENT-0057

## Working context

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

## 01 / Find — Establish the population

Define what should be tested before discussing sample candidates.

- [ ] **What is the intended population for the testing procedure?**

  Notes: ________________________________________________

- [ ] **Which authoritative sources establish completeness, and how were differences reconciled?**

  Notes: ________________________________________________

## 02 / Map — Identify meaningful variation

Describe differences that may change implementation or evidence.

- [ ] **Which locations, technologies, administrative models, business units, periods, acquisitions, or exceptions create variants?**

  Notes: ________________________________________________

- [ ] **Which characteristics are cosmetic, and which could change the control conclusion?**

  Notes: ________________________________________________

## 03 / Explain — Support the selection rationale

Preserve assessor ownership of methodology and final selection.

- [ ] **How does each proposed item represent relevant variants and boundaries?**

  Notes: ________________________________________________

- [ ] **What selection limitation, unavailable item, substitution, or newly found variant must be disclosed?**

  Notes: ________________________________________________

## 04 / Reduce — Make real variation visible

Standardize where appropriate without hiding differences.

- [ ] **Which naming or inventory inconsistency makes the population harder to understand?**

  Notes: ________________________________________________

- [ ] **Which implementation difference can be standardized before future testing?**

  Notes: ________________________________________________

## 05 / Prove — Retain the sample story

Keep population, method, selections, results, and exceptions together.

- [ ] **Where is the dated population snapshot and variant analysis retained?**

  Notes: ________________________________________________

- [ ] **How do failures or discoveries feed back into the sample and population-level conclusion?**

  Notes: ________________________________________________

## Completion check

- [ ] The population exists before selections.
- [ ] Relevant variants are explicit.
- [ ] The assessor’s methodology, rationale, and exceptions remain visible.

## 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._