Product update: approval workflow for proposed rule updates
Proposed rule updates now carry a full change summary, an affected-rules list and an approval history, so you can see exactly what would change before anything is activated.
Published 8 July 2026 · 1 min read
Horizon scanning has always held proposed rule updates for review rather than applying them. This release makes the review itself easier to complete and easier to evidence.
What is new
A change summary on every proposal. Each proposed update now states what changed at the source, what the rule would check after the update, and which of your scanned pages or documents matched the rule in the last 90 days. That last part answers the question reviewers ask first: does this actually affect us?
Affected rules list. Where a single source change touches several rules, the proposal groups them so they can be approved together or separately.
Approval history. Approvals, rejections and edits are recorded with the user, the timestamp and any note added at the time. The history is included in report exports.
Consultation flag. Changes originating from a consultation or draft are marked as not yet in force, so they can be reviewed early without being mistaken for a settled requirement.
Notification changes
Regulatory change alerts now include the number of proposals awaiting review, and the weekly digest lists anything that has been waiting for more than seven days.
Unchanged by design
Nothing is applied to your ruleset without approval. Automatic activation remains off unless you explicitly enable it for a specific source, and it can be switched off again at any time.
Coming next
We are working on rule sets for internal marketing standards, so teams can check their own tone and claims rules alongside regulatory requirements.