LevelUpWith

Explore / Project Risk Management That People Actually Use / Lesson 2

Lesson 2: Risk Appetite, Tolerance and Thresholds

Understand how an organisation's willingness to take risk becomes concrete thresholds that tell the project team when a risk needs escalating or acting on.

Free to read, no account needed. Part of Project Risk Management That People Actually Use.

By the end of this level you'll be able to

  • Tell risk appetite apart from risk tolerance and risk thresholds
  • Write measurable thresholds for cost, schedule, quality and safety on a sample project
  • Decide when a risk has to be escalated beyond the project team, based on agreed thresholds

Why Thresholds Matter

In Level 1 you saw that a risk is an uncertain event that could affect an objective, and that it can be a threat or an opportunity. That raises a practical question. How much uncertainty is acceptable, and who decides?

Without an agreed answer, two things go wrong:

  • Project managers escalate everything, and sponsors get buried in noise.
  • Project managers escalate nothing, and sponsors find out about a disaster too late to act.

The fix is a short chain of three terms: appetite, tolerance and threshold. Each one turns the one before it into something more concrete.

Step 1: Learn the Three Terms

Term Level What it answers Example
Risk appetite Organisation, strategic How much risk are we willing to take to get the reward? "We will take moderate schedule risk to be first to market. We will take no risk with customer data."
Risk tolerance Objective, agreed range How far may this objective vary before it becomes unacceptable? "Cost may vary by up to +5% of budget."
Risk threshold Project, trigger point At what measurable point must someone act or escalate? "Escalate to the sponsor when the forecast cost passes +5%."

Put simply, appetite is the attitude, tolerance is the acceptable range and the threshold is the line that triggers action.

Note on terminology: frameworks use these words differently.

  • PMI (the PMBOK Guide) describes risk appetite as the degree of uncertainty an organisation is willing to accept in anticipation of a reward. It describes a risk threshold as the measure of acceptable variation around an objective. A ±5% cost threshold reflects a lower appetite than a ±10% one.
  • PRINCE2 7 uses tolerances: the permitted deviation from a plan's targets before the issue goes to the next management level. It offers seven tolerance areas: time, cost, scope, quality, benefits, sustainability and risk.
  • ISO Guide 73 defines risk appetite as the amount and type of risk an organisation is prepared to seek, accept or tolerate.

Whatever words your organisation uses, the logic is the same. Do this: check which terms your organisation uses and stick to them.

Step 2: Find the Appetite Statement

Appetite is normally set above the project, by the board, the executive team or a portfolio office.

  1. Ask your sponsor or PMO for any written risk appetite statement or risk policy.
  2. If none exists, ask the sponsor directly: "Which matters most if we have to trade off: date, budget, scope or quality? Where will you accept no risk at all?"
  3. Write the answer down and get the sponsor to confirm it.

Appetite differs between areas, even within one organisation:

  • IT: a start-up may accept high schedule risk on a new feature but no risk on data protection compliance.
  • Construction: a contractor may accept tight margins but have zero appetite for safety risk.
  • Events: an organiser may accept budget pressure but no movement in the event date, because tickets are already sold.

Step 3: Turn Appetite into Measurable Thresholds

A threshold is only useful if anyone can tell, without arguing, whether it has been crossed. Avoid words like "significant" or "major".

  1. List the project's objectives: cost, schedule, quality, safety, plus anything else that matters, such as scope or benefits.
  2. For each one, agree a tolerance: the acceptable range of variation.
  3. Set an escalation threshold at the edge of that tolerance.
  4. Optionally, set an early-warning threshold inside it, so the team acts before the limit is reached.
  5. State the unit of measure and who checks it.

Worked example: corporate conference, budget £200,000, fixed event date

  • Cost: tolerance +5% (£10,000). Early warning when the forecast overspend reaches £5,000. Escalate to the sponsor when it is forecast to exceed £10,000.
  • Schedule: zero tolerance on the event date. Internal milestones may slip up to 5 working days. Escalate any risk that threatens the event date itself, straight away.
  • Quality: average attendee satisfaction of at least 4.0 out of 5, and no AV outage longer than 10 minutes. Escalate any risk forecast to breach either.
  • Safety: zero tolerance. Any risk with a credible chance of injury goes immediately to the sponsor and the venue safety officer, whatever the cost of fixing it.

The same pattern works elsewhere. An IT go-live might have "no more than 2 hours of unplanned downtime". A building project might have "handover no more than 10 working days late".

Step 4: Decide When to Escalate

Once thresholds are agreed, escalation becomes a rule rather than a judgement call. Ask these questions about each risk:

  1. If this risk happened, would it push any objective beyond its tolerance? If yes, escalate.
  2. Does the forecast already show a tolerance being breached? If yes, escalate now rather than waiting for it to happen.
  3. Is it a safety or zero-tolerance area? If yes, escalate immediately.
  4. Does the response need authority or money the project doesn't have? If yes, escalate. This applies to opportunities too, such as spending extra to secure a better venue.
  5. If none of these apply, the project team manages the risk within its delegated limits.

This is what PRINCE2 calls managing by exception: the project manager runs things day to day inside tolerance, and the board only steps in when a tolerance is forecast to be breached.

When you escalate, include:

  • the risk and which threshold it affects
  • the forecast variance (for example, "cost +£14,000, against tolerance of +£10,000")
  • the options available and your recommendation

Key Takeaways

  • Appetite is the organisation's overall willingness to take risk for reward. Tolerance is the acceptable range for each objective. A threshold is the measurable trigger for action or escalation.
  • Appetite varies by area. Many organisations accept schedule or cost risk but have zero tolerance for safety or compliance risk.
  • Write thresholds as numbers with units, such as "+5% of budget" or "5 working days", never as vague words.
  • Set early-warning thresholds inside tolerance so you can act before the limit is reached.
  • Escalate when a risk would push an objective beyond tolerance, when a forecast already shows a breach, when safety is involved, or when the response needs authority the project doesn't have.
  • A tighter threshold reflects a lower appetite for risk.

A 6-question knowledge check follows this lesson in the app, free and without an account.

Keep going: levels 3 and 4 are free

Create a free account to open the next two levels, try the AI tutor, save your progress and pick up where you left off. No card needed.

Next: Level 3, Finding Risks: Identification Techniques.

Create a free account →See the whole course

More like this