Skip to main content
US CMA · Part 2 · Focused technique

Enterprise risk management: from risk register to action

A useful risk register names the objective, event, likelihood, impact, owner, response and monitoring trigger. Review connected exposures together: risks that appear manageable alone can create a severe combined disruption.

Look for shared causes across risks

Exposure
Identify the objective, event and consequence.
Dependency
Check whether one event could affect several suppliers or operations.
Response
Assign an owner, a trigger and a response within the risk appetite.

Two suppliers do not diversify flood risk if both operate in the same exposed location.

See the decision

Two suppliers, one flood zone

A plant uses two suppliers, but both operate in the same flood zone. A replacement supplier outside the zone needs six weeks of qualification. The current dashboard reports only individual supplier on-time delivery.

  1. 01

    Common cause

    Regional flood

  2. 02

    Combined effect

    Both suppliers unavailable

  3. 03

    Response

    Independent geography + lead-time trigger

Add a common-cause scenario and an actionable qualification plan. The control should address continuity, not just improve the dashboard rating.

Original teaching scenario with stated assumptions. Values are illustrative, not market history, search trends or official exam results. See the full working.

How to apply these ideas

  1. 1. Write a scenario

    Describe a cause, event and consequence.

    For example, dependence on one supplier can lead to a production stoppage if that supplier fails. The scenario identifies the process and decision at risk more clearly than a category such as “supply risk.” Define a time horizon for the assessment.

    Watch for: Writing a category label instead of a scenario.

  2. 2. Assess dependencies

    Check whether risks share a common cause.

    Two suppliers in the same flood zone may not provide true diversification. A response that transfers financial loss may leave operational loss intact. Document connections and stress them together instead of adding independent probabilities without justification.

    Watch for: Assuming separately listed suppliers fail independently.

  3. 3. Assign a response

    Give each action an owner and completion condition.

    Acceptance is a deliberate decision within appetite, not a missing action. Reduction, sharing and avoidance require implementation evidence. State which residual exposure remains and who is authorized to accept it.

    Watch for: Recording “monitor” with no owner or intervention rule.

  4. 4. Set a trigger

    Choose an indicator that leads to action soon enough.

    A late-delivery measure is useful when it activates an alternative supply or inventory response. Thresholds should reflect decision lead time. Review indicators after changes to demand, suppliers or controls.

    Watch for: Producing a monthly report after the decision window has closed.

Study the topic

Enterprise risk management: from risk register to action: explanations and applications

Build a risk register that drives action, with defined objectives, dependencies, owners and escalation. The risk-management parent covers enterprise assessment and response choices.

By MiloPrep editorial team. Original teaching explanations and illustrative cases; official curriculum references are listed below.

Write risks as cause, event and consequence

A useful register entry states what could happen and why it matters to a defined objective. “Cyber risk: high” does not identify which service, data or reporting process is exposed. A more useful entry identifies a privileged-account compromise that could alter supplier payment details before detection, causing unauthorized transfers and unreliable records.

Keep causes, events and consequences distinct. Weak access review is a cause or control weakness, unauthorized alteration is an event, and cash loss is a consequence. This distinction helps select a response that addresses the mechanism instead of attaching a generic training action to every risk.

Minimum fields for an actionable registerScroll horizontally to compare all columns.
Minimum fields for an actionable register
FieldUseful contentWeak substitute
ObjectiveWhat must continue or be achievedA department name alone
Risk scenarioCause, event and consequenceOne broad risk label
Existing responseControl or arrangement with evidenceA policy title
Residual exposureRemaining impact and likelihood under assumptionsAn unexplained color
Owner and actionAuthority, deliverable and due date“Management to monitor”
TriggerThreshold and escalation routeA metric without a decision

Review the portfolio, not only individual rows

Several low or moderate entries can share one common cause. Two suppliers may share a sub-supplier, port, power network or geographic hazard. A cash squeeze may occur just when customers pay late and lenders tighten credit. Review connections across operational and financial risks so the register does not imply diversification that is absent.

Aggregate only compatible measures. Adding expected dollar losses across modeled exposures can be useful for a mean under stated assumptions, but it does not reveal the distribution of combined losses. Correlation and common-cause scenarios matter for severe outcomes and capital needs. A sum of ordinal heat-map scores has no natural dollar interpretation.

