EvidenceSheet

9.3 Management review

Top management must review the BCMS on a planned basis against a defined set of inputs, and must record and act on the decisions the review produces.

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

3
artefacts
1
held by a system
1
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

  • Inputs presented and outputs recorded · Policy repository / GRC workspace

periodic reviewEvidence produced at each review

  • Scheduled review with attendance evidencing top management · HR system / LMS

governing documentDocuments that govern the control

  • Actions arising tracked to closure · 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

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

9.2.2 Audit programme(s) · 9.3.1 General