Regulatory change management, mapped before Monday.
Watch the federal banking regulators and your charter state, and get a proposed mapping from each moved paragraph to your library, with citations attached.
- CFPB · 12 CFR 1026Reg Z §1026.19 revisedIn Proposal inbox
- FinCEN · 31 CFR XBSA CIP guidance updateMapped
- OCC · Bulletin 2026-13MRM revised guidanceImpact triage
- NCUA · 12 CFR VIIMember disclosures diffMapped
Primary-source radar
The Regulatory Monitor agent reads primary sources from the federal banking regulators and from the state regulator in nine charter states, so a change is caught where it is published instead of weeks later in a newsletter.
- 01Federal coverage is the Federal Register, OCC, FDIC, the Federal Reserve, NCUA, CFPB, FinCEN and Treasury.
- 02State coverage is your charter state where Zovos has a source. Today that is California, Georgia, Illinois, Iowa, Kansas, Missouri, Ohio, Texas and Wisconsin.
- 03The agent reads primary sources such as the Federal Register and eCFR instead of a single third-party feed.
Paragraph-level diff and version hashing
A change arrives as a diff you can act on, in Reg updates (RegUpdates).
- 01Reg updates is both the change feed and the impact-triage queue.
- 02Each version is hashed so you can prove what the text said, and when.
Impact triage into action plans
Impact does not stop at an alert. It routes into the Proposal inbox as suggested mappings and into Tasks as owned work (LinkInbox, tasks).
- 01Suggested mappings wait for a human to accept in the Proposal inbox.
- 02Accepted impact becomes tasks and action plans with owners and dates.
Enforcement radar and tracker
Peer regulator actions are scored against your own controls, so you can fix a gap before an examiner cites it (EnforcementRadar, enftracker).
- 01Enforcement radar scores peer OCC/FDIC/Fed/NCUA actions against your controls.
- 02Enforcement tracker keeps the underlying peer actions.
Launch delta
When you ship a product or change a process, Launch delta surfaces the obligations that just became newly relevant (LaunchDelta).
- 01Obligation diffs come from your own product and process changes as well as from regulators.
Grounded in shipped behaviour.
- 54 frameworks and 754 indexed citations keep every mapped paragraph anchored to its authority.
- The Regulatory Monitor agent reads primary sources from the Federal Register, seven federal agencies and nine charter-state regulators.
- Changes land in Reg updates as a paragraph-level diff, then triage into the Proposal inbox and Tasks.
- Enforcement radar scores peer regulator actions against your own controls.
Counts come from the platform's regulatory corpus, connector registry, and seed template library at release. See the documentation for the current values.
Questions, answered first.
- Where do the updates come from?
- The Regulatory Monitor agent reads primary sources such as the Federal Register and eCFR. You do not have to trust a single third-party feed blindly.
- How do I know what a change affects?
- Reg updates shows the paragraph-level diff and routes the impact into the Proposal inbox as suggested mappings against your library.
- Does a change edit my library automatically?
- No. Proposed mappings wait in the Proposal inbox for a person to accept before anything in your library moves.
- What is Enforcement radar?
- Enforcement radar scores peer regulator actions against your own controls. You can see where you are exposed before an examiner asks about it.
See regulatory change management on your library.
Bring your controls, a policy, and one regulator paragraph that gives you trouble. We target two-week onboarding.