Choose indicators that give the owner time to respond

A leading indicator should relate to the failure mechanism and provide a usable action window. If replacement takes six weeks, a warning at three days of remaining inventory arrives too late. A lagging indicator, such as last month’s outage, can still support learning and assurance. Name which role the measure serves.

Set the threshold, owner, response and escalation route together. Confirm who can authorize resources or accept exposure above tolerance. Record near misses and review whether a trigger was early enough. Closing an action requires evidence that the response exists and works, not merely that the register row has been marked complete.

Work it through

Worked example: Two suppliers, one flood zone

A plant uses two suppliers, but both operate in the same flood zone. A replacement supplier outside the zone needs six weeks of qualification. The current dashboard reports only individual supplier on-time delivery.

Illustrative inputs and results for Two suppliers, one flood zone
Register fieldCase application
ObjectiveMaintain production continuity
Shared exposureRegional flood disables both suppliers
ResponseQualify an outside-zone supplier
Owner and triggerProcurement lead; escalate before six-week buffer is breached
  1. 1

    The supplier count alone overstates diversification because the common cause can disable both.

  2. 2

    Monitor usable inventory and qualification lead time, and test a regional-outage scenario rather than only individual delivery performance.

Add a common-cause scenario and an actionable qualification plan. The control should address continuity, not just improve the dashboard rating.

Work through the alternatives

More worked cases: enterprise risk management: from risk register to action

Original teaching scenarios. Each case states its assumptions, shows the working and explains the limits of the conclusion.

Turn a vague supplier risk into an operating response

A plant has 28 days of stock. A backup supplier needs 30 days for qualification and 10 for transport. The primary and nominal backup use the same port. The objective is uninterrupted production.

Turn a vague supplier risk into an operating responseScroll horizontally to compare all columns.
Turn a vague supplier risk into an operating response
Register fieldCase-specific entry
ScenarioPort closure interrupts both suppliers
Exposure window40-day replacement path versus 28-day coverage
ResponsePrequalify a supplier using an independent route
OwnerProcurement lead with operations support
TriggerCoverage below approved replacement lead time plus buffer
Evidence of completionQualified capacity, tested route and successful trial delivery
  1. The initial timing gap is 30 + 10 - 28 = 12 days before adding any uncertainty buffer.
  2. Diversification must address the shared port, not just add another company name. Recalculate lead time after prequalification and test whether the revised response meets the continuity objective.

What the result means: The register now connects the risk to an action and evidence. The response is incomplete until the alternative route and capacity are verified.

Practice this topic

Check your understanding

Try each short application before opening its explanation. These are original learning checks, not official exam questions or a score prediction.

  1. 1. A register assigns an action to “all departments.” What is missing?

    Show answer and explanation

    A clearly accountable owner with authority and a defined deliverable.

    Many teams may contribute, but someone must coordinate completion, evidence and escalation.

  2. 2. Two lenders provide equal credit lines but both can cancel when the same covenant is breached. Are the lines fully independent liquidity protection?

    Show answer and explanation

    No.

    The shared trigger creates a common failure mode. Assess covenant headroom and alternative funding under the same stress scenario.

Questions about enterprise risk management: from risk register to action

Is risk appetite the same as a risk limit?
Risk appetite describes the amount and type of risk an organization is willing to pursue or retain. Specific limits translate that stance into operational boundaries and escalation rules.
Why is the core risk-management lesson also needed?
It covers assessment, quantitative comparisons, response choices and residual risk. This focused note demonstrates how to record and act on one connected exposure.

Sources and scope

Curriculum mapping: Part 2, Section D, Enterprise Risk Management. The official outline assigns 10% to the entire domain, not to this individual technique. These are selected study notes, not complete curriculum coverage.

Official curriculum references establish scope and expected skills. The explanations, diagrams and numerical cases are independent teaching material from MiloPrep, not official questions or source-validated solutions. Curriculum references checked 2026-10-10.

Independent US CMA study material. Not affiliated with or endorsed by IMA. This covers management accounting, not medical-assistant certification or the separate ICMAI qualification.