4.3.2 Scope of the business continuity management system
State which parts of the organization are inside the BCMS having regard to location, size, nature and complexity, identify the products and services covered, and document and explain every exclusion so that no exclusion undercuts the organization's ability or responsibility to deliver continuity as established by the business impact analysis, the risk assessment and applicable law.
Source: ISO 22301:2019, 4.3.2. 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
- Exclusion log with the explanation for each exclusion · SIEM / log platform
periodic reviewEvidence produced at each review
- Cross check that no exclusion contradicts the business impact analysis or a legal obligation · Policy repository / GRC workspace
governing documentDocuments that govern the control
- List of in scope sites, entities and functions · Policy repository / GRC workspace
- List of in scope products and services · Policy repository / GRC workspace
First move
Common gaps auditors find
- Exclusions recorded with no explanation, or explained only as out of scope
- A site or entity excluded that the business impact analysis shows supports a prioritized activity
- Products and services described at brand level so the actual delivery chain is untested
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 sheet