Skip to main content

Post-incident review

The structured document written after a data incident's active response has ended, reconstructing what happened, identifying every contributing factor, crediting what worked, and converting the findings into checkable, owned, dated action items intended to permanently close the gaps the incident revealed.

Defined in 3 GAGE programs, which carry 4 distinct definitions of it. The wording above is taught in Certified AI Data Governance Professional (CADGP).

How each discipline defines it

The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.

Certified AI Data Governance Professional (CADGP)

The structured document written after a data incident's active response has ended, reconstructing what happened, identifying every contributing factor, crediting what worked, and converting the findings into checkable, owned, dated action items intended to permanently close the gaps the incident revealed.

Certified AI Governance Professional (CAIGP)

The structured review conducted after a real outage or a genuine test, comparing what actually happened against the continuity table's planned recovery objective and degraded mode, and updating the table with any gap the real event revealed. Deep treatment owned by (see Topic 3.5).

Certified Agentic AI Governance Professional (CAAGP)

A structured review conducted after an incident is resolved, examining what happened, how it was classified and handled, and what should change. Owned in depth by Topic 7.8's forensics treatment. (see Topic 7.8)

Certified AI Data Governance Professional (CADGP)

The Module 11 artifact produced after a data incident, written in the blameless format this topic's glossary connects to the open decisions log's own honesty requirement; both depend on the same willingness to record uncomfortable specifics rather than a flattering summary.

Where it is taught

The exact lessons this term appears in. The first module of every program is free with a free account.

Where it shows up at work

A definition is where Post-incident review starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.

Plans for a vendor failure, an unsafe model change or a suspended service: rollback, manual fallback, data export and safe decommissioning.

One lesson on this page teach it as a primary outcome.

Classifies AI incidents by severity, runs containment, preserves evidence, manages notification, and closes the loop with lessons learned.

One lesson on this page teach it as a primary outcome.

Roles that hire for it

Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.

How job descriptions say it

Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.

“business continuity”“exit plan”“incident response”“incident management”“serious incident”“resilience”

Where the frameworks place it: DORA; NIS2; NIST AI RMF MANAGE 4; EU AI Act Article 73.

One interview question about it

Your AI vendor shuts down next month. What was in your continuity and exit plan, and what did you fail to plan for?

Asked of candidates for ai resilience, continuity and exit planning. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.

If you come from another field

Some backgrounds already carry this competency, and the readiness check gives credit for it.

Terms it appears with

Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.