On this page
A board defines the risk the institution is prepared to take in pursuit of its strategy; management turns that choice into workable limits; business teams own the exposures they create; and independent risk staff monitor and challenge them. This division is the core of risk appetite governance for FRM® Part II. A limit on paper has little value unless a breach changes a decision, reaches the right people and is resolved.
Start with capacity, appetite and the current risk profile
Risk capacity is the amount of risk an institution could bear given its capital, liquidity and other constraints. Risk appetite is the level and types of risk it chooses to accept within that capacity to achieve objectives. The risk profile is the exposure it actually has or expects to have. These are related but distinct: capacity is a constraint, appetite is a board-approved choice, and profile is an observed or projected position. A bank can be below its capacity and still violate appetite. Conversely, a reassuring current profile does not prove that a new strategy fits the approved boundary.
The Financial Stability Board principles describe a framework that connects capacity, appetite, limits and risk profile across business lines and legal entities. That connection matters when one desk looks safe alone but aggregate exposures are concentrated. It also matters when a subsidiary’s local limit is looser than a group commitment. An effective framework must translate an institution-wide decision into the level at which staff can act. If a candidate merely says “the board sets appetite” without explaining this cascade, the answer has described authority but not implementation.
A risk appetite statement can include qualitative boundaries as well as measurable ones. An institution might be willing to provide secured lending within an agreed portfolio limit while refusing a particular concentration or conduct risk. Quantitative limits make a boundary testable; qualitative statements cover risks for which a single number would give false comfort. The Basel Committee’s governance guidance connects the statement to strategy, capital planning and daily decisions. It also expects a way to raise concerns when the written limits are reached or breached.
The board, management and control functions do different work
The board approves and oversees the overall risk direction. It should understand whether strategic plans, compensation and the actual risk profile remain compatible with the appetite it has endorsed. Senior management develops and implements policies, assigns delegated authorities and ensures that business lines can operate within them. This is not a licence for management to change the board’s chosen boundary quietly. If the strategy requires materially more risk, the governance process must bring that issue to the appropriate decision maker. A reported breach is information to act on, not a retrospective permission slip.
The business line is the first line of defence because it chooses transactions and owns the resulting risk. Risk management and compliance provide independent second-line oversight and challenge. Internal audit is the third line, testing whether the governance and control system works. This three-line structure is explicitly set out in the Basel Committee’s guidance. External audit may provide separate assurance, but it should not be presented as a mandatory fourth line of the Basel model. The practical test is whether the same group can take a position, mark it as acceptable and assure the board that the process is sound without independent challenge.
Culture gives the formal framework its force. Staff need a credible route to flag emerging risks, and leaders need to respond consistently even when a profitable activity is involved. A bank can report that every desk is inside a numeric limit while discouraging escalation of near misses, weak controls or new exposures that the metric misses. The Basel Committee’s operational risk guidance places responsibility on the board and management to support risk culture and to integrate operational risk with other risks. In exam terms, the design of a threshold and the behaviour around it are both part of governance.
A worked example of the appetite cascade
Consider an illustrative bank whose board approves a maximum of 80 units of exposure to one type of unsecured corporate lending. Management allocates 50 units to one division and 30 units to another, with the rule that their combined exposure remains within the board’s 80-unit boundary. These invented units are an exercise in governance, not a regulatory ratio or recommended policy. Suppose the divisions currently have 45 and 25 units. The aggregate exposure is 70 units, leaving 10 units under the board limit. A proposed 12-unit loan in the first division would take its exposure to 57 and the total to 82.
The proposed loan creates two distinct problems. It exceeds the first division’s delegated 50-unit limit by 7 units and the group boundary by 2. The first-line lending team should identify both before approval and either reduce, decline or refer the proposal under the bank’s procedure. The second-line risk function should check the numbers, challenge any favourable assumptions and escalate the potential breach. Management cannot solve the group breach by moving two units of allocation from the other division if the loan still takes the combined exposure to 82. Reallocation can change a local limit within delegated authority; it cannot raise the board-approved total.
Suppose instead the borrower repays 5 units of existing exposure before the new loan is drawn. The first division would then move from 45 to 40 and, after the 12-unit loan, to 52; the second remains at 25, so the group total would be 77. The board-level boundary would be respected, but the first division’s 50-unit allocation would still be breached by 2 unless its allocation were formally revised under the bank’s rules. This variation shows why an aggregate pass is not enough. An examiner can change one fact and shift the correct decision from “board boundary breached” to “local delegation breached”.
Internal audit’s role is different again. It might later test whether the bank’s systems combined the divisions’ exposures correctly, whether exceptions were recorded and whether escalation occurred before execution. It does not become the daily credit approver merely because it reviews those controls. Likewise, second-line monitoring does not transfer ownership of the loan away from the first line. Responsibility follows the decision and the relevant control mandate. That distinction is often more useful than memorising job titles, because institutions organise specific teams in different ways.
Operational risk still needs a boundary
A bank may find it harder to express appetite for a system outage or fraud event than for a lending balance. Difficulty of measurement does not remove the need to decide what is unacceptable. The Basel operational risk principles call for an integrated framework, assigned responsibilities, monitoring and escalation. In practice, an institution may use incident thresholds, service resilience measures and control standards together. Each measure has limits: a low historical loss does not prove that an untested recovery process is safe. A candidate should ask how the chosen indicator connects to a real decision and what happens when it gives a warning.
Risk types interact. A cyber incident can interrupt payments, harm customers, create liquidity pressure and damage confidence. A lending concentration can become a capital problem when losses arrive together. Integrated risk management therefore asks for aggregation and coordination across categories, while preserving accountable owners for each exposure. Management should ensure that operational staff communicate with credit, market and other risk functions; the Basel operational risk guidance specifically highlights this coordination. The point is not to add every risk number mechanically. It is to identify where one event can cross several limits or reveal a common source of vulnerability.
How to answer a governance scenario
Read the scenario in this order: identify who chose or created the exposure, find the approved appetite and delegated limit, calculate the current and proposed profile, then identify who monitors and who has authority to approve any change. If a threshold is exceeded, ask whether the text describes a permitted exception, a proposed amendment or an unreported breach. These are not interchangeable. A warning indicator may trigger discussion before a hard limit is crossed; a hard limit breach requires the prescribed response. Do not assume that a profitable transaction, a strong capital position or an informal conversation makes a breach acceptable.
Finally, test whether the control is independent and timely. A report delivered after the position is locked in may document a failure without preventing it. A risk committee that receives only selected exceptions cannot assess the aggregate profile. An audit review may be sound but too infrequent for daily limit monitoring. The FRM programme page gives the exam context, and the Omni how-it-works page describes the study route. For revision, draw one arrow for each hand-off from board choice to management policy, first-line decision, second-line challenge and third-line assurance; label the decision each arrow enables.
Sources
- Principles for an Effective Risk Appetite Framework | FSB · fsb.org · Retrieved
- Corporate governance | Basel Committee · bis.org · Retrieved
- Operational risk | Basel Committee · bis.org · Retrieved
- FRM Study Materials | GARP · garp.org · Retrieved



