How to Build a Leadership Risk Review Agenda in 10 Days

A leadership risk review agenda is the weekly script that tells leaders which risks, controls, decisions, and owners deserve attention before the operation drifts. It matters because a meeting that only receives reports cannot change the work, while a meeting that asks for evidence and decisions can reset it before small losses become bigger ones.

Safety leadership fails when the weekly review becomes a ceremonial dashboard. Across more than 250 cultural transformation projects supported by Andreza Araujo, the same pattern appears again and again. Meetings collect metrics, everyone agrees, and the field keeps its own pace. In Safety Culture: From Theory to Practice, the central point is that culture becomes visible in what leaders inspect and what they ignore.

This guide is for plant managers, EHS leaders, and site directors who need a practical routine. ISO 45001:2018 expects leadership review and improvement, OSHA's Recommended Practices for Safety and Health Programs place management leadership at the center, and HSE's leadership guidance ties good health and safety performance to active involvement and worker participation.

What you need before starting

Bring the last action log, the current control map, one field supervisor, one worker voice, and the names of the people who can approve a change. If your site cannot produce those five inputs quickly, the agenda is already too vague. A review that starts without evidence tends to end with opinions.

Use this routine with how to build a safety metric dictionary in 30 days and how to audit safety KPIs for false confidence in 30 days, because a leadership review only works when the metrics are defined and the dashboard does not hide weak signals. If the site is about to change scope, pair the meeting with how to run a scope change risk review in 20 minutes.

Step 1: Decide what the review is for

Choose one primary purpose for the meeting. It can be control drift, decision closure, or escalation, but it cannot be all three without priority. When the agenda tries to do everything, it becomes a report exchange. Leaders leave with information and no movement.

Write the purpose in plain language and keep it visible. A plant manager who wants faster decisions should say so at the top of the agenda, because people will always optimize for the signal that leadership repeats.

Step 2: Select only the evidence that can change a decision

Use evidence that can drive action, not evidence that merely fills a slide. The best inputs are control verification, new or recurring incidents, temporary changes, worker concerns, and overdue actions that still have a named owner. If a line item cannot alter a decision, it belongs in a report, not in the review.

This is where many teams copy a monthly management review and lose the point. ISO 45001:2018 asks for review, OSHA asks for leadership, and HSE asks for involvement, but none of those sources say a leader should sit through a stack of decorative charts. The agenda has to make the next move obvious.

Step 3: Write one owner next to every line item

Every agenda line needs a named owner and a named decision maker. Without both, the meeting pushes responsibility into the air and assumes someone else will catch it. That is how a risk review turns into a polite conversation.

Use role names only when the role is clear. "Maintenance" is too broad, while "maintenance supervisor on line 2" is usable. The point is not bureaucracy. The point is that a leader should know who can act before the issue sits for another week.

Step 4: Put the field voice before the dashboard

Start the meeting with what the field is saying, not with what the chart is saying. Ask one supervisor, one worker, and one contractor lead what is changing in the work. If their answers disagree with the dashboard, the dashboard may be stale, incomplete, or too flattering.

OSHA's worker participation guidance and HSE's involvement guidance both point in the same direction. Leadership does not improve by speaking more loudly than the field. It improves when leaders build a routine that can hear the field before the field becomes an incident.

Step 5: Turn each topic into a decision question

Do not ask for updates. Ask questions that force a choice. Is the control still effective? Do we keep the job running? Who owns the closure by Friday? Questions like these prevent the meeting from drifting into commentary, which is where weak accountability hides.

Andreza Araujo's book Make The Difference: Be a Leader in Health & Safety is useful here because leadership is not the act of listening to every problem. It is the act of deciding which problem must move first, which one can wait, and which one must go back to the field.

Step 6: Set the escalation rule before the meeting starts

Write the rule that sends an item to the next level. A weak control on a critical task, a recurring deviation, a repeat near miss, or a restart decision that depends on temporary conditions should not stay buried in the site meeting. If the issue can break the site norm, it needs a larger decision owner.

This is the same discipline used in scope change risk review and in permit revalidation routine. Scope drift and stale approvals are often the first signs that the local agenda is too small for the real risk.

Step 7: Convert every decision into an action record

Each decision should leave the meeting with a single owner, a due date, and the proof that will show closure. If the proof is only a note in the minutes, the action is not complete. It is only recorded. The field should be able to confirm that the control changed, not just that the meeting ended.

Use the action log as part of the next agenda, not as a separate archive. That keeps the meeting honest, because leaders can see whether the previous decision changed anything before they add new items to the list.

Step 8: Review the agenda after two meetings

After two cycles, remove any topic that did not change a decision and expand any topic that kept surfacing with no closure. A good agenda gets shorter before it gets smarter. The point is to reduce noise until the meeting can expose the real constraint in the system.

If the same issue keeps returning, the problem is rarely the agenda alone. It is often the control design, the ownership model, or the lack of field verification. In more than 250 projects, Andreza Araujo has seen that the meeting improves only when leaders are willing to change the work, not just the conversation around it.

• Every agenda line has a named owner and a named decision maker.
• The first inputs come from the field, not from the dashboard.
• Each topic is written as a decision question.
• Escalation rules are written before the meeting starts.
• The action log returns to the next meeting for verification.

If you want a stronger leadership rhythm, start with Safety Culture: From Theory to Practice and Make The Difference: Be a Leader in Health & Safety, then align the agenda with the way your site actually makes decisions. You can begin at Andreza Araujo or use the store at Andreza Araujo's store.