What is being communicated and for what purpose?
An unsafe condition is a work situation that can contribute to harm: impaired access, lack of protection, interference with other activities, or an organization that hinders the implementation of controls. Reporting the issue makes it visible and triggers its assessment. It does not require the person observing the situation to have a complete technical solution.
The aim is to improve conditions and learn about the actual work. This channel can complement preventive safety observation, inspections, and other engagement mechanisms. It should not be used as a substitute for risk assessment or as a way to shift all problem detection onto the workforce.
What an unsafe-condition report should include
A helpful notice explains where the situation is occurring, what has been observed, when it is happening, and who may be affected. A photograph can be helpful if it is taken without creating unnecessary exposure or revealing personal information. The description should focus on facts: “the machine guard is open during this operation” provides more information than “no one here is working safely.”
It’s also important to indicate whether the problem persists and what immediate communication has been made. There’s no need to turn the form into a full-blown investigation. Requiring too many fields, specialized terminology, or hard-to-obtain evidence can discourage valuable reports. The person receiving the notification should be able to gather more information later from the individuals involved.
Accessible channels and alternatives
The organization must provide channels that are appropriate for the shifts, languages, and available resources. An app can facilitate tracking, but it’s not a sufficient solution when some staff lack digital access or work in areas without connectivity. Direct communication with management, an internal phone line, or a simple form can complement this.
Employee consultation and participation help design the mechanism and identify barriers. It should be clarified who receives the reports, how they are managed, and what feedback is provided. If anonymous reporting is permitted, its possibilities and limitations should be explained without promising confidentiality that the system cannot guarantee.
Emergency and prioritization
The system must distinguish between routine reports and situations requiring immediate response. In the face of a potentially serious and imminent risk, simply filling out a form and waiting is not sufficient. Applicable protection and communication procedures must be activated, along with the responsibilities and rights stipulated by law.
Priority is determined by the potential severity, exposure, continuity of the situation, and the reliability of the barriers. Order of arrival is not always the appropriate criterion. There should also be a mechanism for reviewing an assigned priority when new information emerges. Internal management timelines do not justify maintaining an exposure that requires immediate intervention.
Assessment, allocation and measures
The person receiving the report verifies the facts, requests technical support when necessary, and assigns the action to a qualified individual. A distinction must be made between provisional measures and definitive solutions. A report is not considered resolved simply because it has been forwarded to another department or because someone has acknowledged receipt.
Corrective measures should address the problem and its root causes. If an area becomes clogged daily, removing materials might be an initial response, but it’s advisable to review storage and workflows. Recurring similar alerts provide information about the system, not a nuisance to be erased from the log.
Practical example
For several shifts, it’s been reported that a pedestrian walkway is blocked by goods. The initial response is to clear it, but the situation recurs. Analysis with the warehouse and production departments reveals that deliveries are arriving before space is available, and the walkway is being used for temporary storage.
The company reorganizes the reception area, defines an available storage area, and monitors traffic flow during peak times. It informs those who reported the problem about the measures taken and observes whether the passageway remains usable. Closure is based on this verification, not solely on a photograph taken after the materials have been removed.
Verifiable response and closure
Providing feedback demonstrates that the channel is useful. The response should explain what has been decided, what has been done, and what remains to be done. If the request is not confirmed or requires another approach, the reason should be explained respectfully. An automated response does not replace information about the outcome.
Verification of the closure process can include individuals familiar with the task, provided they are not given the technical responsibility to accept a risk. It is necessary to verify that the measure works under representative conditions and does not create another problem. When the solution is delayed, the interim measures and the individuals responsible for follow-up must be clearly visible.
Communication culture and channel evaluation
The channel needs to avoid retaliation for communications made in good faith and separate facts from judgments about people. If notifications are used to point fingers or exclusively reward those who register the most, their quality may suffer. Trust is built through consistent responses, accessibility, and observable solutions.
The evaluation may consider response times, closure quality, recurrence, and participation from different shifts. A low number of reports does not, in itself, demonstrate that few unsafe conditions exist. It may indicate a lack of confidence, access difficulties, or unfamiliarity with the reporting channel. Interpretation should combine the reports with work observation and consultation with staff.
