New Safety Governance Coordinator in 60 Days: Build Decision Rights Leaders Can Use

A safety governance coordinator can spend sixty days collecting decisions that nobody is authorized to make. The role becomes useful only when it clarifies who can accept residual risk, who must escalate an unresolved exposure, and what evidence a leader needs before work continues.

Picture a site where the weekly safety review is full, the action tracker is current, and serious questions still wait for a meeting. The coordinator is often blamed for slow follow-through, although the deeper problem is usually structural. A role without decision rights becomes a reporting service. A role with clear boundaries can turn scattered concerns into timely operational choices.

This guide is for a newly appointed safety governance coordinator in a plant, distribution network, construction business, or industrial operation. The sixty-day plan does not make the coordinator the owner of every risk. It gives the role a practical way to make ownership, escalation, evidence, and follow-up visible.

What the role must understand before starting

Safety governance is the operating system around safety decisions. It defines how a concern enters the system, who evaluates it, who has authority to change the work, and how the organization confirms that the response reduced exposure. The coordinator connects those points without taking accountability away from line leadership.

That distinction matters because an EHS function can identify hazards and provide technical advice, while the operating leader controls resources, priorities, staffing, and production conditions. ISO 45001:2018 reinforces the need for leadership, consultation, operational control, and continual improvement, but the standard does not decide which manager has authority at a particular site. Your first responsibility is therefore to make the local decision architecture explicit.

Andreza Araújo makes a related argument in Make The Difference: Be a Leader in Health & Safety. Safety leadership is not measured by how many reports pass through the system. It is measured by whether leaders respond visibly when evidence shows that work is not protected as intended.

Before changing any meeting, dashboard, or escalation form, write down three boundaries. The coordinator facilitates the flow of decisions. The risk owner decides within the approved limit. The accountable leader decides when the exposure exceeds that limit or when the operation cannot maintain the required control.

Days 1 to 10: map decision rights

Start with interviews rather than a new template. Meet the site leader, EHS manager, operations manager, maintenance leader, engineering representative, procurement contact, and at least two frontline supervisors. Ask each person the same questions, then compare the answers.

• Who can stop work when a critical control is unavailable?
• Who can approve a temporary control and for how long?
• Who accepts residual risk after technical review?
• Who receives an unresolved high-hazard action?
• What evidence closes an action instead of merely changing its status?

Do not treat disagreement as a documentation problem. If the operations manager believes the supervisor can accept a temporary deviation, while the EHS manager believes only the plant director can do so, the site has a decision-rights gap that deserves attention before the next serious exposure.

Create a one-page decision map with four columns. Name the decision, the role that recommends, the role that approves, and the condition that triggers escalation. Keep the language operational. “Review risk” is too vague. “Approve a temporary guard removal for one shift after engineering verification” is specific enough to test.

For a deeper model of these boundaries, connect the map to the four decision states that show who can stop unsafe work. The coordinator should not copy that article into a local procedure. Use it to sharpen the questions that local leaders must answer.

Days 11 to 20: test the escalation path

A written escalation path is not reliable until a supervisor can use it during a pressured shift. Select two recent unresolved actions and trace what happened from the first signal to the current status. Record where the issue paused, which role was waiting, and what information was missing.

Then run a short tabletop exercise. Give the group a hypothetical situation in which an engineering control is unavailable, a replacement is delayed, and production wants the task completed. Ask the supervisor to state the immediate boundary, the temporary protection, the person who must be informed, and the deadline for a decision.

The exercise should reveal whether the escalation path depends on personal relationships. If the answer is “call the person who usually helps,” the system is fragile. A dependable path names the trigger, the recipient, the response time, the interim control, and the authority that can stop the task.

Use the same test for concerns raised by contractors and temporary workers. A governance process that works only for permanent employees will miss exposures at the edges of the operating system. The coordinator should verify that the reporting route is available during nights, weekends, shutdowns, and handovers.

The article How to Build a Risk Escalation Path for Unresolved High-Hazard Actions can support this exercise. The useful question is not whether the site has an escalation document. It is whether a person under pressure can identify the next decision without guessing.

Days 21 to 30: establish a review rhythm

Replace large status meetings with a smaller rhythm that separates information from decisions. A weekly operating review should focus on open exposures, overdue control actions, temporary measures, and decisions that need a named authority. A monthly leadership review should examine patterns, resource constraints, repeated exceptions, and risks that cross departments.

Give every agenda item a decision label. “For information” means no decision is expected. “Decision required” means the owner, evidence, and requested action are ready. “Escalation required” means the current role cannot resolve the exposure within its authority. This simple vocabulary prevents a meeting from treating every topic as equally urgent.

