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.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Scheduled review with attendance evidencing top management · HR system / LMS
governing documentDocuments that govern the control
- Inputs presented and outputs recorded · Policy repository / GRC workspace
- Actions arising tracked to closure · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Review delegated to the BCMS manager and the management team merely noted
- Inputs incomplete, so decisions rest on partial information
- Decisions recorded but never converted into tracked actions
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