How to Write a Risk Appetite Statement That Boards and Management Can Actually Use

By Kirsten Smith, Chartered Governance Professional

If management can’t use a risk appetite statement to make a decision, it is worth asking what the statement is actually for.

Many organisations have one. Fewer have one that changes what anybody does.

A useful risk appetite statement should help answer practical questions. Can management proceed with a new initiative? How much financial variation is acceptable? When does an issue need to be escalated? What decisions sit within delegation, and what needs to come back to the board?

That is the real test.

Start with the organisation’s own risks

I don’t think a good risk appetite process should begin with a generic template.

It should begin with the organisation’s strategy, risk register, regulatory environment and the decisions the board is actually likely to face.

This is why I developed a tailored risk appetite module for boards. Directors complete it individually before the workshop, using questions built around the organisation’s own risks.

That gives us a picture of where the board is aligned and where there are genuine differences.

The workshop can then focus on those differences rather than starting from scratch.

For example, directors may all say they have a low appetite for financial risk, but mean very different things by that. One may be thinking about tight budget control, another about protecting reserves, and another about whether the organisation should be prepared to fund a strategic initiative that may not generate an immediate return.

The rating alone does not resolve that. The discussion does.

Don’t stop at low, moderate or high

A risk appetite level is only the starting point.

Take technology risk.

A board might have:

Or take financial risk.

A board may expect tight control of ordinary expenditure, but still be prepared to use reserves for a strategic initiative.

That is why a useful statement needs more than one rating per category.

It should usually include:

Appetite and tolerance do different jobs

Risk appetite describes the amount and type of risk the organisation is willing to accept.

Tolerance tells management when the organisation is moving outside that position.

For example:

A board may have a low appetite for disruption to critical systems.

The tolerance might say that an outage beyond a certain period must be escalated.

A board may have a low appetite for losing key staff.

The tolerance might identify when turnover, prolonged vacancies or the loss of multiple critical roles requires board attention.

A board may have a moderate appetite for strategic investment.

The guardrails might set out how much can be spent, whether reserves can be used, what contingency is required and when the project must return to the board.

That is what turns risk appetite into something operational.

Risk appetite should support strategy

One of the most useful parts of a risk appetite discussion is testing whether the board’s appetite actually supports the strategy it has approved.

An organisation may say it wants to innovate while having almost no appetite for unsuccessful initiatives.

It may want to grow while remaining uncomfortable with expenditure, recruitment or implementation risk.

It may want to diversify income while rejecting the uncertainty involved in testing new revenue sources.

Those tensions are worth surfacing.

The answer is not always to increase appetite. Sometimes the strategy needs to change.

Either way, the board should make the choice deliberately.

Guardrails are often more useful than another rating

A board can be conservative about day-to-day finances while still being prepared to take strategic risk.

The way to make those positions work together is through guardrails.

For example, a strategic initiative might be acceptable if:

That gives management practical room to act without weakening board oversight.

Link the statement to the risk register

The risk appetite statement and risk register should work together.

The risk register tells the board what risks exist and how they are being managed.

The appetite statement tells the organisation whether the remaining exposure is acceptable.

If a residual risk sits above appetite, the board should know.

That does not always mean the risk must immediately be reduced. The board may consciously accept the position for a period.

What matters is that it is a deliberate decision.

Build risk appetite into board papers

A simple way to make risk appetite part of normal governance is to include it in decision papers.

Where a paper seeks a material decision, it should say how the proposal sits against the organisation’s risk appetite.

That may only require one sentence.

Is the proposal within appetite? Does it sit near a tolerance? Does it require the board to accept more risk than usual? Are particular guardrails relevant?

This keeps risk appetite connected to actual decisions rather than leaving it as a document reviewed once a year.

Give tolerances an owner

Each meaningful tolerance should have someone responsible for monitoring it.

The reporting approach can then be simple.

Boards do not need to discuss every tolerance at every meeting. Reporting by exception is often more useful.

Show directors what is outside appetite, or trending towards it, explain why, and identify what management proposes to do.

What happens when a tolerance is reached?

A practical statement should make that clear.

A simple process is:

Escalate. Tell the appropriate executive, Chair or committee.

Explain. Set out what happened and why.

Decide. Take corrective action, or deliberately accept the position for a defined period.

Learn. If the same tolerance is repeatedly reached, reconsider either the controls or the appetite itself.

If the board continually accepts exceptions, the documented appetite may no longer reflect reality.

The workshop matters as much as the document

The final statement is important, but the discussion that produces it can be just as valuable.

In a recent client engagement, I used a tailored online module based on the organisation’s own strategic risk register before facilitating a board risk appetite workshop.

Each director formed a view independently first.

The workshop then concentrated on the areas where those views differed.

That meant the board spent its time on real questions of judgement rather than working mechanically through a generic template.

The final statement reflected the organisation’s own strategy, risks, tolerances and decision-making needs.

That is what a good risk appetite statement should do.

What should a good risk appetite statement contain?

At a practical level, I would expect to see:

It does not need to be complicated.

The best statements are the ones people actually use.

The real test

The quality of a risk appetite statement is not determined by how polished it looks.

Its value becomes apparent when somebody has to make a difficult decision.

Can management tell what it has authority to do?

Can the board see when the organisation is moving outside the boundaries it intended?

Does management know when something needs to be escalated?

And do the board’s risk settings support the strategy it has approved?

If the answer is yes, the statement is doing useful governance work.

If the answer is no, changing the colours on the risk matrix probably is not going to fix it.

Developing a board risk appetite statement

Governance in Focus works with boards to develop practical risk appetite statements using the organisation’s own strategy, risk register and governance context.

The process can include a tailored director risk appetite module, analysis of board responses, a facilitated workshop and development of the final statement, including tolerances, guardrails and escalation points.

The aim is simple: to give the board and management a shared understanding of which risks the organisation is prepared to take, which it is not, and where management has room to make decisions without returning unnecessarily to the board.