Business Continuity, Disaster Recovery and Backup Plan

How we keep client services running and recover from serious disruption, including our recovery targets, how we back up data, and how we manage key-person risk.

1. Purpose and scope

This plan explains how Carefully Coded Ltd prepares for, responds to and recovers from events that could disrupt the services we provide to clients. It covers:

  • client systems we host or manage, including web platforms, back-end services and databases;
  • software and devices we have installed on client sites;
  • our own company devices, accounts, source code and records;
  • the people who deliver our services.

It forms part of our Information Security Policy. Where a client contract sets stricter recovery targets, the contract takes precedence for that client's systems.

2. Recovery objectives

Objective Target Meaning
Recovery time objective (RTO) 24 hours Services we host or manage are restored within 24 hours of a disruption being declared.
Recovery point objective (RPO) 24 hours No more than 24 hours of data is lost.

For equipment installed on client sites, the 24-hour RTO applies to the software and services we control remotely. Where physical replacement is needed, we agree site access with the client as soon as possible and keep them updated.

3. Roles

Role Who Responsibilities
Continuity lead Tom Emmerson Declares a disruption, leads recovery, communicates with clients and approves return to normal service.
Deputy continuity lead Another member of our team, nominated by the director Takes over if the continuity lead is unavailable.

4. Backups

4.1 What we back up

  • Production databases and file storage for client systems we host or manage.
  • Application configuration and infrastructure definitions.
  • Source code, held in version control with an independent copy.
  • Company records needed to run the business.

4.2 How we back up

  • Production data is backed up at least every 24 hours, to meet the RPO.
  • Backups are encrypted in transit and at rest.
  • Backups are held in the United Kingdom. See our Data Location Policy.
  • At least one backup copy is held separately from the live system, in a different location or account, so that one failure or compromise cannot destroy both.
  • Backups are protected from being changed or deleted by the same credentials used to run the live system, to protect against ransomware.
  • Access to backups is limited to those who need it, using multi-factor authentication (MFA).
  • Backups are kept for the periods set out in our Data Retention Policy and each client contract.

Backups are held in the UK cloud region agreed with each client, in storage kept separate from the live system. Our hosting is a UK region of a major cloud provider, agreed with each client in the contract.

4.3 Monitoring

Backup jobs are monitored automatically. Failed backups are investigated and fixed within 1 working day.

5. Restore testing

We test restoring from backup at least every 12 months for each client system we host, and after any major change to how backups work. Each test restores data into a separate environment and checks that it is complete and usable.

We record for each test:

  • the date and system tested;
  • the backup used and its age;
  • the time taken to restore, compared with the RTO;
  • the data loss, compared with the RPO;
  • any problems and the actions taken.

Results are reviewed at management review and shared with clients on request.

6. Key-person risk

For a specialist engineering team, the loss or unavailability of a key person is a significant risk. We manage it by:

  • documenting how each client system is built, deployed, backed up and restored, in a runbook the whole team can access;
  • making sure at least two people can access critical accounts, using individual accounts rather than shared passwords;
  • holding emergency access details for critical accounts in a secure, recoverable store, with recovery set up so that no account depends on one person's phone or device;
  • keeping all code in shared version control, never only on a personal device;
  • reviewing these arrangements at least every 12 months.

If the director is unavailable for an extended period, another member of our team acts as deputy, using the emergency access arrangements above. Clients will be told promptly if a key-person event affects their services.

7. Scenarios

7.1 Loss of a hosting region or provider

  • Confirm the scope of the outage with the provider.
  • If recovery within the RTO is unlikely, restore affected services from backup into another UK region or environment.
  • Update DNS and configuration, test, and confirm service with the client.

7.2 Ransomware or malicious destruction of data

  • Follow our Incident and Data Breach Response Procedure, including notifying the client within 24 hours.
  • Isolate affected systems and revoke compromised credentials.
  • Rebuild systems from clean sources and restore data from the latest backup taken before the compromise.
  • We do not pay ransoms.

7.3 Loss of a staff member

7.4 Loss of office or devices

  • Our work is cloud-based, so we can work from any secure location.
  • Lost or stolen devices are reported as incidents, remotely locked or wiped, and their credentials revoked.
  • Replacement devices are set up to our secure build standard before accessing client data.

8. Communication

During a disruption affecting a client, we will tell them as soon as possible and in any case within 24 hours, and give regular updates until service is restored. After recovery we send a summary of what happened and what we will improve.

9. Testing and review

We review this plan at least every 12 months and after any real disruption. Alongside restore testing, we run a desk-based exercise of at least one scenario in section 7 each year and record the results and actions.

Organisation
Carefully Coded Ltd
Version
1.0
Owner
Tom Emmerson, Director
Effective from
19 November 2026
Next review
19 November 2027

Questions about this policy? Email info@carefully.codes.