How a risk committee turns evidence into challenge, authorised decisions, escalation and accountable follow-up.
Risk committee
A risk committee is a formally constituted group that reviews risk and exercises the oversight, recommendation or approval powers assigned to it. For a quant team, its practical importance is that a risk report can lead to a decision: constrain an exposure, request better evidence, approve an authorised exception, or escalate the matter to someone with greater authority.
The name alone does not establish those powers. A board risk committee and a management risk committee can occupy different levels of the same organisation. Read the charter, reporting lines and delegations before interpreting “the committee approved it”.
The mandate comes before the meeting
In its banking guidance, the Basel Committee calls for committee charters defining mandate, scope, working procedures and reporting to the board. It describes a board risk committee advising on risk appetite, overseeing implementation, and receiving reports on exposures, limits, breaches and mitigation. These are banking governance principles whose application depends on institutional and jurisdictional context. Basel Committee, Principle 3.
An actual charter makes the distinction concrete. Morgan Stanley’s Risk Committee Charter, dated October 20, 2025, assigns oversight and review to the committee while leaving risk assessment and management with management. It also gives the committee specified approval responsibilities, including for significant risk policies, and access to management and advisers. “Oversight” therefore does not imply either unrestricted operational control or an absence of decision powers. Morgan Stanley charter.
For any particular decision, establish:
Question
What the answer changes
Which entity, business and risk are covered?
Whether this committee is the right forum
May it approve, recommend, or only review?
Whether its conclusion authorises action
Which matters are reserved to another body?
Where an escalation must go
What quorum, conflict and decision procedures apply?
Whether the decision is valid under its rules
Who implements and monitors the outcome?
Whether the decision becomes an operating control
Challenge the proposal, then route the decision
Consider a fictional investment firm whose management risk committee may grant temporary internal risk-limit exceptions under a delegated policy. Changes to the firm's overall risk appetite are reserved to its board. This is a stipulated example, not a template for every institution.
A portfolio manager asks to retain an exposure above an internal limit while unwinding it. A useful committee discussion separates the commercial request from the risk evidence. Does the report cover the whole affected book? How current are the positions and prices? Does the stress test include a loss of financing as well as a price shock? Can the proposed reduction actually be executed in the available liquidity? Which assumptions would make the mitigation fail?
Fictional workflow: a proposal and evidence enter committee challenge; matters within delegation can be decided and recorded, while matters outside delegation go to the authorised body. Actions and monitoring follow an authorised decision.
Original fictional workflow. The charter determines the authority boundary; committee support alone does not move it.
Under the assumed policy, the committee could reject the request, request more evidence, or approve a temporary exception with explicit conditions. If the request instead requires a change to risk appetite, the committee must route it to the board under the stipulated delegation. Even unanimous support would not supply a power the committee lacks. Nor would approval reduce the exposure’s economic risk: the hedge, position reduction, financing arrangement or other control has to do that.
The quant’s contribution is to make uncertainty visible enough to challenge. Provide the measurement basis, material data limitations, relevant scenarios and a comparison of feasible actions. The Factor due-diligence capstone develops a specific research memo through mechanism, test design, implementability and monitoring, ending in a reasoned rejection. The full lesson requires membership; a public preview is available.
A decision needs a record and an owner
Basel’s guidance calls for records of committee deliberations, recommendations and decisions. For the fictional exception, a useful record would identify the exposure, evidence considered, material objections, authority used, decision, conditions, expiry, responsible risk owner and follow-up. Recording an objection preserves an unresolved assumption for the next review; it is not proof that the committee has resolved it. Basel Committee, paragraph 66.
The record should make it possible to tell whether conditions were met and who must act if they fail. An urgent breach should follow the institution’s escalation procedure when it arises; a scheduled meeting is not itself a reason to delay action. A committee adds value when evidence changes decisions and those decisions reach accountable implementation.
John C. Hull, Risk Management and Financial Institutions, fourth edition, Wiley, 2015, sections 27.1–27.2, pp. 567–569: risk appetite, business-line limits and disciplined risk decisions.
