How to present the risk register to the board
—10 min read

Present the board with the ten or so top risks on one page: for each risk its owner, current rating, trend since the last report, the status of the main mitigation and whether it is outside the board's risk appetite. Add a heatmap only if it shows movement and uses defined scales. The full register stays in the appendix; the board's time goes to the risks that changed or breach appetite.
What does the board need from the risk register?
The board needs to know whether the company's main risks are understood, owned and under control, and where they are not. It does not need the full register of 80 operational risks. Swiss company law does not prescribe a risk register as such, but it makes the board responsible for the overall direction of the company, for its organisation and financial control, and for overseeing the people entrusted with management (Art. 716a para. 1 nos. 1, 2, 3 and 5 CO). The board may assign preparation and supervision to committees or individual members, but it must ensure adequate reporting to all its members (Art. 716a para. 2 CO), and the organisational regulations set out how management reports (Art. 716b para. 3 CO).
For companies required by law to undergo an ordinary audit, the management report has to give information on whether a risk assessment was carried out (Art. 961 no. 3 and Art. 961c para. 2 no. 2 CO). That is a disclosure duty, not a template: the form of the board's risk reporting is the board's choice. A good board risk report answers three questions: which risks matter most right now, which have changed, and where does management need a decision or a different appetite from the board?
What goes on the one-page summary?
A single table, sorted by importance, with the same columns every time. Sort by rating and appetite status, not by department, so the board reads the most important line first.
| Risk | Owner | Rating | Trend | Mitigation status | Appetite |
|---|---|---|---|---|---|
| Loss of the largest customer | CEO | High | Rising | Contract renewal talks started; due Q1 | Outside |
| Ransomware attack on production systems | CIO | High | Stable | Backup restore test passed in October | Within |
| Key supplier insolvency | COO | Medium | Rising | Second supplier qualified for 40 percent of volume | Within |
| Shortage of skilled engineers | Head of HR | Medium | Stable | Apprenticeship programme expanded | Within |
| Currency exposure EUR | CFO | Medium | Falling | Hedging at 70 percent for 2027 | Within |
Under the table, add three short notes: what changed since the last report, which risks are new or removed, and what the board is asked to do. If the notes are longer than the table, the table is not doing its job.
What does each column mean?
| Column | What it must say | Common error |
|---|---|---|
| Risk | A concrete event with a cause and a consequence, in one line | Vague labels such as «IT» or «Market» |
| Owner | One named executive, not a department | Two owners, which means none |
| Rating | The rating after current mitigation, using the scale the board approved | Mixing before- and after-mitigation ratings in one column |
| Trend | Rising, stable or falling since the last report, with the reason in the notes | An arrow with no explanation |
| Mitigation status | The next concrete step and its date | «Ongoing» |
| Appetite | Within or outside the approved risk appetite statement | Judging against a statement the board never approved |
The appetite column only works if the board has approved a risk appetite statement; how to write one is covered in our post on the risk appetite statement. The one-page layout above is also the basis of the board risk report template.
What does a quarterly risk page look like? A worked example for Muster AG
Muster AG is an invented company used here only to illustrate the format. Its board meets five times a year, its risk manager is the CFO, and it reports the top risks at every meeting. For the meeting in November the risk page contains the table above plus these notes.
- What changed: «Loss of the largest customer» moved from Medium to High because the customer put its framework contract out to tender. «Currency exposure EUR» fell after the hedge ratio was raised.
- New and removed: «Key supplier insolvency» is new, after the supplier's credit rating was lowered. «Loss of the IT service provider» is removed, because the contract was renewed for three years.
- Decision requested: the board is asked to decide whether to accept the customer concentration risk until the renewal is signed in Q1, or to approve an additional sales programme.
The second step is the one most reports skip: the page ends with a decision, not with information. The chair can then put exactly one item to the vote and the minutes record it.
How do you show appetite breaches?
Put them first and propose a response. A risk outside appetite is a signal that either the risk must come down, or the board must consciously accept more risk for a time. Both are board decisions.
- Name the risk and the appetite statement it breaches.
- Say by how much and since when.
- Propose an action with owner and date, or propose that the board accepts the risk temporarily, with a review date.
- Record the board's decision in the minutes and track it like any other action item.
Sample resolution wording for a temporary acceptance: «The board takes note that the risk 'Loss of the largest customer' is outside the approved appetite for customer concentration. It accepts the risk until 31 March 2027, instructs the CEO to report on the status of the renewal at every meeting until then, and will review the decision at the March meeting.» The date matters: an acceptance without a review date becomes a permanent change of appetite by accident.
How do you build a heatmap that does not mislead?
Heatmaps are popular because they are quick to read. They mislead when scales are vague, when ratings are multiplied as if they were precise numbers, and when they show only a snapshot. Likelihood and impact scores are ordinal: a 4 is worse than a 3, but not by a fixed amount.
- Define each scale in words and numbers, and have the board approve the definitions.
- Show movement: an arrow from last quarter's position to this quarter's says more than a dot.
- Plot only the top risks. A heatmap with 60 dots is a pattern, not a message.
- Do not rank risks by multiplying likelihood and impact scores alone. A rare catastrophic risk and a frequent minor one can get the same score and need very different responses.
- Show the rating after mitigation, and say so in the title.
| Score | Likelihood | Impact |
|---|---|---|
| 5 | Expected within 12 months | More than CHF 5 million, or loss of a licence |
| 4 | Expected within three years | CHF 2–5 million, or loss of a key customer |
| 3 | Possible within five years | CHF 500,000–2 million |
| 2 | Unlikely within five years | CHF 100,000–500,000 |
| 1 | Rare | Below CHF 100,000 |
Some boards drop the matrix altogether and use the table with a trend column. That is a legitimate choice, especially for small boards with fewer than a dozen top risks.
Who presents, and how long does it take?
The risk manager or the CFO presents, with the risk owners available for questions on their risks. As a starting point, not a rule, a 15-minute slot can run like this.
| Step | Who | Minutes |
|---|---|---|
| Appetite breaches and the decision requested | Risk manager or CFO | 5 |
| Changes since the last report: new, removed, moved risks | Risk manager | 3 |
| Questions on individual risks | Risk owners | 5 |
| Decision and next review date | Chair | 2 |
Send the page with the board book, so directors arrive having read it; the questions they send in advance tell you which risks to prepare. See questions before the board meeting.
How often should the board see the risk report?
At least once a year in full, as the annual risk assessment, and at every meeting in short form: changes, new risks and appetite breaches. Many boards delegate the detailed review to the audit committee or a risk committee and receive its summary; the committee chair then reports to the board (see the committee chair's report). Delegation does not move the responsibility: under Art. 716a para. 2 CO the board remains responsible for adequate reporting to all its members.
Keep the format stable. A risk report that changes layout each time makes it hard for directors to see trends, which is exactly what the report is for.
What changes with the type of organisation?
| Organisation | What to adjust |
|---|---|
| AG required by law to have an ordinary audit | The management report must report on the risk assessment carried out (Art. 961 no. 3 and 961c para. 2 no. 2 CO); the board report is the evidence of the process behind it |
| GmbH | Management often sits with the managing directors; agree in the articles or regulations which risks go to the shareholders' meeting |
| Verein or Stiftung | Fewer risks, often compliance, reputation and funding; the board of the association or foundation council receives the same one-page format |
| Subsidiary in a group | Align scales with the group so that the local board and the parent compare like with like; add the risks the parent has delegated |
| Listed company | Check disclosure rules with counsel before the risk page is reused in any external report |
Where a row depends on the articles of association or the organisational regulations, read those first: they can add reporting duties that go beyond the law.
How does a board portal help with risk reporting?
A portal keeps the risk report in a fixed place on the agenda, restricts detailed registers to the people who need them and turns the board's decisions into tracked tasks. In Konsaro, access can be restricted per paper and per agenda item, for example for a detailed register that only the audit committee sees, and tasks from the discussion go into the tasks and decisions register with an owner, due date and status. More on board materials and minutes and follow-up.
How decisions on risks stay linked to the risks they affect is covered in linking board decisions to risks; why risk reports can lull a board rather than alert it is the subject of risk paradoxes in board oversight.
What are the common mistakes?
- Sending the whole register. Directors skim it and miss the three lines that matter.
- Changing the layout every quarter, so trends cannot be seen.
- Rating risks before mitigation in one report and after it in the next.
- Listing risks with no owner or with a department as owner.
- Reporting a breach without a proposal, which leaves the chair to improvise a decision.
- Never removing risks, so the page grows until nobody reads it.
Frequently asked questions
How many risks should the board see?
About ten top risks on the summary page, plus any new risks and appetite breaches. The full register belongs in an appendix or with the committee that reviews it.
Who presents the risk report?
The risk manager or the CFO, depending on the company. The risk owners should be available for questions on their risks.
Should ratings be before or after mitigation?
Show the rating after current mitigation, and say so. If the board also wants the rating before mitigation, show both in two columns rather than mixing them.
Is a heatmap required?
No. A clear table with trend and appetite is enough. A heatmap helps if it shows movement and uses defined scales.
Does Swiss law require a risk register?
Not by name. The board must direct and supervise the company and ensure adequate reporting (Art. 716a CO), and companies required by law to have an ordinary audit report on the risk assessment in their management report (Art. 961 and 961c CO). How the board gets its risk information is for the board to decide.
What should the board do with an appetite breach?
Either order measures that bring the risk back within appetite, or accept it consciously for a limited time with a review date. Record the decision in the minutes.
How do you keep the risk page short as the register grows?
Set a fixed number of top risks, for example ten, and require that a risk enters the page only if another leaves or the rating changes. The rest stays in the appendix.
Sources
- Obligationenrecht (SR 220), Art. 716a, 716b: fedlex (checked 29 October 2026)
- Obligationenrecht (SR 220), Art. 961 and 961c: fedlex (checked 29 October 2026)



