Teams starting an ISO 22301 project often ask the same question: how many documents do we actually have to write? The standard does not give a fixed list or template set. It requires "documented information" in specific places and leaves you to decide what else your organisation needs to run its business continuity management system (BCMS) effectively.
This article separates what the standard clearly expects from what is sensible to add, so you can plan your documentation without overbuilding it.
How ISO 22301 treats documented information#
ISO 22301 uses the term documented information for both documents (things you maintain, such as policies and plans) and records (things you keep as evidence, such as test results). Both need to be controlled: identifiable, approved, protected, available when needed, and retained appropriately.
Two practical points follow from this:
- Some items are explicitly required. If they are missing, an auditor will raise it.
- Others are required only to the extent you need them. The size and complexity of your organisation, and the competence of your people, determine how much you write down.
A small organisation with one site may need far less documentation than a multi-site operation with outsourced critical services. Do not copy a large organisation's document set if it does not fit how you work.
Core BCMS documents#
These documents set the direction and boundaries of your system. Most auditors will look at them first.
| Document | What it should cover |
|---|---|
| BCMS scope | Which products, services, locations and functions are included, and any exclusions with reasons |
| Business continuity policy | Management commitment, a framework for objectives, and a commitment to meet requirements and improve |
| Business continuity objectives | Measurable targets, owners, timelines and how progress is monitored |
| Context and interested parties | Internal and external issues, stakeholder needs, and applicable legal, regulatory and contractual requirements |
| Roles and responsibilities | Who owns the BCMS, who leads during an incident, and who deputises |
The context and legal requirements material is often kept as a register rather than a long narrative document. A simple table that lists each requirement, its source and who is responsible is usually enough.
Operational documents: the heart of ISO 22301#
This is where continuity management differs from many other management systems. The standard expects you to analyse the business, decide how to respond, and write down how that response works.
Business impact analysis (BIA) and risk assessment#
You need a defined method for the BIA and for assessing disruption risk, plus the results of applying them. Typical contents include:
- Prioritised products and services, and the activities that support them
- Impact over time if each activity is disrupted
- Maximum tolerable period of disruption and recovery time objectives
- Dependencies such as people, IT systems, suppliers, premises and data
- Risks to those activities and how you decided to treat them
Keep the method separate from the results. The method changes rarely, while the results should be reviewed regularly.
Business continuity strategies and solutions#
Record which options you chose to meet your recovery objectives and why. Examples include alternate work locations, remote working arrangements, supplier redundancy, data backup and recovery arrangements, and manual workarounds. Include resource requirements so that decisions can be funded and reviewed.
Business continuity plans and procedures#
Plans are the documents people will use under pressure, so they must be short, clear and findable. A workable set usually includes:
- Incident response plan: activation criteria, command structure, assessment steps and escalation
- Business continuity or recovery plans: by function, service or site, with prioritised recovery actions
- Communication procedures: internal updates, and contact with customers, regulators, suppliers and emergency services
- Contact lists: kept current, with a stated review cycle
- Recovery procedures: returning from temporary arrangements to normal operations
Write plans for the person who is on call at 3 a.m., not for the auditor. Use checklists and avoid long explanatory prose.
Records that prove the system works#
Many certification findings relate to missing evidence rather than missing policies. Plan to retain the following:
- Competence evidence: training records, role descriptions, and awareness activity for people with continuity duties
- Exercise and test results: scenario, participants, findings, actions and sign-off
- Monitoring and measurement results: how you assess performance against objectives
- Internal audit programme and reports: criteria, scope, findings and follow-up
- Management review minutes: inputs considered, decisions and actions
- Nonconformity and corrective action records: what went wrong, the cause, the fix and a check that it worked
- Incident records: real disruptions, how they were handled, and lessons learned
- Evidence that planned processes were carried out: for example, completed BIA sessions or approved risk treatment decisions
Exercises deserve special attention. A plan that has never been tested is hard to defend. Even a simple tabletop exercise, properly recorded with actions tracked to closure, gives you useful evidence.
Practical tips for building the document set#
- Start with a gap list. Map what you already have, such as disaster recovery plans, crisis procedures or supplier contracts, against the requirements. Reuse before you rewrite.
- Keep documents proportionate. If a one-page procedure works, do not write ten pages.
- Assign owners and review dates. Plans go stale quickly when staff, suppliers or systems change.
- Control versions. Make sure the people responding to an incident are using the current plan, and keep offline copies accessible if systems are unavailable.
- Align with related systems. If you already run an information security or quality system, share the document control, internal audit and management review processes rather than duplicating them.
- Link documents to each other. Objectives should trace to the BIA, strategies to recovery objectives, and plans to strategies. Auditors follow this chain.
If you are comparing documentation needs across standards, our guides to GDPR documentation and ISO 20000 documentation show where similar records can be shared.
Frequently asked questions#
Does ISO 22301 require a documented procedure for everything?#
No. The standard names certain documented information, such as scope, policy, objectives, BIA and risk assessment outputs, strategies, plans and evidence of testing and review. Beyond that, you document what your organisation needs to operate the BCMS consistently and effectively.
Can our existing disaster recovery plan count toward ISO 22301?#
It can form part of your evidence, particularly for IT recovery. However, ISO 22301 covers the whole organisation, so you will also need to address people, premises, suppliers and processes, and link recovery arrangements to your BIA results.
How often should continuity documents be reviewed?#
The standard expects continual improvement and regular review rather than a fixed interval. A sensible approach is to review after any significant change, after every exercise or real incident, and at least once a year as part of management review.
Where to go from here#
Once you know what you need, the main effort is drafting consistent, usable documents. If you would rather start from a structured base than a blank page, the ISO 22301 Toolkit is a ready-to-use documentation toolkit for the standard. If you want to discuss how it fits your situation, you can contact the AdWiser team.
