Why Separate Sources, Events, and Consequences?
A risk description can mix together several different things: a condition that makes loss possible, something uncertain that might happen, and an effect on an objective. Separating them makes the scenario easier to understand. It also helps prevent a familiar error: calling a financial loss the “risk event” when that loss is actually a consequence of an event.
This distinction complements the earlier material on risk relative to objectives and enterprise risk categories. A source, event, and consequence are not three alternative category labels. They are three different parts of a causal explanation. The same broad category can contain many sources, events, and consequences.
The distinction depends on the role an item plays in the scenario, not just on its wording. For example, “a rapid change in market yields” could be the event in one analysis. If the analysis instead focuses on an unexpected bond-price decline, the yield change may be described as the source of that decline. The analyst should identify what is uncertain at the chosen level of detail, then follow the causal sequence consistently.
A source is not necessarily a defect or a failure. It can be an exposure, dependency, external condition, or ordinary business activity. An event is not necessarily a disaster: it might occur without material harm, or it might create an opportunity. A consequence is not guaranteed simply because the event occurs; its magnitude and direction can depend on circumstances such as controls, timing, and the organization’s objectives.
Trace the Causal Sequence
A useful way to analyze a scenario is to ask three questions in order. First, what underlying condition makes the uncertainty relevant? Second, what uncertain occurrence or change might take place? Third, if it does, what could be affected? These questions are a reasoning aid, not a requirement that every scenario have only one source, one event, or one consequence.
Look for the underlying exposure or condition, such as dependence on a system, a location’s exposure to storms, or holdings whose values respond to market changes.
State what might occur or change. Keep it distinct from the reason it could occur and from the harm it might cause.
Ask which objectives, resources, operations, or stakeholders could be affected, and in what direction. Do not assume an effect is certain or limited to one outcome.
This sequence follows from the meanings of the terms. A source is an antecedent condition; an event is an uncertain occurrence; a consequence is an effect that follows. If an item is placed in the wrong position, the explanation becomes circular or skips a causal link. For instance, “a data outage causes an outage” repeats the event instead of explaining what makes it possible or what follows from it.
Technology Failure: A Hypothetical Scenario
Technology scenarios often tempt analysts to use “system failure” for the source, event, and consequence at once. Instead, distinguish the organization’s reliance on technology from the particular disruption that could occur and from its effects.
Worked Example: A Claims Platform Becomes Unavailable
Scenario. A hypothetical insurer relies on a cloud-hosted claims platform to receive and process claim submissions. A software update is scheduled during a period of high submission volume. The insurer has not yet completed a full test of the update’s interaction with an older interface. If the update causes the platform to become unavailable, submissions may be delayed, staff may need to use manual procedures, and some claimants may receive decisions later than planned.
Method. Identify the dependency or condition first, isolate the uncertain occurrence, and then list effects rather than relabeling an effect as the event.
Source. The insurer’s reliance on the cloud-hosted platform and its older interface creates exposure to a technology interruption. The untested interaction and timing during high submission volume are relevant contributing conditions. They explain why disruption is a concern; neither is itself the platform outage.
Event. The relevant uncertain occurrence is that the update results in the claims platform becoming unavailable. The update being scheduled is not the event of interest: it is known to be scheduled. The uncertain part is whether it disrupts service.
Consequences. Possible effects include delayed claim submissions, additional manual work, delayed decisions, and reduced service quality. These are not all inevitable. For example, if the insurer’s manual procedure works effectively, the outage could occur while some delays are avoided.
Common mistake and correction. A mistaken classification is “source: delayed claim decisions; event: platform outage; consequence: platform outage.” This places an effect before its cause and repeats the event as its own consequence. The corrected sequence is: platform dependency and untested interface (source), update-related unavailability (event), and possible delays and extra work (consequences).
Check. The sequence is coherent because the source describes exposure, the event describes an uncertain disruption, and the consequences describe what could be affected if it occurs.
Severe Weather: Separate the Hazard From Its Effects
In a weather scenario, the weather condition or hazard is often mistaken for the source. The right classification depends on the level of analysis. If the uncertain event is a flood, for example, a location’s low elevation and proximity to a river can be sources of exposure. If the analysis concerns the arrival of a severe storm, the storm itself may be the event. Be explicit about which uncertainty is being examined.
Worked Example: A Storm Threatens a Regional Service Center
Scenario. A hypothetical insurer operates a regional service center in a coastal area. The center handles customer calls and document processing. A severe storm may bring flooding and power interruptions. The insurer has backup power, but its backup call-handling staff work from the same region. If the center cannot operate, calls could go unanswered and document processing could be delayed.
Method. Fix the event being analyzed before identifying the conditions that make its effects important. Here, the event is disruption from the storm, rather than the later service delays.
Source. The service center’s coastal location, its dependence on local power, and the concentration of backup staff in the same region are sources of exposure. The location creates potential exposure to flooding; reliance on power and locally concentrated staffing creates potential continuity weaknesses.
Event. The uncertain event is a severe storm causing flooding or power interruption that prevents the center from operating normally. The storm forecast itself is information about the possibility of an event; receiving a forecast does not mean the service interruption has occurred.
Consequences. Possible consequences include unanswered calls, delayed document processing, extra operating costs, or customer dissatisfaction. These effects may differ: backup power might reduce the effect of a power interruption, while locally concentrated backup staff might still be unable to reach an alternative work site.
Common mistake and correction. A mistaken answer calls “unanswered calls” the event and “flooding” the source. Unanswered calls are a possible consequence of service disruption; flooding is part of the uncertain event as framed here. The coastal location and operational dependencies are sources. The correction preserves the order from exposure, to occurrence, to effect.
Check. The storm need not cause every listed consequence. Each is a possible effect, and the backup arrangements may change which effects occur or how serious they are.
Market Change: Distinguish Exposure From Movement
Market scenarios need the same discipline. An organization’s holdings, guarantees, or sensitivity to changing prices may create exposure. A movement in rates, equity prices, or exchange rates is an uncertain change. A fall in asset value, change in earnings, or altered capital position is a possible consequence. Avoid treating a market movement and its financial effect as interchangeable.
Worked Example: A Hypothetical Portfolio Exposed to Falling Yields
Scenario. A hypothetical insurer holds long-duration bonds to support expected policy payments. Its asset values respond to market yields, and the duration of assets and liabilities is not identical. If market yields fall unexpectedly, bond values may rise, while the value of liabilities may also change. The net effect on the insurer’s financial position is uncertain.
Method. Identify what creates sensitivity, state the market change being considered, and describe the possible net effects without assuming their direction.
Source. The insurer’s holdings of long-duration bonds and the mismatch between asset and liability sensitivities create exposure to yield changes. The portfolio is not itself the event; it is the position through which a market change can affect the insurer.
Event. The event is an unexpected fall in market yields. It is not the same as a decline in the insurer’s net financial position. That decline is only one possible outcome after considering both sides of the balance sheet.
Consequences. Bond values may rise; liability values may also rise. The resulting change in the insurer’s net financial position depends on the relative changes in assets and liabilities. Other possible consequences may include changes in investment income or in the resources available to support business plans.
Common mistake and correction. A mistaken answer says “event: the insurer’s capital position worsens” merely because yields fall. This assumes the net effect without examining the asset and liability responses. The correction identifies falling yields as the event and treats a worsening, improvement, or limited net change as possible consequences, depending on the sensitivities.
Check. The classification does not claim that falling yields must worsen the insurer’s position. It preserves the uncertainty in the consequences rather than converting a possible outcome into a guaranteed one.
Common Classification Traps
The labels are useful only when applied consistently to a stated scenario. A short description can contain several stages, so the analyst should make clear which event is being considered and avoid silently shifting from one level of detail to another.
| Trap | Why it is a problem | Correction |
|---|---|---|
| Calling a consequence the event | It skips the uncertain occurrence that could produce the effect. | Ask what may happen before naming what may be affected. |
| Calling every background condition an event | A dependency or exposure may exist even when nothing has happened. | Separate the ongoing condition from a possible change or occurrence. |
| Assuming an event guarantees harm | Controls and circumstances can change whether, and how severely, an objective is affected. | Describe consequences as possible unless the scenario establishes them as certain. |
| Changing the level of analysis mid-explanation | The same change can be an event in one analysis and a source in another, making labels seem contradictory. | State the event of interest and keep the source-event-consequence sequence at that level. |
This separation matters in enterprise risk management because decision-makers need to know whether they are addressing an exposure, preparing for an occurrence, or limiting its effects. A control that reduces the chance of an event is not necessarily the same as a continuity measure that reduces harm after the event. Similarly, monitoring a possible market change is different from deciding how to manage an existing portfolio exposure.
Check Your Understanding
For each scenario, identify the source, uncertain event, and possible consequence. Answers name the main distinctions; other reasonable consequences may also exist.
- A hypothetical insurer depends on a single data vendor. A vendor outage could prevent staff from accessing policy records and delay customer responses. Identify one source, the event, and one consequence. (Answer: Source: dependence on the single data vendor; event: vendor outage; consequence: delayed customer responses.)
- A hypothetical branch is in an area where heavy rain can flood roads. Employees may be unable to reach the branch, interrupting in-person services. Which item is the source, and which is the consequence? (Answer: The branch’s location and reliance on employees reaching it are sources of exposure; interruption of in-person services is a possible consequence.)
- A hypothetical insurer holds assets whose values are sensitive to equity markets. Share prices may fall, reducing the assets’ value. Classify the exposure, event, and effect. (Answer: Source: holdings sensitive to equity-market values; event: a fall in share prices; consequence: a reduction in asset value.)
- A hypothetical company has an untested software change scheduled before a busy reporting period. The change might disrupt a reporting system, leading to delayed reports and additional staff work. Is the scheduled change the event? Give the full classification. (Answer: The scheduled change is a contributing condition, not the uncertain disruption itself. Source: reliance on the system and the untested change during a busy period; event: the change disrupts the reporting system; consequences: delayed reports and additional staff work.)
- A hypothetical insurer has long-duration bonds and liabilities that both respond to interest rates. An unexpected rate movement may change each value, but the net effect is not specified. Explain why “capital worsens” should not automatically be classified as the event. (Answer: The rate movement is the uncertain event; the bond and liability sensitivities are sources of exposure; a worsening capital position is only a possible consequence because the net effect depends on both asset and liability changes.)