Basic Prerequisites: 03 · Validation & Backtesting and 02 · Sources of Model Risk.


1. Intuition & Practical Objective

Validation measures model error; model-risk management decides what to do about it. SR 11-7 frames this as three interlocking pillars, and the discipline is that none of them is optional:

  1. Model development, implementation and use - disciplined development (clear purpose, sound theory, robust data, documentation, testing) and an explicit accounting for the residual uncertainty (conservative adjustments, reduced reliance, supplementary models).
  2. Model validation - the independent three elements of 03 · §3, continuing on an ongoing basis.
  3. Governance, policies & controls - board and senior management ownership, a model inventory, internal audit of the framework, written policy, and a scope of work for external resources.

The organising idea is “effective challenge”: critical analysis by objective, informed parties that can identify model limitations and produce appropriate changes. SR 11-7 is explicit that this “depends on a combination of incentives, competence, and influence.” Miss any one and the framework is theatre. This maps onto the classic three lines of defence:

LineOwnsModel-risk role
Firstbusiness / model owners & developersdisciplined development, use within scope, self-testing
Secondindependent validation / riskthe three validation elements; challenge; inventory
Thirdinternal auditassesses the framework’s effectiveness, incl. the challenge process

The objective of this page: connect model-risk management to numbers a firm actually reports - the regulatory capital multiplier and the aggregate model-risk score - so the framework is accountable, not just compliant.


2. Mathematical Ground Truth & Derivations

2.1 Model risk as regulatory capital (the direct link). For internal-model market risk, Basel ties the capital multiplier to the backtest outcome: , where is the exception count in the past 250 days and plus rises through the yellow zone (BCBS 1996). Market-risk capital is

so the model’s validated accuracy is priced into capital directly. The add-on attributable to model risk is , i.e. in the green zone up to in the red zone at the same VaR - a mechanical, disclosed measure of “we trust this model less”.

2.2 The aggregate model-risk score. A single model’s score multiplies the four SR-11-7 risk drivers - materiality , complexity , extent of use , and residual validation weakness :

The additive sum treats model failures as a portfolio; if failures are correlated across models (they are - shared data, shared code, shared regime) the risk-weighted aggregate uses with a failure-correlation matrix , which is bounded below by the largest single score and above by . SR 11-7 requires managing model risk “both for individual models and in the aggregate”.

2.3 Governing the aggregate. The framework is only effective if the score is actionable: high scores trigger (i) tighter limits on the model’s use, (ii) a conservative adjustment to its output, (iii) redevelopment, or (iv) reliance on a second model. SR 11-7’s list of mitigating steps is exactly this menu. The board’s job is to set the tolerance and prove - the governance analogue of .

2.4 Why adding is not the same as managing. Summing scores overstates risk if failures are independent and understates it if they are correlated; but the real discipline is that every term needs an owner in the first line and a challenger in the second. A score with no owner is a KPI, not a control.


3. Computational Implementation

(A) The capital multiplier. Reproduce the traffic-light schedule and the capital it implies for a $10M VaR - the model-risk add-on becomes a disclosed dollar figure.

The jump from green ($30.0M) to red ($40.0M) at the same VaR is a $10M capital charge placed on model credibility, not on risk. This is the most consequential sentence in the folder for a firm: the validator’s exception count is a capital input.

(B) The aggregate model-risk scorecard. Score a three-model inventory by the SR-11-7 drivers and aggregate.

Reading it: the VaR engine is the most material model but scores lowest () because validation strength is - the framework is working where it is most developed. The stress model scores highest () despite lower materiality, because it is complex, widely used and weakly validated - precisely where SR 11-7 says the framework “should be more extensive and rigorous.” The aggregate is the number compared to the board’s tolerance .


4. Failure Modes & First-Principles Breakdowns

  1. Compliance without effective challenge. The single most common failure: all documents exist, all three elements are ticked, and no one has the influence to block a model. SR 11-7’s triad - incentives, competence, influence - is the diagnostic; a validator who reports to the model owner fails on incentives.
  2. Validation captured by development. If validation staff rotate from (or seek promotion into) the desk, “independence” is nominal. Independence is a structural property (reporting line, budget, incentives), not a statement in a policy.
  3. Inventory incompleteness. “Both types of model risk for individual models and in the aggregate” presupposes you know your models. Shadow models (spreadsheet add-ins, vendor black boxes used by trading) are outside the inventory and outside the framework - and are exactly the ones Derman warned about.
  4. Aggregate risk as a single number. A scalar score hides correlation and hides the tail: one model whose failure is catastrophic is not captured by a small weighted average. The -weighted form (§2.2) and the max-score floor are the guards.
  5. Model-risk adjustment as a rounding error. If the conservative adjustment (SR 11-7’s “well-supported, judgmental conservative adjustments”) is set without theory, it becomes a plug that hides rather than prices the uncertainty. Tie it to the error budget and to the capital link above.
  6. No standing to say “do not use.” SR 11-7 lists “restrictions on model use” as a mitigating step; a framework without a use-restriction mechanism (and someone empowered to invoke it) cannot manage the largest channel, misuse.

5. References

  • Federal Reserve / OCC, SR 11-7 (2011)
  • BCBS, Supervisory Framework for the Use of Backtesting… (1996, BIS)
  • Derman, E., Model Risk (Goldman Sachs QSR, 1996) - “AVOIDING MODEL RISK”: diffuse the model slowly, test boundaries, don’t ignore small discrepancies, modeler–programmer–user co-location. Read in full from the corpus PDF.
  • Morini, M., Understanding and Managing Model Risk (2011)
  • Hull, J. C., Risk Management and Financial Institutions (5th ed.), Ch on model risk

6. Connected Graph Bridges