Workplace Mental Health Escalation Protocol in 30 Days

A workplace mental health escalation protocol is a decision path that tells supervisors, HR, EHS, and occupational health what to do when distress becomes visible at work. It does not turn supervisors into clinicians. It keeps them from improvising when a worker shows anxiety, exhaustion, withdrawal, conflict exposure, suicidal language, panic symptoms, or fitness-for-work concerns.

The common market advice is too soft: train managers to be empathetic, remind employees about the EAP, and assume the case will move in the right direction. That is not a protocol. WHO's mental health at work guidance and the WHO/ILO 2022 policy brief both point to prevention, manager training, return-to-work support, and reasonable accommodation, while ISO 45003:2021 places psychological health and safety inside the occupational health and safety management system. The gap sits between those documents and the shift supervisor at 6:40 a.m., when the person in front of them is shaking, silent, angry, or unsafe to continue a task.

Across 25+ years leading EHS in multinationals, Andreza Araújo has seen that weak escalation creates two predictable failures. Some organizations overreact, remove people from work without enough facts, and damage trust. Others underreact, treat visible distress as attitude, and leave the person alone with risk. In *Sorte ou Capacidade* (Luck or Capability), Andreza Araújo treats safety as a system capability, not a matter of luck or individual toughness. Mental health escalation should follow the same logic.

What you need before starting

Before building the protocol, define the boundary. The protocol is for workplace response, not diagnosis. A supervisor can observe that someone is crying before operating mobile equipment, refusing a safety-critical handover, or reporting that they cannot sleep before every shift. A supervisor cannot diagnose depression, anxiety, trauma, or burnout. That difference protects the employee and protects the company.

You also need a small design group: one HR owner, one EHS owner, one occupational health or medical provider representative, one operations leader, and one legal or compliance reviewer when local law requires it. The group should map the protocol against existing articles on occupational anxiety signals managers should not misread, EAP limits, fit-for-work decisions, return-to-work planning, and psychosocial risk ownership, because escalation works only when those pieces stop competing with each other.

Step 1: Define the escalation triggers

Start by listing the signals that require action. Use observable language rather than clinical language. Good triggers include a worker saying they may harm themselves, a panic episode during safety-sensitive work, sudden withdrawal after harassment, repeated sleep-loss reports before operating equipment, visible intoxication or medication concern, conflict that creates fear of reporting, or a manager's documented concern that the person cannot complete a critical task safely.

The verification question is simple: would two trained supervisors describe the same event in similar words? If yes, the trigger is probably observable enough. If the trigger depends on a label such as unstable, weak, dramatic, resistant, or manipulative, rewrite it. HSE's Management Standards are useful here because they separate work-related stress risk into demands, control, support, relationships, role, and change. Those six categories help supervisors describe context without pretending to be clinicians.

Step 2: Split urgent risk from non-urgent concern

The protocol needs two doors. Door one is urgent risk, where the immediate duty is to protect life, stop exposure, and contact emergency or medical support according to local rules. Door two is non-urgent concern, where the employee may need privacy, support, referral, workload review, or follow-up, but there is no immediate threat to life or safety-critical control.

This split matters because many companies either send every concern to crisis handling or reduce every concern to an EAP suggestion. Neither response is disciplined. The WHO/ILO 2022 policy brief describes support for workers with mental health conditions through reasonable accommodations, return-to-work programs, and supported employment initiatives. Those options require triage, because an EAP referral alone cannot fix a hostile roster, impossible demand, or a role conflict.

Step 3: Assign decision rights before the first case

Write down who can remove a worker from safety-sensitive work, who can approve temporary task changes, who contacts occupational health, who calls emergency services, who informs HR, and who communicates with the employee's manager. If this is vague, escalation becomes a personality contest between the most nervous person and the most senior person in the room.

The best structure is a one-page decision-rights matrix. It should connect with the psychosocial decision-rights matrix already used for role clarity, because mental health escalation often fails when HR owns privacy, EHS owns risk, operations owns staffing, and nobody owns the handoff. Andreza Araújo's work in more than 250 cultural-transformation projects points to the same pattern: accountability has to be visible before pressure arrives.

Step 4: Build the supervisor script

Supervisors need words they can actually say. The script should open with observation, not accusation: I noticed you stepped away from the line twice and said you did not sleep before shift. It should move to safety and support: I want to check whether you can continue this task safely and what support you need right now. It should close with the next step: I am going to involve HR or occupational health according to our protocol.

