EvidenceSheet

8.6 Evaluation of business continuity documentation and capabilities

Evaluate whether the impact analysis, the risk assessment, the strategies, the solutions, the plans and the procedures are still suitable, adequate and effective. Do this through reviews, analysis, exercises, tests, reports after incidents and performance evaluations; evaluate the continuity capabilities of the partners and suppliers that matter; evaluate whether applicable laws, regulations and industry practice are complied with, and whether the organization's own policy and objectives are met; and update documentation and procedures without delay. Carry out these evaluations at planned intervals, after any incident or activation, and whenever significant change happens.

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

5
artefacts
1
held by a system
3
at each review
hard
to go live
Document repository
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

  • Compliance and conformity evaluation results · Document repository

periodic reviewEvidence produced at each review

  • Evaluation records covering each element of the BCMS documentation set · Document repository
  • Partner and supplier continuity capability assessments with evidence behind them · Vendor register / contract repository
  • Post incident and post activation evaluations · Document repository

governing documentDocuments that govern the control

  • Documentation update records traceable to evaluation findings · Document repository

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Document repository on a schedule; put the documents under version control with an owner and review date, and log each review 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

8.5 Exercise programme · 9.1 Monitoring, measurement, analysis and evaluation