Business continuity
Engagement continuity
Every engagement has a named second who holds the context. Delivery documentation is written to be picked up by someone who was not in the room, which is also why we write it that way for the client.
Source and artefact custody
Client-owned code is held in the client’s own repositories wherever the client can host it. Where we host, an escrow or handover arrangement is available and is agreed in the contract rather than after an incident.
Backup and restore
Backups for services we operate are taken on a stated schedule and restore is tested. The tested restore date is what matters, and it is available on request.
Incident response
A named rota, an escalation path, and a post-mortem policy. Where we operate under managed services the response times are contractual rather than aspirational.
Supplier failure
Deployments are designed so that a single managed-service supplier failure degrades rather than stops the system, and the degraded mode is documented.
What we have not done yet
A formally tested, documented disaster-recovery exercise across the full practice estate has not yet been completed. It is scheduled, and this page will state the date it was last run once it has been.