Business Unit Ownership of ORSA Inputs

Why Business Ownership Matters in ORSA

An Own Risk and Solvency Assessment (ORSA) depends on more than a model or a centrally assembled report. It depends on accurate information about what the business currently does, what it plans to do, and what could change its risk. Business leaders are close to those exposures and decisions. Their contribution is not simply to send data when asked: they must be able to explain and validate the information supplied for their areas.

That does not mean a business unit prepares the whole ORSA independently. Central coordination can set common instructions, bring inputs together, identify inconsistencies, and ask for clarification. The distinction is between who is accountable for the business facts and judgments and who coordinates their use in the assessment. This distinction supports the ORSA’s own view of risk and its connection to strategy and capital management, topics established in the earlier material on ORSA purpose and governance.

Definition: Business-unit ownership of ORSA inputs means that the relevant business leader is accountable for the completeness, accuracy, context, and explanation of information about that unit’s exposures, plans, controls, and decisions that is used in the ORSA. Central coordination means organizing the assessment across the organization—for example, setting common instructions, consolidating submissions, checking consistency, and referring questions to the relevant owner. Coordination does not, by itself, transfer accountability for the underlying business information.

An input may include current exposure data, a forecast, a management action, or an explanation of a change in the risk profile. A business leader should be prepared to answer practical questions: What does this figure cover? Which entity or product does it relate to? What changed since the last assessment? What decision or assumption explains the projected result? A number without scope or context may be technically correct and still mislead the ORSA.

Ownership is not the same as sole authorship. Actuaries and other specialists can calculate measures, assess the implications of assumptions, and explain limitations, as described in the earlier material on actuarial contributions without transferring ownership. A business leader can remain responsible for the underlying forecast or operational facts while relying on specialist support to evaluate them. Conversely, a central team’s ability to edit a submission does not make it the source owner.

What the Business Owner Contributes

The specific information varies with the business, but a useful submission usually makes four things clear:

Exposure: what is written, held, processed, or otherwise at risk, with scope, units, and relevant segmentation.
Assumptions and judgments: what the business expects or considers plausible, the basis for that view, and material uncertainty.
Plans and decisions: what the business intends to change, including the timing and scale of planned growth, product changes, or controls.
Explanation: why the input differs from prior information or from other stated plans, and who can clarify it.

The owner need not make every technical calculation. The owner must, however, provide enough context for specialists and central coordinators to use the information appropriately. If the business does not recognize a forecast as its plan, or cannot explain a key exposure figure, the ORSA process has an accountability and information-quality problem even if a spreadsheet has been completed.

Worked Example: A Portfolio Expansion Changes the Exposure Mix

A hypothetical property insurer’s regional leader reports 800 current policies: 120 coastal policies with an average limit of $2,000,000 each, and 680 inland policies with an average limit of $1,000,000 each. The approved plan adds 200 policies: 120 coastal and 80 inland. Calculate the current and projected policy counts and aggregate policy limits, then identify what the leader should explain to the ORSA coordinator.

Method. Calculate each segment separately, using policy count multiplied by average limit. Treat the result as aggregate contractual limits, not as an estimate of expected claims or required capital.

Current position. Coastal aggregate limits are $120 \times \$2{,}000{,}000 = \$240{,}000{,}000$. Inland aggregate limits are $680 \times \$1{,}000{,}000 = \$680{,}000{,}000$. Total current policy count is $120 + 680 = 800$, and current aggregate limits are $\$240{,}000{,}000 + \$680{,}000{,}000 = \$920{,}000{,}000$.

Projected position. Coastal policies become $120 + 120 = 240$; inland policies become $680 + 80 = 760$. The projected total is $240 + 760 = 1{,}000$ policies. Projected coastal aggregate limits are $240 \times \$2{,}000{,}000 = \$480{,}000{,}000$; projected inland aggregate limits are $760 \times \$1{,}000{,}000 = \$760{,}000{,}000$. Projected aggregate limits are therefore $\$480{,}000{,}000 + \$760{,}000{,}000 = \$1{,}240{,}000{,}000$, an increase of $\$320{,}000{,}000$ from the current position.

