Mon–Fri 09:00–18:00 UK

Overview / Resilience · B04

Standards we keep, outcomes you can check

Delivery standards for every engagement, written so you can hold us to them.

No uptime figures or certifications are claimed. Each standard below produces evidence you can inspect.

StandardWhat we doEvidence you receive
Separated copiesBackups held apart from primary data, with one copy protected from ordinary deletionBackup configuration summary in environment record
Tested restoresRestore tests on an agreed schedule, including partial and full restoresRestore test notes with time taken and issues found
Traceable runsEvery processing run logged: inputs, outputs, rejections, durationRun log available on request or in periodic reports
Access hygieneNamed accounts, least privilege, scheduled reviews, prompt removalAccess list with review dates
Change recordsChanges to environments and jobs recorded with reason and dateChange history
Handover-readyRunbooks written for a competent strangerRunbooks, checked at handover
Clean exitDocumented export and account handoverExit plan
Failure

When things break

They do. A source changes format, a provider has an incident, a credential expires. Resilience is about the second hour, not the first minute: knowing what failed, what was affected and how to recover.

For ongoing work, each runbook defines what counts as a failure, who is notified, and the recovery steps. During working hours we act on failures directly. Outside hours, arrangements are designed so that a failed run stops cleanly and waits, rather than producing half-finished output.

After any significant incident we write a short, blame-free note: what happened, impact, fix, and what changes.