Name who may authorize and perform a store restoration

Define the recovery decision the owner is delegating

A restoration can replace records the business still needs. Before release, state which site and which recovery action the responsibility record covers: restoring a complete store is a different instruction from replacing an individual file. Name the business decision-maker and point to the existing agreement or written authorization that gives that person authority. A general instruction to maintain the website does not tell the team which recovery decision has been delegated.

Record who must approve the proposed recovery point and its effect on newer records. If the authorized person cannot be reached, use only an alternate or escalation arrangement the business has actually approved. Leaving that authority unresolved is more accurate than assigning it to whoever happens to be online. This is the exceptional restoration decision; routine permission to edit content does not answer it.

Match execution responsibility to the actual access boundary

WordPress distinguishes capabilities within a single site. An Administrator can manage plugins, themes, settings and users; an Editor has content responsibilities without those installation capabilities. Neither role label, by itself, documents access to a host’s backup controls or the ability to retrieve a particular database and files. Read the actual account and support arrangement for the planned operation.

For the executor, record the named person or vendor, the system they would use, the authorized role they currently hold, and the scope they have agreed to perform. If restoration must be requested through hosting support, record that route and who may submit the request under the account terms. If the evidence only shows WordPress access, leave host restoration access unconfirmed. Keep a reference to the access record, never a password or a backup download token.

Make preservation of current records a condition of the decision

WordPress describes a typical complete recovery as needing both the database and files from a consistent set. The files include themes, plugins, uploads and configuration. A person who can replace files has not thereby established that they can restore a complete store, and a folder download alone ordinarily does not contain its database.

Identify the candidate backup set and its recorded capture time, then assign responsibility for identifying current orders and other operating changes after that point. Require the proposed recovery decision to state how those newer records will be preserved and reconciled. Do not assume that a website restoration reverses activity recorded separately by the payment provider or fulfillment partner. The executor needs an approved scope and a preservation plan before any overwrite; this worksheet is not a procedure for performing one.

Use an explicit handoff when recovery is considered

The recovery request should give the decision-maker the affected site, observed failure, proposed recovery point, records at risk, executor and outstanding constraints. Keep the approval reference and its time with the executor’s acknowledgment. If scope or recovery point changes, bring that changed decision back through the named authority. A message that someone is investigating does not record approval to replace store data.

Before release, unresolved authority, an unconfirmed executor or unknown access should remain visible as a recovery dependency for the release owner. If a Prism checkout-review consultation would help define the website question, describe the planned change and the unassigned responsibility without sending account records. Scope, responsibilities, fees and terms are agreed before work; do not list Prism as the restoration operator unless that role is actually agreed. The public inquiry receives email follow-up and does not book a service or authorize a restoration.

Recovery responsibility record

Use existing agreements and account records to fill the final column for one store and one recovery scope. Any missing approver, executor or preservation condition is an unresolved dependency. Completing the sheet does not grant access or approve an overwrite.

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.