Why ORSA Boundaries Matter
An insurer may operate within a group that includes several insurance companies, a holding company, and shared service businesses. Risks can cross those boundaries: one entity may provide services, capital support, or guarantees to another, while group-wide events may affect several entities at once. An ORSA that considers only the consolidated group can miss vulnerabilities specific to an individual insurer. An ORSA that considers only one insurer can miss dependencies and concentrations elsewhere in the group.
The governance question is therefore not simply, “Which report should be prepared?” It is also, “Which entity owns which assessment, and who is responsible for considering the connections among entities?” The answer depends on the group structure and the applicable requirements. The underlying distinction remains important: a group-level perspective supplements the relevant insurers’ own perspectives; it does not automatically replace them.
An entity boundary identifies the legal entity whose obligations, resources, and risk profile are being assessed. A group boundary identifies the set of entities included in the group perspective. These are related but distinct choices. A non-insurance parent may be relevant to a group ORSA because it provides services or support, even though it does not itself have an insurer-level ORSA.
The insurer remains responsible for its own assessment of its risks and circumstances. At group level, the designated group governance arrangements need to make sure that the group perspective is coherent and that material connections between entities are considered. The precise allocation of responsibilities and required reporting varies by jurisdiction and group structure; it should be determined from the applicable requirements rather than assumed from an organizational chart.
Two Perspectives, Connected but Not Interchangeable
At insurer level, the assessment should be meaningful for that insurer’s policyholders, obligations, assets, operations, and ability to respond to adverse developments. A group-level assessment asks additional questions: does a risk affect more than one entity, does one entity rely on another, and could a problem in one part of the group disrupt another part?
These perspectives can use common information, assumptions, and governance processes. But a common process does not make the entity-level assessment redundant. For example, a consolidated view may appear resilient while one subsidiary depends on a service provider that is financially or operationally vulnerable. The group view should make that dependency visible; the subsidiary’s own ORSA should also assess the consequence of relying on the provider.
| Question | Insurer-level perspective | Group-level perspective |
|---|---|---|
| What is being assessed? | The risks and circumstances of a particular insurance legal entity | The group’s relevant entities, connections, and overall risk perspective |
| Who is accountable? | The insurer’s own governance and management arrangements, under applicable requirements | The designated group governance and management arrangements, under applicable requirements |
| What can be overlooked? | Risks transmitted through affiliates, shared services, or group-wide events | Differences among insurers and vulnerabilities specific to an individual entity |
| What is the relationship? | Provides the entity’s own view and informs the wider picture | Connects entity views and assesses material dependencies; does not erase them |
A useful way to organize the analysis is to distinguish three layers: the legal entities, the relationships among them, and the governance arrangements responsible for assessing each layer. A risk may sit primarily within one insurer, arise from a shared activity, or be transmitted through a relationship such as a guarantee, reinsurance arrangement, or common service. Identifying the relevant location of the risk is not the same as assigning ownership of the assessment: an insurer can be exposed to a risk generated by another group entity and must consider that exposure in its own view.
Worked Applications
Worked Example: Two Insurers and a Shared Service Company
A hypothetical group has a holding company, Harbor Life, and Harbor General, both insurers, plus Harbor Systems, a non-insurance company that runs policy administration for both insurers. A cyber incident at Harbor Systems could interrupt claims processing at both insurers. Identify the relevant ORSA perspectives and the questions each should address.
Step 1: Identify the insurer-level assessments. Harbor Life and Harbor General are separate insurers. Each needs an assessment relevant to its own policy obligations and operations. Harbor Life should consider how an outage would affect its policy administration and claims handling. Harbor General should make the corresponding assessment for its own business. Neither insurer can treat the issue as irrelevant merely because the system is operated by an affiliate.
Step 2: Identify the group-level connection. The same service company supports both insurers. A single incident could therefore create related operational impacts across two entities. The group perspective should identify the common provider, the potential for simultaneous disruption, and the channels through which a problem at Harbor Systems could affect the insurers.
Step 3: Separate the roles of the service company and the insurers. Harbor Systems may provide information about its controls and continuity arrangements, but it is not a substitute for either insurer’s assessment. Each insurer considers its exposure to the service provider; the group perspective considers the shared dependency.
Conclusion. There are two insurer-level views and a group-level view of the common dependency. The method is to map both legal-entity exposures and cross-entity connections. A common mistake is to label this “only a group risk” and omit it from the insurers’ own assessments.
Worked Example: A Parent Guarantee and Entity Accountability
A hypothetical holding company, Cedar Group, guarantees up to $12 million of a lender’s borrowing to Cedar Specialty, an insurance subsidiary. Cedar Specialty also has a separate $3 million obligation to that lender. Determine what each perspective should capture, and explain why the group view should not simply count the guarantee as a second, independent $12 million external obligation.
Step 1: State the subsidiary’s direct obligation. Cedar Specialty owes $3 million under its own borrowing. That is its direct obligation to the lender and belongs in its insurer-level assessment.
Step 2: Identify the guarantee’s legal and economic connection. The guarantee is Cedar Group’s commitment, capped at $12 million, to the lender in relation to Cedar Specialty’s borrowing. It creates a potential call on the parent if the specified conditions are met. Cedar Specialty should assess its reliance on the parent support and the consequences if that support is unavailable or insufficient.
Step 3: Determine the group-level treatment. The group perspective should identify the guarantee, the possible cash call on Cedar Group, and the connection between the parent and subsidiary. The $12 million is the guarantee limit, not a statement that $12 million has already been paid or that an additional independent external loss has occurred.
Step 4: Check the combined description. The subsidiary’s separate direct obligation is $3 million. The guarantee limit is $12 million. Adding those figures gives $15 million as a simple sum of the stated amounts, but that sum is not automatically an estimate of group loss: the guarantee relates to the subsidiary’s borrowing, and actual payment depends on the guarantee terms and triggering conditions.
Conclusion. Cedar Specialty assesses its own obligation and dependence on support; the group view assesses the parent guarantee and the relationship it creates. The common mistake is either to omit the guarantee from the group view because it is not the subsidiary’s direct obligation, or to add the limit mechanically as if it were a separate, certain loss. The correction is to describe the legal obligation, potential trigger, and inter-entity dependency explicitly.
Worked Example: A Local Risk With a Group-Wide Cause
A hypothetical group owns North Coast Insurance and Valley Insurance. North Coast insures properties in one region; Valley insures properties in another. A severe storm is expected to damage North Coast’s insured properties, and the same storm may also interrupt a group-owned data center used by both insurers. Which parts belong in each ORSA perspective?
Step 1: Separate the insurer-specific exposure. North Coast assesses the storm’s direct effect on its own insured properties, operations, and ability to meet its obligations. Valley does not include North Coast’s insured property exposure as though it were Valley’s own policy exposure.
Step 2: Identify the shared operational dependency. Both insurers rely on the data center. Even if the physical damage to insured properties is concentrated in North Coast’s region, an outage could disrupt administration at both insurers. Each insurer should assess the effect of that outage on its own operations.
Step 3: Add the group perspective. The group view connects the common cause (the storm) with the shared data center and identifies the potential for concurrent effects across the two insurers. This is not the same as treating every consequence as one entity’s loss; it is a way to understand how the effects may propagate through the group.
Conclusion. North Coast’s direct insurance exposure is insurer-specific; the shared data-center dependency is relevant to both insurers and to the group. The method is to trace the event through each entity and relationship rather than assign the whole scenario to only the entity where it first appears.
Why the Group View Is Not a Simple Sum
The purpose of a group view is to understand the group’s risk profile, not merely to add labels or amounts from separate entity reports. A group can have shared services, support arrangements, common exposures, or restrictions that affect whether resources can move between entities. These connections can make a group outcome different from the sum of isolated entity narratives.
A compact way to express the scope of the inventory is to let \(\mathcal{R}_j\) denote the material risks identified for entity \(j\), and let \(\mathcal{D}\) denote material dependencies or transmission channels among entities. Then the group risk inventory must consider the entity risks and the connections among them:
This is a scope statement, not a capital formula. The justification is direct: a risk can affect the group because it affects an entity, because it travels through a relationship, or both. Reviewing only the separate entity lists would identify the first category but could miss how a shared provider, guarantee, or common event connects the entities. Conversely, a group inventory that contains only consolidated labels could conceal which insurer is exposed and what that exposure means locally.
This also explains why the same risk may appropriately appear in more than one assessment without representing multiple independent events. A shared service outage can be described in each insurer’s assessment as a threat to its operations and in the group assessment as a common dependency. The descriptions should clarify the perspective and avoid implying that the underlying event has been counted as several unrelated events.
Common Boundary Mistakes
- Replacing entity ownership with group reporting. A consolidated report does not, by itself, show that each insurer has assessed its own obligations and dependencies.
- Assuming only insurers matter to the group boundary. A non-insurer may provide a critical service or support arrangement and therefore be relevant to the group perspective.
- Stopping at the legal-entity chart. An organization chart shows ownership, but may not reveal shared providers, guarantees, or other channels through which risk can move.
- Assuming a risk belongs only where it originates. A risk originating at one company can create exposure at another. Assess the affected entity as well as the source.
- Confusing repeated descriptions with independent losses. The same event may be relevant in several perspectives. Explain the connection rather than simply adding amounts or treating the descriptions as separate events.
For an exam-style boundary question, first name the legal entities and identify which are insurers. Then identify the relevant group perimeter and relationships. Finally, state what each insurer must understand for its own assessment and what the group perspective adds. This sequence helps keep accountability distinct from coordination. It is aligned with the CAS Exam 9 (Risk Management for Actuaries) syllabus.
Check Your Understanding
For each scenario, identify the insurer-level perspective and the additional group-level consideration. Answers follow each question so you can check your boundary analysis.
- A holding company owns two insurers and a non-insurance company that provides claims software to both. State which entities need insurer-level perspectives and what the group view should add. (Answer: Each insurer assesses its own exposure to interruption of claims software; the group view identifies the shared provider and the potential for a common disruption across both insurers.)
- An insurer’s parent promises a lender up to $8 million if the insurer fails to meet a specified payment. The insurer separately owes the lender $2 million. Identify the amounts and connections that should be described, without treating them as a certain $10 million group loss. (Answer: The insurer’s direct obligation is $2 million; the parent guarantee is capped at $8 million and is conditional. The insurer assesses reliance on support, while the group view considers the potential parent cash call and the inter-entity connection. The simple sum is $10 million, not a certain loss estimate.)
- A group has two insurers. A flood threatens one insurer’s insured properties, while both insurers depend on a records center located in the flood area. Which perspective considers the insured-property exposure, and which considers the shared operational channel? (Answer: The exposed insurer assesses its own insured-property risk; both insurers assess their own dependence on the records center, and the group view considers the common operational dependency and possible effects across the group.)
- A non-insurance affiliate provides a critical service to one insurer but has no ownership interest in that insurer. Explain why it may still be relevant to ORSA boundary analysis. (Answer: Ownership is not the only connection that matters. The insurer assesses its dependency on the service provider, and the group perspective includes the relationship if the provider is within the group perimeter or otherwise material to the group’s risk view.)
- A group report describes a common cyber event once, while each of three insurers separately explains how the event could disrupt its own operations. Is this necessarily double counting? Explain the distinction. (Answer: No. The group description captures the common event and shared dependency; each insurer’s description captures its own exposure and consequences. They are different perspectives on a connected event, not automatically three independent events.)