Crew Resource Management Explained: 4 Communication Routines for Safer Decisions

Crew Resource Management (CRM) is a communication and coordination method that helps a team detect weak signals before they become unsafe decisions. In workplace safety, its value appears when a supervisor, operator, contractor, or engineer can challenge the plan and the team knows how to convert that challenge into evidence, action, and follow-up.

The aviation origin matters, but copying an aviation briefing into a plant does not create CRM. The practical question is narrower: which communication routines keep information moving when work changes, authority is uneven, and production pressure makes silence convenient? Across 25+ years of multinational EHS leadership, Andreza Araujo has seen that voice becomes a control only when the response is designed in advance.

Crew Resource Management is a structured way to use the knowledge, authority, and attention of everyone involved in a task. It combines briefings, closed-loop communication, challenge-and-response, and handover discipline so that a safety concern can change a decision before exposure reaches a person.

What does Crew Resource Management mean in safety?

CRM treats communication as part of the control system rather than as a soft skill added after the technical plan is complete. Amy Edmondson's work on psychological safety explains why people need enough interpersonal safety to raise information, while James Reason's work on latent failures explains why an unshared concern can align with other weak barriers.

That combination gives CRM a clear boundary. It does not mean accepting every opinion, removing accountability, or replacing a permit, risk assessment, or stop-work rule. It means making relevant information easier to raise and harder to dismiss without examination. This connects naturally with the 10-minute psychological-safety check before every shift.

4 communication routines that make CRM useful

Briefing before the task changes

A briefing should identify the task, the credible exposure, the critical control, the decision owner, and the condition that would require a pause. Keep the conversation tied to the actual work sequence. A five-minute discussion before a lift, isolation, or simultaneous operation is more useful than a generic reminder that everyone should be careful.

Verification requires one person to restate the highest-consequence condition in their own words. If the response is vague, the team has not yet established a shared picture.

Closed-loop communication

Closed-loop communication has three parts. One person states the information or instruction, the receiver repeats the meaning, and the sender confirms or corrects it. The loop prevents a message about a valve, boundary, load, or restart condition from being treated as complete merely because someone heard sound, and it makes the control whose status matters visible to everyone involved.

Use it for information that changes exposure or authority, especially when two crews share equipment or when a contractor is working inside an operating area. The shift-handover risk-transfer approach shows why the receiver must understand what remains open, not just what was completed.

Challenge and response

A challenge should describe the condition, the possible consequence, and the evidence that is missing. “I am not comfortable” may be an important signal, but “the isolation record does not match the equipment label” gives the team a testable starting point.

The person receiving the challenge should acknowledge it, examine the control, and state the decision. The answer may be to continue, change the sequence, add a control, or stop. Andreza Araujo's *Safety Culture: From Theory to Practice* supports this distinction because culture is revealed by repeated responses to inconvenient information, not by the number of values printed on a wall.

Handover with unresolved conditions

A handover is incomplete when it reports only finished work. It should also identify open hazards, temporary controls, changed assumptions, pending verification, and the person who can make the next decision. A useful handover can fit on one page, but it must preserve the decision trail.

Review the handover after 24 hours and again after 30 days if the condition remains open. Those two review points help distinguish a temporary arrangement that is being controlled from one that has quietly become permanent.

How can a supervisor differentiate CRM from a safety meeting?

The distinction matters because a meeting can be well attended and still leave weak coordination behind. CRM is present when communication changes the quality of the decision. That is why a supervisor should trace one concern from the first message through the final verification instead of counting how many people attended.

When should a site use CRM?

Use CRM when work contains multiple interfaces, changing conditions, high-energy exposure, or a large difference in authority between the people who see the risk and the people who control the work. Start with one task family, one supervisor group, and four routines rather than launching a slogan across the entire site.

In more than 250 cultural-transformation projects supported by Andreza Araujo's work, the durable shift has been practical. Leaders make it easier to raise information, then prove that the information can change sequencing, ownership, or control verification. The same logic helped inform the 50% accident-ratio reduction achieved in six months during her PepsiCo South America tenure, although CRM itself should not be presented as a single-cause explanation for that result.

For a broader diagnostic approach, read the distinction between psychological safety, trust, and unrestricted error tolerance. Then choose one upcoming task and test whether the team can brief, repeat, challenge, and hand over the decision without losing the concern.