9.3.2 Management review input
The review must consider the status of actions from previous reviews, changes in external and internal issues relevant to the BCMS, BCMS performance information including trends in nonconformities and corrective actions,
5
artefacts
0
held by a system
2
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
- Review pack demonstrably covering every required input · Policy repository / GRC workspace
- Evidence that previously unaddressed risks were surfaced rather than dropped · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Trend data rather than point in time figures for nonconformities, measurement and audits · Policy repository / GRC workspace
- Near miss and disruption lessons presented with the actions arising · Policy repository / GRC workspace
- Interested party feedback captured and presented · 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
- Input pack covering audit results and little else
- Near misses never captured, so the richest source of learning is absent
- Trends replaced by the current month, hiding deterioration
- Risks judged out of scope in an earlier assessment quietly disappear rather than being re presented
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