Generally available
Regulations broken into things you can actually test
Obligations Library
- 69,000+
- obligations in the shared library
- 38%
- average control duplication removed
- 100%
- of obligations carry a source citation
You cannot assign, control or test "the Factories Act". You can assign, control and test "maintain the register of adult workers in Form 12 and produce it on inspection".
The problem
What this module exists to fix
Rules and work are different shapes
Programmes fail because a lengthy Act is treated as a single line item on a plan. The real unit of compliance is the individual obligation, and most organisations have never written theirs down.
Obligation registers rot
Teams that do build a register maintain it in a spreadsheet that drifts from the source text within two quarters. There is no link back to the section, so no way to know what an amendment broke.
The same requirement appears across states
Registration, return filing and record-keeping obligations recur across Central Acts and dozens of state variants. Without deduplication you build one control per state where a shared design would do, and audit each one separately.
Capabilities
What it does
Section-level decomposition
Each Act and its Rules are parsed into obligations with a normalised structure: obligated party, required action, trigger condition, threshold, frequency, deadline, prescribed form and evidence expectation. Every field carries a citation anchor back to the source section.
State variant tracking
Obligations expressing the same underlying requirement across states are held as one family with the state-specific parameters preserved — different thresholds, different forms, different return dates — rather than flattened into a lowest-common-denominator obligation.
Control mapping
Link obligations to your existing control library, whether it lives in Regulens, Archer, ServiceNow IRM, or a spreadsheet. Coverage gaps and orphaned controls both become visible.
Versioning with carry-forward
When the source section changes, the obligation forks. Prior assessments, control links and evidence stay attached to the old version and are proposed for carry-forward, with the delta highlighted for review.
Taxonomy that matches your world
Ships with an eight-domain compliance taxonomy covering corporate & secretarial, labour & employment, EHS & environment, data & cyber, tax & GST, product standards, sectoral licensing and competition & consumer — extensible with your own risk taxonomy.
Regulatory obligation API
Everything in the library is available over a REST and GraphQL API, so obligations can drive your own workflow, data quality or testing systems.
How it works
Step by step
- 01
Parse
The Act, Rules and any state amendment are segmented into provisions with stable anchors that survive republication.
- 02
Extract
Each normative provision becomes a candidate obligation with structured attributes and a confidence score.
- 03
Review
Regulens analysts and your subject-matter experts confirm, merge or reject candidates. Nothing enters your register unreviewed unless you choose that.
- 04
Cluster
Equivalent obligations across states are grouped into families with a canonical statement and the state deltas preserved.
- 05
Map
Obligations are linked to controls, SOPs, processes and owners — the connective tissue everything downstream relies on.
Questions
The things people actually ask
Including the ones where the answer is a limitation.
- Is the library shared or tenant-specific?
- Both. The canonical obligation set derived from public instruments is shared and continuously improved. Your scoping, control mappings, assessments and any obligations you author yourself are strictly tenant-isolated and never contribute to the shared library.
- Can we import our existing compliance register?
- Yes. We import from spreadsheet, Archer, ServiceNow, MetricStream and similar tools, then run a reconciliation that shows what you have that we do not, what we have that you do not, and where your wording has drifted from the current source text. The state layer is usually where the largest gap appears.
- Who validates the decomposition?
- Every obligation in the shared library is reviewed by a qualified analyst — company secretaries, lawyers, EHS specialists and tax practitioners — before publication. Confidence scores and reviewer identity are visible on each record.
See Obligations Library against your own footprint
A two-week scoped pilot on your real entities and jurisdictions. You compare the output against what your team found in the same period.