Skip to content

Incidents & Loss Events ​

Material business, operational, technology, security, compliance, third-party, conduct, fraud and privacy incidents, and the losses that may follow them.


Pages in this area ​

PageRouteWhat it does
Incidents/incidentsThe incident register and its full lifecycle

Documentation for this area ​

ArticleWhat it covers
Incidents & Loss overviewThe seven invariant distinctions
Incident RegisterFields, deep links and connected objects
ClassificationCategory, severity, impact and reportability
Investigation & Root CauseTimeline, root cause and contributing factors
Loss EventsThe financial ledger and currency handling
Closure GovernanceThe state machine and the immutable snapshot

Loss is never inferred from severity

A Critical incident with zero financial loss is entirely normal. So is a Medium incident that becomes reportable and a High incident that does not.

Severity, loss and regulatory reportability are set independently, from different criteria.


Permissions and entitlement ​

Requires the Incident & Loss Event Management entitlement. Closure requires incident.review and governed review approval — direct transition to closed is prohibited from every state.


OrviQ Enterprise Governance, Risk & Compliance Platform