---
title: "Incidents and events"
url: "https://docs.4hse.com/incidents"
description: "What an office's event register holds (accidents, accidents and near misses, non-compliance, reports and requests) and how an event connects to the rest."
---

# Incidents and events

The **event register** holds what went wrong in an office, what nearly did, and what needs reporting so that it does not happen. It is in the menu of every **office**, under **Events**.

Every event has a **category**:

-   events with harm or a risk of harm: **Accidents**, **Accidents and near misses**;
-   departures from a rule: **Non compliance**;
-   **reports** of a malfunction or a failure;
-   **requests** for an inspection, maintenance, a replacement or an intervention.

The full list is in [Event types](/incidents/event-types).

## Why they belong together

[Section titled “Why they belong together”](#why-they-belong-together)

All categories are recorded with the same form and read in the same list. An accident tells you what happened; a near miss or a report tells you what could happen next time. Keeping them in one register lets the latter inform prevention before they turn into harm.

## What an event carries

[Section titled “What an event carries”](#what-an-event-carries)

An event records:

-   **what happened**: date, description, witnesses, the corrective actions proposed;
-   **who manages it**: the manager, assignee, watcher and recipient roles;
-   **who was involved**: the people of the office, with each one’s days of sickness;
-   **what was involved**: workplaces, equipment, substances, PPE, work phases;
-   **what is being done about it**: the linked prevention actions;
-   **the evidence**: documents and photos.

An event starts as **New**, becomes **Open** while it is being handled, and is **Closed** when it is concluded.

## Where it leads

[Section titled “Where it leads”](#where-it-leads)

An event recorded and left there has documented a problem. An event with a linked corrective action has started to solve it: the action is an ordinary [prevention action](/prevention-and-protection/), with its own deadline and certificate, and it appears in the [scheduler](/scheduler-and-notifications/) like every other.

The resources involved connect the event to the [risk assessment](/risk-assessment/): a piece of equipment that shows up in three near misses says something about the risk of the work phase it is used in.

## Procedures

[Section titled “Procedures”](#procedures)

-   [Register an event](/incidents/register-an-event)
-   [Link a corrective action](/incidents/link-a-corrective-action)
-   [Close an event](/incidents/close-an-event)
-   [Let guests report events](/incidents/guest-reporting)

This site is protected by reCAPTCHA and the Google [Privacy Policy](https://policies.google.com/privacy) and [Terms of Service](https://policies.google.com/terms) apply.