9.3.3 Management review outputs
The review must produce decisions on continual improvement opportunities and on any changes needed to improve BCMS efficiency and effectiveness, covering variations to scope, updates to the business impact analysis, risk
4
artefacts
0
held by a system
3
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
- Minutes recording decisions against each required output area · Policy repository / GRC workspace
- Communication records to relevant interested parties · Policy repository / GRC workspace
- Evidence of the resulting change in the BCMS artefacts · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Actions with owners and dates traceable from the decisions · 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
- Minutes that record discussion but no decisions
- Decisions on how control effectiveness will be measured omitted, so measurement never improves
- Results not communicated beyond the review attendees
- Actions raised and then closed administratively at the next review without evidence
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 sheet9.3.2 Management review input · 10.1 Nonconformity and corrective action