4.4 Business continuity management system
Set up a business continuity management system, put it into effect, keep it running and keep improving it, including the processes it needs and how they interact, as the standard requires.
Source: ISO 22301:2019, 4.4. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO 22301:2019 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Evidence of operation across a full cycle rather than at implementation only · Document repository
governing documentDocuments that govern the control
- BCMS manual or equivalent showing the constituent processes and their interactions · Document repository
- Process owners named for each BCMS process · Document repository
First move
Common gaps auditors find
- A documented system that exists on paper with no evidence any process actually ran
- Process interactions undocumented, so handoffs between impact analysis, strategy and planning are invisible
- Continual improvement asserted but not evidenced anywhere in the BCMS
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet4.3.2 Scope of the business continuity management system · 5.1 Leadership and commitment