How to Run a 10-Minute Psychological-Safety Check Before Every Shift

A supervisor can ask whether the team has any concerns and still hear nothing useful. The silence may reflect agreement, but it may also mean that workers do not know what will happen after they speak. This 10-minute psychological-safety check is designed for the second problem.

The routine does not ask a shift team to share every feeling in public. It gives people a short, repeatable way to name a changed condition, challenge a plan, or request help, while giving the supervisor a visible duty to respond. Across 25+ years of EHS leadership, Andreza Araujo has seen that speaking up becomes a safety control only when the response is faster and clearer than the fear of raising the issue.

What you need before starting

Use the check at the start of a shift, before a handover, or before work with a changed risk profile. The supervisor needs the current work plan, the authority to pause or re-sequence the task, and a simple place to record the concern, owner, and next review time.

Keep the group small enough for every voice to be heard. A crew of six can usually complete the conversation in ten minutes. A larger operation should run the check by work team rather than turning it into a broadcast meeting. The aim is not to produce a perfect conversation. It is to create a dependable decision path.

This routine complements a daily safety meeting that surfaces bad news, but it is narrower. It tests whether people can influence the next shift decision, not whether the organization can collect another list of observations.

Step 1: State the purpose without asking for permission to speak

Open with one sentence that gives the check operational meaning. Say that the team is looking for changed conditions, unclear controls, and information that could alter the plan. Do not begin with “Does anyone have a problem?” because that wording places the burden on the worker to label a concern before the supervisor has defined what matters.

Explain what happens after a concern is raised. The supervisor will clarify the exposure, decide whether the work can continue, assign an action, or escalate the issue. Amy Edmondson’s work on psychological safety is useful here because it frames voice as a condition for learning and coordination, not as a request for unrestricted error tolerance.

Verification is simple. Ask one worker to repeat the purpose in their own words. If the answer is “we are just doing another safety talk,” the routine has started as a ritual rather than a control.

Step 2: Name the work that changed since the last shift

Review the differences that can change the risk picture. Cover the task sequence, equipment condition, staffing, interfaces with contractors, weather or site conditions, and any production decision that altered the original plan. The supervisor should describe the change before asking the team for reactions, since people often notice a mismatch only after they hear the expected sequence.

Use a visible work board or permit when one exists. Link the conversation to the same evidence used for control-of-work decisions, such as the decision gates for an unsafe restart. That connection keeps psychological safety from becoming detached from technical risk management.

Verify the step by asking, “Which part of today’s work is different from yesterday?” Accept a small answer. A changed delivery route or missing mechanic can be enough to require a new decision.

Step 3: Ask for the concern that is hardest to raise

Use a question that makes dissent concrete. Ask, “What could make our current plan wrong?” Then wait. Silence after a question is not proof that there is no concern, so give the group time to think and invite written input if speaking in front of peers is difficult.

The supervisor should answer with curiosity before judgment. “What did you see?” and “Which part of the plan does that affect?” keep the discussion connected to evidence. “Why did you do that?” usually pushes the conversation toward personal defense, especially when the concern involves a previous decision.

Verification requires at least one alternative view, even if the group initially agrees. Ask a rotating crew member to challenge the plan from the position of someone arriving late, working nearby, or responding to an abnormal condition. That practice strengthens the team’s ability to notice weak signals without pretending that every opinion carries the same technical weight.

Step 4: Separate a technical disagreement from a personal accusation

When someone challenges the plan, restate the issue in technical language. Replace “John is not following the procedure” with “the isolation step and the field condition do not match.” This protects the person who raised the issue while preserving the seriousness of the exposure.

James Reason’s work on latent failures helps explain why this distinction matters. A visible action may be the final point in a chain of design, planning, supervision, and equipment conditions. A supervisor who turns every challenge into a question about character loses information about the system that shaped the action.

Verify the reframing by asking the group to identify the barrier, condition, or decision that needs attention. If the conversation remains focused on who is at fault, pause the task discussion and reset the language before continuing.

