Regulatory watch: track changes, decide, and leave a trail
Delegated acts, guidance, harmonised standards and national implementation — logged by your team in a change register: assess relevance, record the decision, and turn planned actions into scheduled reviews.
Operations → Regulatory Watch is the regulatory-change register. The AI Act isn't finished — delegated acts, Commission guidance, harmonised standards and national implementing laws keep arriving — and an auditor will eventually ask not just "did you notice?" but "what did you decide, and when?".
The register
Each entry is one regulatory development: what it is, its source, the date, and your assessment:
- Relevance — does it touch your systems, your role, your sector?
- Decision — no action needed / monitor / action required, with reasoning recorded.
- Planned actions — when action is required, the plan becomes a review schedule: it lands on the Calendar with an owner and a due date, and its completion drops a dated entry into the dossier trail like any other review.
That last step is the point: a regulatory change that requires action leaves the register and enters the same tracked, audited machinery as the rest of your compliance work — it can't quietly rot in a "we should look at this" list.
Feeding the register
Add entries manually as your team spots developments, or start from the curated regulatory news Veritome surfaces on the dashboard. Aria can summarise a development against your portfolio — ask it what a guidance document means for your registered systems — but the relevance decision is yours, and the register records a human made it.
Related
- Risk register, Art. 9 risks and review schedules — the review mechanics that planned actions reuse.
- Calendar & deadlines — where the resulting reviews surface.