Business Continuity and Backup Policy template (free, plain-language starter)
Free business continuity and backup policy template for small companies: full text, the controls it supports and the decisions to make. Not legal advice or a certificatio
Backups, restore tests, recovery targets and how the company keeps working through a disruption. This free starter covers 3 controls and leaves 4 decisions for you; it is original text, not a standard’s wording, and adopting it is not a certification.
Backups, restore tests, recovery targets and how the company keeps working through a disruption. Customers and auditors ask for it in customers who depend on your uptime; write it once customers rely on your service daily.
Controls it supports
| Ref | Control | Starter framework |
|---|---|---|
| TC-AVL-01 | Backups are taken and tested | SOC 2-style common criteria starter |
| TC-AVL-02 | Continuity is planned | SOC 2-style common criteria starter |
| IS-TEC-05 | Backup | ISO 27001-style Annex A starter |
Decisions to make before approving
[24 hours][daily][30 days][6 months]
The policy text
Purpose
To make sure [Company] can keep serving customers, or get back to serving them quickly, after a disruption such as an outage, data loss, ransomware, the loss of a key supplier or a key person being unavailable.
Scope
Systems and data that customers depend on or that the company needs to operate, and the people and suppliers who run them.
Critical systems and recovery targets
[Policy Owner] keeps a list of critical systems. For each it records the owner, the backup method, and two targets:
- Recovery time objective (RTO): how long the system may be unavailable. Default for customer-facing systems: [24 hours].
- Recovery point objective (RPO): how much recent data may be lost. Default for customer data: [24 hours].
Backups
- Customer data and other critical data are backed up at least [daily].
- At least one copy is kept separate from the production account or provider, so that a single compromised account cannot delete both data and backups.
- Backups are encrypted, access to them is limited to named people, and deleting them requires extra approval where the tool allows it.
- Backups are kept for at least [30 days], or longer where law or contracts require.
- SaaS tools used to hold important data (for example document storage, CRM, accounting) are reviewed for their own backup and export options; exports are taken where the provider's protection is not enough.
Restore tests
- A restore of each critical system's backup is tested at least every [6 months], and after major changes to the backup setup.
- Each test records what was restored, how long it took and whether the targets were met. Failures are fixed and re-tested.
Continuity plan
- The plan lists who decides that a disruption is serious (the incident lead in the Incident Response Policy), how staff and customers are informed, and the alternative ways of working (for example working from home, a status page, manual processes).
- Contact details for staff and key suppliers are kept where they can be reached during an outage, not only in the systems that might be down.
- Key knowledge is not held by only one person: critical procedures are written down and at least two people can carry them out.
Exercises
The continuity plan is exercised at least once a year, for example by walking through an outage scenario. Lessons are recorded and the plan updated.
Exceptions
Exceptions to this policy must be requested in writing, approved by [Policy Owner], recorded with a reason and an end date, and reviewed when they expire.
Enforcement
Breaking this policy may lead to loss of access and to disciplinary action in line with employment contracts and local law. Contractors may have their engagement ended.
Review
[Policy Owner] owns this policy and reviews it at least every [Review Period], and after any major incident or change in how [Company] works. Questions go to [Security Contact].
Adopt it
- Copy the policy below, or create it from the starter library in Controlkeep, where [Company], [Policy Owner], [Security Contact] and [Review Period] are filled from a form.
- Decide the 4 remaining bracketed items so the rules match how you actually work.
- Approve it, ask staff to acknowledge it, and link it to the controls it supports so auditors can follow the trail.
Related: collecting audit evidence, policies help, Data Classification and Handling Policy, Remote Work and Device (BYOD) Policy.
Questions and answers
What is the difference between backup and continuity?
Backups restore data; continuity keeps the business running (people, suppliers, communication) while you restore.
Does adopting this business continuity and backup policy make us SOC 2 or ISO 27001 compliant?
No. Policies are one part of a programme; an auditor tests whether you follow them over time. Controlkeep helps you keep the evidence, but it is not a certification or an audit opinion.
Try Controlkeep free
A working control register: owners, evidence, policies and reviews in one place, with exports your auditor can read. The Free plan needs no card; you can export or delete your data any time.