AI incidents
Log it when an AI tool gets something wrong, assess how serious it is and keep a record of what you did.
Read the video as text
AI incidents, in Valdra.
The clinic in this video is made up, and so is every detail.
When an AI tool gets something wrong and someone is harmed, or could have been, log it as an AI incident.
Give it a title, the closest category and the AI system involved.
On the incident page, assess its severity. Where the EU AI Act applies, the page shows whether it must be reported and the deadline.
Record the fix under Resolution: the status, the remediation steps and the root cause.
Follow up notes go on the timeline, so the file shows what you did and when.
What this is for
An AI tool made a mistake that harmed someone, or could have. You log it, assess how serious it is and record how you fixed it. The page follows the European Union AI Act, Article 73, which sets deadlines to report serious AI incidents.
This is general guidance, not legal advice.
Before you start
- Plan: every plan can log and assess incidents. Draft the report needs Starter and up.
- Role: an Admin or a Member can log and change incidents. An Auditor can read them.
- Have ready: what happened, when, which AI system was involved and how many people were affected.
Steps
Open AI incidents
In the menu, open AI governance, then click AI incidents under Operate.

Click Log an incident
Type a Title. Under Category (Art. 73), choose the closest one, for example Malfunction. Under AI system involved, pick the system.
Add a Description and the Nature of harm if you know them. Type the number of Individuals affected.
Click Log incident.

Open the incident
The incident shows under Open. Click its title to open it.

Click Assess severity (Art. 73)
Valdra assesses how serious the incident is and whether it must be reported. Before that, the incident shows Not assessed. Then the severity shows: Not serious, Serious or Critical, with the reasons under Assessment.
Under Facts, Jurisdictions shows a short code, such as CA-QC, not the name of the place.

Record the fix
Under Resolution, set the Status. Fill in Remediation steps and Root cause. Click Save. You will see Saved.
Add follow up notes under Timeline notes.
What you will see
The list has views: Open, Reportable, Past deadline, Drills and Closed. A reportable incident shows the time left to report it.
When an incident must be reported, Draft the report writes a report for the authority. The report shows under Authority report (Art. 73). It is written in English. Once you have told the authority, click Mark authority notified. Type the Authority and the Date notified, then click Record.
Was personal information lost or shared by mistake? On the incident page, click Open breach response.
Run a drill creates a practice incident. It shows only under Drills, not in the other views.
Common mistakes and fixes
The Log incident button stays grey. The Title is empty. Type one.
Draft the report is greyed out. You see Assess first: not reportable yet. Click Assess severity (Art. 73) first.
You changed the category. Assess severity again after changing the category.
If it did not work
Individuals affected is a whole number, 0 or more. Type a number without decimals.
The incident was not logged. Try again. Wait a moment and click Log incident again.
Automatic drafting is not available right now. Try Draft the report again later.
The action failed. Try again. The button you clicked did not finish. Try again.
Saving failed. Try again. Your change did not save. Click Save again.
The note was not added. Try again. Click Add again.
The drill did not start. Try again. Click Run a drill again.