Home / Guides / Risk Appetite, Tolerance, and Limits
Guide

Risk Appetite, Tolerance, and Limits

How appetite and tolerance guide decisions, escalation, and resource allocation without becoming vague slogans.

By Adrian M. FenwickReviewed August 3, 2026

Risk appetite describes the amount and type of risk an organization is willing to pursue or retain in support of objectives. Tolerance and limits translate that intent into more specific boundaries for decisions and performance.

Connect appetite to objectives

Appetite should not be a generic claim that the organization is low risk. Different objectives require different choices. An organization may accept experimentation in product development while maintaining very low tolerance for non-compliance or unsafe operation.

Use layers of guidance

LayerRole
PrinciplesOverall stance and non-negotiable expectations
Objective-level appetiteAcceptable uncertainty for a specific objective
TolerancePermitted variation around targets
Limits and thresholdsBoundaries for action or escalation
Delegated authorityWho may accept exposure at each level

Make it operational

Link appetite to decision rules, project gates, control requirements, indicator thresholds, and escalation paths. Staff should know what to do when a boundary is approached or exceeded.

Avoid false precision

Not every appetite statement needs a number. Where reliable measures exist, quantitative limits can help. Where they do not, use specific qualitative conditions and examples rather than arbitrary percentages.

Review when context changes

Strategy, financial capacity, regulation, stakeholder expectations, and external conditions can change the willingness or ability to retain risk. Review appetite alongside strategy and major decisions.

Use with judgmentRisk methods support decisions; they do not remove uncertainty. Record assumptions, limits, and acceptance authority.

Translate broad statements into decisions

“Low appetite for operational disruption” is too general to guide a front-line decision. Appetite becomes useful when connected to objectives, measures, tolerances, limits, approval levels, and escalation triggers. Different activities may have different tolerances, and an organization can accept one kind of exposure while being highly cautious about another.

Appetite is not a promise of zero risk

Some objectives require taking uncertainty deliberately, such as investing in a new service or entering a new market. Appetite helps define the nature and amount of uncertainty the organization is prepared to pursue or retain. It should also clarify when temporary breaches can be approved, by whom, and for how long.

Practical questions

  • Which measures show that exposure is approaching a limit?
  • Who can approve an exception?
  • How are competing objectives balanced?
  • Are statements understood by the people making daily decisions?
  • When will appetite and tolerances be reviewed?