Summary Investment risk limits are the operational face of risk appetite in asset management. Their credibility depends on calibration, monitoring and — most importantly — on escalation paths that hold up when markets stress. This article sets out how to design limits and liquidity management that work under pressure, not only in calm conditions.
Limit design Limits should be structured across the risks that matter: tracking error, VaR, concentration (single-name, sector, geography), counterparty, leverage, currency, and liquidity. Each limit should have a documented rationale, a defined owner, and a defined escalation on breach. Limits without escalation are indicators.
Liquidity management Fund liquidity — asset side and liability side — is the risk that most often materialises adversely under stress. Liquidity buckets, redemption assumptions, and stress scenarios should be modelled explicitly. Liquidity management tools (swing pricing, gates, side pockets) require governance around when and how they are used.
Monitoring cadence Monitoring should match the volatility of the exposure. Market risk limits typically require daily monitoring; concentration and liquidity limits may be weekly or monthly. Cadence that is slower than exposure change means limits are reported after they matter.
Escalation Escalation is the discipline that turns limits into control. Thresholds should be objective, escalation paths named, and closure discipline enforced. Breach registers should be visible to the risk committee, with ageing and remediation.
CRO and board implications Boards should see limits framework health as a leading indicator of investment risk control: breach frequency, ageing, escalation compliance, and calibration reviews. A framework with no breaches over long periods is not necessarily well-calibrated — it may be uninformative.
Practical implementation Documented limits framework with rationale and ownership; daily/weekly monitoring per exposure type; liquidity stress framework covering asset and liability sides; documented use of liquidity management tools; breach register and closure discipline.
Limitations No limit framework prevents market losses. It disciplines exposure to defined bounds and forces escalation when those bounds are approached.
Related reading See [Investment & Asset Management risk governance](/insights/risk-governance-for-investment-firms), [Financial Risk](/expertise/market-liquidity) and [Enterprise Risk](/expertise/enterprise-risk).
Frequently asked questions
What should risk leaders know about limit design?
Limits should be structured across the risks that matter: tracking error, VaR, concentration (single-name, sector, geography), counterparty, leverage, currency, and liquidity. Each limit should have a documented rationale, a defined owner, and a defined escalation on breach. Limits without escalation are indicators.
What should risk leaders know about liquidity management?
Fund liquidity — asset side and liability side — is the risk that most often materialises adversely under stress. Liquidity buckets, redemption assumptions, and stress scenarios should be modelled explicitly. Liquidity management tools (swing pricing, gates, side pockets) require governance around when and how they are used.
What should risk leaders know about monitoring cadence?
Monitoring should match the volatility of the exposure. Market risk limits typically require daily monitoring; concentration and liquidity limits may be weekly or monthly. Cadence that is slower than exposure change means limits are reported after they matter.
What should risk leaders know about escalation?
Escalation is the discipline that turns limits into control. Thresholds should be objective, escalation paths named, and closure discipline enforced. Breach registers should be visible to the risk committee, with ageing and remediation.
What should risk leaders know about cRO and board implications?
Boards should see limits framework health as a leading indicator of investment risk control: breach frequency, ageing, escalation compliance, and calibration reviews. A framework with no breaches over long periods is not necessarily well-calibrated — it may be uninformative.