What we doAdvisory & ConsultancyRisk Appetite & Enterprise Risk Governance
Risk appetite that binds when it matters.
Nearly every institution has a risk appetite statement; very few are constrained by one. The document speaks in adjectives, the metrics nobody breaches because nobody could, the cascade stops at the first business line. When a real decision arrives — a concentration, an acquisition, a new market — the statement is silent. BIZENIUS builds appetite that binds: limits derived from capital and liquidity capacity, cascaded to where decisions are made, governed by a board that knows what it has agreed to forgo.
Where this begins
The tells that appetite exists on paper only.
No breach has ever occurred
Years of green dashboards — because the metrics were set where the business already was, not where capacity runs out. Appetite that cannot be breached cannot bind.
The statement didn’t vote
A major decision — a concentration, a market entry — went to the board, and the risk appetite statement was not cited once. The document and the decisions live apart.
The supervisor called it generic
The findings letter used the word — or its polite cousins: “not sufficiently institution-specific”, “limited evidence of use”. The next review expects an appetite the institution visibly runs on.
What we deliver
Appetite with arithmetic behind it.
An appetite engagement connects three things most frameworks keep apart: what the institution can absorb, what it chooses to pursue, and what its desks are actually permitted to do.
Capacity analysis
Appetite derived from capital and liquidity capacity — the arithmetic that turns “moderate risk appetite” into numbers with a defensible origin.
The appetite statement
Institution-specific, metric-anchored, honest about trade-offs — a document that can say no, written with the board that must mean it.
The cascade
Appetite translated into limits, thresholds and mandates at business-line and desk level — so the statement governs decisions it will never attend.
The ERM frame
Risk universe, taxonomy and governance — committees, escalation, reporting — proportionate to your institution, with the three lines of defence given real content.
The board’s instrument panel
Reporting that shows position against appetite in decision form — including the breaches, because a framework without breaches is a framework without information.
How the engagement runs
Diagnose. Design. Build. Embed.
Diagnose
The current statement against use: capacity link, cascade depth, and whether one recorded decision cites it.
Design
Metrics, limit architecture and governance — derived from your capital and liquidity reality, not a peer template.
Build
With the CRO office and business lines — capacity analysis, statement and cascade drafted together, tested against last year’s real decisions.
Embed
Board session on the trade-offs being signed, cascade briefed to the desks it governs, first monitoring cycle run with our review.
Perimeter and fee are fixed at the diagnostic — full framework or appetite statement and cascade alone.
Asked before engaging
The questions CROs and board chairs put to us first.
We have a risk appetite statement. What would actually change?
The test is simple: name one decision in the last year the statement changed. If the answer is slow to come, what changes is everything between the document and the desks — capacity arithmetic behind each metric, a cascade that reaches where risk is taken, and reporting the board can govern with. The statement may keep its title; it stops being decorative.
How does this relate to our ICAAP?
Appetite and ICAAP share a spine — capital capacity. We derive appetite metrics from the same capacity analysis the ICAAP rests on, so the two documents agree by construction rather than by annual reconciliation. Clients who rebuild both with us get one framework wearing two covers.
How long does this take?
Fixed at the diagnostic. Statement and cascade typically span a quarter; a full ERM framework build runs longer and is staged so governance improvements land before the paperwork does.
Who does the work?
Practitioners who have held the CRO seat and sat on board risk committees — people who have both written appetite statements and been bound by them. No junior consultants.
What do you need from us?
The current statement and its metrics, capital and liquidity positions, a sample of last year’s significant risk decisions, and board risk-committee time at two points. Listed in full at the diagnostic.
The Capability Arc™
This practice is one point on the arc.
Appetite clients usually pair the framework with the masterclass that equips their risk function — and the reporting that keeps position against appetite visible.
Learn it · Training
Advanced Enterprise Risk Management (ERM) Masterclass
Appetite, taxonomy and governance as one discipline — taught by practitioners who have run risk functions.
Automate it · Smart IT
Risk Data, Controls & MI (BCBS 239)
The data and reporting spine that shows position against appetite — with lineage an examiner can follow.
The ask
Request a confidential appetite review.
A senior practitioner reads your appetite statement against your capital reality and your last year of decisions — and tells you privately whether it binds, or merely describes.
Confidential by default; under NDA on request. A senior practitioner responds within two working days.
Risk Appetite & Enterprise Risk Governance
Leave the question with us.
Two lines on the mandate is enough — a senior practitioner replies within one business day.