Regulatory Alerts

A scannable, relevance-scored feed of new publications from European and national supervisory bodies, so you can see what has changed and hand the items that matter on for assessment.

The sidebar calls this screen Regulatory Alerts; the page header calls it Regulatory Intelligence. Both names describe the same thing: an inbox of regulatory updates collected by a daily background scan. Each entry — an alert — carries the feed it came from, a relevance percentage, a review tag, a short excerpt, the publication date, a link out to the original document, and a link into the assessment workflow described in Regulatory Changes. Nothing is created or edited here; the screen exists so you can triage quickly and decide what deserves a proper look.

This screen needs a licence flag

Regulatory Alerts is a premium feature, gated by the REGULATORY_INTELLIGENCE flag. If your licence does not include it, the route shows a locked panel instead of the feed: a padlock icon, a Premium feature badge, a short description of what the feature does, three ticked bullets naming what it adds (daily scans, relevance scoring, a prioritised alerts feed), the line Available on the Professional plan and above., and an Upgrade your plan button that opens your licence page in Settings. That panel means the feature is switched off, not that something is broken.

Who uses it

Reading the feed needs the regulatory:read permission, which every standard role holds. There is nothing to edit here, so all four roles see the same screen. The roles only pull apart on the assessment screen that Assess change opens, where recording a decision needs regulatory:write.

What's on this screen

The page opens straight onto the feed — there is no create button, because you do not author alerts. Working down the capture:

Opening the feed and getting your bearings

Regulatory Alerts sits in the Compliance group of the left menu, beside the assessment screen it feeds. Note the neighbouring groups too — most of what you do with an alert continues in one of them.

  1. Open the Compliance group in the left menu and select Regulatory Alerts. The feed loads with the summary strip, the filter row, and the most recent alerts underneath.
  2. Note the Risks group directly above. When an alert turns out to affect your organisation, this is usually where it ends up — as an entry in the risk register.
  3. Note Privacy & Whistleblowing further down. Data-protection material from sources such as the EDPB and GDPRhub is common in the feed, and the follow-up work lands in GDPR.
  4. The ? button in the top bar opens the help panel, a slide-in panel with help topics for the page you are on and a search box.
  5. The open-book button beside it opens this guide at the matching chapter if you need a reminder of how the feed works.
The Regulatory Alerts feed — summary strip, filter row, and most-recent-first alert cards — /compliance/regulatory.
The Regulatory Alerts feed — summary strip, filter row, and most-recent-first alert cards — /compliance/regulatory.

Triaging a single alert

Each card is built to be read in a few seconds. Work across the badge row first.

  1. Read the feed name and the Relevance badge. The colour follows the score: red at 70% and above, amber from 40% to 69%, green below 40%.
  2. Check the review tag. Pending review means nobody has assessed this change yet; a green Reviewed tag with a tick means someone already has.
  3. Read the title and the two-line excerpt to judge whether it touches your obligations, then check the Published date underneath it. When the feed gave no date, the line reads Published: Date unknown.
  4. Select View source to open the regulator's own document in a new browser tab when you need the full text. The link only appears when the feed supplied a web address.
  5. Select Assess change to move to Regulatory Changes, where the impact and the decision are recorded. The detail window for that change opens straight away, on top of the change-tracking table. Close it and you are left on the table, with the full list of changes.
Excerpts come from the feed

The excerpt is the summary the source publishes, tidied up for display. On some feeds that is a clean abstract; on others it is little more than an identifier. Where nothing useful survives the tidy-up, the card shows no excerpt at all — only the title and the date. A thin or missing excerpt does not mean the alert is unimportant, so open the source document before you judge it.

Narrowing the feed

A busy feed runs to hundreds of items. The four filters combine, and changing any of them returns you to page one.

  1. Type into Search alerts... to match on the title and the summary text of the updates. The match ignores upper and lower case, and the list refreshes as you type.
  2. Pick a feed from the Source dropdown. The options are built from the data: every feed name already stored on an alert, plus every feed an administrator has registered and enabled. Below All sources you therefore see the feeds your tenant actually scans, in alphabetical order.
  3. Set From and To dates to bound the feed by publication date. Either one works on its own, and both ends are inclusive.
  4. Select Clear filters — it appears once any filter is set — to reset all four fields and return to the full feed.
  5. Use Previous and Next below the list to move through the results twenty at a time. The page number between them tells you how far in you are.

When the list is empty

The feed area tells two kinds of empty apart. If your filters match nothing, it shows No alerts match your filters with a document icon, a note asking you to adjust or clear them, and a Clear filters button that resets all four fields. The Total alerts card still shows the full count, which confirms the feed itself is there.

If nothing has been ingested at all, the area shows No regulatory alerts yet with a clock icon and a note that the scan runs daily and the first scan may not have run yet. There is nothing to clear on a newly provisioned tenant — alerts appear once the first scan completes.

If the feed fails to load rather than coming back empty, a red panel headed Could not load regulatory alerts appears with a Retry button. Retry first; if it keeps failing, see Getting help.

The AI assist

The feed itself has no AI action to run — the round violet button in the bottom-right corner of the capture is the app-wide assistant described in The screen layout, not a feature of this screen. It is worth being precise about the relevance percentage too. It is calculated when the daily scan ingests each item, by matching the item's text against the frameworks and sectors recorded in your organisation profile — 30 points per matching framework, 20 per matching sector, and 10 more if the item was published in the last 30 days, capped at 100. That is keyword matching, not a model's judgement, even though the locked upgrade panel describes it as AI relevance scoring. Treat it as a triage hint: a high score means "read this one first", and a low score never means "ignore this". The AI-assisted triage and suggested-action features live on the assessment screen in Regulatory Changes, and there, as everywhere in Aegis, a person reviews the suggestion and decides. Aegis never assesses or closes a regulatory change on its own.

One consequence worth knowing: if someone runs an impact analysis on a change, the score stored on that record is replaced by the overall relevance the analysis produced, so the percentage you see in the feed may be an analysed figure rather than the scan's original one. A score set by a person outranks both. Later scans respect that order: the daily keyword score never overwrites an analysed or hand-set figure, and an impact analysis never overwrites a hand-set one.

One thing does happen automatically. When the scan ingests a new change scoring 50 or above, it sends a regulatory-update notification to the users subscribed to that type — in-app, and by email, Slack or Teams where those channels are enabled. A single change produces one alert naming it; a large batch collapses into one summary message so nobody is flooded.

Tips and limits

Where this connects