Enterprise Risk Management Report: What to Include, With a Sample

November 17, 2026

An enterprise risk management report (ERM report) is the document through which the risk function tells the board and senior management what the organisation's risk profile is, how it has changed since the last report, whether it sits inside the agreed risk appetite, and what decisions are needed. It is the output that justifies the whole ERM programme: a risk register nobody reports from is an inventory, not risk management.

This guide is written by a practitioner for the person who has to produce one: a chief risk officer, head of risk or compliance officer at a mid-size organisation. It covers the types of ERM report, the ten sections a good one contains, a worked sample for a fictional payment institution, how to write it so a board actually reads it, and the mistakes that make directors stop trusting the numbers.

What Is an Enterprise Risk Management Report?

ISO 31000:2018 treats reporting as part of the risk management process itself (clause 6.7, "Recording and reporting"): its purpose is to communicate risk management activities and outcomes, provide information for decision-making, and support oversight by those accountable. COSO's 2017 ERM framework makes "Information, Communication and Reporting" one of its five components. Both say the same thing in different words: the report exists to support decisions, not to prove that the risk team was busy.

In practice, an ERM report answers five questions for its reader:

  1. What are our most significant risks right now?
  2. What has changed since we last looked, and why?
  3. Are we inside or outside our risk appetite?
  4. Are the actions we approved actually being delivered?
  5. What do you need us, the board, to decide?

If a report answers all five on its first two pages, it is doing its job. If the reader has to reach page 14 to find the answer to question 5, it is not.

Types of ERM Report

"The risk report" usually means several documents with different readers and rhythms. Mixing them up is one of the most common reasons reports are too long.

ReportReaderFrequencyFocus
Board / risk committee reportBoard, audit and risk committeeQuarterlyTop risks, appetite, decisions required
Annual risk reportBoard, sometimes regulator or shareholdersYearlyFull risk profile, year-on-year movement, effectiveness of the framework
Management risk reportExecutive committeeMonthlyKRI breaches, overdue actions, new incidents
Risk owner viewProcess and risk ownersContinuousTheir own risks, reviews and actions due
Thematic or deep-dive reportCommitteeAd hocOne risk area in depth, e.g. cyber, liquidity, a key supplier

The quarterly board report is the one most people mean when they search for an ERM report, and it is the one this guide focuses on. The annual risk report uses the same structure with a longer look-back and a section on how well the framework itself worked.

What to Include: the Ten Sections

A good quarterly ERM report has a fixed structure, so that directors know where to look and can compare one quarter with the next. These are the ten sections that matter, in the order they should appear.

1. Executive summary (one page)

Three to five sentences on the overall risk profile, the two or three things that changed, and the decisions requested. Write it last and make it the only page some directors will read. Every claim in it must be supported by a later section.

2. Risk profile against appetite

A short table showing each risk category (strategic, financial, operational, compliance, technology, people) with its current position against the appetite statement approved by the board: within appetite, approaching the limit, or outside it. Appetite without a reported position is a policy nobody can test.

3. Top risks

The top eight to twelve risks by residual score, each with its owner, inherent score, residual score, movement since the last quarter and one line of commentary. Use the same scale every time. If you use a 5×5 matrix, follow the conventions in our guide to the ISO 31000 risk matrix so that a 15 means the same thing in every business unit.

4. Heat map

One heat map of the top risks at residual level, ideally with arrows or "ghost" markers showing where each risk sat last quarter. Movement is the information; position alone is not.

5. Key risk indicators

The indicators that breached or approached their thresholds, not all of them. For each: the metric, the threshold, the current value, the trend over the last three periods and what was done. Our guide to key risk indicators covers how to set thresholds that make this section meaningful.

6. Incidents and loss events

Material incidents in the period, near misses that reveal a control weakness, and the cumulative loss figure against the prior year. Link each incident to the risk it crystallised; an incident that does not map to any register risk is a sign the register is incomplete.

7. Emerging risks

Two to four risks not yet on the register or not yet scored highly, with a sentence on why they deserve attention: a regulatory change, a new market, a supplier concentration, a technology shift. This is the section boards value most and risk teams most often skip.

8. Action plan status

Treatment actions due in the period: delivered, on track, overdue. Report overdue actions by name and owner, with the new date and the reason. A report that shows 40 actions "in progress" every quarter is telling the board nothing.

9. Assurance

What internal audit, compliance monitoring and external reviewers found in the period that bears on the risk profile: open high-rated findings, their linked risks and the agreed management response. Our article on internal audit management explains how to keep findings and risks linked so this section writes itself.

10. Decisions requested

Explicit, numbered requests: accept a risk outside appetite until a date, approve additional budget for a treatment, change an appetite limit, approve a new policy. If there are no decisions to request, say so; that is also information.

A Worked Sample: Quarterly ERM Report for a Payment Institution

The following is a condensed sample for a fictional mid-size payment institution, "Example Payments Ltd", for the third quarter. Scores use a 5×5 matrix (likelihood × impact, 1 to 25).

Executive summary. The overall risk profile is stable, with one risk outside appetite. Supplier concentration risk rose from 12 to 16 after our card-processing provider announced a platform migration for the first quarter of next year; it is now outside the operational appetite of 15. Fraud losses fell 22% quarter on quarter after the new transaction-monitoring rules went live. We ask the committee to (1) accept the supplier risk outside appetite until 31 March, subject to the exit-plan test described in section 8, and (2) approve the budget for a second processor proof of concept.

