Overview

Risk register
What it is A domain of risk, and the unit of configuration
Example IT & Security Risk, Branch Network Risk
Holds risks? Yes
Methodology Owns it
Appetite Owns it
Layout Owns it

A risk register is a domain of risk — operational risk, information security, third party. It is also the unit of configuration: the methodology, appetite and form layout all live here.

Why the register owns the configuration

Because the register is where the numbers are. Risk appetite is meaningless without the scale it is expressed in, and the scale comes from the assessment methodology. Put both on the same object and they can never drift apart.

This also keeps the permission model small. Because a workspace holds no configuration of its own, it does not need to be a separate dimension of access — it is simply one of the things a grant can point at.

Choosing between them

Create a new register when a set of risks needs its own methodology, its own appetite, or its own owner.

When in doubt, create a register. Registers are cheap; workspaces are structure.