Why ORSA Needs Deliberate Committee Design
An ORSA involves business leaders, risk specialists, actuaries, finance teams, and directors. Their involvement is useful only when each knows what it may decide, what it must challenge, and what it must send to another authority. Without those boundaries, a committee can appear to oversee risk while no one is accountable for a decision, or several forums can issue inconsistent directions.
Committee design is therefore an allocation of authority, not simply a meeting schedule. It should connect the people who own business decisions to the people responsible for independent risk challenge, executive accountability, and board oversight. This tutorial is aligned with the CAS Exam 9 (Risk Management for Actuaries) syllabus.
A committee may be authorized to approve a management action within delegated limits, but it should not be treated as a substitute for the accountable executive or the board. The board retains its oversight responsibilities; management remains responsible for running the insurer and delivering the ORSA. A committee structure makes those responsibilities workable by defining how information and recommendations reach the proper decision-maker.
A Practical Allocation of Forums and Authority
A workable structure can use a small number of connected forums. The names of committees vary across insurers; the important feature is a clear mandate and an identified authority for each decision. The following allocation is illustrative, not a required organizational chart.
| Forum or role | Primary responsibility | Typical decision boundary |
|---|---|---|
| Board | Oversee risk governance, challenge management’s assessment, and provide the required approval or direction. | Decides matters reserved to the board, such as risk appetite or strategic direction, under the insurer’s governance arrangements. It does not perform management’s operating work. |
| Executive ORSA or risk steering committee | Integrate the risk assessment with strategy and capital management; resolve cross-functional issues; make or sponsor recommendations. | Decides only matters delegated to it. It recommends reserved decisions to the accountable executive or board. |
| Risk committee or equivalent management forum | Review the risk profile, controls, assessment methods, and consistency of risk information; challenge the assessment. | May direct risk-function work within its mandate; does not take over business-unit risk ownership. |
| Capital or finance forum | Assess capital implications, financial resources, and proposed capital actions. | Recommends or decides capital actions within delegated authority; does not unilaterally redefine risk appetite. |
| Business-unit leaders | Own relevant business decisions and provide timely, supportable information about risks and planned actions. | Decide within their delegated operating authority; refer matters beyond it to the proper executive forum. |
| Risk, actuarial, and internal audit functions | Provide analysis and challenge, or independent assurance, according to their roles. | Do not acquire management’s decision ownership merely by producing analysis or testing controls. |
A committee charter should make the boundaries explicit. It can specify the committee’s purpose, membership, chair, quorum, decision authority, reporting line, and how disagreement is handled. It should also distinguish a decision from a recommendation. For example, a capital forum may recommend a change in capital deployment, while the executive committee or board makes the final decision depending on the delegation.
The risk function should have a route to present an independent view, including when its analysis differs from the business owner’s view. Actuarial input may inform measurement and interpretation, but technical expertise does not by itself transfer accountability. Internal audit provides independent assurance within its mandate; it should not be asked to approve management’s risk assessment.
How Decision Rights Fit Together
A committee structure is easiest to test by tracing a decision from its origin to its authority. The business owner describes the exposure and proposed response. Risk and actuarial specialists assess and challenge relevant assumptions. Finance evaluates capital implications. An executive forum integrates these views and either decides within its delegation or refers the matter to the accountable executive or board. The board then exercises oversight on matters reserved to it.
State the question in terms of a choice, such as whether a proposed plan is consistent with the approved risk appetite and available capital.
Identify the business owner, the functions responsible for analysis and challenge, and any forum responsible for integrating the views.
Determine whether the committee may make the decision, may only recommend it, or must refer it to an executive or the board.
Ensure the decision or recommendation reaches the body with authority and that relevant participants receive the resulting direction.
This sequence follows from the distinction between information and authority. An analyst can calculate or explain an implication, but that work alone does not confer authority to choose a business response. Likewise, a committee can discuss a proposal without having delegated power to approve it. If the decision-maker is not named, the process has a governance gap even when the analysis is technically strong.
The sequence is a governance logic, not a formula for measuring risk. It does not prescribe a particular number of committees or require every matter to pass through every forum. For a decision within a business leader’s delegated authority, additional committee approval may be unnecessary. For a matter reserved to the board, a management committee can prepare and recommend but cannot replace the board’s decision.
Worked Examples
Worked Example: A Growth Proposal with a Capital Implication
Hypothetical scenario. A business unit proposes entering a new commercial line. Its leader can approve ordinary product changes but cannot approve a new line. The risk function identifies an exposure requiring executive review, and finance estimates that the proposal would use 12% of the insurer’s currently available capital under the management scenario. The insurer’s charter reserves material strategy changes and risk-appetite changes to the board. No probability distribution, interest rate, or mortality assumption is used here; this is a decision-rights problem, not a capital calculation.
Method. Separate the proposal’s ownership, analysis, recommendation, and approval.
Step 1: Identify the owner. The business-unit leader owns the proposal and must explain its business rationale and operating assumptions. The leader cannot approve the new line because the stated delegation does not cover it.
Step 2: Assign analysis and challenge. The risk function assesses the relevant exposure and challenges the business assumptions. Finance provides the capital implication: 12% of currently available capital under the stated management scenario. That figure is an input to the decision, not a decision in itself.
Step 3: Use the executive forum to integrate. The executive ORSA or risk steering committee reviews the business case, risk view, and capital view. Because the board reserves material strategy changes and risk-appetite changes, the committee prepares a recommendation rather than approving the new line.
Step 4: Route the decision to the board. The board considers the recommendation and makes the decision within its reserved authority. The executive committee then communicates the board’s direction to the business owner and relevant functions.
Check. The 12% figure remains a scenario result, not an automatic approval threshold: no threshold was specified. The decision path respects the stated delegation. A common mistake is to treat the executive committee’s review as approval simply because it considered all the analysis. The correction is to check the charter: integration and recommendation do not override authority reserved to the board.
Worked Example: Resolving a Disagreement About an ORSA Assumption
Hypothetical scenario. A business unit proposes using a favorable assumption in its ORSA forecast. The actuarial team considers the assumption insufficiently supported, while the business leader argues that it reflects the intended plan. The risk committee can require additional analysis but cannot approve the business plan. No stochastic model or distribution is specified or needed; the issue is how to allocate challenge and decision authority.
Method. Preserve both the business owner’s responsibility for the plan and the independent challenge function’s ability to raise a concern; then route the unresolved judgment to the authorized executive.
Step 1: Keep input ownership with the business. The business leader explains the intended plan and remains accountable for the business assumptions supplied to the assessment. The actuarial team does not become the plan owner by evaluating an assumption.
Step 2: Use technical challenge appropriately. The actuarial team explains why support for the assumption is inadequate and identifies the implication of using it. The risk committee can require that the rationale and alternative view be considered in the integrated assessment, consistent with its stated authority.
Step 3: Do not let the committee exceed its mandate. Because the risk committee cannot approve the business plan, it cannot resolve the disagreement by simply substituting its own preferred plan assumption. It sends the unresolved issue and the competing views to the executive with authority over the plan.
Step 4: Make the executive decision explicit. The authorized executive decides whether to proceed with the plan assumption or revise the plan, taking account of the challenge. The result should be communicated back to the risk and actuarial participants so the ORSA assessment reflects the decision.
Check. The business leader remains accountable for the plan; the actuaries provide challenge; the risk committee acts within its remit; the executive decides. A common mistake is to treat the technically qualified function as the owner of the assumption. The correction is to separate the right to challenge from the authority to set the business plan.
Worked Example: Avoiding Duplicate Approval of a Capital Recommendation
Hypothetical scenario. A finance team proposes retaining more earnings rather than distributing them. The capital committee is authorized to assess and recommend capital actions but not to approve a distribution. The executive ORSA committee may approve capital actions within delegated limits, while a distribution outside those limits requires board approval. The proposal is outside the executive committee’s limit. No investment return, interest rate, or forecast distribution is assumed; the decision boundary is provided by the hypothetical charter.
Method. Trace the recommendation to the body with the necessary authority and avoid creating multiple implied approvals.
Step 1: Assign the recommendation. Finance prepares the proposal and its capital analysis. The capital committee evaluates the proposal and recommends retaining earnings.
Step 2: Identify the limit. The proposal is outside the executive committee’s delegated limit. Therefore, that committee cannot convert the recommendation into an approval, even if its members agree with the capital committee.
Step 3: Route to the board. The executive committee forwards the recommendation, together with its assessment, to the board. The board makes the decision because the stated delegation reserves this action to it.
Step 4: Notify responsible functions. After the board decides, the executive committee communicates the direction to finance and the relevant business leaders. This closes the authority route without asking the capital committee to approve an action it can only recommend.
Check. There is one recommendation from the capital committee and one authorized approval by the board. A common mistake is to interpret unanimous executive support as permission to exceed a delegation. The correction is that agreement does not change the charter; a decision outside delegated authority must go to the body authorized to make it.
Common Design Failures and Their Corrections
A committee chart can look complete and still leave decision rights unclear. The following traps are especially important when an insurer connects ORSA work to strategy and capital management.
- Giving two committees the same approval right. Overlapping authority can produce inconsistent decisions or delay. Specify which body decides and which body recommends or provides review.
- Confusing challenge with ownership. Risk and actuarial functions can question assumptions without taking responsibility for the business decision. Keep the business owner identifiable.
- Making a committee accountable without giving it authority. A forum that is expected to resolve issues but cannot decide or refer them has an incomplete mandate. Provide either defined delegated authority or a clear route to the decision-maker.
- Routing every issue to the board. The board’s oversight role does not mean it should perform routine management decisions. Use executive delegations for matters within management authority and reserve board attention for decisions under its remit.
- Treating attendance as accountability. A person’s presence at a meeting does not establish that the person owns an input, can challenge it, or has authority to decide. State these roles explicitly.
The practical test is to select a consequential ORSA decision and ask: Who owns the underlying business choice? Who provides analysis? Who can challenge? Who recommends? Who has final authority? If any answer is unclear, revise the mandate or route before relying on the committee structure.
Check Your Understanding
For each hypothetical situation, identify the appropriate decision route. The answers assume only the authority stated in each question.
- A business leader owns a proposed operational change but may approve only changes within the unit’s existing delegation. The change exceeds that delegation, and the executive committee may approve it. Who owns the proposal, and who decides? (Answer: The business leader owns and presents the proposal; the executive committee decides because the change is within its stated authority.)
- The risk function challenges an assumption used by a business unit, and the risk committee may require analysis but cannot approve the business plan. What should happen if the disagreement remains unresolved? (Answer: Preserve both views and route the issue to the executive authorized to decide the business plan; the risk committee does not take over plan approval.)
- A capital committee may recommend a capital action, but the board has reserved approval of that action. The executive committee supports the recommendation. Who makes the final decision? (Answer: The board; executive support does not change the reserved authority.)
- An actuary prepares an analysis for an ORSA assessment, while the business leader supplies and owns the underlying plan. Who is accountable for the plan, and what is the actuary’s role? (Answer: The business leader remains accountable for the plan; the actuary provides technical analysis and challenge without acquiring plan ownership.)
- A charter says the risk committee both approves risk assumptions and independently challenges those same assumptions, while the business leader is described as their owner. What governance issue should be corrected first? (Answer: Clarify and separate decision authority from challenge; identify who sets or approves the assumptions and preserve an independent challenge route, rather than giving the same committee an ambiguous combined role.)