FAQ
Answers to the questions we hear most often
Including the ones where the answer is a limitation, and the one about who should not buy this.
Product
- What exactly does Regulens do?
- It monitors Central, state and municipal sources, works out which obligations apply to each of your specific sites, breaks the applicable law into individual obligations with owners and deadlines, and shows you which parts of your organisation each one affects. From there it manages assessment, ownership and evidence. Policy and BRD automation extend this into drafting; Compliance Audit extends it into testing obligations against live ERP and HRMS data.
- Is this only for large manufacturers?
- No. The horizontal domains — corporate, labour, EHS where relevant, data, tax, product standards — apply to any organisation with employees, premises and a registration. A 300-person IT services firm with offices in four states carries a substantial obligation load. What changes by sector is the licensing layer that stacks on top.
- How is this different from a law firm update or a compliance newsletter?
- An update tells you a notification exists. That is roughly eight percent of the effort. The remaining ninety-two percent is deciding which of your sites it applies to, extracting what it requires, working out who acts on it and proving what you did. Regulens does those four things.
- How is this different from a GRC platform?
- GRC platforms manage controls, risks and issues once you know what they are. They generally assume the obligation register already exists and is current. Regulens produces and maintains that register from primary sources including all state variants, and integrates with your GRC platform rather than replacing it.
- How does the platform grow with us over time?
- It starts with intelligence, obligations, impact and reporting — live today. From there, policy and SOP automation and BRD automation add drafting capability, currently in early access. Compliance Audit, open to design partners from 2027, adds continuous testing of obligations against ERP, HRMS and plant data. Each capability builds on the same register and site graph rather than asking you to start again.
Coverage
- Do you really cover all the states?
- All 28 states and 8 union territories are maintained for labour, EHS, licensing and shops and establishments. Depth is greatest where our customers operate — Maharashtra, Karnataka, Tamil Nadu, Gujarat, Telangana, Haryana, Uttar Pradesh and West Bengal are deepest. We will tell you exactly what we hold for your specific states before you buy, including where it is thinner than you would want.
- Do you cover municipal bye-laws?
- For the major municipal corporations, yes — trade licences, fire NOCs and local requirements. Coverage is being extended through 2026. India has thousands of local bodies and we do not claim to cover all of them; we cover where our customers operate and onboard new ones on request.
- What about sector-specific regulators?
- RBI, SEBI, IRDAI, CDSCO, FSSAI, BIS, CPCB, CERC and TRAI are covered in depth. State-level sectoral authorities — drug controllers, pollution control boards, electricity commissions, food safety commissioners — are covered for the states where we have depth.
- How current is the content?
- Sources are polled on schedules tuned per publisher, with median publication-to-alert under 30 minutes for high-priority Central sources and same-day for most state gazettes. Obligation decomposition for a significant new instrument is typically published within five working days, and always after analyst review.
- Do you track court judgments?
- Yes, for decisions that change the operative position on a tracked obligation — Supreme Court and High Court decisions, and significant tribunal orders. This matters more in India than it might appear: several obligations have been materially altered by judgment rather than by notification.
Implementation
- How long does implementation take?
- Essentials: about three weeks to a live scoped register. Professional: eight to ten weeks including site modelling and licence register construction. Enterprise: ten to eighteen weeks depending on site count, licence condition extraction and integrations.
- What do we need to provide?
- Your entity structure, a list of sites with state, headcount, category and process, and access to your licence documents. Plus a working group who can answer questions about how each site actually operates. Most other inputs are imported from systems you already have.
- What is the licence audit and why does it take time?
- We ask each site to produce every licence, consent, registration and NOC it holds, then extract the conditions inside each one and convert them to tracked obligations. For a site with twenty licences this is a few days of careful reading. It is also, consistently, the single highest-value output of the first month — the first pass almost always finds an expired licence or a role named to someone who has left.
- Can we import our existing compliance register?
- Yes, from spreadsheet or from the major GRC platforms. We run a reconciliation showing what you have that we do not, what we have that you do not, and where your wording has drifted from current source text. The state layer is usually where the largest gap appears.
- Can we start with one plant?
- Yes, and most large customers do. A single high-exposure site is a sensible first scope, and expansion is site by site rather than a group-wide commitment on day one.
AI and data
- Where is our data stored?
- In India by default — Mumbai and Hyderabad regions. Enterprise customers can deploy single-tenant or entirely within their own infrastructure, which is what most Compliance Audit design partners choose.
- Do you train models on our data?
- No. Your content is never used to train shared or third-party models. Retrieval runs over your tenant-isolated index, and inference runs under zero-retention terms with our model providers.
- How do you prevent the AI from making things up?
- Retrieval is restricted to a curated corpus, generation is constrained to cited passages, and a separate verification pass checks each claim against its citation before display. Where grounding is insufficient the system declines and shows what it searched. The specific risk we design against is a model answering an Indian question with reasoning from a foreign regime — which reads plausibly and is wrong.
- Who reviews the obligation content?
- 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, and you can challenge any of it.
- What is Regulens’ own role under the DPDP Act?
- We act as Data Processor for personal data you upload or connect. Our processing agreement is aligned to the DPDP Act and Rules, and we commit to intimating you within six hours of confirming a breach so your own CERT-In and DPDP clocks are not consumed by our response time.
Commercial
- How is pricing structured?
- A fixed annual fee driven by locations, states and modules enabled, exclusive of GST. We do not meter queries or charge per API call, because a platform that charges per question discourages people from asking them.
- Is there a trial?
- A three-week scoped pilot rather than a self-serve trial: we model two of your locations, build the obligation register for them, and you assess it against what your team currently believes applies. The gap is usually the whole business case.
- What happens to our data if we leave?
- You export everything you created — assessments, mappings, the site graph, licence records, evidence, interpretations — in structured formats, at any time during the contract and for 90 days after. No charge, no proprietary lock.
- Who is Regulens not right for?
- If you operate one entity, in one state, from one location, with a small headcount and no manufacturing or regulated activity, a well-organised company secretary with a good checklist will serve you better and more cheaply. The economics turn on site count, state count and whether you hold licences, roughly in that order.
Question not answered here? Try the glossary, the security page, or ask us directly — we reply to everything within one business day.
Still deciding whether this is for you?
Send us your entity count, jurisdictions and how regulatory change reaches you today. We will tell you honestly whether a platform is the right answer.