EHS Coordinator in 90 Days: Build Safety Voice

A new EHS coordinator usually inherits two things at once: a list of formal obligations and a workforce that has already decided whether speaking up is worth the risk. The second inheritance matters more than the first during the first 90 days, because a reporting channel that nobody trusts is only a decorated mailbox.

The common mistake is to start with a campaign. Posters, slogans, and toolbox reminders may create visibility, but they do not create psychological safety. In the field, people learn from the response they receive after raising a concern. If the first worker who reports a weak signal is ignored, exposed, or buried in bureaucracy, the next ten workers receive the message without attending any training.

Across 25+ years of executive EHS work and more than 250 cultural transformation projects supported by Andreza Araujo, one pattern keeps appearing: safety voice grows when response discipline becomes visible. The coordinator does not need to promise that every request will be accepted. The coordinator does need to prove that every serious concern will be heard, assessed, routed, and closed with a reason.

What the EHS coordinator must understand before starting

Psychological safety in occupational safety is not softness, permission to bypass rules, or a meeting style. It is the operating condition in which a worker can report a hazard, challenge a shortcut, or ask for help without expecting humiliation, retaliation, or career damage. Amy Edmondson's research on psychological safety gives the concept its academic foundation, while ISO 45001:2018 reinforces the management-system requirement for worker participation and consultation.

For a new coordinator, the practical question is narrower. Can a mechanic say that a lockout looks incomplete? Can a forklift operator tell a supervisor that a route is unsafe? Can a contractor ask for a work pause when the permit no longer matches the job? If the answer depends on who is listening, the site has a personality-based system rather than a safety system.

The coordinator's first 90 days should therefore focus on three signals: how concerns enter the system, how supervisors respond in the first hour, and how closure is communicated back to the person who raised the issue. Those signals are more persuasive than any stated value, because they are observable.

First week: map where silence already exists

The first week is not the moment to redesign every process. It is the moment to listen for the places where workers have stopped expecting a response. Review the last three months of near misses, hazard reports, stop-work events, maintenance delays, and informal complaints. Then compare the volume of reports with field exposure. A high-risk area with almost no weak signals is rarely a perfect area; it is often an area where people have learned to stay quiet.

Walk the site with supervisors, not as an auditor hunting defects, but as a coordinator testing the social path of a concern. Ask workers what usually happens after someone reports a hazard. Ask how long it takes to hear back. Ask which topics are safe to raise and which ones create friction. These questions reveal the real reporting culture faster than a generic survey.

If the site already has a formal stop-work process, connect the mapping exercise to the existing stop work authority protocol. That link matters because stop-work authority fails when it is treated as a heroic exception. The new coordinator should make it a normal escalation route with clear triggers, review rules, and supervisor response expectations.

First 30 days: make response time visible

By day 30, the coordinator needs a simple concern-response routine. The routine can start small: one intake point, one triage owner, one severity screen, one expected response time, and one visible closure rule. The point is not administrative elegance. The point is to prevent worker concerns from disappearing into personal inboxes, informal chats, or meetings where nobody owns the next action.

Set a response expectation for every safety concern that enters the system. A serious concern should receive same-shift acknowledgement, even if the full corrective action takes longer. The acknowledgement should say what was heard, who owns assessment, what immediate control is in place, and when the worker will receive an update. When the coordinator cannot accept a proposed fix, the answer still needs a technical explanation.

This is where many sites damage trust. They close the item in software, but the person who raised it never hears the decision. In *Safety Culture: From Theory to Practice*, Andreza Araujo emphasizes that culture becomes visible through routine decisions, not declared intent. Closure without feedback teaches silence, because the worker sees effort leaving their hands and never returning as learning.

Month 2: train supervisors to receive bad news

During the second month, the coordinator should shift attention from the reporting channel to the receiving behavior of supervisors. Workers do not report to an abstract management system. They report to a foreman, team leader, engineer, or manager whose facial expression and first sentence determine whether the conversation continues.

Train supervisors on the first minute after a concern is raised. They need to pause, thank the worker for the signal, ask what changed in the job, clarify exposure, and decide whether immediate control is required. They also need to avoid the three responses that kill voice: defending the plan before understanding the risk, asking who caused the problem, or treating the report as a personal inconvenience.

