List each recurring function and tie it to the agreement that names its owner, covered work, start and end conditions, and limits. Keep software updates, backup creation, restoration, content changes and support response separate. A delivered site or a paid build invoice does not by itself establish the maintenance coverage described in that list. Where the documents are silent or conflict, mark the responsibility unresolved and obtain an explicit agreement.
For: A research-only merchant confirming ongoing website responsibilities after an agency or implementer delivers the site.
Translate maintenance language into observable work
Collect the actual build scope, handoff record, current maintenance agreement and any approved changes. Record which document covers the period after delivery. Separate work already completed from recurring duties: delivery of the site is evidence of a project milestone, while ongoing coverage needs its own stated responsibilities.
For each function, write what the owner is expected to do and what record would show it happened. Software updates need a defined scope of components and an agreed way to record results. Content work needs named pages or types of edits and a person who can approve the wording. Support needs a route for reporting an issue and the response or investigation commitment actually offered.
Treat broad labels such as maintenance or support as starting points for clarification. Do not expand them into unlimited edits, monitoring, emergency repairs or continuous availability. Equally, a silent clause does not prove a duty is excluded; mark the coverage unconfirmed until the parties resolve it.
Separate storing a backup from being able to restore
WordPress’s backup guidance describes a typical complete restore as needing both database and files in a consistent set. A download of the WordPress directory ordinarily does not include the database. The files include items such as themes, plugins, uploads and configuration. A responsibility described only as copying files therefore needs a scope check before it is treated as complete backup coverage.
Record who creates the backup, what it includes, how old the available copy is and who can retrieve it. Then separately identify who may authorize restoration and who would perform it. A host’s backup offering does not establish retention, retrieval time or recoverability for the merchant’s account. Use the actual account terms and genuine recovery evidence where available.
If no restoration evidence exists, record that absence without claiming failure or success. This coverage map does not authorize a restoration or overwriting live order history. It identifies which party needs to resolve recovery scope and authority before those actions are required.
Distinguish the work owner from access and approval
Name the party responsible for each task and confirm that it has accepted that responsibility. A vendor that holds an account or receives a renewal notice is not automatically contracted to perform every task associated with it. Keep access details as role or custody references, never passwords or keys in the worksheet.
For content changes, distinguish drafting, business approval and publishing. For software work, distinguish proposing an update, authorizing the change and carrying it out. For an incident, distinguish receiving the report, investigating the symptom and implementing a correction. These can belong to different people, but the handoff should say who takes the next action.
Add the limits the agreement actually states: covered components, included work, support hours if stated, charging rules, dependency conditions and when coverage ends or renews. Do not infer a response deadline from the existence of an inbox. If the merchant needs a commitment that the current documents do not establish, record it as requested coverage until agreed.
Resolve gaps before treating the handoff as covered
Compare the task list with the agreements and mark each function as confirmed, expressly excluded or unresolved. For a confirmed duty, retain the clause reference and named owner. For an excluded duty, record who will take it on if the business still needs it. For an unresolved duty, state exactly what remains open: the owner, the scope, the timing, access or the commercial terms.
Where two vendors both describe coverage, compare the specific actions instead of assuming duplication. One may store the backup while another performs restoration; the problem can be the handoff between them. Confirm that handoff and record what each party has agreed to provide. Do not assign an obligation to a vendor solely because it is technically capable of doing the work.
A Prism checkout-review consultation can start with the website, research-only products and the gap that affects ongoing checkout or storefront work. Prism’s published process defines pages, questions and follow-up before work; it does not establish an ongoing maintenance commitment for this site. Ask for the needed scope and confirm responsibilities, fees and terms. The public inquiry receives email follow-up and does not itself book or purchase coverage. Keep contracts, customer records and credentials in your own controlled records rather than the form.
Maintenance coverage map
Use the final column to record the actual agreement reference, named owner, coverage limit and any unassigned responsibility for each function. A blank clause is unresolved coverage. Record a proposed owner separately from one that has accepted the duty.
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.
Maintenance coverage map. The last column is for temporary notes.
Ongoing function
Actual agreement to locate
Boundary or gap to resolve
Your agreement, owner and limits
Software updates
Actual agreement to locateClause naming the platform, extensions, theme and custom components covered.
Boundary or gap to resolveWho proposes, approves and performs changes; how results and unresolved faults are recorded.
Backup creation
Actual agreement to locateAccount terms or maintenance scope identifying database and file coverage.
Boundary or gap to resolveWhether copies form a consistent set, their actual age and the stated retention.
Backup retrieval and restoration
Actual agreement to locateAgreement naming retrieval access, restore authorization and the party performing recovery.
Boundary or gap to resolveAny unsupported retrieval-time or recoverability claim; the existence or absence of genuine restoration evidence.
Content maintenance
Actual agreement to locateScope for edits to actual catalog, policy and other storefront pages.
Boundary or gap to resolveWho approves business wording, who publishes it and which changes require a separate agreement.
Support and incident handling
Actual agreement to locateCurrent reporting route and expressly agreed response or investigation coverage.
Boundary or gap to resolveSeparate receiving a report from diagnosing it or carrying out a repair; leave unstated hours and deadlines unknown.
Dependency renewals
Actual agreement to locateRecords for services or licenses the actual store depends on, with renewal and payment responsibility.
Boundary or gap to resolveWhether the notice recipient is also the agreed action owner; record unresolved continuation arrangements.
Coverage end and handoff
Actual agreement to locateCurrent term, ending conditions and agreed handoff obligations.
Boundary or gap to resolveWho assumes each continuing function after this coverage ends.
Unassigned responsibility
Actual agreement to locateFunction with no confirmed clause or owner, and the clarification requested.
Boundary or gap to resolveRecord the person obtaining agreement and the decision needed; do not silently assign the duty.
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
This is a coverage inventory using the parties’ real agreements, not a legal determination that a build fee includes or excludes maintenance.
WordPress backup guidance does not prove a particular host’s retention or the recoverability of this store. The worksheet authorizes no restore or live-data overwrite.
Prism’s public consultation process establishes no maintenance hours, response deadline or ongoing coverage for an unseen engagement. Confirm requested work before it begins.
Do not place account credentials, API keys, identity documents, bank details or customer records in the worksheet or public inquiry.
Prism: How it works — checked 2026-09-21. Consultation scope defines the pages, questions and follow-up before work; the merchant decides which updates to make. No response time is stated. This does not establish ongoing maintenance coverage.
WordPress backups — checked 2026-09-29. A typical complete restore needs a consistent database and files set; downloading the WordPress directory ordinarily does not copy the database. Host backup offerings do not establish account-specific retention, retrieval time or recoverability.
Prism solutions — checked 2026-09-21. Published support covers 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 form asks for the website, products and question, excludes card details, passwords and customer records, and leads to email follow-up. A request does not book an appointment or purchase a service.