AIGovernrAIGovernrDocs
Ctrl K
Open workspace
Getting started
AIGovernr documentationQuickstartNavigating the appCore conceptsHow everything connects
Workspaces
CompaniesProjectsTeams & responsibilitiesDashboards & assignments
Account & administration
Plans & billingAccess control & rolesAccount securityNotifications
AI systems
AI SystemsRegister an AI SystemAI System classificationAI System Governance planGovernance plan vs PlaybookSystem documentation & testing recordsVendors & dependenciesShadow AI & asset graph
Obligations
Frameworks & obligationsRequirements & tasksGovernance knowledgeRegulatory updates
Assurance
Assure overviewControlsAssurance methodsTechnical evaluationsDPIAEvidence managementISO/IEC 42001 readinessGovernance maturity
Issues & actions
Findings vs risksCorrective actions
Decisions
ApprovalsApproval PoliciesDecision LedgerExceptions & reassessment
Continuous governance
MonitoringIncidentsAgent & MCP governance
Reusable governance
AI governance policiesPolicy templatesPlaybooks
Reporting
Reports, certificates & audit export
Client collaboration
Client portal & engagement
Guides
Run a client governance engagementOperate an AI governance programmeFramework implementation guides
Discovery tools
Website Compliance Scanner
AI assistance
AI Assistant
Developers
Integrations & APIs
Help
Troubleshooting & FAQ
DocsContinuous governance
Continuous governance

Incidents

Record AI incidents, track regulatory notification deadlines, and connect the incident to the corrective actions and reassessments it causes.

In the app
Project → Decide & Operate → Incidents

Report an incident

  1. 1Choose Report Incident and record the AI System, type, severity and what happened.
  2. 2Types: Bias, Hallucination, Data breach, System failure, Unauthorised use, Harm to user and Other. Severity: Critical, Major, Minor or Near-miss.
  3. 3Record affected people and jurisdictions. Regulatory clocks track notification deadlines.
  4. 4Use Add Update as the incident moves through Open, Investigating, Contained, Resolved and Closed.
  5. 5Record the root cause (including a 5-whys analysis) and use Preserve incident evidence to place related evidence on hold.

Connect follow-up work

Link the incident to corrective actions and reassessment cases. Record any findings or risks it reveals separately in Findings and Risks. Incidents raised by runtime threshold breaches are created automatically.

Last reviewed 2 October 2026

Next stepAgent & MCP governanceDefine what an AI agent may do (tools, MCP servers, data, spend and human approval boundaries), check actions against that policy at runtime, and review redacted traces.
MonitoringAgent & MCP governance
On this page
Report an incidentConnect follow-up work
Capability status

Check current availability and limitations before relying on a feature.

View matrix