9.2.2 Audit programme(s)
Plan, set up, run and keep up an audit programme that fixes how often audits take place, the methods, who is responsible, planning requirements and reporting, giving weight to how important the processes involved are and what earlier audits found. Set the criteria and scope for every audit; choose auditors and run audits so that the process stays objective and impartial; report the results to the managers concerned; keep documented evidence of the programme and its results; make sure the corrective actions needed to remove detected nonconformities and their causes are taken promptly; and make sure follow-up checks what was done and reports what the check found.
Source: ISO 22301:2019, 9.2.2. 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.
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
none for this control
periodic reviewEvidence produced at each review
- Auditor selection records evidencing objectivity and impartiality · Policy repository / GRC workspace
- Management reporting records · Policy repository / GRC workspace
- Corrective action records with timeliness evidence and verification of the actions taken · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Documented audit programme with frequency, method and responsibility, risk weighted · Policy repository / GRC workspace
- Per audit criteria and scope statements · Policy repository / GRC workspace
First move
Common gaps auditors find
- Programme frequency uniform across all processes, ignoring importance and prior audit results
- Auditors selected for availability, auditing their own work
- Corrective actions raised without a due date, so undue delay cannot be detected
- Follow up confirms an action was recorded rather than verifying it worked
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