Observations (Enterprise)
Report what you noticed from wherever you noticed it, through a public link with no login and a form built for a phone. Nothing to install, and no category to get right before you can send it.
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
One public link with no login, so any colleague can report what they spotted from a phone in half a minute. It lands in an inbox with an owner, where a person decides whether it becomes a risk scenario.
Unlimited users • Free onboarding and support • No commitment
Risk observations
A technician on a service round notices that only one of three pumps in a technical room is still running. She has no login to Meridian's compliance platform and no reason to want one, so she opens a link on her phone, writes down what she saw and gets on with the round. Meridian Nordic is an energy and utilities group, 850 people across Denmark, Sweden and Germany, with NIS2 to answer to and a certified information security management system to keep, and Anders Krogh is the CISO who used to be the only route into its risk register. Now the register starts with her, and the review starts with him.
Half a minute, no login
A colleague opens a public link on their phone, writes what they saw and is done. No account, nothing to install.
One link you can print
The link does not expire, so the same one can sit on the intranet, in onboarding material and on a sign in the building.
A name on every report
The reporter gives name and email, so whoever reviews it can go back and ask what they actually saw.
Closing it counts
Not everything needs to become a risk. A person reviews each observation, and closing one is a valid outcome on the record.
Risk observations
Most of what an organisation needs to know about its own risk is noticed by somebody who has no reason to open a compliance platform. It gets mentioned at a handover, and then the day moves on.
Risk observations
The link is public, there is no login in front of it, and the form is deliberately short. This is also the second place in the platform where somebody without a seat can do useful work.
Risk observations
The link is permanent. That sounds like a small detail until you have tried to keep a temporary one alive across three countries and a shift pattern.
Risk observations
The person reporting states their name and email. That has an obvious upside, and one thing we would rather be blunt about than leave for you to discover.
Risk observations
Everything reported lands in an inbox with an owner. From there it goes one of two ways, and both of them are a result.
Risk observations
Three things that are easy to assume in our favour, so we will say them ourselves.
Report what you noticed from wherever you noticed it, through a public link with no login and a form built for a phone. Nothing to install, and no category to get right before you can send it.
One shareable link that does not expire, so you put it up once instead of replacing it later. Print it where the work happens, not where the risk work happens.
Name and email come with every observation, so a review can start with a question to the person who filed it. It is not an anonymous hotline, and you should know that before the link goes up.
Everything reported lands in one place, where a person reviews it rather than a rule sorting it. Nothing reaches the risk register before somebody has read it.
Convert a relevant observation into a risk scenario in one step, with the person responsible for the area notified automatically. From there it follows the normal assessment flow.
Not every observation belongs in the register. Closing one is a valid outcome that stays on the record, and it is what keeps the register worth reading.
Run your information security management and meet NIS2, ISO 27001 and more in one place. The risk work an observation feeds into sits alongside it, not inside 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.
No. Observations come in through a public link with no login, and the form is deliberately short and built for a phone. That matters most for the people furthest from a desk, because they are usually the ones who notice something first and the least likely to have a seat in the platform. Nothing has to be installed, and there is no password to keep track of.
Run awareness training that reaches every colleagueNo, and that is worth being clear about before you put the link on a sign. The person reporting states their name and email, so every observation is attributed. The upside is real: whoever reviews it can go back to the person and ask what they actually saw, which is usually the difference between a usable observation and a guess. The consequence is just as real, so we will say it plainly. This is not an anonymous channel and it is not a whistleblower scheme, and it should not be introduced to your colleagues as either.
The link is permanent, so it does not expire. That is the point of it: one link can sit on the intranet, in onboarding material and on a printed sign for years without anybody reissuing it. Whether a link can be switched off again is not something we have documented, so put that question to us on a demo instead of reading an answer into this page. What we can say is where the control sits today. Because there is no login in front of the form, the review step in the inbox is what decides what enters your risk register, and a person does that review.
Not at the moment, and it is better you hear that here than assume it. There is no external subscription and no feed bringing advisories into the platform. What works instead is the same link: somebody in your organisation reads an advisory, decides it is relevant to you, and files it as an observation like any other. It then goes through the same review as everything else, which also means somebody has judged that it applies to your estate rather than to the sector in general.
It lands in an inbox with an owner, and a person reviews it. From there it goes one of two ways. If it is worth acting on, it converts into a risk scenario in one step and the person responsible for the relevant area is notified automatically, after which it follows the normal assessment flow with consequence, probability and a justification on both. If it is not, you close it. Both are outcomes, and both stay on the record.
No, and that is deliberate. An observation can be filed independently of risk area, and consequence and probability can be left empty. A technician who notices something on a service round should not have to learn your risk model first, and asking them to would cost you the observation. Placing it in the right area and putting numbers on it is the job of the person reviewing the inbox, and they have the whole model in front of them.
What a risk assessment involvesNot in a way we would build a process on today, and it is better you hear it here than find out later. Access decides what somebody can reach in the platform, but the step from an observation to a risk scenario is not gated by role. Where that line should sit is a question about your organisation rather than about the product, so bring it to a demo.
No, and the two routes are cut on direction rather than on mechanics. Observations point inwards and nobody asked for them: a public link with no login that anybody in your organisation can use to report what they noticed, landing in a risk inbox. The audit engine points outwards: a questionnaire you have sent about a named activity or supplier, answered by the person you sent it to, who does not become a user either. They are two different features, so ask about them separately, but between them they cover most of the people who have to do something in your compliance work without a seat.
What due diligence on a supplier involvesIt is a purchase. Observations belong to Enterprise Risk Management, and both arrived in August 2026. Enterprise Risk Management is part of the Enterprise plan, and what it costs for your setup is agreed with you rather than a line on a page, so bring it to a demo.
No, and that boundary is worth drawing hard. The platform receives what a person files. It does not scan your services, it does not watch anything, and it does not raise something on its own, so it is not a SIEM and should not be bought as one. What it gives you is somewhere for a human observation to land, a review step, and a documented route from a report to an assessed risk.