← Back to Application

Incident Type Classification

EU AI Act Compliance Guidance

Why Classify Incident Types?

Properly classifying incidents helps you:

  • Track patterns and identify systemic issues
  • Map incidents to relevant EU AI Act Articles
  • Prioritize remediation efforts
  • Meet record-keeping requirements (Article 12)

Common Incident Types

Transparency & Explainability

User cannot understand why the AI made a decision

Relevant Articles: Article 13 (Transparency), Article 14 (Human Oversight)

Human Oversight Failure

Human oversight mechanisms failed to prevent harm

Relevant Articles: Article 14 (Human Oversight)

Bias & Discrimination

System exhibits unfair treatment based on protected characteristics

Relevant Articles: Article 10 (Data Governance), Article 15 (Robustness)

System Malfunction

Technical failure causing incorrect outputs or service disruption

Relevant Articles: Article 15 (Robustness), Article 12 (Record-Keeping)

Data Quality Issue

Problems with input data affecting system performance

Relevant Articles: Article 10 (Data Governance)

Keyword-Based Suggestions

The system analyzes your incident description and suggests the most likely incident type based on keywords. You can accept the suggestion or select a different type that better fits your situation.

Tip: Always review the suggested type and ensure it accurately reflects the incident. Accurate classification is essential for compliance reporting and internal analysis.

EU AI Act Article Mapping

Each incident type maps to specific EU AI Act Articles that may be relevant:

  • Article 9: Risk management system requirements
  • Article 10: Data and data governance
  • Article 11: Technical documentation
  • Article 12: Record-keeping
  • Article 13: Transparency and provision of information
  • Article 14: Human oversight
  • Article 15: Accuracy, robustness, and cybersecurity

Note: For official compliance guidance, consult legal counsel and refer to the EU AI Act official resources.