UNLISTED REVIEW EDITIONPractice supplement · Draft · Not in public catalog
thrivePCI Site v0.43.62+20261122T201000Z · Published November 22, 2026

SUPPLEMENTARY PRACTICE · CONCEPT DRAFT 0.1.0

Pause for a moment.
Then make the request clear.

A short optional settling pause and a focused practice activity can help learners turn course ideas into useful work. This sample uses a warm Ember surface with Mist accents from the complementary palette set.

New draft for Scott's review. The current training review pass remains complete. This supplement was created afterward and has not been reviewed. Its example is fictional, generic, and not a PCI DSS interpretation. This unlisted, noindex page is not private or access-controlled.

Suggested time: 8 minutes · Format: individual reflection or small-group debrief · Relative-time convention: R = the date a request is received

01 ARRIVE

A one-minute settling pause

Participation is optional. Stay seated or stand in a comfortable position. Let your eyes rest on one neutral point or keep them open. Notice the support under your feet or chair. Let your shoulders soften if that feels comfortable. Take one ordinary, unforced breath, then return attention to the task in front of you.

There is no breathing target, breath hold, or health claim. Skip or adapt this pause whenever it does not feel useful.

02 MAKE IT ANSWERABLE

What would you clarify first?

"Please provide records supporting your team's process."

This fictional request is intentionally incomplete. It does not identify the process, covered population, requested period, acceptable record types, response format, accountable contact, or delivery deadline.

Separate known from unknown

Write down what the request actually says. List the missing context without filling gaps with assumptions.

Choose the next question

Select the smallest set of clarifications that would make the request answerable and route it to an owner.

Use relative time

For this mock exercise, use R for request received and describe the requested period relative to R. Do not treat example dates as requirement timing.

Open a facilitator debrief

A strong first response

"We can prepare a traceable response. Please confirm the process and population in scope, the period you want covered relative to R, the accepted evidence types and format, the delivery date, and the person coordinating follow-up. We will map the confirmed request to source records and identify gaps rather than infer missing facts."

What to notice

  • The learner distinguishes the request's words from their interpretation.
  • The period is clarified before records are selected.
  • Evidence is traced to a source and an accountable owner.
  • Unknowns remain visible instead of being silently guessed.
03 CONNECT TO THE COURSE

Use this as a pattern, not a fixed lesson

Once Scott provides the consolidated request list and its tranche groupings, each request can become its own short, source-backed learning unit. The same practice structure can support it while the scenario, source map, response boundaries, and answer key follow the actual request and supplied documentation.

  1. Restate the request and identify the request and tranche IDs.
  2. Explain the evidence purpose and map it to the authoritative supplied source.
  3. Practice locating, checking, and presenting a relevant record.
  4. Separate evidence gaps, scope questions, and accountable decisions.
  5. Debrief with a source-backed rationale and a next action.

Mock engagement timelines will use relative anchors such as R (request received), P (requested period), and D (response due). Example calendar dates will not drive the teaching point. Real source artifacts will retain their own metadata when that is necessary to understand them.

This is a design sample, not a released course, assessment tool, compliance determination, or claim that a particular record satisfies a PCI DSS requirement.

Return to the review hub