Instead of Bloomberg Regology
Stop renting Bloomberg Regology. Own your regulatory change desk.
We build your version around your regulators, review process and decision makers. We map your authorised Regology exports, bring the records across and run the agreed workflow for you.
Regology Professional lists US$1,700 per user per month with a three-year contract. That is US$20,400 per user a year. Enterprise is quoted separately.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
The recurring bill
The subscription covers intelligence and the work around it
Regology combines a legal-content service with assessment and reporting workflows. Start by separating the sources you need from the decisions and evidence your own team creates. Published plan details checked 6 November 2026.
A price for each Professional user
The published rate is US$1,700 per user per month on a three-year contract. A reviewer and an analyst do different work, so examine who actually needs a paid licence.
A long contractual term
The displayed Professional rate carries a three-year commitment. Check your own renewal and notice terms before planning a switch.
A supplied legal library
Professional includes the Smart Law Library and US federal and state coverage. Decide which sources your business requires and who will maintain that coverage in your version.
Change alerts and impact assessment
Professional includes regulatory change alerts and impact assessments. Your applicability decisions, owners and reasons can live in your own database.
Dashboards and downloadable reports
Reports present the work your team has already recorded. Keep the underlying change, decision and implementation evidence together so your review can follow your own questions.
Enterprise coverage and team workflows
Global jurisdictions, group workflows and broader integrations sit within the Enterprise offering. Enterprise DNA scopes your required sources, team access and connections around the work you need done.
Your own working record
From an incoming notice to evidence a reviewer can follow
Source review
Know what has actually been checked
Each source has an owner, jurisdiction, review interval and recorded check. A changed saved source enters triage for human review.
- check Show sources that have never been checked
- check Compare the latest saved text with the previous capture
- check Keep the capture reference and the person who checked it
- check Set review intervals around your own coverage policy
Impact decisions
Keep the reason beside the change
Record whether the change applies, does not apply or needs monitoring. Keep the source citation and the decision maker attached to the current version.
- check Assign an owner and a review date
- check Leave an unknown effective date visibly unknown
- check Review high-priority changes without an assessment
- check Require a fresh decision when imported facts change
Implementation
A completed action needs current evidence
Turn an applicable decision into named work. Evidence from an earlier version does not complete a revised requirement.
- check Chase overdue actions by owner
- check Keep evidence references with their purpose
- check Show completed work that became stale after a revision
- check Prepare an assessment record and an evidence pack in your brand
Independent review
Make the sign-off explain itself
A different reviewer checks a definitive assessment and the implementation record. The sign-off stays tied to the version reviewed.
- check Keep old decisions when a change is revised
- check Refuse sign-off while required work is incomplete
- check Review retention dates without removing legal holds
- check Ask which sources account for the unassessed workload
Make it yours
Design your own Bloomberg Regology replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Bloomberg Regology. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Bloomberg Regology data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real command results from synthetic demo records. The notices and dates below are examples, not announcements of new laws.
Regulatory Change for Claude Code
Connected to your own database
Which changes still need an impact assessment?
DEMO-001
- Title
- Review privacy retention practice
- Owner
- Morgan
- Review due
- 2026-11-01
- Priority
- high
DEMO-003
- Title
- Triage business notice
- Owner
- Morgan
- Review due
- 2026-11-09
- Priority
- high
| External id | Title | Owner | Review due | Priority |
|---|---|---|---|---|
| DEMO-001 | Review privacy retention practice | Morgan | 2026-11-01 | high |
| DEMO-003 | Triage business notice | Morgan | 2026-11-09 | high |
Ask it anything
Ten questions to ask across your own records
These queries run today. The examples use synthetic records, and we have not tested the same questions in a configured Regology account.
Switching
How to switch from Bloomberg Regology
A clean mapped register can move in a day, while the full switch depends on your source coverage, history and contract.
- 1
Export your records
Ask Bloomberg Regology which authorised exports your account allows. The vendor documents CSV interchange and report downloads, but not a standard export layout. Prioritise the change register and the source, assessment, action and evidence records you need. Check whether original documents and historical approvals are included, since they may need separate migration and rights review.
- 2
Map and test the import
The replacement accepts CSV with an explicit mapping from your export headings to its records. Have the mapping prepared, then run the import in test mode first so it does not save changes. Review the test results before loading anything. If you have Enterprise DNA run the migration, they handle this mapping and test-run process with you.
- 3
Review the import results
Check the results for rows that were rejected, duplicates and headings that did not map as expected. Reconcile the imported change register against your Bloomberg Regology records and correct the mapping or source data where needed. Confirm that important fields, such as applicability decisions, owners, actions and evidence references, came across as intended before relying on the new records.
- 4
Run both systems briefly
Keep Bloomberg Regology available while you work through a complete review cycle in the new desk. Compare the official sources you check, incoming changes, impact decisions, assigned actions and evidence. The replacement does not provide a global legal-content feed, so confirm that your source coverage and operating process meet your needs before you depend on it.
- 5
Switch off Bloomberg Regology
Once the review cycle is complete and you have reconciled the records you chose to migrate, arrange to stop using Bloomberg Regology under your contract. Keep any authorised exports and backups private, and test that you can recover your new database before cutover. Do not assume that a clean import alone confirms source coverage or that every historical record has been carried across.
Where the real effort goes
The import itself is usually not the main effort. Most work goes into mapping your own fields and rules, checking the results, and deciding how much history to bring. Historical approvals, original documents and licensed content need separate migration and rights checks. If Enterprise DNA runs the replacement for you, they handle the mapping and test-run as part of the agreed migration.
Not ready for a call?
Get your Bloomberg Regology switch plan by email
We will send you the step-by-step plan for moving your business off Bloomberg Regology, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Bloomberg Regology switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Do it yourself, have it customised, or have it run for you
Open source
Do it yourself
Free, open source
- 1 Clone the repo, run npm install and npm test
- 2 Run npm run demo and inspect the synthetic records with Claude Code, Codex, OpenCode or Cursor
- 3 Map your authorised Regology CSV headings and test the import before saving
- 4 Configure your sources, backups and access, then run a complete review cycle
Built around your business
We customise it
One setup fee, then a retainer for ongoing work
- check Your sources, review rules, business units and required fields
- check Your authorised Regology records mapped, imported and reconciled
- check A web front end and different technology stack where your team needs them
- check Your source monitoring and business connections scoped and built
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed with controlled access and tested backups
- check Weekly triage, action reviews and evidence packs prepared
- check Source connections and review routines maintained to the agreed scope
- check Run through Omni by Enterprise DNA beside the rest of your business
Questions
Instead of Bloomberg Regology, answered
Does this replace the regulatory intelligence service as well? expand_more
The free version manages your recorded sources, changes, assessments, actions and evidence. It compares saved source text that an operator supplies. Enterprise DNA can build the monitoring and connections your business needs into your version. Agree the required coverage and verify it through a complete review cycle before replacing your existing service.
Can you bring our Regology history across? expand_more
Regology documents report downloads and CSV interchange, but its public pages do not specify one fixed export layout. We inspect your authorised export, map the headings and reconcile the imported change register. Historical approvals, original documents and licensed content need a separate migration and rights check. The free version includes the same mapping and test-run process.
What happens when a requirement changes after sign-off? expand_more
Revised imported facts create a new version. Earlier decisions and sign-offs remain in history, while the current version requires a fresh assessment and current evidence. A different reviewer must sign it off after the implementation work is complete.
Does a clean check prove we comply with the law? expand_more
No. Checks identify configured record gaps, overdue reviews and evidence that needs attention. People determine applicable obligations and verify the originals. Privacy checks cite New Zealand and Australian guidance, and local workflow rules are identified separately. Your version is built around the controls your responsible reviewer agrees.
How does paying Enterprise DNA work? expand_more
There are three routes: run the free version yourself, have Enterprise DNA customise it, or have us run it through Omni by Enterprise DNA. Our work starts with one setup fee, then a retainer. We agree your migration, source coverage and operating scope before building your version.
Review the subscription and the work you need
Spend 30 minutes with Sam. Bring your Regology renewal, the sources your team watches and one change you recently assessed. We will work through the records to bring across, the coverage to keep and what your own version needs.
Regulatory Change for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Bloomberg Regology?
Get your version built