Skip to content

Web services.
Simply looked after.

Prepare a rollback plan before a website change

A rollback plan explains how an authorised person would return to a known acceptable state if a change causes problems. It needs a usable recovery source, a decision-maker and a plan for data created since that source. A backup existing somewhere is not enough detail.

Before you start

  • Define the proposed change and the important functions it could affect.
  • Identify who is authorised and able to restore the relevant system.

What to do

  1. Identify what recovery actually includes

    A website can involve code, uploads, settings and a database. Email or booking tools may be separate. For a WordPress change, confirm the relevant files and database are covered. A screenshot or last month's export may not represent a working recoverable version.

  2. Check the source before changing anything

    Ask the responsible administrator when the recovery copy was created, where it is held and how restoration has been checked. Use a suitable non-live test where feasible. Do not discover after a failed change that the only copy is incomplete or inaccessible to the business.

  3. Protect activity that happens afterwards

    Consider new enquiries, bookings, orders or edits received during the change window. Restoring an older database can overwrite that activity. Agree how it will be preserved or reconciled rather than treating return to the previous design as the only important recovery outcome.

  4. Agree the decision and final checks

    Name who decides whether to roll back, what symptoms justify it and who communicates with the business. After recovery, verify the relevant public pages and connected functions. Record both the action taken and any outstanding data reconciliation rather than calling it complete because the homepage loads.

What to check

  • A named authorised person can access a relevant recovery source.
  • New data and external dependencies have been considered.
  • Success means restored functionality and understood data, not only restored appearance.

Sources and further reading

Platform features can change. Check the provider’s current guidance before changing a live service.

A little help, when you need it

What can we help with?

Leave a message for PresGro support. This is not live chat. Please don’t include passwords or payment details.

Daily, 08:00–18:00 UK time

We aim to give an initial reply within 3–4 support hours. This is a target, not a guaranteed response or resolution time. Help outside these hours may be available.

Your details are used to respond to this enquiry. Read our privacy notice. Never send passwords. Prefer email? help@presgro.com.

Visit the support centre →