Risk appetite explained: 4 decision levels leaders should separate

Risk appetite is the amount of risk an organization is willing to accept before it changes the plan. It matters because teams often mix appetite, tolerance, threshold and capacity into one vague idea, which makes the policy look clear while the work still runs on improvisation.

Risk appetite is the level of risk leaders are prepared to accept in pursuit of an objective. In safety, it only works when the organization translates that choice into visible limits, because a written appetite without a stop rule becomes a slogan the field has to guess its way through.

Across 25+ years in multinational EHS, Andreza Araujo has seen this confusion appear in permit reviews, contractor mobilization and shutdown planning. In Safety Culture: From Theory to Practice, repeated decisions matter because the pattern of decisions tells the truth about the site.

If you want the control side of the same problem, Risk Matrix: 6 Failures That Hide Serious Risk shows why a score is not a decision. For a supervisor view, Pre-Task Risk Assessment: 7 Supervisor Checks shows what should happen before work starts.

Definition

Risk appetite is not a comfort statement and it is not a numeric target by itself. It is a leadership choice that says which exposures the organization will accept, which ones it will challenge and which ones will trigger redesign, escalation or a stop to the task.

The problem starts when leaders speak about appetite at board level but never define the limits that matter on the floor. Once that gap opens, supervisors and workers are left to guess whether pressure is supposed to bend the rule or whether the rule still governs the work.

4 decision levels

1. Board appetite

Board appetite answers a strategic question. How much uncertainty will the organization accept while it pursues production, growth or cost control? If the board never answers that question, every later discussion becomes a negotiation after the fact.

2. Manager tolerance

Manager tolerance answers a practical question. What deviation can continue this quarter before the site has to intervene? Tolerance should stay narrower than appetite, because managers translate policy into action and they should not expand the policy just to protect schedule.

3. Supervisor threshold

Supervisor threshold answers an immediate question. When does the job stop today? A good threshold is visible, simple and tied to the work itself, which is why it belongs in the pre-job conversation rather than hidden in a document no crew can remember under pressure.

4. Operating capacity

Operating capacity answers a human question. How much variability can the team absorb before judgment starts to slip? When fatigue, overload and conflicting demands pile up, the stated appetite may stay the same while the real ability to act safely has already fallen.

How to differentiate in practice

The fastest way to separate the four terms is to ask who owns the decision and what would change if the limit is crossed. That is the difference between a policy that sounds mature and a system that actually controls work.

Appetite

Owned by senior leadership or the board. It sets the broad risk choice.

Tolerance

Owned by management. It defines what can continue for now.

Threshold

Owned by the supervisor and crew. It tells people when to stop the task.

Capacity

Owned by the operating system. It reflects how much change, load and uncertainty the team can absorb.

When to use appetite vs tolerance vs threshold

Use appetite when the executive team is deciding what the organization will accept. Use tolerance when the site is deciding what it can live with for now. Use threshold when the crew needs a clear line that triggers a pause, escalation or redesign.

The trap is to let appetite do the work of threshold. That mistake looks elegant on a slide, but it turns into pressure on the floor because workers are then asked to interpret a strategic idea as if it were an operating rule.

What leaders should do next

Pick one high-risk activity and write the four levels in plain language. Then test them against the field by asking the supervisor what would stop the job, asking the manager what would force escalation and asking the board whether the stated appetite still fits the exposure that the work actually creates.

If those answers do not line up, the policy is not finished. It is only abstract. Andreza Araujo's work keeps the same warning in view: a site is judged by the decisions it repeats under pressure, not by the wording it uses on the first page.

Talk to Andreza Araujo if you want help turning risk appetite into a working decision rule.