IRDAI extended the deadline for comments on its proposed Public Insurance Registry on September 30, moving the last date from that day to Saturday October 17, 2026. The stated reason was to facilitate comprehensive participation, wider industry deliberation and detailed submissions from all stakeholder groups, and all other terms of the consultation paper are unchanged. The paper itself was released on September 1, describing the registry as a foundational, population-scale, interoperable and non-exclusionary digital public infrastructure for insurance, intended to let insurers, distributors and other participants discover, verify and exchange insurance information in a consistent way. Submissions must use the prescribed Excel template, either through the designated portal at iib.gov.in/pir or by email to the address given in the release. The regulator has specifically asked stakeholders to comment on the user stories in Section 8 and the consultation questions in Section 15, which is the part of the document most likely to decide the outcome.
Context: what the registry is meant to be, and why the sections named are the ones that matter
The registry is proposed as a regulator-promoted market infrastructure institution, which puts it in a different category from the insurer-backed platforms the same consultation paper contemplates, where at least eleven insurers would establish a not-for-profit entity such as Bima Sugam. The relationship between the two is the design decision that matters: the chairman of the regulator has said the principle is protocols rather than platforms, and that the registry should support multiple customer-facing platforms rather than become the only one. If the registry becomes a single front door, it is a different proposition from a registry that sits behind competing front doors, and the section of the paper that sets out who can query it and on what terms is where a stakeholder can affect that. The named sections are a signal in themselves. User stories describe what the registry is meant to let people do, and questions in a consultation are the regulator asking what it has not thought of. Commenting on the user stories is a way of changing the specification; commenting on the summary is not.
Implication: what an extension does and does not tell you
- It is evidence that the consultation is live and contested, not delayed. An extension of seventeen days on the stated ground of detailed submissions from all stakeholder groups is a regulator expecting to receive material it will have to answer. It is not an extension that follows silence, and it is not a sign the paper is being withdrawn. The distribution consultation closes on October 25, so both consultations are now open in the same window, which is a genuine scheduling pressure on any organisation that intends to comment on both.
- The consent question is the one the user stories are likely to turn on. A registry that consolidates policy and claims information across insurers is valuable to a policyholder precisely because it is hard to assemble today, and the same consolidation is the thing that makes consent, access control and data minimisation unavoidable. The consultation paper's own framing is that the registry is to be consent-driven and legally compliant, and the published commentary on it has raised privacy and consent as among the open issues. A registry that could be queried without a lawful basis would be a more attractive target than the scattered systems it replaces, not a safer one.
- Nothing here creates a right you can exercise. The registry is a proposal at the stage where the regulator is asking what to build. No policyholder can require an insurer to report a policy to it, and no nominee can use it to find a dormant policy, because none of the operational machinery exists. What exists is a document and a deadline. The practical consequence for an individual is that the only available action is a comment, and a comment from a policyholder on a user story is worth more than a comment from a policyholder on the vision statement.
Action
If you intend to comment, the mechanics matter and they are narrow. The submission must be in the prescribed Excel template, submitted through the portal or by the published email address, and the regulator has directed comments at the user stories in Section 8 and the questions in Section 15. A free-form letter will be harder to process than a completed template, and a comment that identifies a user story which should not exist is more useful than a comment that says the registry is a good idea. If you are an insurer or distributor, the questions worth answering are the ones about what you may query, on what consent, at what cost, and what you must hand over: a registry that requires you to disclose a policyholder's details to competitors is a commercial problem, and the template is where that objection is made most efficiently. If you hold a policy from a company that has gone quiet or is difficult to reach, note that the registry is the mechanism intended to solve that eventually, and that the answer available to you today is the unclaimed-amounts route, not the registry. Watch item: whether the final structure preserves the protocols-not-platforms principle, and whether consent is specified as a per-query requirement or a blanket one-time authorisation. Those two choices decide whether the registry is a genuine public utility or a database insurers share and individuals do not control.
Watch item: how the registry interacts with the distribution consultation closing on October 25, since the same paper proposes seller-level mis-selling records in the public domain and the registry is the infrastructure that would hold them. Whether the public-record proposal survives without a public registry is the substantive question, and the extension gives both consultations time to be answered in relation to each other.