MADISON · REGULATORY CHANGE AGENT
Helping compliance teams see what every rule change touches.
Madison traces each amendment to your policies, procedures and controls, and shows you the gaps. Your owners make every call.
Built for US banks and credit unions.
RUNS ON
- AWS
- Microsoft Azure
- Google Cloud
- NVIDIA
- Optimus
TRY IT
Trace a rule change through a sample bank.
- 01Watching sources
- 02Breaking into obligations
- 03Testing applicability
- 04Tracing coverage
- 05Finding gaps
- 06Drafting recommendations
- 07Recording decisions
Pick a rule change and press Trace the change.
SAMPLE LIBRARY · HARBOR POINT BANK
That’s the whole loop. Want to see it on your own policy library? Book a free GRC audit
SAMPLE RUNHypothetical amendments on sample data. Runs in your browser; nothing is stored.
THE PROBLEM
Months to answer one question: what does this touch?
12 CFR 1026.7 · AMENDED
PUBLIC
- WEEK 1POLICY
SHAREPOINT - WEEK 2PROCEDURE
INTRANET - WEEK 3CONTROL
SPREADSHEET - WEEK 4EMAIL
THREAD - WEEK 5MEETING
NOTES - WEEK 6OWNER
INTERVIEW
ANSWER
?
?
?
NO TRAIL
When an examiner finds a failed control, the same hunt runs in reverse.
HOW MADISON RUNS IT
Seven steps, every rule change.
Madison does the reading, mapping and drafting. Your people keep every decision.
Drag to compare. One amendment at a synthetic $4B bank. Illustrative.
PRICING
One price. Every rule, every user.
One agent for your whole compliance team, priced per year rather than per seat or per rule. It starts from your policy library, so there’s no integration project to fund first.
REGULATORY CHANGE AGENTPricing proposal
$100,000per year
- Every amendment to the rules you rely on, watched
- Every obligation mapped and cited
- Unlimited users
- Set up in your cloud
- Your own model keys
- Full audit trail
- Examiner-ready impact assessments
Lyzr Optimus Micro
Air-gapped, in your data centre
+$50,000
- Ask for the rate card
Forward-deployed engineers
Fitted to your policy library and systems
- See the agent
Control testing agent
Tests every control, every quarter
HOW IT RUNS
Inside your environment. Read-only to your systems.
Your cloudAWS, Azure, Google Cloud or Optimus
Read-onlyNo write-back to core banking
Your keysModel and encryption keys
AuditedWho decided, and when
FAQ
Questions compliance officers and examiners ask.
No. It proposes whether each obligation applies, with the reasoning and the citation. A named person at your bank decides, and that decision is recorded.
Your policy library as it stands today. A folder of documents is enough for a first coverage map. There’s no integration project.
The coverage map starts from your policy library, with no write-back to your core system. Evidence retrieval and control testing, where used, need read-only connectors.
Yes. Every obligation cites the rule text it came from, every mapping cites the policy section or control it points to, and every decision shows who made it, when and why.
It depends on grounding and document quality, so we don’t publish a single accuracy figure. Every mapping cites the rule and your own documents, and a reviewer confirms it before it counts.
No. It stays your system of record. Madison does the reading, mapping and drafting, and feeds the results back in.
GET IN TOUCH
Book a free GRC audit.
Bring your policy library. Leave with your coverage map.
- A coverage map of your library
- Every gap in it
- What your next rule change touches
We reply within one business day.
Booked.
We’ll reply within one business day.