---
tool_id: WACK-TOOL-0015
concept_id: WACK-CONCEPT-0010
playbook_content_id: WACK-CONTENT-0095
status: draft
technical_review: pending
artifact_type: working_worksheet
---

# Assessment Claim Ledger

> Turn every proposed assessment result into a bounded, testable, reconstructable claim before artifacts become conclusions.

**Expected output:** A claim-to-testing-and-evidence ledger with populations, periods, owners, exceptions, dispositions, and report lineage.  
**Working time:** 75 minutes  
**Derived from:** WACK-CONTENT-0095

## Working context

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

## 01 / Find — State the claim

Replace status shorthand with the exact assertion being evaluated.

- [ ] **What subject, environment, period, expected condition, and result does this claim cover?**

  Notes: ________________________________________________

- [ ] **Which words could different participants interpret as a larger or smaller boundary?**

  Notes: ________________________________________________

## 02 / Map — Bind claim to test and population

Connect the assertion to the prescribed work and complete population.

- [ ] **Which requirement, testing procedure, reporting field, population, and sampling rationale apply?**

  Notes: ________________________________________________

- [ ] **Which evidence items, owners, systems, and dates cover the population?**

  Notes: ________________________________________________

## 03 / Explain — Qualify the conclusion

Make evidence relevance and limitations visible.

- [ ] **Why is the evidence direct, timely, scope-specific, and sufficient for this claim?**

  Notes: ________________________________________________

- [ ] **Which exceptions, contradictions, or missing periods qualify the result?**

  Notes: ________________________________________________

## 04 / Reduce — Shrink claim debt

Split oversized assertions and remove unsupported artifact reuse.

- [ ] **Which claim should be divided by system, population, period, or control behavior?**

  Notes: ________________________________________________

- [ ] **Which repeated evidence request can be replaced with one governed source and explicit lineage?**

  Notes: ________________________________________________

## 05 / Prove — Retain the chain

Make the result reconstructable without team memory.

- [ ] **Where are the claim, representation, test, evidence, exception disposition, reviewer, and report reference retained?**

  Notes: ________________________________________________

- [ ] **What change or new evidence automatically reopens the result?**

  Notes: ________________________________________________

## Completion check

- [ ] Every result has a precise claim and complete population.
- [ ] Evidence sufficiency is explained rather than assumed.
- [ ] Every exception and reopening trigger is 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._