On this page
Under the Basel Committee's operational-risk principles, the board approves and oversees the framework and risk appetite, while senior management turns that direction into workable policies, ownership and reporting. Business units manage risks in their work, the second line challenges them and the third line independently reviews the framework. An FRM® candidate should locate a failure in this chain before proposing the next action; a board-approved document alone does not prove effective governance.
Read Basel as an allocation of decisions
Operational risk can arise from failed processes, people, systems or external events. This definition includes legal risk but excludes strategic and reputational risk in the Basel capital framework. The categories matter, but governance questions usually ask something more practical: who was supposed to identify a risk, who could challenge the assessment, and who had the authority to demand correction? The Basel operational-risk chapter sets out roles across governance, the management environment, technology, continuity and disclosure. Its structure is a useful map for a candidate reading a scenario.
The operational risk management framework, or ORMF, is the bank's organised approach to identifying, assessing, monitoring and controlling operational risk. It must connect to ordinary decisions, such as launching a new process or responding to an outage. Basel says the framework should reflect the nature, size, complexity and risk profile of the bank. That qualification matters: the principles apply broadly, but an appropriate structure for a simple bank need not look identical to the structure of a complex international bank. A candidate should test whether the arrangements are effective for the stated activities rather than assume one committee chart fits every institution.
The BIS executive summary of the revised principles explains the division of work. The board leads risk culture, approves and periodically reviews the ORMF and the operational-risk appetite and tolerance statement, and checks that management implements the framework. Senior management develops a suitable governance structure for board approval, translates the framework into processes and ensures that staff have the capabilities and resources to operate them. These are different verbs with different evidence: approve, implement, challenge, report and review.
What the board must be able to see
Board oversight is more than signing a policy. The board should understand the operational risks in current and planned activities and ask whether the framework still covers them. A new product, material process change, rising transaction volume or deteriorating control environment can make an old framework inadequate. Basel calls for periodic review and for revision when material changes affect the risk profile. There is no universal fixed review interval in the principle, so do not invent a required number of months from the word periodic.
The board also approves and periodically reviews a statement of operational-risk appetite and tolerance. The statement should describe the kinds and levels of risk the bank is willing to assume and set boundaries or indicators that can be monitored. It should be intelligible enough to guide an operational decision. A broad declaration that risk is low leaves a manager unable to tell whether a process exception requires action. Conversely, a threshold alone is not the whole governance framework: the bank still needs ownership, controls, reporting and response.
In an exam case, look for evidence of active oversight. Did the board receive information on breaches, emerging risks, significant events and remediation? Did it ask for the causes and completion dates? Did it reconsider its appetite when the activity changed? Basel's reporting principle identifies those elements as useful to proactive management. A dashboard with a green summary, unsupported by escalation of material issues, is weak evidence. The board can delegate operational tasks, but it cannot satisfy its oversight role by treating management's assurance as conclusive.
What management must put into operation
Senior management converts the board-approved framework into clear responsibilities and repeatable procedures. It should define who owns each material risk, which function monitors it, how exceptions reach decision makers and what happens after an issue is found. The Basel chapter emphasises robust challenge and issue-resolution mechanisms, including systems to report, track and escalate matters. A bank with a complete policy but no owner for a new outsourced process has an implementation problem, even if the policy uses the right terminology.
Management also needs a route for change. A new system or product can introduce failure modes that the previous control map never considered. Basel's principles ask for a process to identify, manage, challenge, approve and monitor change, with roles and oversight controls made clear. In a scenario, check when the assessment happened. A post-launch meeting that merely records a new risk does not substitute for a decision process that challenges it before or during implementation and follows up afterwards.
The first line is the business activity that takes and manages the risk. The second line reviews and challenges its assessment rather than simply accepting it. The third line independently reviews whether the framework works as intended. These lines describe functions, not a promise that every bank has exactly three departments with those labels. Basel's key point is that responsibility and independence are credible in operation. A risk function that reports to the same manager whose control failure it is assessing may struggle to challenge that manager, even if the organisation chart calls it independent.
An illustrative breach from signal to board
Consider an invented bank operating a payment-processing service. For this exercise, suppose its board-approved operational-risk statement requires management review when an internal service is unavailable for more than two hours and board reporting when an incident causes more than £1 million in direct losses. These numbers are invented teaching assumptions, not Basel thresholds or market data. In one month, a processing change leads to a three-hour outage and an estimated direct loss of £1.2 million. The calculation is simple: three hours exceeds the assumed two-hour review trigger by one hour, and £1.2 million exceeds the assumed board-reporting trigger by £0.2 million.
The payment team, as the first line, should record the event, restore the service, identify affected transactions and assess the immediate exposure. The second line should challenge the impact estimate, examine whether the pre-change risk assessment and control testing were adequate, and check that the issue is escalated under the assumed thresholds. Senior management should assign an owner to the remediation, provide resources, decide on temporary controls and track progress. The board should receive a report that explains the event, breach, cause, response and remaining exposure, then test whether the framework and appetite still fit the activity.
The third line can later examine the design and operation of the change-control and escalation process independently. It need not run the outage response itself; doing so could compromise its ability to assess that response. If the second line had warned about incomplete testing before the change and management ignored the warning, the examiner should locate the management decision failure. If the board received repeated unaddressed breach reports and never challenged them, the failure also reaches board oversight. A useful answer traces both the event and the missed decision, rather than attaching every problem to the chief risk officer.
Conditions that change the governance conclusion
Suppose the bank outsourced payment processing. The external provider may perform the activity, but the bank must still understand the material operational risk and oversee the arrangement within its framework. In a case, ask who at the bank owns provider performance, incident reporting, contingency arrangements and escalation. Calling the outage a vendor problem does not settle the bank's accountability to its own customers or board. The candidate should not assume that outsourcing itself is prohibited; the question is whether risk identification, monitoring and response remain effective.
Now suppose the outage produced no direct financial loss but exposed a severe control weakness. A loss-only dashboard might show nothing, yet the weakness could still require attention. Basel describes operational-risk reports as including emerging risks and significant events as well as losses and breaches. The lesson is to read the substance of a risk signal, not only a monetary threshold. An appetite indicator should support judgement rather than replace it.
Finally, distinguish the principles from a universal legal rule for every firm. The Basel Committee articulates sound banking practices, and local implementation may differ. Its principles also require proportionality to a bank's profile. An FRM answer should apply the source's governance logic to the scenario without asserting an invented deadline, committee title or fine. The GARP programme overview identifies operational risk and resilience as a Part II domain, and GARP study materials locate the learning objectives in the curriculum. The detail tested here is the allocation of action and challenge.
The exam mistake to avoid
A common answer says that the board owns all risk and therefore must operate every control. That collapses oversight into management. Another says that senior management is responsible for implementation, so board approval ends the board's role. That ignores periodic review and oversight of effectiveness. A third assigns the second line the business unit's own risk ownership, leaving the first line with no duty. Each error confuses a link in the chain.
Read a governance case in four passes. Name the activity and material risk. Identify the decision that should have happened before exposure grew. Place that decision with the board, management or a line of defence. Then state what evidence would demonstrate that the action actually occurred, such as a challenged assessment, an escalation record, a remediation owner or a board review. The FRM study page provides programme context; Omni's methodology page is a separate guide to working with concepts. For this topic, the best answer is an accountable sequence of decisions, grounded in the Basel principles.
Sources
- Operational risk | Basel Committee · bis.org · Retrieved
- Principles for Sound Management of Operational Risk | BIS · bis.org · Retrieved
- FRM Exam | GARP · garp.org · Retrieved
- FRM Study Materials | GARP · garp.org · Retrieved



