Risk Decision Log Explained: 4 Fields That Prevent Silent Risk Acceptance

A risk decision can disappear even when the risk itself remains visible. A register may show the exposure, a permit may authorize the task, and a meeting may mention the problem, yet nobody records who accepted the remaining uncertainty or what evidence would change that decision.

A risk decision log is a controlled record of a specific exposure, the person with authority to decide, the response required, and the evidence that will confirm whether the decision remains valid. It turns a temporary judgment into a traceable management choice that can be reviewed when conditions, controls, or assumptions change.

What is a risk decision log?

A risk decision log records the moment when an organization decides how to respond to a meaningful exposure. The decision may involve delaying work, adding an engineered safeguard, changing the method, escalating the issue, or accepting a bounded residual risk for a defined period.

That focus separates the log from a general list of hazards. ISO 31000:2018 treats risk management as a process connected to decision-making, while ISO 45001:2018 expects organizations to plan controls and manage operational change. A useful log connects those expectations to the question leaders often avoid, which is who decided that the work could continue under the stated conditions.

Andreza Araujo makes a similar distinction in Sorte ou Capacidade (Luck or Capability). Managing risk is not the same as taking it on and hoping that experience will compensate for weak controls. The log creates a visible point where method, authority, and evidence must meet.

4 fields that prevent silent risk acceptance

1. Exposure statement

Describe the unwanted event and the condition that makes it credible. “Working at height risk” is too broad to support a decision. “A temporary platform has an unverified edge-protection change before the maintenance window” identifies the exposure, the trigger, and the point that needs attention.

Write the statement so a supervisor, engineer, and manager would recognize the same situation. If the wording cannot be tested in the field, the log is recording a label rather than a decision problem.

2. Decision owner

Name the person who can change the method, fund a control, alter the schedule, reject the work, or accept a defined residual risk. The person exposed to the hazard is not always the person with authority over the conditions that create it.

This field prevents a common failure in operational meetings. Several people discuss the risk, but nobody owns the decision, so the work proceeds through momentum. A role title alone is weak evidence. The entry should identify the accountable manager and the decision they are authorized to make.

3. Required response

State what must happen before the decision can remain valid. The response may be an engineered change, a revised sequence, an isolation test, a competent resource, a change in staffing, or a formal escalation. Do not write “monitor” unless the log states what will be monitored and what result requires intervention.

The response should also show what the organization is not using as a substitute. A briefing can clarify a control, but it cannot replace a missing guard. Personal protective equipment can reduce harm, but it does not remove the exposure that earlier controls could have prevented.

4. Verification evidence

Specify the proof that will show whether the response is present and working. Evidence may include a functional test, a field inspection, a design review, a photo with location and time, a completed isolation record, or a supervisor observation tied to the actual task.

Add the review trigger. The decision should return to the log when the work changes, a control fails, a contractor interface appears, a near miss occurs, or the stated evidence no longer matches field conditions. Without a trigger, a temporary acceptance quietly becomes normal work.

How to differentiate a risk decision log from a risk register

Use the three tools together when they answer different questions. A matrix can support prioritization, a register can keep the exposure and treatment visible, and a decision log can show why work continued, stopped, or changed. The risk register explained guide covers the ownership and evidence structure that should feed the decision log.

When should leaders use a risk decision log?

Use it when a critical task starts with an unresolved control, when a temporary deviation is proposed, when production pressure competes with a safety requirement, or when a decision depends on evidence that will only become available later. It is especially useful for shutdowns, simultaneous operations, contractor interfaces, management of change, and work that crosses departmental boundaries.

A risk decision log is not a permission slip for weak controls. Its value is that it makes uncertainty visible, gives the right person a decision to own, and sets a condition under which the decision must be reopened. If the entry has no owner, no response, or no evidence, the organization has not managed the risk. It has only documented its discomfort.