Mix check. Coastal policies are $240/1{,}000 = 24\%$ of projected policies, compared with $120/800 = 15\%$ currently. Coastal limits are $480/1{,}240 \approx 38.71\%$ of projected aggregate limits, compared with $240/920 \approx 26.09\%$ currently. The leader should confirm the planned coastal growth, the limit assumptions, the period covered, and whether the figures use the same scope as the current data. Central coordination can check that the submission is consistent with the approved plan and present the segments on a common basis.

Check. Projected counts sum to $240 + 760 = 1{,}000$; projected limits sum to $\$480{,}000{,}000 + \$760{,}000{,}000 = \$1{,}240{,}000{,}000$. Common mistake avoided: applying the overall policy growth rate of $200/800 = 25\%$ to every segment. The additions are not distributed evenly, so that shortcut would conceal the increase in coastal concentration.

Why Coordination Does Not Replace Ownership

The logic is straightforward. The ORSA uses information about exposures and decisions to assess the organization’s risk and solvency. The business area that generates or controls that information is usually best placed to confirm what it covers and explain the decisions behind it. If coordination is mistaken for ownership, a central team may be left to certify facts it did not create and cannot validate. If ownership is mistaken for independent control of the whole assessment, business units may use inconsistent definitions or assumptions.

A sound process keeps both links: the business owner validates the source information and its context; central coordination establishes how submissions fit together and raises questions when they do not. This is a practical justification for assigning ownership to the business while coordinating centrally: it preserves access to business knowledge without losing a consistent organization-wide assessment.

Business leader supplies and explains.
The relevant leader confirms the exposure, plan, assumption, or decision for the unit and identifies its scope and basis.

Specialists assess implications.
Actuarial or other technical contributors can calculate or analyze implications, while clarifying what the calculation does and does not establish.

Central coordination checks and combines.
The coordinator uses common instructions, checks for gaps or inconsistencies, and consolidates the information for the ORSA.

Unresolved points return to the owner.
Where a figure or judgment is unclear, the owner explains or corrects it rather than leaving the coordinator to guess at business intent.

Worked Example: Estimating a Claims-Handling Disruption

A hypothetical claims unit reports a scenario in which a system outage delays handling for three days. The unit estimates that 40 claims per day would be affected, with an average incremental service and remediation cost of $250 per affected claim. It also expects a fixed $20,000 vendor response cost. Calculate the scenario cost and identify which input belongs with the business owner.

Method. Calculate the number of affected claims, multiply by the stated per-claim incremental cost, then add the fixed response cost. The problem defines a scenario estimate; it does not provide a probability, so the result is not an expected annual loss.

Affected claims are $3 \times 40 = 120$. The variable cost is $120 \times \$250 = \$30{,}000$. Adding the fixed vendor response cost gives a total scenario estimate of $\$30{,}000 + \$20{,}000 = \$50{,}000$.

The claims leader should validate the outage duration, daily affected claim volume, cost basis, and whether the fixed vendor cost is additional rather than already included in the per-claim estimate. A central coordinator can check that the scenario is described consistently with other submissions and that its scope is clear. The calculation alone does not establish likelihood or a capital amount.

Check. The variable cost covers 120 affected claims, and the stated fixed amount is added once, giving $50,000. Common mistake avoided: calling $50,000 an expected loss. Without an assigned probability and a defined frequency framework, it is only the stated cost under this hypothetical scenario.

Ownership of Assumptions and Planned Decisions

Business ownership also matters when an input is a forecast rather than a count of current exposures. Forecasts depend on management choices and judgments: planned sales, retention, product mix, operating capacity, or the timing of a change. The owner should distinguish approved plans from exploratory possibilities and state the basis and limitations of the numbers. Central coordination can ask for a consistent horizon and format, but it should not silently turn an unapproved idea into the business forecast.

A scenario assumption needs similar discipline. The owner should be able to explain why it is relevant to the unit and what conditions it represents. A stress scenario is not automatically a forecast, and a forecast is not automatically a stress. Labeling the input correctly lets the ORSA use it for the appropriate purpose.

Worked Example: Lapse Assumptions and the Meaning of an Exposure Figure

