A guardrail on a mezzanine stayed loose for four months at a site I know. Not because it was hidden. Three people had clocked it. The maintenance lead figured the shift supervisor had raised it. The supervisor figured it was already on maintenance’s list. The safety officer assumed, reasonably, that a loose rail on a walkway was somebody’s obvious priority. It came up eventually in a near-miss report, after someone caught themselves against it and it gave.
No policy was missing that day. A person was.
That’s the quiet failure mode nobody writes into a procedure. Hazard Identification and Risk Assessment holds together only when the roles behind it are actually named, not left to whoever assumes it’s covered. So this piece walks through who does what, and why that clarity ends up mattering more than any checklist or software an organization buys.
Why Roles Have to Be Spelled Out
An assessment is only as strong as the accountability sitting behind it. Spot a risk and it means nothing if no one owns the fix. Rate that risk carefully and it still means nothing if the rating never lands in front of someone who can actually authorize the repair.
Written policies love general language. “Management” is involved. “Staff” are responsible. It reads fine in a binder. Then a real hazard shows up on the floor at 2pm on a Tuesday, and “staff are responsible” turns out to mean nobody moves.
The frustrating thing is that the right people are almost always already there. What’s missing usually isn’t skill or willingness. It’s a plain map of who owns which stage, so that goodwill actually converts into a closed action instead of a shared shrug.
Breaking Down Each Role
Clarity starts with names, not categories that blur the moment work begins.
Employers and senior leadership carry the ultimate legal and ethical weight. They’re accountable for making sure assessments happen at all, that findings get acted on, and that there’s actually money to fix what turns up. Leadership also sets the temperature. If safety reads as a genuine priority at the top, that travels. If it reads as an afterthought, that travels too.
Safety or EHS managers run the machinery of the process. They build the framework, keep the documentation straight, track corrective actions, and hold things consistent across departments or sites. The job isn’t to personally spot every hazard on the property. It’s to build a system that catches hazards even when no one’s looking directly at them.
Supervisors are the bridge between the written procedure and the way work is really done, which are rarely the same thing. They tend to be the first to notice when a process has quietly drifted away from the safe design it started with, because they watch it happen every shift.
Workers on the floor are next to the hazard all day, and they see things nobody else does. A machine vibrating in a way it didn’t last week. A blind spot by the loading dock. A task that feels heavier than it should. Observations like those almost never reach a formal report unless people are genuinely encouraged to raise them, and believe something will come of it.
Contractors and third parties belong on this list too, and they’re the ones most often left off it. They’re working in a space they don’t know as well, which cuts both ways: they need clear, specific briefing on the site’s hazards, and they need a real channel to flag whatever looks off to them. Treating a contractor as an outsider to the safety process, rather than a participant in it, is a gap that shows up again and again in incident investigations.
A detailed breakdown of who is responsible for conducting a hazard assessment takes these roles further, and lands on the same conclusion: responsibility works better spread out than piled onto a single title.
How HIRA Ties the Roles Together
On its own, that’s just a list of people with opinions. HIRA is what turns them into a system, because the process itself creates checkpoints where each role hands off to the next.
Identification usually begins with workers and supervisors watching conditions firsthand. Evaluation, where hazards get ranked by likelihood and severity, generally falls to safety professionals who know how to weigh those two against each other without letting one drown out the other. And resourcing the fix, the new equipment or the rewritten procedure, sits with leadership, because that’s usually where the budget approval lives.
If you’re still formalizing all this, a practical guide to Hazard Identification and Risk Assessment is a better starting point than bending a generic template that was never built around how your operation actually runs.
When Roles Overlap or Go Undefined
Two patterns cause most of the damage. One is overlap: several people think they own the same task, so effort gets duplicated in one spot while a gap opens somewhere nobody’s watching. The other, and the more common one, is the vacuum, where no single person feels they own a particular hazard, so it just sits there, unaddressed, until something forces the issue.
Both come from the same place. The responsibilities were assumed, never assigned. Verbal agreements and “we all just know” don’t survive staff turnover, a busy quarter, or the slow drift that comes with growth. Written role definitions, looked at now and then, hold up long after the days when the team was small enough that everyone knew each other’s habits.
Clarifying Responsibilities in Practice
The fixes are small and mostly about discipline. Write down what each role owns inside the assessment process, not just their general job description. Put a named person, never a department, against every open corrective action, because you can’t chase down a department. Fold quick check-ins into your regular safety meetings instead of saving everything for the annual audit. Brief new hires on their specific part in hazard reporting during onboarding, not three months in when they’ve already learned to stay quiet. And revisit the role definitions whenever you restructure or add a site, since that’s exactly when the old assumptions quietly stop matching reality.
None of that costs much. It asks for a willingness to name specifics rather than settle for language that sounds tidy in a policy and falls apart the moment conditions get real.
The Takeaway
HIRA works when everyone involved knows precisely what they’re on the hook for, instead of trusting the process to run itself. Employers set the expectation. Safety teams build the framework. Supervisors turn policy into daily practice, and workers supply the ground-level detail no report ever fully holds.
Getting the roles right isn’t extra bureaucracy. It’s closing the small gaps where hazards slip through for months, purely because nobody was certain whose job it was to catch them. And once that clarity becomes a habit, it stops feeling like added work and starts feeling like the ordinary way things get done, the loose guardrail flagged on day one instead of month four.
