7.5.1 General
The BCMS must include both the documented information the standard requires and whatever further documented information the organization itself judges necessary for the BCMS to be effective.
Source: ISO 22301:2019, 7.5.1. 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 the set is proportionate to the size and complexity of the organization · Document repository
governing documentDocuments that govern the control
- Mapping from each documentation requirement of the standard to the document that satisfies it · Policy repository / GRC workspace
- Rationale for additional documentation the organization chose to hold · Document repository
First move
Common gaps auditors find
- Documentation assembled to a template with no mapping back to requirements
- Organization specific documentation absent, leaving gaps the standard does not name explicitly
- Volume mistaken for effectiveness, with documents nobody uses
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