The coordinator can use field scenarios instead of classroom theory. A worker challenges a scaffold tag. A contractor reports that a line is not depressurized. A technician says the written procedure does not match the equipment. These are not communication exercises; they are risk-control exercises whose quality depends on the supervisor's ability to receive inconvenient information.

Month 3: create a technical dissent route

By month 3, the site needs a route for concerns that involve disagreement between knowledgeable people. Technical dissent is different from a casual complaint. It appears when an operator, engineer, technician, or supervisor believes the planned control is insufficient and the decision owner disagrees. Without a clear route, the weaker voice usually adapts to the stronger title.

The coordinator should define when dissent is escalated, who reviews it, what evidence is required, and how the final decision is documented. The review does not need to be slow, but it must be real. If a dissent route becomes a symbolic form that always confirms the original decision, the workforce will read it as compliance theater.

This is why a separate technical dissent protocol protects both safety and leadership. It gives the coordinator a way to separate personality conflict from risk disagreement, and it gives decision makers a record of why a control was accepted, changed, or rejected.

Month 4 onward: turn voice into leading indicators

After the first 90 days, the coordinator should stop measuring only the number of reports. Volume matters, but it can mislead. A site can have many low-quality reports and still miss serious exposure, while another site can have fewer reports with sharper risk information. The better dashboard asks what kind of voice is emerging.

Track concern response time, percentage of concerns closed with feedback, number of high-severity weak signals, repeat concerns by area, dissent cases reviewed, and corrective actions verified in the field. These indicators show whether voice is becoming useful for risk management. They also help prevent the organization from celebrating participation while leaving the same uncontrolled exposure in place.

The coordinator should review these indicators monthly with operations, maintenance, HR, and senior leadership. Psychological safety belongs in that room because silence is not only a human problem. It is a risk-data problem, a supervision problem, and a decision-quality problem.

Common mistakes that weaken the first 90 days

The first mistake is asking for more reports without fixing response. Workers quickly notice when the organization wants input but does not want the cost of action. The second mistake is treating every concern as equal. A broken sign and a degraded isolation barrier cannot move through the same priority lane, because one is housekeeping and the other may be a serious precursor.

The third mistake is allowing supervisors to personalize bad news. James Reason's work on latent failures remains useful here, because many events originate in conditions created far from the final action. When the first question is about who failed, people protect themselves. When the first question is about which control was missing, weak, or bypassed, the conversation can produce prevention.

The fourth mistake is hiding decisions behind EHS language. If a concern is rejected, say why in operational terms. If a corrective action is delayed, explain the interim control. If the worker misunderstood the risk, teach the distinction respectfully. Silence often grows from vague answers, not only from hostile ones.

Resources to deepen the coordinator's work

A new coordinator should study three adjacent capabilities. The first is safety culture diagnosis, because voice depends on the wider pattern of trust, accountability, and leadership behavior. The second is incident investigation, because post-event interviews often reveal whether people felt safe to speak before the event. The third is supervisor coaching, because the coordinator cannot personally receive every signal on every shift.

For a practical next step, pair this plan with a formal safety concern triage routine. Triage keeps the system credible by separating urgent exposure from routine improvement, assigning ownership, and making follow-up visible. Without that discipline, psychological safety becomes a good conversation with weak operational memory.

Andreza Araujo's work in *Safety Culture: From Theory to Practice* and her global safety-culture projects give the coordinator a useful principle for the first 90 days: do not ask the workforce to trust the system before the system proves it can respond. Start with response, train the receivers, document dissent, and let trust grow from repeated evidence.

Final field test for day 90

On day 90, the coordinator should be able to answer five questions without preparing a presentation. Which area has the most silence relative to risk? Which supervisor has improved response quality? Which concern changed a control? Which dissent case changed a decision? Which worker received feedback after raising an uncomfortable issue?

If those answers are available, psychological safety has moved from concept to operating practice. If they are not available, the next 90 days should not bring a new campaign. They should repair the response system until workers can see that speaking up changes how risk is controlled.

Organizations that need support building this kind of culture can work with Andreza Araujo to diagnose safety voice, strengthen leadership response, and convert worker participation into reliable risk controls.