xmodoxmodo

Platform · Incident

Meet every incident-reporting deadline

When an incident is detected, the regulator's reporting deadline starts to run. xmodo builds each jurisdiction's reporting timelines into the incident workflow.

Reporting deadlines built in

xmodo sets reporting timelines for each incident based on jurisdiction. DORA's 4-hour initial notification, NIS2's 24-hour early warning and the DFSA's 72-hour material-incident report appear as live countdowns on the record. Each step from detection to notification is timestamped.

Response times you can see

Each incident has a severity, a priority and response SLAs. Breached SLAs are clearly flagged on the record.

From root cause to corrective action

The root-cause analysis is recorded on the incident and linked to the control gap it exposed. From there, you raise a corrective action (CAPA) to close that gap.

Incident
Control gap
Audit finding
Corrective action
Evidence of closure
Each record links to the one before it, so a closed finding can be traced back to the incident that caused it.

Frequently asked questions

Which regulatory reporting timelines are included?

Reporting deadlines are configured for each regulation, including DORA's 4-hour initial notification, NIS2's 24-hour early warning, the DFSA's and ADGM's 72-hour breach and incident windows, and GDPR's 72-hour breach notification. The countdown runs on the incident record from detection to notification.

How does an incident become a CAPA?

The root-cause analysis on the incident links to the control gap it exposed. Raising a corrective action creates a CAPA with an owner and a due date, which closes with evidence. Every step can be traced from the incident to closure.

See how xmodo works for your organisation

Get a demo on the frameworks that apply to you.

Get a demo