A working preview is not evidence of a completed live release

Start with the address that was actually observed

Open the delivery receipt alongside the agreed scope. Identify whether the vendor promised a preview, files for later integration, or a released change on the public store. Then locate the address used in the demonstration and the date it was observed. A cropped screenshot that omits the address leaves the environment unidentified, however complete the page looks.

Compare the shown address with the intended public address. Ask the implementer to identify the installation serving each one and any access restriction that affected the demonstration. A familiar logo or copied catalog does not establish that two addresses are the same installation. If the receipt shows only a local or preview address, mark the demonstrated work as preview evidence; do not rewrite it as a live observation.

Record service connections separately from appearance

For each behavior claimed in the delivery, record which service the shown installation uses. Payment processing, order records and outgoing messages need their own connection evidence when they are part of the agreed scope. Record the environment and an authorized account label, together with where the implementer verified the connection. Do not copy credentials, customer records or private access links.

WooCommerce provides a concrete reason not to infer the payment environment from a troubleshooting label. Its Health Check guidance says troubleshooting mode does not put the payment gateway into sandbox mode; an order placed there can still take a live payment. A view that differs from what ordinary visitors see can therefore retain a live payment connection. Do not place an order merely to establish the environment. Use the configuration and existing records available to the authorized owner.

Match the release claim to evidence at the destination

For a live-delivery claim, look for evidence that identifies the delivered version, the intended public address and the time the change reached that destination. Compare that release record with a dated observation of the agreed behavior at the public address. The release record connects the work to a destination; the observation shows what that destination actually served. A preview demonstration supplies neither connection by itself.

Keep the scope of each observation narrow. Seeing the revised page confirms its visible content at that address and time. It does not confirm a payment, an order handoff or an email delivery unless the matching records were also examined. If those operations were included in the agreement but were not verified, list them as outstanding live requirements. An existing genuine operational record may supply evidence; its absence should remain visible rather than be filled with an invented transaction.

Write an acceptance record with separate completion states

For each agreed deliverable, state what was observed in the preview, what was released to the public store, and what remains unverified there. If the contract only called for a preview, accepting that milestone can be accurate. If it called for a live release, the same evidence supports only partial delivery until the destination and required behavior are established. This comparison does not decide a contractual dispute or create additional work outside the agreement.

Assign an owner to each missing live requirement and name the evidence that would close it. For a Prism checkout-review consultation, summarize the website, the research-only products and the specific difference between the delivery claim and the evidence. Prism discusses scope, responsibilities, fees and terms before work; the merchant chooses changes and the provider decides processing eligibility. The public form starts an inquiry followed up by email, not a booked appointment, purchase or processing application.

Delivery environment record

Complete one record for each claimed deliverable. Compare source records privately and enter only public addresses, non-sensitive environment labels and findings. Unknown means the live claim is still unverified, not that the feature necessarily failed.

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.