Regulatory intelligence model
The set of linked data fields a regulatory intelligence platform captures for every obligation: jurisdiction, industry, sub-industry, activity, authority, authority type, regulation, guidance, controls and enforcement actions.
Overview
A modern regulatory intelligence product needs more than a library of documents. It needs structured metadata that lets an organisation ask precise questions and get precise answers.
The core fields are jurisdiction, industry, sub-industry, activity, regulatory authority, authority type, regulation, guidance, controls and enforcement actions. Together they let a platform scope obligations to the exact activities a business performs, in the exact places it performs them.
It connects most directly to Regulatory relationship chain, Jurisdiction, Industry, Activity and Authority type.
Check the official sources below for legal scope, applicable dates and exceptions. This entry is an explanatory reference, not legal advice.
Why it matters
Structured metadata is what turns a pile of regulatory text into answers: which rules apply, who enforces them and which controls cover them.
Who it affects
Product, data and compliance teams designing or evaluating regulatory intelligence and GRC systems.
Where it sits
Ten linked steps connect where you operate to the proof that you complied.
- 01Jurisdiction
- 02Industry
- 03Activity
- 04Authority
- 05Regulation
- 06Requirement
- 07Guidance
- 08Control
- 09Evidence
- 10Enforcement
Connections
The terms most closely tied to Regulatory intelligence model. Select one to open it.
What to do about it
- 1Map where your obligations come from.
- 2Link each one to the controls and evidence behind it.
- 3Review the map whenever the business or the rules change.
From requirement to evidence.
Regulation Layer’s graph is built on this model, and every field is available through the API and the hosted MCP server.
Request early access →