Incident Management Overview

What is Incident Management?

While Issues are used for routine defects (like a broken lightbulb or a leaky pipe), Incidents are used for significant events that require formal reporting, investigation, and root cause analysis.

Incidents typically include:

• Health and Safety events (e.g., Near Misses, First Aid Injuries, LTI).
• Environmental spills or breaches.
• Security breaches or property damage.
• Significant operational disruptions.

Key Capabilities

The Algus Incident Management module is an advanced workflow engine designed to handle the entire lifecycle of an incident:

1. Immediate Reporting: Quickly capture the initial details of an event via the web or mobile app.
2. Phase-Based Data Collection: Unlike static forms, Incident forms are dynamic. As the incident moves through its lifecycle (e.g., from Open to Under Investigation), new fields automatically appear to collect investigation data, root cause analysis, and witness statements.
3. Advanced Categorization & Severity: Classify incidents by type and use sophisticated Risk Matrices to automatically calculate risk scores based on likelihood and consequence.
4. Quality Managers & Executive Oversight: Designate supervisors or lead investigators (Quality Managers) who hold full control, permissions, and administrative authority over specific incident types. Higher-level roles (such as the CEO or operations executives) can be assigned to ensure complete oversight and real-time visibility across all site activities. Quality Managers are automatically assigned (Directly or by Acknowledgement) upon creation, and can also be managed dynamically on the fly in the details page.
5. Departmental Investigations: Divide complex investigations among specialized departments (e.g., Maintenance, Safety, HR) concurrently. Once globally enabled in settings, department groups can be defined with customized trigger stages (such as Open or Under Investigation), isolated tab-based fields, and immediate edit lockouts upon submitting a closure request. Access control is built-in; department members only see the incident in their list once their triggered assignment status becomes active.
6. Corrective & Preventative Actions (CAPA): Create linked tasks to address the root cause and prevent recurrence.
7. Controlled Closure: Ensure incidents are only closed when all investigations are complete and all CAPA tasks are resolved.

The Incident Lifecycle

An incident in Algus moves through a strict workflow driven by Statuses:

1. Open: Initial details logged and ready for review.
2. Under Investigation: Coordinators and departments are actively investigating the root cause. This phase typically reveals new mandatory data fields that must be completed.
3. Remediation: The investigation findings are being applied, and the team is working on corrective actions and linked tasks.
4. Closed: All actions are complete, and the incident is formally resolved.

Because incidents often involve sensitive data (like employee medical information), this module features rigorous Access Controls to ensure only authorized personnel can view specific incident types.