Business Continuity and Disaster Recovery Policy

How we protect client work when things go wrong

1. Introduction

2. Purpose and scope

3. Objectives

  • maintain critical creative and production services wherever reasonably possible;

  • protect client data, project files and intellectual property from loss, corruption or unauthorised access;

  • minimise avoidable downtime and disruption;

  • provide clear points of contact if an incident affects a client project; and

  • review and improve our continuity arrangements as our studio, systems and client requirements develop.

4. Roles and responsibilities

  • use approved tools and storage locations;

  • follow data-protection and information-security requirements;

  • report any incident that may affect service delivery, client information or system availability; and

  • cooperate with recovery steps where needed.

5. Risk assessment

  • power cuts, connectivity issues or equipment failure;

  • loss, theft or damage of devices used to access client work;

  • cyber incidents, malware, unauthorised access attempts or account compromise;

  • unavailability of key third-party services, including cloud storage, communications, project-management and web platforms;

  • illness or unexpected unavailability of key personnel; and

  • delays caused by third-party production, print, hosting or software providers.

6. Preventative and continuity measures

  • use reputable cloud-based tools for file storage, collaboration and communication;

  • protect devices with strong authentication, automatic locking and appropriate access controls;

  • keep key project files, templates and brand assets in access-controlled locations rather than on a single local device;

  • maintain alternative methods of communication where appropriate;

  • document key project information so another authorised person can assist where needed; and

  • use third-party suppliers with appropriate service, security and continuity arrangements where available.

7. Backup and recovery

  • store active project files in secure cloud environments with redundancy and version history where appropriate;

  • maintain backup arrangements for key storage locations;

  • keep backup copies of final deliverables for a reasonable period after project completion, unless agreed otherwise;

  • use version-control or file-history tools where appropriate; and

  • periodically check that key files can be accessed and restored.

8. Incident response and communication

  • assess the incident and contain the immediate risk;

  • prioritise protection of client data and time-critical deliverables;

  • notify affected clients where the incident is likely to affect deadlines, deliverables or data;

  • agree practical workarounds or revised timelines where needed; and

  • record the incident, cause and actions taken so we can improve our controls.

9. Remote working and site access disruption

  • continue working from alternative secure locations where possible;

  • use cloud-based tools to access project files and communicate with clients and suppliers;

  • avoid using insecure public networks for confidential client work unless appropriate protection is in place; and

  • inform clients if there is a material impact on delivery timescales.

10. Third-party services and suppliers

  • their information-security and availability commitments;

  • their own continuity and disaster recovery arrangements;

  • whether we can export or recover our data if the service becomes unavailable; and

  • whether an alternative provider or temporary workaround is available.

11. Testing, review and improvement

  • key operational risks;

  • backup and recovery arrangements;

  • contact details, tools and procedures;

  • lessons learned from any disruption; and

  • whether any improvements are needed.

12. Contact