New signups are temporarily closed.Existing customers can still sign in. Contact us to be notified when we reopen.
Skip to main content
Documentation

Ongoing operations

Enterprise Risk Register

The Risk Register is a broader lens than any single framework's obligation checklist: strategic, operational, regulatory, technical, and AI-safety risks, scored on a standard 5x5 likelihood/impact matrix and tracked through to treatment. It sits alongside, not instead of, your framework-specific compliance work. A risk here can optionally link to a registered AI system and to a Compliance Plans task, so mitigation has a real owner and deadline on the Gantt roadmap.

Transcript

The Risk Register is a board-level view: strategic, operational, regulatory, technical, and AI-safety risks, scored on a standard five by five likelihood and impact matrix and tracked through to treatment.

Add a risk and rate its likelihood and impact from one to five each. The score and risk level update live as you pick, so you can see exactly how a risk lands on the heatmap before you save it.

Every open risk lands in its cell on the five by five heatmap, color-coded from low to critical. Click any cell to instantly filter the register table below to just the risks sitting at that exact coordinate.

Choose a treatment strategy, then re-score likelihood and impact after mitigation to record the residual risk. The Risk Reduction Index on the summary compares average inherent to residual score across every mitigated risk, so a board can see the treatment programme is actually working.

Attach an existing Compliance Plans task as the risk's remediation. That proves the risk has a real owner and deadline, and gives you a direct link from the register straight to that task on the Gantt roadmap.

This is a general enterprise register, not a replacement for a system's EU AI Act risk classification, which is a separate, specific regulatory determination under Article 6. The two are complementary: one tells you whether a system's use case triggers legal obligations, the other tells you which risks, across the whole organisation, actually deserve attention first.

Why this is required

A framework's obligation checklist tells you what a regulation requires. It doesn't tell you which of your organisation's risks are actually the biggest, or whether your mitigations are working. A board wants the second question answered, not just the first.

Showing inherent risk next to residual risk (after treatment) is the standard way to demonstrate that a mitigation programme is doing something, not just generating paperwork. The Risk Reduction Index on the register summarises exactly that gap.

What EuroCompliant does

Every risk is scored on two 1-5 scales (likelihood and impact), multiplied into an inherent score from 1 to 25. The same two scales, entered again after treatment, produce a residual score, so the register can show the before/after of a mitigation directly.

The heatmap groups every open, mitigating, or accepted risk into its 5x5 likelihood/impact cell. Closed risks drop out of the heatmap (they're no longer live exposure) but stay in the register's history. Clicking a cell filters the table below to just the risks sitting at that coordinate.

Treatment strategy is one of four standard responses to a scored risk: mitigate, transfer, accept, or avoid.

A risk can optionally link one Compliance Plans task as its remediation: doing so is proof the risk has an assigned owner and a deadline, not just a treatment strategy noted in a text field, and shows up as a direct link from the register straight to that task's Gantt view.

Walking through it

1

Score a risk

Open Risk Register and add a risk. Rate likelihood and impact from 1 to 5 each. The resulting inherent score and risk level update live as you pick.

Open /risks →
2

Record the treatment and residual score

Choose a treatment strategy, and once mitigation is underway, re-score likelihood and impact to reflect the residual risk after treatment.

Open /risks →
3

Link a remediation task

Attach an existing Compliance Plans task to the risk so it has a tracked owner and deadline, visible from both the risk register and the plan's own Gantt view.

Open /risks →

The law

Frequently asked

How is this different from a system's AI Act risk classification?

The AI Act risk classification (Prohibited / High-Risk / Limited / Minimal) is a single regulatory determination for one AI system under Article 6. The Risk Register is a general-purpose 5x5 register that can cover strategic, operational, regulatory, technical, or AI-safety risks across the whole organisation, only some of which are tied to a specific AI system.

What happens to a risk's heatmap cell when I close it?

Closed risks are excluded from the heatmap's counts, since a closed risk no longer represents live exposure, but the risk itself stays in the register with its full history.

Is the Risk Register available on all plans?

It requires the Business plan or higher.

Related guides

Try it on your own systems

Everything in this guide runs in the live product. Start a free trial and follow along with your own data.

Start free trial