The script must also ban three habits. Do not ask for diagnosis details. Do not promise secrecy when safety or legal escalation may be required. Do not debate whether the person is strong enough. In *Make The Difference: Be a Leader in Health & Safety*, Andreza Araújo treats operational leadership as a daily discipline of presence, clarity, and follow-up. The mental health script should reflect that same standard, since vague kindness is not enough when the worker needs a concrete path.

Step 5: Connect EAP, fit-for-work, and accommodation paths

Put the three support routes on one page. EAP is confidential personal support. Fit-for-work review answers whether the person can safely perform a specific task under current conditions. Accommodation changes the work, schedule, exposure, supervision, or recovery space so the person can keep working safely where possible.

The trap is using EAP as a disposal chute for organizational risk. An employee may need counselling and still need workload control, conflict intervention, or a temporary change in safety-sensitive duty. The article on EAP program traps for HR and EHS is relevant here because a high EAP utilization rate can hide weak prevention if the work conditions remain untouched.

Step 6: Protect confidentiality without blocking safety

Define what gets recorded, who can see it, and what never enters the supervisor's notebook. The supervisor record should focus on observable facts, immediate safety decisions, referrals made, and agreed work adjustments. It should not include diagnosis guesses, therapy details, medication assumptions, or personal history unless the employee voluntarily provides information that is required for an agreed workplace adjustment.

Privacy does not mean paralysis. If a worker states an immediate intent to self-harm, threatens another person, or cannot safely continue safety-sensitive work, the protocol must permit escalation to emergency, medical, or security channels according to local law. The credibility test is whether the organization can explain the boundary to employees before any case occurs. Hidden rules create fear, and fear damages early reporting.

Step 7: Add a work-design review to every repeated case

When similar cases repeat in the same team, shift, manager group, customer interface, or work area, do not treat them as isolated employee fragility. Run a work-design review using the HSE categories: demands, control, support, relationships, role, and change. Then compare the result with ISO 45003:2021, which gives guidance for managing psychosocial risks within an OH&S management system.

This is where the protocol becomes prevention rather than case administration. If three employees report anxiety before the same weekly production meeting, the problem may be the meeting design, not three individual conditions. If night-shift workers repeatedly escalate fatigue and panic symptoms before overtime blocks, the control belongs in staffing, rest, and shift planning. That connection is why the comparison of ISO 45003, WHO guidance, and ILO C190 matters for HR and EHS teams that need a shared technical language.

Step 8: Test the protocol with realistic scenarios

Run tabletop exercises before launch. Use five scenarios: a worker expresses suicidal language, a forklift operator reports panic symptoms, a supervisor sees a worker crying after customer abuse, an employee returns after mental-health absence, and a team reports fear of a manager. Ask each participant to decide what happens in the first ten minutes, first hour, first day, and first week.

The verification test is not whether the group knows the policy. The test is whether they can act without calling six people for permission. If the exercise exposes delays, missing phone numbers, unclear authority, or confusion about privacy, fix the protocol before communicating it widely.

Step 9: Launch, measure, and revise after 30 days

Launch with supervisors first, then HR and EHS, then the workforce. Measure the first 30 days with practical indicators: number of supervisors trained, number of cases triaged by pathway, time from concern to first response, number of work-design reviews triggered, number of accommodations agreed, and number of cases where the first escalation was unclear.

Do not measure success by low use. Low use may mean stability, but it may also mean distrust. A better question is whether people know where to go before a crisis, whether supervisors can describe their role, and whether repeated cases trigger prevention. For employees returning after absence, connect the protocol with a structured mental-health return-to-work plan so the escalation path does not end at the first conversation.

Final checklist before approval

• Triggers use observable language and avoid diagnosis.
• Urgent risk and non-urgent concern follow different routes.
• Decision rights are visible for supervisors, HR, EHS, occupational health, and operations.
• The supervisor script protects dignity, safety, and privacy.
• EAP, fit-for-work, and accommodation are connected instead of competing.
• Repeated cases trigger work-design review, not only individual referral.
• Tabletop tests prove that the first ten minutes are clear.

A mental health escalation protocol is not a poster, campaign, or awareness week. It is an operating routine for moments when distress intersects with safety, privacy, and leadership. Andreza Araújo's safety-culture position is useful here because it refuses the split between technical control and human care. In *Muito Além do Zero* (Far Beyond Zero), the central critique is that absence of accidents is not proof of a healthy system. In mental health at work, absence of visible crisis is not proof of care either.