What evidence do auditors commonly ask for on CPS 230 para 31 Identify, escalate, record and address incidents and near misses?

Incident and near-miss register with detection, escalation and closure timestamps; Incident management and escalation procedure, including near-miss capture; Evidence of incidents feeding risk profile and control effectiveness reassessments (e.g. RCSA updates).

What is the most common gap auditors find on CPS 230 para 31?

Near misses not captured at all

APRA CPS 230 · Operational risk management, controls and incidents (paras 23 to 32)

`CPS 230 para 31` Identify, escalate, record and address incidents and near misses

The entity must make sure near misses and operational risk incidents are promptly identified, escalated, recorded and dealt with, and must promptly feed them into its assessment of the operational risk profile and of control effectiveness.

Source: APRA CPS 230, CPS 230 para 31. 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 APRA CPS 230 in the compliance library.

Applies to APRA-regulated entities.

artefacts

held by a system

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. 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

none for this control

periodic reviewEvidence produced at each review

Evidence of incidents feeding risk profile and control effectiveness reassessments (e.g. RCSA updates) · Document repository

governing documentDocuments that govern the control

Incident and near-miss register with detection, escalation and closure timestamps · Policy repository / GRC workspace
Incident management and escalation procedure, including near-miss capture · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Near misses not captured at all
Incidents closed without updating risk or control ratings

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

CPS 230 para 30 Remediate material weaknesses and keep them in the risk profile until fixed · CPS 230 para 32 Notify APRA within 72 hours of a material operational risk incident