Platform
One connected model, from the regulator’s clause to the record that proves you complied
Architecture
Five layers, and everything above depends on the layer below
The reason obligation decomposition and the organisational graph get so much attention on this site is that nothing above them works without them.
- 05Sources140+ regulators, central banks, standard setters and official journals, polled continuously with change detection on amended documents.
- 04Regulatory recordNormalised instruments with stable clause anchors, classification, lifecycle stage and extracted dates.
- 03Obligation registerAtomic obligations with actor, action, condition, threshold and deadline — each citing the clause it derives from.
- 02Organisational graphEntities, divisions, products, processes, systems, controls, policies and third parties, with the relationships between them.
- 01Work and evidenceAssessments, gaps, remediation, approvals, attestations and, through Compliance Audit, test results — all written to an immutable trail.
How it builds up
Know, act, prove
Most customers start with the modules available today and stop there. The modules that follow reuse everything already built, rather than asking you to model your organisation again.
Know and assess
Find every Central, state and municipal obligation that applies to each of your sites, break it into atomic obligations, and understand precisely which division, plant and person is affected.
- Continuous monitoring of 780+ Central and state authorities
- Applicability scoping against your entities, sites, states and licences
- Obligation decomposition with section-level traceability
- Impact analysis down to site, function, process and system
- Automated insight digests and board-ready reporting
Translate into action
Turn an obligation into the artefacts a compliance or change programme actually needs: updated SOPs and policies, and complete business requirements documents.
- Policy impact mapping — which SOP clauses a notification breaks
- AI-assisted drafting and redlining with section-level citations
- Full policy lifecycle: draft, review, approve, attest, version
- End-to-end BRD generation from obligation to acceptance criteria
- Two-way sync with Jira, Azure DevOps and ServiceNow
Prove compliance continuously
Connect to ERP, HRMS and plant systems so the platform can test whether you actually comply — continuously, and against any new rule you point at it.
- Read-only connectors into ERP, payroll, plant and transaction systems
- Rules compiled into executable tests over real records
- Continuous control monitoring with exception workflow
- "Am I compliant with this new rule?" answered against live data
- Immutable evidence trail for inspectors and internal audit
Modules
Every module in one place
Regulatory Intelligence
Generally availableRegulens monitors Central, state and municipal sources continuously, classifies what it finds, and scopes each item against your entities, sites, states and licences — so your team reads the twelve things that matter instead of the three hundred that do not.
Obligations Library
Generally availableA statute is not a unit of work. Regulens decomposes each Act, its Rules, state amendments and notifications into atomic obligations — a single requirement, with an actor, an action, a condition and a deadline — each anchored to the exact provision it came from.
Impact Analysis
Generally availableRegulens holds a model of your organisation — entities, sites, states, functions, processes, systems, controls, policies and vendors — and propagates each obligation change across it, so impact is computed rather than guessed in a workshop.
4 weeks to 4 days
typical impact assessment cycle
2.7x
more downstream impacts identified vs. workshop baseline
Insights & Reporting
Generally availableAutomated narrative insight, horizon dashboards and audit-ready reporting generated from the same records your team works in — including evidence supporting the Section 134(5) directors’ responsibility statement.
2 days to 20 min
to assemble a monthly compliance pack
100%
of reported figures traceable to a source record
Policy Automation
Early accessMap every SOP and policy clause to the obligations it discharges, so when a rule changes you know which paragraph of which document is now wrong — and get a drafted redline to fix it.
9 weeks to 12 days
median SOP update cycle in early access
100%
of clauses traceable to an obligation
BRD Automation
Early accessGenerate a complete business requirements document from an obligation set — scope, current and target state, functional and non-functional requirements, data requirements, acceptance criteria and traceability matrix — then push it straight into delivery.
4 weeks to 3 days
to a reviewable first-draft BRD
100%
requirement-to-provision traceability from day one
Compliance Audit
Design partnerConnect Regulens to your ERP, HRMS and plant systems and compile obligations into executable tests, so compliance is measured against real data continuously rather than sampled once a year.
Regulens Copilot
Generally availableAsk a question in plain language and get a cited answer drawn from the Central and state law that applies to you, the obligations derived from it, your policies and controls and, where connected, your transaction data.
94%
of answers rated correct in blind expert review
0
uncited factual claims permitted in a response
Design principles
What we optimise for
Primary sources, not a summary of a newsletter
We read the gazette, not a summary of a summary. Every obligation carries a citation anchor to the section it came from, and that anchor survives amendment.
Scoped to your sites, not your sector
Generic sector feeds tell a Bengaluru IT firm about Maharashtra factory rules it will never meet. Regulens scopes against your entities, sites, states and licences and shows its reasoning.
The state layer is not an afterthought
All 28 states and 8 union territories are maintained as separate variants — thresholds, forms, return dates — because a Central rule and a state rule are frequently not the same obligation.
Obligations as the unit of work
Decomposition into atomic, testable obligations is what makes control mapping, policy linkage and automated testing possible. It is the hardest part and it is the foundation.
AI that refuses rather than invents
In this domain a confident wrong answer is a liability — particularly one built on reasoning imported from a legal system that does not apply here. Every claim is cited and verified against its source.
Built for the inspector at the gate
Immutable audit trails, evidence packs assembled by obligation, and a defensible record of who knew what and when — because that is what the conversation is eventually about, and because personal liability makes it personal.
Start with the layer you are missing
Most teams already have a GRC platform and a feed. What they lack is the obligation register and the organisational model that make both of those useful. That is a six-to-eight week piece of work, and we will scope it honestly.