Protocol

Run a risk review before a material operational change

A control can be perfectly designed for yesterday's system.

About 2 min read

Before you use it

Use when
  • A change affects tools, automation, staffing, workload, sequence, authority, dependencies or operating conditions in a consequential workflow.

Keep this limit in mind

  • Do not turn minor reversible edits into bureaucracy. Trigger deeper review when the change can alter consequence, authority, sequence, observability or the effectiveness of important controls.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Before the change goes live, identify which hazards may be introduced, which old controls might become weaker, what assumptions change and what evidence will show the new state is acceptable. Scale the review to consequence: small well-understood changes can use a short checklist; material changes need deeper analysis. Pair this pre-change review with post-change safeguard revalidation.

Steps

  1. Name the operational assumptions that change.
  2. Identify existing controls that depend on those assumptions.
  3. Look for new failure paths created by the change.
  4. Define preconditions, monitoring and stop criteria for rollout.
  5. Plan the post-change evidence that will confirm controls still work.

An example

Moving a critical approval from a human queue into an AI-assisted workflow changes timing, observability and decision ownership; review those risks before rollout rather than only testing whether the automation runs.

Check your result

The change record names both new hazards and existing controls whose effectiveness could change, plus how they will be verified.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingRun a risk review before a material operational change

Evidence and sources
Supports

OSHA process-safety guidance recommends identifying and reviewing changes before implementation and specifically says temporary changes need a monitored time limit because uncontrolled temporary changes can become permanent.

The guidance is written for hazardous industrial processes; the general exception-control pattern is transferred here by analogy.

Compliance Guidelines and Recommendations for Process Safety Management · Managing Change

Supports

FAA guidance notes that organizational or operational changes can introduce new hazards and can reduce the effectiveness of existing controls, so significant changes should go through a documented management-of-change process.

The advisory circular concerns fatigue risk in aviation; only the management-of-change principle is transferred.

AC 120-103A: Fatigue Risk Management Systems for Aviation Safety · Step 4: Identify Changes Affecting the FRMS

All sources (2)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details