Anchor Software
CONTINUITY

Continuity, kept short

A continuity plan is useful only if someone can follow it on a bad day. Here is how we build one that fits on a few pages.

  1. List what you rely on

    Email, files, accounts software, phones, customer records, the website. Include the suppliers behind each.

  2. Rank by impact

    For each, ask how long you could work without it and how many people it affects. The sorter on our tools page does this quickly.

  3. Write the first hour

    For the top items: who notices, who decides, what is done first, and how staff and clients are told.

  4. Prove recovery

    Test a restore for the most important data and note how long it took.

  5. Walk it through

    A one-hour desk exercise: "email has stopped, what now?" Gaps found here are cheap to fix.

  6. Review twice a year

    People, suppliers and systems change. A dated review keeps the plan honest.

EXAMPLE PAGE, ILLUSTRATIVE

Lost or stolen laptop

First ten minutes

The person reports it by phone to the named contact. The device is locked remotely if management is in place.

First hour

Their password is changed and sessions signed out. Two-step sign-in devices are checked. If the laptop held personal data, the decision-maker considers reporting duties.

Same day

A replacement or loan device is prepared to the standard. Work resumes from shared storage.

Afterwards

Record what happened, how long each step took, and what to change.

Continuity plans describe practical IT steps. Decisions about legal reporting duties, insurance claims or regulatory notifications belong to your organisation and its advisers; the plan simply makes sure the right person is asked at the right time.