Skip to content

Codes, statuses and values

Every code, status and fixed value a user meets in Risk Core, in one place, each linked to the page that explains it. Codes are issued by the system, and tiers, bands and statuses are derived by it: none of them is typed.

See Computed, never typed.

RecordFormatIssuedExplained in
RiskCM-RISK-2026-001When the risk is first savedRisk register
Loss eventLE-2026-0001When the event is first savedRecording a loss event
KRIKRI-CM-001When the indicator is first savedKRI library

A code cannot be typed or changed.

StatusMeansMoves to
DraftThe Risk Champion is preparing the filing; its risks can be editedSubmitted
SubmittedSent for review; its risks are lockedReviewed or Returned
ReviewedPassed by the Reviewer; waits for the ApproverApproved or Returned
ApprovedSigned off; a snapshot of what was approved is recorded, and the heat map, dashboards and report-up read itDraft, when the entity’s own Entity Risk Manager reopens it
ReturnedSent back to the Risk Champion with a reason; editable againSubmitted

Explained in Submission and sign-off.

StatusMeans
DraftBeing completed by the first line; seen only inside the entity
Submitted to Risk ManagementComplete and sent for validation
Under review by Risk ManagementThe Entity Risk Manager is checking it
Returned for more informationSent back to the reporter, then submitted again
Validated — in the loss data setAccepted by the entity’s Entity Risk Manager; validator stamped; reported up
Rejected — not an operational risk eventNot accepted, with the reason; left out of the data set and the monthly report; not reported up
ClosedHandling finished; stays reported up

Explained in Validation and visibility.

TierRouted to
Tier 1The Risk Champion
Tier 2The route the group sets
Tier 3The RMC and the board

The tier is computed from the event’s latest position against the group’s thresholds. Explained in Materiality tiers.

BandMeans
GreenWithin appetite
AmberApproaching the limit — an early warning
RedOutside appetite — a breach; an explanation is required and an action item is created

Explained in Thresholds and Observations and breaches.

A critical activity’s criticality tier is computed from its MTPD against the MTPD bands the group root sets. The bands, and so the tiers, are group configuration and mean the same thing in every company of the group. Explained in Critical activities and Group configuration.

LevelMeansRecorded in ERM Core as KRI band
NormalNo incident is open for this hazardGreen
StandbyThe hazard is expected; prepareAmber
ActivatedThe plan is in forceRed
ClosedThe incident is over; a draft loss event is created—

Every change of level is pushed to every staff phone. Explained in BCP levels and External KRIs from BCP Core.

CodeLevel-1 event type
EL01Internal fraud
EL02External fraud
EL03Employment practices and workplace safety
EL04Clients, products and business practices
EL05Damage to physical assets
EL06Business disruption and system failures
EL07Execution, delivery and process management

Explained in Standards mapping.

ValueMeans
SafeYou are safe
AffectedYou are safe but affected, for example water near your home or no way to travel
Need helpYou need help now
Not reportedNo check-in yet; team heads and HR see who has not reported — see Team and unit status
Work statusMeans
In officeWorking at the office today
Working from homeWorking from home today
Unable to workCannot work today
On leaveOn leave today

Explained in Check-in and Work status.

ValueValuesExplained in
Customer risk levelLow · Medium · HighRisk scoring and adjustment
Approval routeLow and Medium: Maker → Checker · High: Maker → Checker → ApproverNew-customer approval
Restriction modesFULL LOCK · FULL ASSET FREEZE · EXIT-ONLYRestrictions and orders
Agent Core periodOPEN → FROZEN → APPROVED → PAIDPeriod close, payout and tax