Who report types are for and why
Any logged-in user can report a hazard, a fault or a potentially accident-causing event: with a location from the plant dictionary, a type, a description and photos. The list of reports is kept by privileged roles. This means entry is wide open, and the quality of the flow depends on how the OHS manager defines the types and the teams.
Badly defined types have two effects: a report about a forklift collision lands with the person responsible for lighting, or everything goes into one mailbox from which nobody picks the urgent matters.
Recommendation 1: assign priority to the type, not to the single report
Priority is a property of the report type, not of an individual report. That is why the type 'potentially accident-causing event on the road' should have high priority by definition, regardless of how the reporter describes it.
This protects against under-rating the importance by someone who lacks the competence to assess it. The reporter chooses the type after observation, and the assessment of weight stays in the definition.
Recommendation 2: narrow types for roads and traffic
For plant roads, several narrow types work better than one general type: condition of the surface, visibility and markings, a blocked escape route or pedestrian crossing, an event involving a forklift or vehicle, and a potentially accident-causing event.
A narrow type makes the choice easier for the reporter and speeds up handover. It is worth limiting the number of types to what an employee can handle in a few seconds.
Recommendation 3: match notifications to the weight of the type
A type can send an e-mail for each new report, as well as a collective summary, and it has default handling teams. For urgent types, turn on a notification for every report. For routine types, a collective summary is enough.
The rule protects against a flood of messages that teaches people to ignore them. Urgent matters should be rare and loud.
Recommendation 4: assign teams to plant areas
The team handling reports is assigned to plant areas, such as a hall or a zone, and the team's view can be narrowed to its areas. The maintenance team for Hall A does not need to see reports from the storage yard.
Dividing into areas shortens response time and clarifies responsibility. With organisational changes, it is enough to change the team assignment, not the definitions of the types.
Recommendation 5: watch the statuses and the reason for rejection
A report has the statuses: new, in progress, resolved, and rejected with a stated reason. Rejection is a final state and does not count as a repair. Reports should therefore never mix rejected ones with resolved ones.
Require a reason for rejection. A reporter who sees the justification will report better next time. A reporter who sees silence will stop reporting.
Recommendation 6: link reports to permits and audits
A work permit can be created from a report, and reports from one hall patrol are grouped into an audit with a name, a date and an auditor. When a road fault requires repair work, the permit is created from the ready report without retyping the data.
How to put these recommendations into practice
Start by reviewing the reports from recent months and grouping them into a few categories. If most of them land in one general type, that is a signal that the division needs to be narrowed. Introduce new types in stages: first those for events involving vehicles, then the rest.
After a month, check whether reports reach the right teams without manual forwarding. Every forwarding is a sign that the type or the area assignment needs improving. Repeat the review every quarter together with the managers of the handling teams.
Video
Frequently asked questions
Who can report a hazard?
Any logged-in user. They choose the location from the plant dictionary, the type, a description and add photos.
Can the priority of a single report be changed?
Priority is a property of the type. If a matter needs a different weight, choose the right type or define a new one.
What about a rejected report?
It stays in the final state with the stated reason and does not count as a repair.
Put order into reports about plant roads
Send us the list of types you use today. We will help narrow them down and assign them to teams and areas.
Let's talk