Step 5: Decide what can continue and what must stop

Every concern needs a decision boundary. Classify the issue as work that can continue with a defined control, work that must be re-sequenced, or work that must stop until an authorized person resolves the exposure. Do not leave the team with a vague promise to “look into it later,” because uncertainty teaches people that speaking up creates delay without changing the job.

The decision should match the evidence available at the point of work. A supervisor may not need a full investigation to stop an activity when the critical control is absent, while a lower-consequence planning question may require a named follow-up before the next task phase. This is where a field verification routine, such as the one described in six safety-walk questions, can add evidence without replacing the immediate decision.

Verify by asking the person who raised the concern whether the decision addresses the condition they observed. If they say no, the supervisor has not closed the loop yet.

Step 6: Assign an owner and a time for the response

Record three facts in plain language: what was observed, who owns the response, and when the team will hear the result. The owner may be the supervisor, maintenance lead, planner, or EHS professional, but it should never be “the safety department” without a named person.

Set the review time before the conversation ends. A concern that remains open until the next weekly meeting may be acceptable for a low-risk improvement, but it is not an adequate response when the issue affects a critical control or a worker’s ability to refuse an unsafe task.

Verify the record by reading it back. The worker should recognize the concern without needing to correct a softened version of it. Accurate wording is a form of respect, especially when the original message was difficult to deliver.

Step 7: Report what happened to the previous concern

Start the next check with one short update on the last concern. State what changed, what did not change, and why. This is the part many teams skip, even though it provides the strongest evidence that speaking up affects management action.

If the response was incomplete, say so directly. A supervisor can explain that a decision is pending without pretending that the risk has disappeared. When leaders hide unfinished work to appear in control, the team learns to hide unfinished information in return.

Verify the step with a question such as, “What would you do if the same condition appeared on another shift?” The answer shows whether the team understands the new control or is merely waiting for a particular supervisor to be present.

Step 8: Close with the next opportunity to speak

End by naming when the team can raise a concern again and how to reach the supervisor outside the meeting. Mention the next handover, the point of work, and the escalation route for a condition that cannot wait. The closing message should be specific enough that a quieter worker can act without guessing.

Thank the team for useful information, not for being agreeable. Praise the decision that improved the work, whether it came from an operator, contractor, engineer, or supervisor. That distinction reinforces a culture in which technical dissent is part of safe execution rather than a challenge to hierarchy.

Verify by asking each person to identify one condition that would trigger an immediate pause. The answers should refer to the work, not to the personality of the supervisor.

What supervisors should record after the check

A short record is enough when it preserves the decision trail. Capture the changed condition, the concern raised, the control or decision selected, the owner, and the review time. Avoid turning the form into a survey with scores that create the appearance of measurement without showing whether risk changed.

Review patterns weekly. Repeated concerns about unclear permits, late maintenance, missing information, or production handoffs may indicate a design problem that individual coaching cannot solve. A supervisor who sees those patterns can escalate them through the same management system used for other operational risks.

Use this check alongside a post-incident psychological-safety review when an event has already occurred. The daily routine protects the next decision; the post-incident review examines whether the organization made it safe to report what happened.

Final checklist for the first week

• Explain that the check changes work decisions, rather than collecting opinions for its own sake.
• Describe what changed in the task, interface, equipment, staffing, or work environment.
• Ask what could make the current plan wrong, then wait long enough for a real answer.
• Translate personal accusations into technical descriptions of conditions and barriers.
• Choose whether work continues, changes sequence, or stops.
• Assign one owner and one review time for every concern.
• Report back on the previous concern before opening the next shift discussion.
• End with a clear route for raising information outside the meeting.

A 10-minute check cannot create trust by itself. It can reveal whether the operation is prepared to act when someone questions the plan. That is the practical test of psychological safety for a supervisor. Safety is about coming home, and people are more likely to protect one another when the system makes useful truth easier to say.