Summary Risk appetite statements are commonly board-level and abstract; business limits are operational and specific. The cascade between them is where appetite either becomes a management tool or remains a document. This article sets out how CROs design, operate and maintain that cascade.
The cascade A functioning cascade moves from board appetite statement (qualitative and quantitative), through second-tier metrics (aggregated appetite thresholds), to third-tier operating limits (business-line, portfolio, product, desk or team level). Each level is derived from and traceable to the level above.
Design principles Limits should be operable (the business unit has the authority and information to manage against them), measurable (data exists, timely and accurate), meaningful (not so wide as to be uninformative, not so narrow as to be constantly breached), and defensible (the calibration rationale is documented).
Monitoring and MI Monitoring cadence should match exposure volatility. Reporting should show current position, trend, headroom and breach history. MI that shows only "green" is often uninformative; RAG conventions should have real thresholds.
Breach governance Breach management is where credibility is tested. Objective thresholds, defined escalation, closure discipline and root-cause analysis distinguish a functioning framework from a nominal one. Repeated breaches without recalibration or remediation are a governance failure, not a data issue.
Recalibration Appetite and limits should be reviewed at least annually, and after material events (strategy change, market regime shift, model change, incident). Recalibration should be documented and approved at the appropriate level; drift by accretion is the most common failure mode.
CRO and board implications Boards should see the cascade as a whole, not only headline appetite. Where appetite is comfortable but limits are constantly stressed, the appetite statement has lost contact with the business.
Practical implementation Documented cascade with derivation logic; monitoring MI with headroom and trend; breach register with ageing and remediation; annual recalibration cycle; documented rationale for material threshold changes.
Limitations No limits framework prevents all losses. It disciplines exposure, forces escalation, and provides a defensible record of how appetite translated into decisions.
Related reading See [Enterprise Risk](/expertise/enterprise-risk), [Governance, Risk and Compliance](/expertise/grc), [Effective CRO operating model](/insights/effective-cro-operating-model) and [Governance](/governance).
Frequently asked questions
What should risk leaders know about the cascade?
A functioning cascade moves from board appetite statement (qualitative and quantitative), through second-tier metrics (aggregated appetite thresholds), to third-tier operating limits (business-line, portfolio, product, desk or team level). Each level is derived from and traceable to the level above.
What should risk leaders know about design principles?
Limits should be operable (the business unit has the authority and information to manage against them), measurable (data exists, timely and accurate), meaningful (not so wide as to be uninformative, not so narrow as to be constantly breached), and defensible (the calibration rationale is documented).
What should risk leaders know about monitoring and MI?
Monitoring cadence should match exposure volatility. Reporting should show current position, trend, headroom and breach history. MI that shows only "green" is often uninformative; RAG conventions should have real thresholds.
What should risk leaders know about breach governance?
Breach management is where credibility is tested. Objective thresholds, defined escalation, closure discipline and root-cause analysis distinguish a functioning framework from a nominal one. Repeated breaches without recalibration or remediation are a governance failure, not a data issue.
What should risk leaders know about recalibration?
Appetite and limits should be reviewed at least annually, and after material events (strategy change, market regime shift, model change, incident). Recalibration should be documented and approved at the appropriate level; drift by accretion is the most common failure mode.