Skip to content
Operational Risk Management | Part 8 of 8

Running the Register: Review Rhythm and Seven Key Figures

One file, one owner, one version, fixed dates. The four reviews that keep a register alive, the seven figures that steer it, and the cheapest honest check there is.

Most registers are not wrong. They are old. The rating was honest on the day it was made, the measure was started, and then nobody looked again until the next audit. Dates are what separate a register from a workshop memory.

Four reviews

Monthly, the risk owner of the site produces one page: measures past their date, risks past their review date, new events. If the page is too long to read out loud, the problem is already visible.

Quarterly, the site team goes through every risk above the threshold with its owner. Is the rating still right? Does the measure work? What has the last quarter taught us?

Twice a year, plant management sees the key figures, the risks above the threshold, the second list of impact class 5, and the decisions it owes.

Once a year, the full collection round runs again, every risk is reviewed, and the scales and thresholds are confirmed or changed deliberately.

And after every event, whatever its size: was it in the register, was the rating right, what changes in the plan?

Seven figures

Key figure Start Month 12
Expected loss per year EUR 1,000,000 EUR 469,350
Risks in the red field 1 0
Risks in the orange field 3 2
Measures overdue 5 0
Risks reviewed within twelve months 54 % 100 %
Continuity exercises in twelve months 1 4
Events that were in the register 60 % 88 %

The first four say whether the work is being done. The fifth says whether the register is alive. The sixth says whether the plans are real. The seventh is the only one that tests the whole system.

The cheapest honest check

Write down every event that cost more than one day or EUR 25,000 and ask whether it was in the register.

The example plant, a site for conveyor components, had eight such events in twelve months: a spindle failure, a voltage dip, a late casting supplier, a compressed air trip, a test bench out of calibration, water through the roof, an insolvent forwarder and an agency shortage in the autumn peak. Seven of the eight were in the register. The eighth, the casting supplier, became risk R-25 within two weeks.

The actual loss of those eight events was EUR 498,000, against an expected EUR 469,350 for the whole year. That closeness is the best evidence there is that the scales are honest. Far apart in either direction, and the scales need a review rather than the register.

What the register has to hold

The sentence with cause, event and effect. The owner by name. Probability, impact in EUR and in days, the two classes, the score, the level. The expected value, because it is the only field that can be summed. The option, the measure, its cost, owner, date and status. The residual probability, impact and score. The last review, the next review and the source.

One file, one owner, one version. Several published standards describe this cycle, among them ISO 31000 for risk management and ISO 22301 for business continuity, and in their own words they ask for much the same sequence: identify, analyze, evaluate, treat, monitor and report. Keep the register you actually use. A register built for an auditor and not for the plant will be correct and useless.

Newsletter

One Lean idea.
Every two weeks.