Set a time limit for temporary controls. A temporary measure without an expiry condition can become the permanent design through routine. The coordinator should record the owner, the compensating protection, the verification date, and the condition that ends the temporary arrangement.

Keep the meeting close to the work. When an action remains open because the control cannot be verified from a report, schedule a field check rather than another discussion. A focused safety walk that verifies one control often produces more useful evidence than a longer review of percentages.

Days 31 to 45: connect evidence to action

Governance improves when evidence is attached to the decision that it supports. For each high-consequence action, define the proof before asking the owner to close it. The proof may be a guard test, a competency observation, a maintenance record, a field verification, an engineering calculation, or a worker confirmation that the changed method is usable.

Do not accept photographs as universal evidence. A photograph can show that a barrier was present at one moment, but it may not show that the barrier was correctly installed, maintained, understood, or available during the task. The coordinator should ask what failure the evidence rules out and what failure it cannot rule out.

Build a small evidence register with five fields. Record the exposure, the critical control, the owner, the verification method, and the next decision date. If a field cannot be completed, leave the gap visible. A complete-looking tracker with weak evidence creates more confidence than the operation has earned.

Use leading indicators carefully. Counts of inspections, meetings, observations, or training hours can show activity, but they do not prove that serious exposure fell. Pair activity measures with control verification and unresolved-risk aging so leaders can see whether work changed or whether the system simply became busier.

The distinction is consistent with the warning in A Ilusão da Conformidade, which treats completed requirements as insufficient evidence that protection works. The coordinator's job is to preserve that distinction when a dashboard makes administrative completion look reassuring.

Days 46 to 60: make accountability visible

By the seventh week, publish a short governance scorecard for leaders. Do not rank departments by the number of actions they closed. Show the decisions that were made, the high-hazard actions that remain unresolved, the temporary controls that are approaching expiry, and the barriers whose effectiveness still lacks evidence.

Every item should have one accountable owner, one next decision, and one date. Shared accountability sounds collaborative, but it often makes follow-through ambiguous. Several people may contribute. One role must still own the decision.

Ask leaders to review three cases in public. The first should show a risk that was escalated and resolved. The second should show a control that was challenged and improved. The third should show an issue that remains open because the organization has not yet provided a reliable solution. Showing unresolved work is not a weakness. It tells the workforce that governance is a route to action rather than a performance display.

At this stage, connect the scorecard to a monthly executive safety dashboard that changes decisions. The coordinator should keep the leadership view small enough that a director can ask a useful question about each line item.

Leadership visibility also changes the quality of reporting. When people see that a concern can alter a plan, a maintenance priority, or a staffing decision, they have a reason to raise it early. That is how governance supports safety culture without turning the coordinator into the owner of worker voice.

Common mistakes that weaken the role

The first mistake is accepting coordination without authority to convene the right decision-maker. The coordinator may not approve the control, but the role needs a clear route to the person who can.

The second mistake is measuring responsiveness by meeting attendance. A full room can still leave the same exposure unresolved. Track decision age, temporary-control age, and the time between escalation and an accountable response instead.

The third mistake is turning the action tracker into a second incident database. Governance should use existing evidence where it is reliable, while adding only the fields needed to make ownership and decisions visible.

The fourth mistake is treating every concern as equally urgent. A governance process must distinguish administrative housekeeping from an exposure that can produce serious harm. Otherwise, the most dangerous issue competes with routine completion tasks.

The fifth mistake is escalating without a recommendation. Escalation should state the exposure, the current protection, the missing decision, the options considered, and the time boundary. Leaders need a decision package, not a forwarded problem.

Resources to deepen the work

Use Make The Difference: Be a Leader in Health & Safety when the challenge is leadership behavior and operational follow-through. Use A Ilusão da Conformidade, translated as The Illusion of Compliance, when completed requirements are being mistaken for effective protection. Use Safety Culture: From Theory to Practice when the governance process needs to connect leadership habits, culture diagnosis, and field behavior.

James Reason's work on latent conditions and the Swiss Cheese Model can help the coordinator examine how decisions, resources, design, supervision, and frontline actions combine before an incident occurs. ISO 45001:2018 and ISO 31000:2018 provide useful management-system and risk-management reference points, but the local operating model still has to define who acts when conditions change.

After sixty days, the coordinator should be able to answer five questions without opening a spreadsheet. Which risks are waiting for a decision? Who owns each decision? What evidence is missing? When does a temporary control expire? What will change if the exposure remains unresolved?

A safety governance coordinator creates value when those answers lead to visible action. The role is not to make the organization look controlled. It is to help leaders decide whether the work is protected well enough to continue, and to make the next decision unavoidable when it is not.