# Recording script: Review the change before it ships

Content version `0.1.0+20261119T221256Z` · Draft for professional review

Estimated narration: approximately 8 minutes, based on the written script. This is not measured media runtime. No audio, video, or timed captions have been produced.

## change-review-01 · Review the change before it ships

Welcome. In this short field lab, we will practice a useful handoff when a payment-related change is proposed. We will not decide whether a system is in scope or whether a requirement applies. Instead, we will make the change understandable: what is different, which facts need confirmation, what records may need attention, and who should evaluate the impact. Our example is fictional. Use the process to improve questions and coordination, then use the actual environment, current PCI DSS text, and the responsible parties for any real determination.

## change-review-02 · A change is a signal to look closer

A change ticket is an invitation to ask what else may need review. Start with a clear description of the current state and the proposed state. Mark what is confirmed, what came from a proposal, and what is still unknown. The goal is not to label the change as significant or insignificant from a title alone. PCI DSS Requirement 12.5.2 addresses documenting and confirming scope at least every twelve months and upon significant change to the in-scope environment. Whether a particular change is significant depends on the environment and the applicable requirements. This field lab gives you a way to prepare the facts for the people responsible for that evaluation.

## change-review-03 · Build the change picture

Gather the change facts before forming a view. What business capability is being introduced? Which channels are affected? How is account data entered, transmitted, stored, or otherwise handled in the proposed design? Which systems and connections are new or changed? Which provider service is involved, and what does the service actually do? What supporting infrastructure or responsibility information may need attention? Requirement 12.5.2 lists minimum elements for scope validation, including payment data flows and channels, account-data locations, system components, segmentation controls, and third-party connections. This is a preparation conversation, not a replacement for the full requirement or its testing procedures. Use current source records and note uncertainty explicitly.

## change-review-04 · Notice common change signals

PCI SSC FAQ 1317 describes examples included in the significant-change definition: new or replaced hardware, software, or networking equipment in the CDE; changes in the flow or storage of account data; boundary or assessment-scope changes; changes to supporting infrastructure; and changes to relevant third-party providers or services. The FAQ also explains that significance depends on the configuration of the particular environment and that the listed activities have potential impact and must be considered in context. Treat these as signals to investigate. Do not use a checklist result to declare that a change is or is not significant. Record which facts support the review and who is responsible for the conclusion.

## change-review-05 · Practice with a fictional proposal

Harbor Learning plans to add subscription billing. A proposal names a new hosted payment service. A provider contact says card details are tokenized, but the statement is not yet tied to Harbor’s exact configuration. The current flow diagram only shows one-time payments. What should the team do next? It should verify the consumed service, payment stages and channels, data entry and transmission, any storage, system connections, and the evidence behind the provider statement. It should identify the diagram owner and the person responsible for the impact review. The team should not declare the service out of scope because the page is hosted, or in scope because a provider is named. The facts are incomplete; the handoff should make that visible.

## change-review-06 · Write a handoff another person can use

A useful handoff is short enough to read and specific enough to act on. Name the change, the business owner, and the proposed timing. Describe the current and proposed payment flow using source records rather than assumptions. List systems, services, providers, connections, and supporting dependencies that may be affected. For every unknown, name the question and the person or record that can answer it. Identify the accountable reviewer and the next action. A tracker can help coordinate this work; it is not evidence that the review is complete. Keep sensitive data out of shared training materials and public channels. For a real project, follow the organization’s approved data-handling practices.

## change-review-07 · Close the loop after the change

The review should end with an owned next step, not an untracked conversation. Requirement 12.5.2 states that scope is documented and confirmed at least once every twelve months and upon significant change to the in-scope environment. Requirement 6.5.2 separately addresses completion of a significant change: applicable requirements are confirmed to be in place on new or changed systems and networks, and documentation is updated as applicable. Do not collapse these provisions into one blanket workflow or assume every change triggers identical work. Follow the exact applicable requirements, their notes, the system facts, and the assessment instructions. Record what the authorized reviewer concluded and which follow-up remains open.

## change-review-08 · The useful next step is a clear question

Choose the response that best supports a responsible review. A is not supported: hosting alone does not establish the result. C delays a question that may need attention as part of the proposed change. B makes the information gap visible, asks for source-backed details, and assigns the impact review to the accountable owner. The answer is not a scope conclusion; it is a better next step. Take one proposed payment change from your own environment and write a three-line handoff: what is changing, what facts remain unverified, and who owns the next review. Keep the system’s actual facts and the current PCI DSS source in view. This lesson is a preparation aid, not a compliance determination.

## Pronunciation and production notes

- CDE: say “cardholder data environment” on first use.
- PCI DSS: say “P-C-I D-S-S.”
- TPSP: avoid this abbreviation; say “third-party service provider.”
- Requirement IDs: say “Requirement 12 point 5 point 2” and “Requirement 6 point 5 point 2.”
- The generated artwork is conceptual. Explain that it is not an environment diagram.
- Produce VTT captions only after the actual recording exists; review timing against the exported MP4.
