top of page

Your Safety Team Can't Be Everywhere. Your Managers Already Are.

Andrew Feehan
2 days ago
6 min read

Shared responsibility for safety means the people closest to the work own the safety issues in their area, with safety professionals supporting, coaching and stepping in where specialist expertise is needed. Most of the decisions that affect safety are made outside the safety team: how work is planned, how priorities are set, how people are supervised and how managers respond when something doesn't look right.


Yet in many organisations, safety work steadily drifts onto the safety team's desk. Over 25+ years working alongside safety teams, we've seen both models, and some clear patterns in what makes shared responsibility work without expecting everyone to become a safety expert.


Who is responsible for workplace safety?


Everyone in an organisation has a part in workplace safety, but the parts are different. Workers understand what the job looks like in practice. Managers understand their people, priorities and day-to-day operations. Operational leaders influence resources and decisions. Safety professionals bring specialist WHS knowledge, visibility across the organisation and experience in risk, investigation and controls.


Australia's model WHS laws already reflect this spread. The model Work Health and Safety Act places duties on the business or undertaking (section 19), on officers to exercise due diligence (section 27) and on workers to take reasonable care (section 28). The legal framework is context, not the reason to share responsibility. The stronger reason is practical: safety happens wherever work happens.


Why does safety responsibility end up with the safety team?


Responsibility concentrates in the safety team because they're the people everyone naturally turns to. Safety professionals have the knowledge, experience and judgement to handle difficult issues, so when something needs attention, it often lands with them.


That's understandable, but it has a cost over time. The people closest to the work can become less involved in managing the safety issues in their own areas. Some organisations we've worked with have found a different balance, where safety professionals stay closely involved but spend more of their time helping others carry their responsibilities instead of taking those responsibilities on themselves.


A few signs that responsibility has concentrated in the safety team:

  • Managers forward incident reports to the safety team without reviewing them first.

  • The safety team's list of open investigations keeps growing.

  • Managers describe issues in their own area as "a safety matter".

  • Hazards raised in a team only get addressed when the safety team follows them up.


Neither model is right for every organisation. Size, structure, risk profile and capability all play a part, and some concentration is sensible for high-risk or specialist work.


What safety responsibilities should line managers own?


Line managers are usually best placed to own the immediate response when something happens in their area. Take a reported incident. The line manager may be the right person to:

  • Speak with the worker involved.

  • Understand what was happening at the time.

  • Gather the immediate context around the event.


The safety professional then brings a different perspective, helping with classification, risk, investigation requirements and broader oversight. Both contributions matter. We've seen this work particularly well when the manager isn't expected to suddenly become a safety expert, and the safety professional isn't expected to take the whole issue away from them.


What is the difference between supporting responsibility and absorbing it?


Supporting responsibility means helping someone carry their accountability. Absorbing it means taking that accountability away from them. The difference changes where safety expertise gets applied.


Instead of personally investigating every event or managing every hazard, a safety professional who supports responsibility might:

  • Coach a manager through an investigation.

  • Review how an event has been classified.

  • Help someone understand the relevant risk or controls.

  • Step further into an issue when the circumstances require it.


The safety professional is still closely involved, in a way that helps others understand the parts of safety that sit within their own roles. We've seen this create a very different relationship between safety and the rest of the organisation. The safety function becomes a source of expertise and support, and the work stays connected to the people managing the area where it happened. That relationship depends heavily on trust between managers and safety professionals.


Does shared responsibility mean everyone does the same thing?


No. Shared responsibility doesn't mean identical responsibility. One risk in talking about shared safety responsibility is making it sound as though everybody should do the same thing. That hasn't been our experience.


We've seen managers handed safety activities without enough guidance or support, and the result is inconsistency and uncertainty about what's expected. Something as simple as classifying the severity of an event becomes difficult when people apply different interpretations or come from different backgrounds.


In those situations the safety professional's value goes up. Their experience helps create consistency, explain why a decision was made and build confidence in the people doing the work.


Why is so much safety work really capability building?


Some of the most effective safety work is also the least visible. It might be a safety professional:

  • Helping a manager through their first investigation.

  • Explaining why an incident was assessed a particular way.

  • Challenging a conclusion without taking the work over.

  • Helping someone connect an individual event to the hazard or control behind it.


It also includes spotting patterns across teams and locations that an individual manager would never see alone. This work is hard to measure, because the outcome is someone else becoming more confident and capable. Over time it lets safety knowledge travel further through the organisation, which is also what makes learning from incidents stick beyond a single team.


How do you balance safety workload between managers and the safety team?


Be deliberate about who does what and why, instead of letting responsibility pile up with the experts by default. There's a real workload issue underneath this. A safety team that personally investigates every incident, manages every hazard and owns every control can only stretch so far. Shifting work to managers without considering their capacity, confidence or knowledge creates a different problem.


A few questions help when you're working out the balance:

  1. Which safety activities need specialist WHS judgement, and which need local knowledge of the work?

  2. Do managers have the guidance, templates and coaching to do their part consistently?

  3. Where does the safety team add the most value: doing the work, reviewing it or coaching others through it?

  4. How will the safety team keep visibility of what's happening across the organisation?


There's no single model that suits everyone. Organisations work through this differently depending on their size, structure, risk and the capability of their people.


How can safety systems support shared responsibility?


Shared responsibility is easier when the system knows who owns what. If every report lands in a central safety inbox, the safety team ends up triaging everything by default.


Because SafetySuite is integrated with SAP SuccessFactors, incident and event management and risk and hazard management can use the organisational structure you already maintain. Reports route to the responsible manager through automated workflows, role-based access gives each person the right view, and the safety team keeps oversight through dashboards across the whole organisation. Managers stay connected to the issues in their area, and safety professionals can see where to step in.


Frequently asked questions


Q: Who is responsible for safety in the workplace?

A: Responsibility for workplace safety is shared. Under Australia's model WHS laws, the business, its officers and its workers all have duties. In practice, workers, managers, operational leaders and safety professionals each hold different parts of safety, based on what they know and control.


Q: What are a line manager's safety responsibilities?

A: Line managers typically own safety in their own area. That includes supervising how work is done, responding when something doesn't look right and leading the immediate response to incidents, such as speaking with the worker and gathering context. Safety professionals support them with classification, risk and investigation expertise.


Q: What does a safety professional do if managers own incidents?

A: Their role shifts towards coaching, review and oversight. They guide managers through investigations, check classifications for consistency, help people understand risks and controls, spot patterns across sites and step in when an issue needs deeper expertise.


Q: How do you build safety capability in managers?

A: Give managers clear guidance, coach them through their first investigations and explain the reasoning behind decisions such as severity classifications. Build capability gradually, and keep the safety team available for complex or high-risk issues so managers aren't left on their own.


Safety happens throughout an organisation


Shared responsibility for safety isn't about safety professionals stepping away, and it isn't about expecting everyone to become a safety expert. Safety happens throughout an organisation. Some of the most useful work safety professionals do is helping the people closest to the work carry their part of it, with the right support around them.


Want to see how SafetySuite routes safety work to the right people, integrated with SAP SuccessFactors? Talk to Us about sharing safety responsibility across your organisation. Talk to Us

 
 
bottom of page