Skip to content
FTRA
Insights

Operational risk

Why Operational Risk Registers Need Owners and Review Dates

A general guide to risk descriptions, controls, accountable owners, residual risk and action tracking.

For general education only. Any example is fictional, and this article is not legal, insurance or financial advice.

A register is a management tool, not a document

Many organisations have a risk register that was completed once and rarely opened again. A register only reduces risk when someone is accountable for each risk and the entries are reviewed on a schedule.

Write risks clearly

A useful risk description explains the cause, the event and the consequence. 'Vehicle breakdown' is vague; 'Missed preventive maintenance leads to a breakdown on a long-distance route, delaying deliveries and exposing the driver to roadside risk' gives the owner something to manage.

Record the controls you actually have

List the controls that are in place today, not the ones you intend to introduce. Planned improvements belong in the action column, with a due date and an owner.

Every risk needs an accountable owner

The owner is the person with the authority to make decisions about the risk and its controls. Naming a role as well as a person helps the register stay current when people move on.

Understand residual risk

Rate each risk before and after its current controls. The residual rating shows where controls are working and where the organisation is still carrying more risk than it is comfortable with.

Set review dates and track actions

Review dates turn the register into a living process:

  • Higher-rated risks are reviewed more often than lower-rated ones.
  • Each action has an owner, a due date and a status.
  • Reviews record what changed, even if the answer is 'nothing'.
  • New incidents and near misses trigger a review of related risks.

More insights