A copy change needs an exact list of affected pages

Turn the requested correction into a visible boundary

Start with the actual request and the current public page. Record the full public URL, the heading or other location of the text, its current wording and the approved replacement or precise factual correction. A page title alone can identify several versions; a request such as update the policies does not identify which sentences may change. Include language or page variants only when they are part of the real request.

Separate wording that is ready to publish from wording that the writer is being asked to propose. For proposed wording, name the person who will approve the final text and retain the version that person approves. The release scope should distinguish permission to draft from permission to publish. PRISM's How it works page places the choice of updates with the merchant after the consultation defines the pages and questions.

Trace shared text before deciding the affected URL list

Ask the site maintainer where the named text is stored: on that page, in a reusable component or template, or in another shared content setting. Use the actual installation to answer this. Matching words on two pages do not prove that editing one will change the other, and a single editable field can have more public placements than the original request names.

For each shared dependency, list the actual consuming pages or attach an explicit URL inventory. Give every affected placement an outcome: approved to change, protected from this release, or unresolved. If the same source supplies both approved and protected pages, ask the maintainer whether the requested limited change can be made without changing the protected placements. Any work needed to separate them must be included in the agreed scope before it becomes part of this release.

Avoid a sitewide search-and-replace instruction unless its entire reach has been examined and approved. A repeated phrase may occur in a policy, a navigation label and an article for different reasons. The correction needs the context of each occurrence, not just a matching string.

Name the things a wording edit must preserve

Record the protected route, links, original artwork, layout and any relevant checkout controls alongside the approved text change. Identify actual elements rather than adding a general instruction to keep everything else the same. Text in an image is a separate dependency: editing adjacent page copy will not correct those pixels, and replacing the image needs an explicit decision about that asset.

A longer replacement can also change how a page reads at its existing widths. Include readable wrapping and the continued visibility of nearby links or controls in the acceptance comparison. If the correction cannot fit without a layout change, return that specific issue to the approval owner. This gives the merchant a concrete choice about the extra work instead of allowing a wording request to expand silently into a redesign.

Where a provider requested the correction, preserve the provider's exact question and keep it distinct from the merchant's publication approval. A finding about website content is informational; PRISM's features page does not describe it as legal certification or processing approval.

Accept the release against the same list

Compare the delivered wording with the approved version on every affected URL. Check protected shared placements as well as the requested page, and record any unexpected change against the element it affects. A successful correction has both a confirmed replacement and a documented preservation result. An unexamined page remains unexamined; a changed shared component does not justify marking the entire site reviewed.

For a scoped PRISM checkout-review consultation, bring the website, the research-only products, the correction you want and the shared dependency that makes its reach uncertain. Confirm writing, implementation, reporting and follow-up responsibilities, fees and terms before work. The public form receives an inquiry followed up by email; it does not book an appointment, purchase work or submit a processing application.

Content release scope

Complete one copy for each requested correction. Keep the URL inventory with this record. A correction is ready to assign when its wording, shared reach, protected elements and approval owner are explicit; unresolved shared reach remains a scope question.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.