What the risk would cost you
A loss estimate that goes on the assessment itself, put there by the same colleague who is already weighing how bad it would be and how likely it is. It is not a separate finance exercise bolted on afterwards.
Modules
.legal AI
All AI features →Integrations
See all integrations →Platform & features
Understand the rules
See it in action
All customer stories →Plan your switch
Stay up to date
When more mitigation work lands on your desk than there is budget for, the order has to come from arithmetic: what a risk would cost you if it happened, where that figure lands once a plan is done, and what the plan itself costs. You supply the estimates. The platform holds them together and keeps the reasoning attached.
Unlimited users • Free onboarding and support • No commitment
Risk exposure and mitigation cost
Every autumn Anders Krogh goes into Meridian Nordic's budget round with more mitigation work in front of him than there is budget for. He is the group's security lead, he answers for risk across three countries, and the case he could make used to be a list of risk levels and a request. Two risks sitting at the same level told nobody which one to deal with first. Now each assessment can carry what the risk is estimated to cost if it happens, each plan says what it will cost and where the exposure is expected to land afterwards, and Anders arrives with a difference and a price per plan.
Compare plans, not levels
Two risks at the same level say nothing about which to fix first. The three figures behind each plan do.
The reduction is the point
Exposure now, and where it lands once the work is done. The difference between the two is what you are actually buying.
Stated before the spend
A plan carries its estimated cost and the risk level expected on completion, so what the work is meant to achieve is on the record first.
Your estimates, your arithmetic
Every figure is one you put in. No benchmark, no industry table, no model. The platform adds them up and stores the reasoning.
Risk exposure and mitigation cost
The register does its job. Anders can see what sits above appetite and what does not. The awkward part starts one step later, when he has to choose which of those things gets dealt with this year.
Risk exposure and mitigation cost
The first of the three figures sits where the risk is assessed rather than in a separate financial exercise. Whoever states the consequence level and the probability level can put a figure on the loss at the same time.
Risk exposure and mitigation cost
The other two figures live on the mitigation plan, and the useful one is the distance between them. Exposure now, exposure once the work is done, and the gap that separates the two.
Risk exposure and mitigation cost
This is the part of the job that has no honest answer without figures. Line up the three numbers behind each open plan and the plans stop competing on who asked most persistently.
Risk exposure and mitigation cost
The numbers are entered once, on individual assessments and plans, and they aggregate on their own. Nobody rebuilds the argument in a spreadsheet to answer the question one level up.
Risk exposure and mitigation cost
This is the part we put in writing rather than leave for a demo to find. The platform has no idea what an outage would cost Meridian, and it does not pretend to.
A loss estimate that goes on the assessment itself, put there by the same colleague who is already weighing how bad it would be and how likely it is. It is not a separate finance exercise bolted on afterwards.
A plan says where that estimate is expected to sit once the work is finished. It is the half of the argument nobody could produce before, and it is the half a budget owner asks for first.
The same plan carries an estimated cost, so both halves sit on one object and neither can be put in front of anybody without the other.
A plan also carries the risk level expected once the actions are complete, so the effect is documented before anything is committed rather than reported after.
The three figures aggregate by risk area and then across areas into the management report, so answering upwards does not mean rebuilding the case in a spreadsheet.
Exposure is a field you can leave alone. A risk area can run on its levels only, and where you do use figures they sit alongside the scale rather than replacing it.
Run your information security management and meet NIS2, ISO 27001 and more in one place. The risk work on this page sits beside it.
Explore Information Security ManagementGet access to flexible risk management with multiple areas - and make one report for all of them.
Explore Enterprise Risk Managementcompanies
users
contracts
processing activities
Bech-Bruun
Mikkel Friis Rossa (Partner)
Fenerum
Rasmus Boutrup (Financial Controller)
Lægeforeningen
Michael Berner (Lawyer)
Molecule Consultancy
Nanna Rodian Christensen (HR & Operational Manager)
Plum Safety
Ulrik Dueholm Beckmann (QC, CM og ESG Lead)
Bech-Bruun
Mikkel Friis Rossa (Partner)
Fenerum
Rasmus Boutrup (Financial Controller)
Lægeforeningen
Michael Berner (Lawyer)
Molecule Consultancy
Nanna Rodian Christensen (HR & Operational Manager)
Plum Safety
Ulrik Dueholm Beckmann (QC, CM og ESG Lead)
Novicell
Julie Oxenvad (Legal Consultant)
Min By Media
Tinna Schultz (HR Manager)
DMJX
Kaspar Rochholz (GDPR Coordinator)
Axel Kaufmann ApS
Julie Lundkvist Andreasen (Lawyer and Head of Costumer Service)
NRGi
Mette Mühlendorph (Compliance Specialist)
Novicell
Julie Oxenvad (Legal Consultant)
Min By Media
Tinna Schultz (HR Manager)
DMJX
Kaspar Rochholz (GDPR Coordinator)
Axel Kaufmann ApS
Julie Lundkvist Andreasen (Lawyer and Head of Costumer Service)
NRGi
Mette Mühlendorph (Compliance Specialist)
Every use case is a real piece of compliance work, told the way it actually runs in the platform. Filter by who you are, what you work with, and which frameworks you answer to.
22 use cases
No use cases match that combination yet. Try removing a filter.
By making the plans comparable. Each assessment can carry what you estimate the risk would cost if it happened, and each mitigation plan carries what it is expected to cost together with where the exposure is expected to land once the work is done. Put those next to each other and the comparison makes itself: what a plan takes out, held against what it takes up. A plan that costs little and removes little can end up below one that costs more and removes far more, which is exactly the comparison a risk level cannot make for you.
Your own estimate of what the risk would cost the organisation if it happened. It belongs to the assessment, so it is stated by the person who is already deciding the consequence level and the probability level and writing a justification for both. It is a separate thing from the mitigation plan's figures: the assessment says what the risk could cost you, and the plan says what the exposure would be afterwards and what getting there is expected to cost.
No. Risk exposure is optional, and a risk area can run perfectly well on its levels alone. Plenty will, and that is a legitimate way to work rather than a half-finished setup. Where the figures earn their place is the funding conversation, so a common pattern is to use them in the areas where you have to defend a spend and leave them out of the ones where you do not. How the figures should be expressed in your own environment is worth settling on a demo rather than reading off a page.
Precise enough to compare, and no more than that. What the decision needs is the order of magnitude and the direction: is this risk roughly ten times the size of that one, and does the plan take a lot out or a little. Chasing decimal places on an estimate of something that has not happened is effort spent on false accuracy. Being consistent across your entities matters far more than being exact on any one of them, because consistency is what makes the totals mean anything.
No. That is worth being unambiguous about, because a demo can easily leave the opposite impression. There is no recommendation, no ranking, no scoring of plans against each other and no budget optimiser anywhere in the module. What the platform does is put the exposure now, the exposure expected afterwards and the plan's estimated cost in the same place, keep them next to the assessment they came from, and add them up. The judgement, and the order you fund things in, stays with you.
There is not, and this is the honest centre of the page. Nothing in the platform models what an incident would cost your organisation, and no reference table sits behind the field. Every figure on an assessment and on a plan is one of your own people's estimates, made with a justification attached and a timeline that keeps it. If your first plan is to get better at estimating, the platform is a place to do that in the open rather than a place that does it for you.
Yes. The same three figures aggregate from the individual assessments and plans upwards, by risk area and then across areas into the management report, so the case you built to get a plan approved is the case management reads. That is the reason to be consistent about how you estimate. What the report itself shows, and how it leaves the platform, is covered on our risk reporting page.
Not today, and that is worth knowing before you build a process on it. A plan moves through proposed, approved and completed, and those statuses are a record of the decision rather than a lock on it: someone with access can move a plan along. What the platform does give you is the substance of the decision in front of the decision, because the estimated cost and the expected risk level on completion are on the plan before anyone approves anything. How tightly that step ought to be locked down differs from one organisation to the next, so put it on the list for a demo.
What governance means in practiceIt is not part of every plan. Risk exposure on the assessment, the exposure a plan expects to leave behind, and the price the plan is put at, all came in with Enterprise Risk Management in August 2026, which is part of the Enterprise plan and priced by agreement. The risk assessment that has been in the platform for years is a different product, it stays live, and it has none of these figures and no mitigation plan object to hang them on. So this is a new register rather than a setting you switch on.