A hypothetical savings-product unit has 5,000 in-force contracts at the start of a one-year projection. For a simplified illustration, assume no new business or other contract decrements during the year. The unit’s baseline lapse assumption is 6%; a specified adverse scenario uses 10%. The average account balance is $80,000 per contract. Calculate the implied lapse counts and the account balances associated with those counts.

Method. Apply each stated rate to the same 5,000 starting contracts, then multiply the resulting counts by the average account balance. These calculations describe associated balances, not a direct loss or capital requirement.

Under the baseline assumption, $5{,}000 \times 0.06 = 300$ contracts lapse. Their associated account balance is $300 \times \$80{,}000 = \$24{,}000{,}000$. Under the adverse scenario, $5{,}000 \times 0.10 = 500$ contracts lapse, associated with $500 \times \$80{,}000 = \$40{,}000{,}000$.

The scenario has 200 more lapses than the baseline, and the difference in associated account balances is $200 \times \$80{,}000 = \$16{,}000{,}000$. The product leader should explain the basis for the baseline assumption, why the adverse assumption is relevant, and whether the same contract population and balance measure are used in both calculations. A technical contributor may assess how lapse behavior affects the insurer’s financial position; the $16,000,000 difference alone does not quantify that effect.

Check. The rates are applied to the same start-year count: 300 baseline lapses and 500 scenario lapses. Common mistake avoided: treating the $16,000,000 associated balance difference as a loss. It is an exposure measure attached to the difference in lapse counts; further analysis is needed to determine the financial consequences.

Common Ownership Errors

Ownership is most useful when it is visible in the way inputs are prepared and discussed. Watch for these errors:

Submitting a number without its scope. A count or amount should identify the unit, period, product or exposure segment, and relevant basis.
Letting the coordinator invent business intent. A central team can seek clarification; it should not guess which plan or assumption the business meant to report.
Treating technical calculation as business validation. A correct calculation cannot establish that its source data or management assumptions are complete and appropriate.
Mixing a plan with a possibility. Identify whether an action is approved, proposed, or only under consideration.
Presenting unlike inputs as comparable. Different horizons, units, populations, or scenario definitions can create apparent inconsistencies that require explanation before consolidation.

For example, if a business forecast conflicts with a separately stated plan, the right response is not automatically to average the two figures. The owner should explain the difference, and the coordinator should ensure the ORSA does not obscure the unresolved basis. A clear account of uncertainty or disagreement is more informative than a falsely precise consolidated number.

Key takeaway: Business leaders own the accuracy, context, and explanation of ORSA inputs about their exposures and decisions. Central coordination makes those inputs consistent and usable across the organization, but does not replace the business knowledge and accountability that the inputs require.

Check Your Understanding

For each problem, distinguish what the business owner should validate from what central coordination can organize or check.

A unit has 500 policies, of which 100 are coastal. It plans to add 100 policies, split equally between coastal and inland. Coastal policies have an average limit of $3,000,000 and inland policies $1,000,000. Calculate projected counts by segment and projected aggregate limits. (Answer: 150 coastal and 450 inland policies; $900,000,000 projected aggregate limits.)
A hypothetical service interruption affects 30 transactions per day for two days. Incremental cost is $400 per affected transaction, plus a fixed $12,000 response cost. Calculate the scenario cost and state what the result does not establish. (Answer: $36,000 scenario cost; it does not establish the probability or expected annual cost.)
A unit has 2,500 contracts and considers baseline and adverse one-year lapse assumptions of 4% and 7%. Average account balance is $60,000. Calculate the lapse counts and the difference in associated account balances. (Answer: 100 baseline lapses, 175 adverse lapses, and a $4,500,000 difference in associated balances.)
A business leader submits exposure data that exclude a recently approved product launch, while the central coordinator has a separate launch forecast. What should happen before the figures are combined? (Answer: The business owner should confirm the exposure-data scope and explain the launch treatment; the coordinator should reconcile the inputs on a consistent basis rather than silently inserting or omitting the launch.)
A hypothetical unit reports $120 million of next-year premium, while its approved plan reports $100 million; the prior-year amount was $80 million. Calculate the growth rates relative to prior year and describe the ownership response. (Answer: The submitted forecast implies 50% growth and the approved plan 25% growth; the owner should explain the $20 million difference and confirm which input reflects the business view before central consolidation.)

What You'll Learn