Top risks (extract).

#RiskOwnerInherentResidualLast QMovement
1Card-processor concentrationCOO201612▲
2Safeguarding reconciliation failureCFO201212▶
3Payment fraudHead of Fraud201015▼
4AML control failure in onboardingMLRO1699▶
5Key-person dependency in IT operationsCTO1286▲

Key risk indicators (breaches only).

KRIThreshold (amber / red)Q1Q2Q3Status
Share of volume through one processor70% / 85%82%84%88%Red
Safeguarding breaks open > 1 day1 / 3012Amber
Onboarding files with missing source-of-funds evidence2% / 5%4.1%3.0%2.4%Amber, improving

Actions. Of 14 actions due this quarter, 10 were delivered, 2 are on track for a revised date and 2 are overdue. The overdue items are the processor exit-plan test (COO, moved from 30 September to 15 November because the vendor test environment was unavailable) and the IT operations runbook (CTO, moved to 31 December).

Emerging risk. The processor's migration creates a change-freeze window that overlaps our peak season; we propose adding a dedicated risk with an owner in the next review cycle.

Notice what the sample does. Every number in the executive summary appears in a table below it. The one risk that moved most is explained in a sentence. The KRI table shows three periods, so the trend is visible without commentary. The decisions are numbered and tied to evidence. Nothing in it would surprise a director who had read the previous quarter's report, which is exactly the point.

How to Write an ERM Report the Board Will Read

  • Lead with movement, not levels. Directors remember last quarter's picture. Tell them what is different.
  • Apply the "so what" rule. Every chart and table needs one sentence explaining why it matters. If you cannot write that sentence, cut the chart.
  • Keep the scales fixed. Changing the impact scale between quarters makes every comparison meaningless and quietly erodes trust in the whole report.
  • Separate the summary from the evidence. A two-page front section and an appendix beats a 30-page narrative. Committees read the front and consult the back.
  • Name owners and dates. "IT is working on it" is not reportable. "CTO, 31 December" is.
  • Report from the system of record. If the report is assembled from spreadsheets and slides, the numbers will disagree with the register within a quarter. Generating it from the live register means the heat map, the KRI table and the action list all describe the same reality.

Common Mistakes

  • The top-40 list. Reporting every risk at board level hides the five that matter. Keep the full register in the appendix or the system.
  • Inherent scores only. The board needs to know the position after controls, and how much it relies on those controls working.
  • No link between incidents and risks. If a material incident happens and the related register risk was rated low, the report should say so and the score should change.
  • Green everywhere. A report where nothing is ever amber or red is either a very lucky organisation or a reporting culture that suppresses bad news. Boards and supervisors tend to assume the second.
  • No decisions. A report that never asks the board for anything turns the risk committee into an audience.

These problems are usually symptoms of the wider issues discussed in our piece on the challenges of enterprise risk management: inconsistent scales, weak ownership and data held in too many places.

Producing the Report from Live Data

The labour in risk reporting is rarely the writing; it is collecting and reconciling the inputs. A practical sequence for each quarter:

WeekStep
Quarter end − 3Risk owners complete their reviews and update residual scores in the register
Quarter end − 2KRI values loaded, thresholds checked, breaches commented by owners
Quarter end − 1Action status confirmed; overdue items explained; audit findings linked
Quarter endDraft report generated from the register; executive summary written; CRO sign-off
Committee − 1 weekReport circulated with the decision papers

This is where software earns its cost. In ActiveERM, for example, the register, KRIs, actions, incidents and audit findings are linked records, so the board report is produced from the same data the owners maintain rather than rebuilt in slides each quarter. Whatever tool you use, the test is the same one we set out in our eGRC platform buyer's guide: can the board report be generated from live data without manual reconciliation?

FAQ

What is an enterprise risk management report?

An enterprise risk management report is a periodic report from the risk function to the board and senior management. It sets out the organisation's most significant risks, how they have changed, their position against the approved risk appetite, the status of treatment actions, relevant incidents and assurance findings, and the decisions management needs from the board.

What should an ERM report include?

At minimum: an executive summary, the risk profile against appetite, the top risks with inherent and residual scores and movement, a heat map, key risk indicator breaches, material incidents, emerging risks, the status of treatment actions, assurance findings, and a list of decisions requested. Keep the structure the same every period so readers can compare.

How often should an enterprise risk report be produced?

Most organisations report to the board or risk committee quarterly, with a monthly management report for the executive team and an annual risk report that reviews the whole year and the effectiveness of the framework. Regulated firms should also follow any frequency set by their supervisor or their own governance documents.

What is the difference between a risk register and an ERM report?

The risk register is the complete, maintained inventory of risks with their owners, scores, controls and actions. The ERM report is a selective, interpreted view of that register for a particular reader at a particular time: it highlights what matters, explains what changed and asks for decisions.

Who prepares and approves the ERM report?

The risk function, usually led by the chief risk officer or head of risk, prepares it using inputs from risk owners, compliance and internal audit. The CRO signs it off and presents it to the risk or audit committee, which reviews it and records its decisions in the minutes.

Is there a sample enterprise risk management report template?

Use the ten sections in this guide as the template and the worked sample above as a model: a one-page executive summary, a top-risks table with inherent, residual and prior-quarter scores, a KRI table showing three periods, an action summary with overdue items named, and numbered decisions. Adapt the risk categories and appetite limits to your own organisation.

Explore ActiveERM

See how ActiveERM helps you with governance, risk, compliance, and audit in one platform.