What evidence do auditors commonly ask for on 8.2.1 General?

Written method for each process showing it is systematic and repeatable; Planned review interval with evidence reviews occurred; Change triggered reviews evidenced against actual organizational changes.

What is the most common gap auditors find on 8.2.1?

Method exists as a spreadsheet convention rather than a documented process

ISO 22301:2019 · Operation, ISO 22301:2019

`8.2.1` General

Put in place and keep up systematic processes both for analysing what a disruption would do to the business and for assessing the risk of disruption, and review what both produce at planned intervals and whenever the organization, or the setting it works in, changes significantly.

Source: ISO 22301:2019, 8.2.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.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

Planned review interval with evidence reviews occurred · Document repository

governing documentDocuments that govern the control

Written method for each process showing it is systematic and repeatable · Document repository
Change triggered reviews evidenced against actual organizational changes · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Method exists as a spreadsheet convention rather than a documented process
Planned interval set at annual and then missed without escalation
Significant change defined nowhere, so the change trigger never fires

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

8.2 Business impact analysis and risk assessment · 8.2.2 Business impact analysis