Incidents

The Incidents page is a single register for anything that went wrong: security incidents, health and safety (HSE) incidents, quality incidents, and environmental incidents. Each incident gets an automatic number, a severity, and a lifecycle from first report through investigation and containment to closure. Serious incidents can be escalated into a CAPA with one click.

Before you start

• The Incidents module (category: Health, safety & environment) must be enabled in Settings > Modules. It is on by default. The page lives at /incidents and appears in the side nav as Incidents.
• You need to be a member of an organization. Any member can report and update incidents. Only admins can change module settings.
• To use Raise CAPA, the CAPA module must also be available (it is on by default).

Report an incident

1. Open Incidents in the side nav and click Report Incident.
2. Fill in the dialog:
   • Title (required): what happened, in one line.
   • Description: what happened, who was involved, and the impact.
   • Category: Security, HSE, Quality, Environmental, or Other. Defaults to Other. Security incidents map to ISO 27001 A.5.24 to A.5.28; HSE incidents map to ISO 45001.
   • Severity: Minor, Moderate, Major, or Critical. Defaults to Moderate.
   • Occurred on: the date the incident happened.
   • Detected on: the date it was noticed. These can differ, for example a security breach found weeks later.
   • Location: site, area, or system.
   • Reported by: the name of the person who reported it.
   • Immediate action taken: the containment or first response already done.
3. If you pick the HSE category, four extra fields appear:
   • Injury type: for example laceration or sprain.
   • Body part: for example left hand.
   • Lost time (days): whole number of work days lost.
   • Recordable incident: check this if the incident counts as recordable under your reporting rules.
4. Click Report incident. The incident is saved with status Reported and gets an automatic number in the form INC-0001, INC-0002, and so on, sequential per organization.

Read the register

• The stats bar shows four counts across the whole register: Total, Open, Critical, and HSE recordable.
• Filter the list with the Status, Category, and Severity dropdowns. The stats bar keeps showing whole-register numbers even while filters are applied.
• Each row shows the incident number and title, the description, and tags: category, severity, status, the occurred or detected date, location, red lost-day tags for HSE incidents with lost time, a Recordable tag, and a CAPA tag once a CAPA is linked.

Move an incident through its lifecycle

The lifecycle is: Reported > Investigating > Actions in progress > Closed. Each row shows one forward button for the next step:

1. On a Reported incident, click Investigate. Status becomes Investigating.
2. On an Investigating incident, click Actions. Status becomes Actions in progress, and CompStack stamps the containment time on the record.
3. On an incident with Actions in progress, click Close. Status becomes Closed, and CompStack stamps the closure time.

The containment and closure timestamps together give you the incident timeline: reported, contained, closed. They are stamped once and are not overwritten if you pass through a status again.

Edit an incident

1. Click the pencil (edit) button on the row.
2. The same dialog opens with one extra field that only appears when editing: Root cause, the underlying cause found during the investigation.
3. Change any field and click Save. Switching the category away from HSE clears the injury fields.

Raise a CAPA from an incident

1. Move the incident past Reported first. The Raise CAPA button appears once the incident is Investigating or later and has no CAPA linked yet.
2. Click Raise CAPA. CompStack creates a CAPA titled "Incident INC-XXXX: