Skip to content

Action register

Every follow-up in Risk Core lands in one action register: from a failed control test, a Red KRI, a loss threshold review, a single point of failure, an exercise finding, an incident lesson or a management review decision. Each action has an owner, a due date and a status, and links back to where it came from.

Who uses it: everyone with actions sees and updates their own. The Entity Risk Manager sees every action of their entity. Executives and the RMC read their entity and everything beneath it. See Roles and permissions.

SourceCreated whenPage
Control testa test failsControls and control testing
KRIan observation falls in the Red bandObservations and breaches
Loss eventa threshold review is flaggedMateriality tiers
BIAa single point of failure has no workaroundDependencies
Exercisea finding is recordedExercise log
Incidenta lesson is recorded after closingClosing an incident
Management reviewa decision is takenManagement review
  1. Open Actions. Your own open actions are listed first, with those past their due date on top.
  2. Open an action to see its source, owner, due date and history.
  3. Choose In progress when work starts, and add notes as it moves.
  4. When it is done, choose Close and write what was done; attach evidence if you have it.

The Entity Risk Manager can change an action’s owner or due date; each change is kept in the action’s history.

Open → In progress → Closed. An action past its due date and not closed is shown as overdue, with the days overdue, on the action list, the executive summary and the management review.

  • Every action keeps its source. It links back to the test, KRI, loss event, BIA activity, exercise, incident or review that created it, and cannot be deleted.
  • Closing needs a note of what was done.
  • Each company owns its actions. A parent reads its subsidiaries’ open and overdue actions through report-up and never creates, edits or closes them (Subsidiary-Independence).
  • Every change is recorded in the audit log.