Website care: test backups and forms

Test one complete customer action

Choose the main journey: enquiry, booking or purchase. Complete it on a phone using fictional contact details. Check required fields, the confirmation and the saved record. Repeat in every supported language; a translated button does not establish a working form.

Also test missing information and a duplicate submission. Visitors should understand what to correct. A system must not confirm receipt if it could not save the request.

Check storage and email separately

A saved enquiry, mail-server acceptance and inbox receipt are different outcomes. Check the request list and an actual test inbox. Assign responsibility for failed or uncertain delivery and agree how customers remain contactable.

Do not blindly repeat an uncertain email: the first attempt may already have been accepted. Check provider records and receipt first. The same distinction applies to payments; a thank-you page does not establish a completed transaction.

Restore a backup away from production

Identify the backed-up components: website files, database and uploads. Restore a selected copy in a separate environment and find a fictional enquiry and attachment. Record the date, backup used and result.

Agree how much data loss and downtime the business can tolerate. Last month's recovery test does not prove every later backup is complete. Plan suitable checks and retention periods.

Make changes and handover manageable

Apply updates where they can be checked first and agree how to roll back a failure. Afterwards retest forms, links, languages and mobile display. Assign responsibility for alerts and access to the required accounts.

Ask which tasks your support agreement includes and which require separate approval. This checklist is a verification approach; it does not certify a particular provider's production backups or maintenance coverage.

Related reading