10.2 Continual improvement
Continually improve the suitability, adequacy and effectiveness of the BCMS using qualitative and quantitative measures, considering the results of analysis and evaluation and the outputs of management review to determin
4
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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
- Improvement register or backlog with items traceable to analysis, evaluation or management review · Policy repository / GRC workspace
- Evidence of improvements delivered over successive cycles · Document repository
governing documentDocuments that govern the control
- Both qualitative and quantitative measures in use · Document repository
- Link from business change into the improvement determination · Document repository
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
- Improvement evidenced only by corrective actions, so nothing improves that was not first broken
- Quantitative measures only, missing qualitative signals from exercises and near misses
- Improvement register that accumulates items and closes none
- Business needs never considered, so the BCMS improves against itself rather than against the organization
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