InnerWeb
Skip to main content

Incident reports on internal roads: questions from the health and safety manager

Incident reports on internal roads can be submitted by all logged-in users, and they are handled by designated teams assigned to plant areas. Below we answer the questions the health and safety manager asks before rollout: who sees the list, how to set priority and when a report may be rejected instead of closed as fixed.

4
report statuses: new, in progress, resolved, rejected
Source: karta

Who can report an incident

Any logged-in user can report a hazard, a defect or a potential accident event. A report contains a location chosen from the plant dictionary, a type, a description and photos. The location dictionary matters: instead of the description "at the gate, where that puddle is", the system stores a specific place that can be counted in statistics and assigned to a team.

The full list of reports is kept by privileged roles, for example health and safety or maintenance. An ordinary employee sees only their own reports, which reduces the fear that reporting puts colleagues under judgement. For the plant this is essential: the culture of reporting potential accident events, meaning events that did not end in an injury, depends on whether the person reporting feels safe.

On internal roads a report most often concerns a damaged road surface, missing signage, a vehicle parked badly next to an evacuation exit or dangerous behaviour of a forklift truck. Each of these cases is worth having as a separate report type.

Who takes over a report and how to set priority

Priority is a property of the report type, not of an individual report. A report "oil leak on the road" may have a higher priority than "faded road markings", and this is set once at the type level rather than by each reporter separately. This limits the situation in which everything is "urgent".

A report type can send an e-mail for each new report as well as a summary, and it has default handling teams. For example, for a type concerning the road surface the default team will be the traffic maintenance service, and for a type concerning driver behaviour: security and health and safety.

The handling team is assigned to plant areas, meaning halls and outdoor areas, and the team view can be narrowed to its areas. In a plant with several halls and a manoeuvring yard, this avoids a situation in which the team of one hall sees and closes reports from another.

  • the report type sets priority and notifications
  • a default team is assigned to the type
  • the team has assigned plant areas
  • e-mail for each report or only as a summary

Example split of internal road reports by status

Example split of internal road reports by statusPie chart of 100 example reports: 62 resolved, 18 in progress, 10 new, 10 rejected.Resolved: 62 reports (62%)In progress: 18 reports (18%)New: 10 reports (10%)Rejected: 10 reports (10%)100reportsResolved62 reports (62%)In progress18 reports (18%)New10 reports (10%)Rejected10 reports (10%)
Source: Example calculation on 100 reports; illustrative values, not plant data

Statuses: when to reject and when to close

A report moves through the statuses new, in progress and resolved, and it can also be rejected with a stated reason. Rejection is a final state and does not count as a repair. This distinction matters for safety statistics: if rejected reports fed the repair counter, the response rate would look better than it is.

A report may be rejected if it does not concern the plant (for example an event outside its grounds), is a duplicate of an already open report, or describes a condition that is not a hazard and has been verified on site. The reason for rejection is mandatory, so that the reporter knows why their matter was not fixed.

Closing as resolved is used only when someone has removed the cause: repaired the surface, set a sign or changed the traffic organisation. The health and safety manager reviewing quarterly statistics can then count rejected reports separately from fixed ones.

From report to work permit and audit

A work permit can be created from a report. If repairing the road surface requires work in a traffic zone, the report becomes the basis of the permit, and its description and location do not have to be rewritten.

Reports from one site walk of a hall are grouped into an audit with a name, a date and an auditor. For an internal road this means that the result of the weekly road review is one document with a list of findings, not scattered reports without shared context.

For the health and safety manager the difference between a report and an accident is also useful: a report describes a hazard or a potential accident event, so it does not replace the accident documentation required by separate regulations.

Video

Frequently asked questions

Does a report have a location on the map?

A report has a location from the plant dictionary. The administrator sets up the dictionary, so the same places can be counted in statistics.

Can a rejected report be reopened?

Rejection is a final state. If the hazard returns, the reporter files a new report, which gets its own history.

Can a team see reports from halls outside its own?

The team view can be narrowed to its areas, so the team of one hall does not need to see reports from another.

Can a report type send e-mail?

Yes. A type can send an e-mail for each new report as well as a summary.

See how reports are handled on your roads

We will propose a set of report types and a split of teams across plant areas, and then show it in the panel.

Let's talk