Incident management is how organisations respond when something goes wrong in production— restoring service, communicating clearly, and learning so the same failure is less likely next time. It sits at the heart of ITSM and supports ISO 27001–style assurance when evidence of handling and improvement is required.
What counts as an incident?
In plain language, an incident is an unplanned interruption or reduction in quality of an IT service (or another agreed service) that affects users or business outcomes. Typical examples include outages, major performance degradation, security events that need coordinated response, or loss of access to a critical application.
That is different from a service request (“please reset my password”, “please provision access”), which is usually planned work on a known catalogue item. Mixing the two in one undifferentiated queue makes reporting, SLAs, and post-incident review unreliable.
What “good” looks like
Effective incident management usually includes:
- Single intake so every report has an owner, a timestamp, and structured detail—not only a chat thread.
- Prioritisation so responders tackle the highest business impact first, using agreed scales (for example impact and urgency mapped to priority).
- Lifecycle and communication—clear statuses, updates to stakeholders, and handover if shifts change.
- Closure and learning—what was done, what root cause analysis (where appropriate) will follow, and whether controls or documentation need updating.
Basic vs full incident capability
Basic incident management gives you governed intake, impact and urgency, a priority matrix, incident-specific statuses, and tickets that carry incident fields—enough for many teams to run a credible desk without a separate niche product. ISMSVision includes this with Service Management and the service desk; customer portal reporting is available when you enable it (alongside Knowledge Base for self-service).
A future Full Incident Management add-on is planned with deeper ITIL-style workflows and reporting as a chargeable module—coming soon.
For step-by-step configuration in the product, see our practical configuration guide.