How to Run a Weekly Leadership Risk Review in 30 Minutes

A weekly leadership risk review is not a reporting ritual. It is the short meeting where plant leaders decide whether the current control picture still deserves trust, whether a weak signal needs escalation, and whether the operation should slow down before the next shift normalizes the problem.

In Make The Difference: Be a Leader in Health & Safety, Andreza Araujo treats safety leadership as repeated decisions under pressure, not as a communication style. Across 25+ years in multinational EHS and more than 250 cultural transformation projects, she has seen the same pattern: the sites that improve fastest are the ones where leaders review risk before the incident forces the conversation.

The thesis of this guide is narrow on purpose. A weekly leadership risk review works when it is built around evidence, ownership, and next decisions. It fails when leaders use the meeting to admire dashboards, defend delays, or postpone the hard call until next month.

For teams that already use a safety decision log or risk trigger thresholds, this routine becomes even stronger because the meeting has a place to record and escalate what the review uncovers.

What you need before starting

Bring four things to the meeting. Bring the last decision log, the current top risks, field evidence from the work itself, and one leader who can move resources or stop exposure. If the room does not have those inputs, the meeting should not pretend to be a risk review. It is only a status chat.

The agenda should stay small enough to fit on one page. If the review needs a deck, a subdeck, and a backup deck, the meeting is already trying to cover too much. Andreza Araujo's work in Safety Culture: From Theory to Practice keeps returning to the same point: culture shows up in repeated decisions, so the meeting has to expose the decisions that matter.

• Last week's decisions and overdue actions.
• The five most material risks or weak signals.
• Current field evidence, not only email updates.
• One person who can commit the area to action.

Step 1: Fix the time and the chair

Set the review in the same weekly slot and keep it there. A risk review that moves every week teaches the organization that the meeting is optional, and optional meetings do not change behavior. The chair should be the person who can make a decision move, not the person who only knows how to collect notes.

For a plant manager, that usually means chairing the meeting or naming a deputy with direct authority. For an EHS lead, it means bringing the evidence, challenging weak logic, and making escalation clear. For a maintenance or operations leader, it means showing up with the ability to change sequence, staffing, or timing when the review reveals a real gap.

The verification test is simple. If the chair cannot approve a resource, escalate a control failure, or stop a risky job, the meeting is already underpowered.

Step 2: Limit the agenda to five risks

Do not open the meeting with a full department report. Choose the five risks that are most severe, most active, most changed, or most likely to surprise the operation in the next seven days. That usually includes critical controls that are weakening, temporary deviations, repeat weak signals, contractor interfaces, and overdue actions with real exposure behind them.

The purpose is not to make the list feel complete. The purpose is to make the list actionable. A leadership team that tries to review twelve topics in thirty minutes will end up reviewing none of them deeply enough to matter. Smaller scope creates sharper judgment.

If a sixth or seventh issue appears, park it for the next review unless it is immediate danger. That rule protects the meeting from drift and keeps the team focused on the exposures that can actually change today.

Step 3: Bring field evidence into the room

Each risk line needs current evidence from the work itself. That can be a control verification, a walkdown note, a permit check, a maintenance record, a supervisor observation, a worker concern, or a photo that shows the condition as it exists now. If the team cannot show evidence, it should not pretend that the risk is understood.

This is where many reviews weaken. The dashboard looks clean, the action tracker looks current, and the team still has no proof that the barrier exists in the field. A meeting that relies only on slides will reward the smoothest narrative, not the most honest risk picture.

Use the same discipline that a good control review uses, because field evidence and control verification belong together. If your team needs a stronger evidence base, the article on critical control verification is the right companion read.

Step 4: Ask the same four questions in the same order

Every risk line should be tested with the same four questions. What changed? What evidence proves it? What decision is needed now? Who owns the next proof? The order matters because it keeps the review from jumping straight to solutions before the team understands the condition that created the pressure.

James Reason's work on latent conditions is useful here because the visible problem is often only the last layer. The review should keep asking until the team can see which condition changed upstream, which control weakened, and which decision allowed the gap to remain open.

When the room cannot answer one of the four questions, the response should not be debate for its own sake. The response should be to fetch the missing evidence or escalate the issue to someone who can answer it.

Step 5: Decide, do not just discuss

