Platform · Regulatory change management
Only the rule changes that touch you, sent to the person who owns the requirement.
Regulatory change management collects rules, proposed rules, guidance and enforcement actions from the agencies that issue them, every day. The ones that fit your business are reviewed by a person, then routed to the requirement they affect in your inventory, so the owner sees what changed and what it means for them.
The problem it removes
A newsletter is not a change process
- Alert feeds send you everything, so the one proposed rule that matters to your product sits between forty that don't.
- Even when someone spots a relevant change, nothing ties it to the requirement, the policy or the control it affects.
- Examiners ask how you knew about a change and what you did about it. An inbox rarely answers either question.
What you see
A short list of changes, each tied to a requirement
Each item names its source and date, whether it's final or proposed, why it fits your profile and which requirement it touches. When a change affects a requirement you already carry, a proposed finding opens for you to accept or decline.
| Date | Change | Stage | Affects | Next step |
|---|---|---|---|---|
| 2026-09-16 | Amendment to funds-transfer recordkeeping threshold | Proposed | Travel rule records | Owner notified, comment period open |
| 2026-09-12 | Interpretive guidance on overdraft fee disclosures | Final | Account disclosures | Proposed finding opened |
| 2026-09-10 | Consent order against a payments firm for monitoring gaps | Enforcement | Transaction monitoring | Noted for your next test |
Illustrative example with invented items. Each change carries its source and the requirement it was routed to.
How it works
Collect, match, review, route
- Collect. Rules, rulemakings, guidance and enforcement actions are taken from the issuing agencies every day, not from a reseller's summary.
- Match. Written rules match each new or proposed rule to your business profile and to the requirements in your regulatory inventory. AI may draft a plain-English summary of what changed; it doesn't decide whether a change applies to you.
- Review. A practitioner reviews each match before it reaches you, and drops the ones that don't hold up.
- Route. The change goes to the owner of the requirement it affects. If it changes something you already have to do, a proposed finding opens, and it becomes work only when you accept it.
This is continuous regulatory monitoring: it watches the rules. Your controls are tested separately, on the schedule you set, through automated control testing.
Guardrails
What it will never do
- It doesn't watch your own controls. It monitors regulation, and tells you when a rule you depend on moves.
- It doesn't try to win on volume. The measure is whether the changes that reach you're the right ones, not how many sources sit behind them.
- It doesn't send you a change no one has reviewed. Every match is checked by a person first.
Where it shows up
The work this part does for you
Plain English
What this is, and how anyone does it
Reference articles from our library, cited to the published rules and standards. No sales copy.
- ReferenceRegulatory Change Management: Definition, Process and Supervisory ExpectationsIdentifying new and amended rules, assessing applicability, analysing impact on policies and controls, implementing and documenting the change, and where the CFPB, OCC and FFIEC expect it.
- CMSCompliance Management System (CMS): The CFPB FrameworkWhat a CMS is under the CFPB framework: board and management oversight plus a compliance program of policies, training, monitoring and audit, and consumer complaint response. How examiners assess it and how to build one.
Connected parts
What it works with
Talk to a practitioner
Book a 15-minute chat with our founder.
A real conversation with a senior compliance leader, to see if there's a fit. Not a sales call, not a demo, no pressure.