1. Regulatory Change Management
  2. Features
  3. Rule Changes
Feature · Rule Changes

Rule Changes

Register a rule publication and carry its implementation decision into the assessment.

OverviewRule Review Queue
Regulatory Change Management · Rule Changes

Rule Review Queue

Approval conditions

New
StatusRevisionAuthoritySource publicationEffective fromParent
Submitted450ATH-370SP-40511 OctASS-54822
Submitted740ATH-567SP-29910 OctASS-27369
Submitted940ATH-417SP-25621 OctASS-78528
Submitted930ATH-106SP-15016 OctASS-64911
Submitted420ATH-722SP-90322 OctASS-87097
6 of 6 records
ATH-370Rule changes 2 · RC-22172
Submitted
Revision450
Source publicationSP-405
Effective from11 Oct
ParentASS-54822
Example screen with sample data

What you can do

Give each change a working home

A new publication reaches the compliance team with an authority, a source reference and an effective date. The Control Owner opens the rule change against the right organization and assessment. That link matters: reviewers need the actual assessment context when they decide whether the proposed implementation is ready. A draft can be prepared without presenting it as an approved plan.

The register separates work still being prepared from changes submitted for review. A rejected change stays visible with its decision history. Completion is recorded after the approved implementation work, so the team can distinguish an accepted plan from a completed one. Operations Overview helps the team monitor the review workload across authorized organizations.

How the work is organized

  • Source. Capture the authority and publication reference beside the organization that must respond.
  • Impact. Use the linked assessment, its business unit and the affected control count to guide the review.
  • Decision. Keep the revision and decision date with the change as it moves through review and completion.

What to agree during setup

Decide who receives publications, who chooses the affected organization and who owns the assessment. Agree how a source publication will be cited so different owners can find the same notice. Define when a revised draft is ready to submit and who may decide on it. These choices make the register useful across teams that hear about the same change at different times.

For a change effective next quarter, start by confirming the organization and the related assessment period. The Control Owner can record the source and estimate affected controls, then ask the Independent Assurance Reviewer to inspect the submitted revision. If the source or impact changes, identify the new revision before treating an earlier decision as current.

Check the handoff on an actual case

Take one rule change from draft through submission. Open its linked assessment and confirm that the organization and business unit describe the intended scope. Ask the reviewer to locate the cited publication and the assessment evidence without a separate email trail. Check that the decision record refers to the revision under review and the linked assessment. If it is returned or rejected, have the owner revise and resubmit. If approved, follow the plan until the status reflects completed work.

Where an operation receipt is recorded, compare its result and expected revision with the decision. Reconcile a failed result before treating the action as finished. This is also a useful rehearsal for changes with the same effective date across different organizations.

What your team sees

  • Rule Change Board — Scan draft, submitted, approved, rejected and completed changes by status.
  • Rule Review Queue — Open submitted changes that need an independent decision.
  • Submitted Rule Changes — Compare upcoming effective dates and linked assessments.

Follow the work through

What it keeps track of

Data model
Rule changes 2
Incoming regulatory rule changes and implementation plans
Assessments 2
Impact and control assessment periods per organization and owner
Organizations 2
Regulatory entities operating the change programme
Review decisions 2
Independent reviewer decisions recorded per source revision
Operation receipts 2
Durable operation receipts for guarded workflow commands

Who uses it

Permissions
Control Owner
Prepares and submits the change.
Independent Assurance Reviewer
Records the decision.
Auditor
Reads the resulting history.

Set up Regulatory Change Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started