At the end of each risk line, the team should choose one of four outcomes. Accept for now, escalate, stop, or redesign. Anything else is just talk. The decision must also name the owner, the deadline, and the next proof that will show whether the decision changed the field condition.

This is the point where a weekly review becomes a leadership tool instead of a meeting about concern. Andreza Araujo has seen in more than 250 transformation projects that the best sites do not have more concern. They have faster decisions when the concern is real.

If your organization needs help turning that discipline into a repeatable routine, Andreza Araujo and ACS Global Ventures can help build the cadence, the decision log, and the escalation logic around the work.

Step 6: Separate immediate risk from slow drift

Not every issue belongs in the same lane. Immediate risk belongs in the same day lane, because the exposure can change before the next shift. Slow drift belongs in a tracked lane with a date for review, because the problem is real but not yet acute. That separation stops the review from treating every issue as an emergency and from treating every issue as a background note.

This is where risk trigger thresholds help. A leadership team that knows when to watch, verify, escalate, or stop can avoid the common trap of turning every weak signal into a vague action item. Thresholds make the review faster because they reduce argument about urgency.

For the plant manager, this step matters because production pressure is always trying to flatten the difference between urgent and important. The review should protect that distinction.

Step 7: Record the decision in one sentence

The log entry should be short enough to read next week without translation. It should capture the risk, the decision, the owner, the evidence, and the next proof. Do not record the whole discussion. Record the choice that changes exposure.

A good entry reads like this. \"Critical control on Line 3 degraded after repeat bypass finding. Maintenance owner to restore guard by Thursday. EHS to verify in field before restart.\" That sentence tells the next leader what mattered, who owned it, and how the team will know whether the decision held.

A decision log only works when it stays close to the meeting. If the record is buried elsewhere, leaders stop using it. If you want the structure behind that habit, keep the safety decision log next to the weekly review and not off to the side.

Step 8: Review the pattern after four weeks

After four weekly cycles, step back and look for repetition. If the same risk keeps returning, the issue is probably not the meeting. The issue is a control gap, a decision gap, or a pressure point that the organization has not fixed. Repetition is a signal, not a coincidence.

That pattern review is where safety leadership becomes visible. A site that keeps reexplaining the same weak signal without changing the underlying condition is not learning. A site that changes the control, the owner, or the threshold is doing real work.

Across 25+ years of executive EHS work, Andreza Araujo has seen that repeat issues usually come from one of three places. The control was weak, the owner lacked authority, or production pressure kept outrunning the review. The meeting should be designed to expose which one is true.

Final checklist

• The review is fixed to one weekly slot and chaired by someone with real authority.
• The agenda stays limited to the five most material risks or weak signals.
• Every risk line brings current field evidence into the room.
• Each line ends with one decision, one owner, one deadline, and one next proof.
• Repeat issues are reviewed after four weeks so the same gap does not keep cycling forever.

FAQ

How long should a weekly leadership risk review take?

Thirty minutes is enough when the agenda is tight and the chair keeps the room on the decision path. If the meeting needs more time every week, the real fix is usually better scope, not a longer calendar block.

Who should attend the review?

The people who can change the risk should attend. That often means the plant manager or operations lead, the EHS lead, the area owner, and the person who owns the relevant control or resource. A large audience usually slows the decision and adds little value.

What if the team has no change to report?

No change is a valid result when the field evidence supports it. The important part is that the team can explain why the control picture is still stable. Silence without evidence is not the same thing as no change.

Is this the same as a dashboard review?

No. A dashboard review shows numbers. A leadership risk review decides what those numbers mean for exposure, ownership, and action. Dashboards can support the meeting, but they should not replace it.

What if new issues keep appearing during the review?

Use a parking list for items that are not immediate danger, then assign them to the next review or to a separate owner. If an issue is acute, the meeting should switch from discussion to escalation right away.

A weekly leadership risk review becomes valuable when it changes the next seven days, not when it makes the room feel informed. If your operation wants the deeper system behind that habit, start with Make The Difference: Be a Leader in Health & Safety and the rest of Andreza Araujo's leadership work, then connect the review to real decisions, real evidence, and real field proof.

For support, use Andreza Araujo or the Andreza Araujo store to reach the book and advisory ecosystem behind this cadence.