A structured incident record
Title, description, category, severity, status, owner and the affected business service sit on one record with a stable business reference, so people discuss INC-2026-0001 and never an opaque identifier.
Incident Register
An incident register that carries every incident from report to governed closure
Keep one record per material incident: severity, owner, affected business service, investigation, financial loss and regulatory reporting position. Link it to the services, assets, controls and risks it touches, and freeze the record when it closes.
From report to governed closure
Reported and classifiedCategory, severity and owner recorded against the affected business service
InvestigatedNarrative, root cause category and contributing factors captured
Linked to the wider recordServices, assets, controls, risks and evidence connected as what they are
Remediation decided by a personA finding or action plan is created deliberately, never automatically
Closed with a snapshotThe closed state is frozen for later review
Incident lifecycle in OrviQ. Each incident has a stable business reference in the form INC-YYYY-NNNN.
Register Capabilities
One register for incidents and what they affect
The register holds the incident. It links to canonical records elsewhere in OrviQ instead of duplicating them.
Investigation and financial ledger
Record the investigation narrative, root cause category and contributing factors, plus estimated loss, actual loss, recovery and net loss in the stated currency.
Regulatory reporting position
Capture reportability status, the regulatory bodies involved and the reporting deadline on the incident itself, so a disclosure date is not held in a separate spreadsheet.
The incident workflow
Six steps from first report to the closed record
Each step produces a distinct, attributable fact on the incident.
1. Report
Log the incident with title, description, category and severity from Low to Critical.
2. Assign
Name an accountable owner and the business service that was affected.
3. Investigate
Record the narrative, root cause category and contributing factors as understanding develops.
4. Connect
Link business services, assets, third parties, risks, controls, requirements and evidence.
5. Decide on remediation
A person decides whether the incident warrants a finding or an action plan, and creates it explicitly.
6. Close
Closure is governed, and an immutable snapshot of the closed incident is retained.
Honest by design
An incident is an event, and a judgement is separate
OrviQ avoids turning an event into a conclusion nobody made.
No automatic findings
Creating a finding or action plan from an incident is an explicit human action, because incidents often occur while controls operate exactly as designed.
Linking a control is not blame
Linking a control to an incident records that the control was relevant. It does not assert the control failed.
Business references only
People see INC-YYYY-NNNN references everywhere. Internal identifiers are never shown to users.
Connected Mesh
Related capabilities
Demonstration
See the incident register in OrviQ
Walk through an incident from report to closure with our product team.