What evidence do auditors commonly ask for on 4.3.1 General?

Scope document referencing the context issues and party requirements it was derived from; Evidence of management approval of the scope; Version history showing the scope has been maintained.

What is the most common gap auditors find on 4.3.1?

Scope asserted without any traceable derivation from context or obligations

ISO 22301:2019 · Context of the organization, ISO 22301:2019

`4.3.1` General

Set the limits of the BCMS and where it applies, drawing on the context issues, what interested parties require, and the organization's own mission and goals and its obligations inside and outside the organization; keep the resulting scope as documented information.

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

moderate

to go live

Policy repository / GRC workspace

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

Version history showing the scope has been maintained · Policy repository / GRC workspace

periodic reviewEvidence produced at each review

Evidence of management approval of the scope · Policy repository / GRC workspace

governing documentDocuments that govern the control

Scope document referencing the context issues and party requirements it was derived from · Policy repository / GRC workspace

First move

Start with the 1 of 3 artefacts that already live in a system (Policy repository / GRC workspace); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Scope asserted without any traceable derivation from context or obligations
Mission and external obligations ignored, so scope is drawn on organizational convenience
Scope never re-derived after the context analysis changed

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

4.3 Determining the scope of the business continuity management system · 4.3.2 Scope of the business continuity management system