Heat Maps for Backtesting Value at Risk
Summary
The document clarifies that “heat-map method” may refer to a way of assessing VaR model performance rather than a procedure for calculating VaR. In the answer provided, historical VaR breaches are counted over a review window and mapped to colored zones: a lower count is green, a cautionary count is yellow, and a higher count is red. The color bands offer a compact view of whether realized static P&L exceeded the VaR forecast too often.
The source gives an illustrative breach-count scheme, but it does not present a universal regulatory standard or explain how to calculate the underlying VaR estimate. It also notes possible ambiguity: a client may mean a visual presentation of backtesting results rather than a specific validation measure. The thresholds and interpretation therefore depend on the convention being used, and should be confirmed before applying the label to a model review.
Key ideas
- A VaR heat map can describe a backtesting assessment rather than a VaR calculation method.
- The described assessment counts days when static P&L exceeds the VaR estimate.
- Breach counts are grouped into green, yellow, and red zones to communicate model performance.
- The term is ambiguous, and the document does not define a universal set of thresholds.
Tags
Full text
# What is the heat-map method of calculating VaR? # What is the heat-map method of calculating VaR? I'm familiar with the historical full revaluation, VcV, and Delta-gamma methods, but a client keeps talking about a heat-map method and I'm not sure what he's talking about. Any ideas? ## Answer by Gordon (score 1) https://quant.stackexchange.com/a/27506 Unless otherwise defined, the heat map is a VaR back-testing measure for the soundness of the VaR measure. For example, it may be allowed to have 4 VaR breaches, where the static P&L is greater than the VaR, for the past 250 business days, and any breaches with a total number not more than 4 are said to be in the green zone, while 5 to 9 breaches are in the yellow, or cautionary, zone, while 10 or more breaches will be in the red zone. ## Answer by Nicholas (score 0) https://quant.stackexchange.com/a/22968 Not sure whether your client wants "method" or "visualisation". I might be guessing that he expects you to present results similar to what's shown here https://msci.com/resources/research/articles/2015/Research_Insight_Backtesting_Risk_Models_2014_YearInReview.pdf
Shown in full with attribution under the source's licence. Licence: CC BY-SA 4.0 (Stack Exchange)
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.