Continuous monitoring
A scheduled recheck once a year means the company learns about a supplier’s bankruptcy six months late. Continuous monitoring cuts this to days: a registry event turns into an alert, and a critical alert creates an unscheduled check on its own.
Plan Standard plan and above, limited by the number of subjects on monitoring.
What is inside
- Fifteen event types: liquidation, bankruptcy, change of director and founders, tax debt
- New court cases and enforcement proceedings, sanctions lists, unreliable supplier registry
- Internal events: expired verdict or document, revoked consent, new relation with an employee
- Alert severity: informational, warning, critical
- A critical alert creates an unscheduled check automatically
- Per-subject sensitivity rules, so alerts do not turn into noise
- Bulk monitoring setup from the registry and removal with a reason
- Notifications in the interface, by email and in Telegram, a webhook to external systems
Boundaries
The plan limit counts subjects on monitoring, not events. When the limit is reached, new subjects cannot be added, while those already monitored continue to be tracked.
Frequent questions
Where do events come from?
From change subscriptions at external sources that support them, from periodic polling of the rest, and from internal events of the product itself.
What if an alert is false?
The specialist closes it with a reason. Sensitivity rules can be set for the subject so that minor events do not distract.
Who learns about a critical event?
The responsible specialists through the chosen channel: in the interface right away, by email or in Telegram, in a daily digest. External systems receive a webhook.
Use cases with this feature
Other features
Shall we bring order to your checks?
We will show the dossier, a check, a verdict and monitoring on a demo environment, review your regulations and calculate a pricing plan for your actual volume.