List the original artwork a content project must preserve
Identify each protected asset by its actual file or media reference and each place it appears, then record the visual properties that must survive the content change. Preserve both the original file and its agreed presentation: keeping the file while changing its crop, scale, position or surrounding layout can still alter the artwork visitors see. Give every proposed exception a precise permitted change and a named approval owner before assigning the work.
For: A research-only merchant commissioning writing or template work while retaining the storefront's existing original artwork.
Tie the visible artwork to the files actually in use
Open the current page and identify the artwork being protected. Record its public placement, file or media reference and the component or template that selects it, using the maintainer's knowledge of the actual site. A design name such as homepage hero is not enough when several files or responsive versions exist. Include the variants actually used at different widths or in different page states.
Keep a dated view of each relevant placement alongside the file reference. The view establishes what the merchant wants preserved; the file reference establishes which asset supplies it. One without the other leaves a gap. A screenshot is not an editable source file, and a source file on disk does not establish where or how the site displays it.
This record defines the preservation boundary for the current project. A wider request for original master files or a transfer of artwork rights is a separate handover question. Do not treat possession of a public image URL as evidence that every original source file or license has been delivered.
Define preservation as a set of observable properties
List the properties that matter for each actual placement: the selected file, crop, aspect ratio, scale, position, background, layering and relationship to adjacent text. Preserve embedded lettering and marks where present. If animation or several image variants are part of the existing work, record the specific behavior or variants that the merchant wants retained. Do not add properties that the current asset does not have.
A copy change can affect those relationships even when no one edits the image file. Longer text can occupy different space; a template change can select another asset or change its presentation. Ask the maintainer to identify which shared style or template controls the protected placement, and include other placements affected by that dependency in the record.
Avoid a vague permission to optimize the image. If the merchant permits a file-format, size or other change, describe that exact exception and the visual result that must remain. If no replacement or modification is approved, record that explicitly. Where the requested wording and protected layout cannot both be retained, present the conflict to the owner as a scope decision before changing either.
Keep preservation evidence separate from recovery claims
Retain the original asset files and the relevant placement configuration in the recovery material agreed for the project. For WordPress, its backup guidance says a typical complete restoration needs both the database and files as a consistent set. Copying the WordPress directory ordinarily does not copy the database. A folder of images therefore does not by itself preserve a complete restorable site.
Record the actual backup scope and date, who can retrieve it and who may authorize restoration. WordPress files can include themes, plugins, uploads and configuration; identify what the retained copy actually contains rather than assuming a host's backup offering covers it all. A promise of backups does not establish the account's retention, retrieval time or recoverability.
Use existing genuine recovery evidence if available and identify any unverified part plainly. Do not claim a restoration was tested when it was not. If recovery later becomes necessary, the authorized owner must account for the current store and any newer operating records; this artwork inventory is not permission to overwrite a live store with an older database.
Accept the content change and preserved artwork separately
Compare the delivered page with the dated reference at the same relevant widths and states. Confirm the intended asset is still selected and the listed visual properties remain as agreed. Check every protected placement affected by a shared template change. Matching file bytes alone cannot prove that placement is unchanged, while an apparently similar screenshot cannot prove that the original file remains recoverable.
Record the owner's decision for each item: preserved as agreed, changed under a named approval, or unresolved with a specific difference. A correction to the copy can be finished while an unintended artwork change remains a defect. Keep the two acceptance decisions visible so approval of the wording is not mistaken for approval of a replacement design.
PRISM's consultation process defines the pages, questions and follow-up before work, and the merchant decides which updates to make. For a checkout-review consultation involving protected presentation, bring the affected URLs, the requested content change and this preservation boundary. Confirm any artwork, writing, template or recovery work in the scope, responsibilities, fees and terms. The public inquiry asks for the website, research-only products and question; email follow-up does not book an appointment, purchase work or submit a processing application.
Protected-artwork record
Complete one copy for each protected asset and its actual placements. Use current files and dated views, not a proposed replacement. Acceptance needs evidence of both the retained asset and its agreed presentation; a missing reference remains an unresolved preservation 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.
Protected-artwork record. The last column is for temporary notes.
Preservation item
Evidence to record
Acceptance comparison
Your record
Asset reference
Evidence to recordActual file or media identifier, retained original location and any variants the page currently uses.
Acceptance comparisonConfirm the intended original or explicitly approved variant remains selected and retained.
Current page placement
Evidence to recordExact URL, page element, relevant width or state and dated view of the existing artwork.
Acceptance comparisonCompare the delivered placement under the same conditions.
Permitted change
Evidence to recordThe precise modification the owner approved, or no asset modification approved.
Acceptance comparisonTreat any change outside that exception as unresolved scope or a defect.
Protected property
Evidence to recordThe relevant crop, scale, position, background, layering, lettering or relationship to adjacent text.
Acceptance comparisonCheck these visible properties individually instead of relying on a general impression.
Shared placement dependency
Evidence to recordThe actual template or style that controls the artwork and the other affected placements.
Acceptance comparisonInspect each protected placement reached by the shared change.
Recovery material
Evidence to recordOriginal asset copy and configuration coverage; for WordPress, the consistent database/files set, date and authorized recovery owner.
Acceptance comparisonSeparate what is retained from what genuine evidence establishes as recoverable.
Owner acceptance
Evidence to recordNamed approver, compared version, date and any explicitly approved exception.
Acceptance comparisonRecord preserved, approved change or unresolved difference for this asset.
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.
Limits
The inventory is a proposed preservation method, not evidence that this site's files have been backed up, restored or accepted.
WordPress backup requirements apply to WordPress. Other platforms need their own documented recovery scope.
Confirm PRISM's requested work before relying on artwork or implementation assistance. Website acceptance does not establish provider eligibility or legal clearance.
Record safe file references and authorized owners, not passwords, API secrets, private customer data or payment details.
Prism: How it works — checked 2026-09-21. The consultation defines the pages, questions and follow-up before work; the merchant chooses updates. This does not establish any particular artwork-preservation or recovery engagement.
WordPress backups — checked 2026-09-29. A typical complete restore needs a consistent database/files set. Copying the WordPress directory ordinarily omits the database, and a host backup offering does not establish actual retention, retrieval time or recoverability.
Prism solutions — checked 2026-09-21. Published support includes storefront review, processing preparation and provider website questions. Scope, fees and terms are discussed before work; the provider decides eligibility and account terms.
Prism contact — checked 2026-09-21. The public form requests website, products and question without card details, passwords or customer records; email follow-up is not an appointment, purchase or processing application.