Reg 30 Disclosures: Why "Material" Isn't What You Think

If you read the text of Regulation 30 once, you might conclude that material event disclosure is straightforward. The regulation lists 35-plus specific events that are deemed material — board changes, related party transactions above thresholds, scheme of arrangements, fraud, regulatory orders, and so on. Disclose those within 24 hours. Done.

But the most consequential part of Reg 30 is not the enumerated list. It is the catch-all standard that sits alongside it — and the obligation to maintain a Material Event Policy that captures events not specifically listed but nonetheless material to the company's investors.

The deemed material events

Schedule III of LODR enumerates events that are deemed material — meaning disclosure is mandatory regardless of the company's own materiality assessment. These include board and KMP changes, declared dividends and buybacks, fraud or default, scheme of arrangement, ratings actions, regulatory orders, related party transactions over the prescribed thresholds, and material litigation.

For these enumerated events, the company has no discretion. The event happens; the disclosure is required; the timeline is 24 hours from the trigger. Most compliance failures on enumerated events are timing failures rather than judgment failures.

The catch-all standard

Beyond the enumerated list, Reg 30 requires disclosure of any other event or information that, in the opinion of the board, is material. The regulation provides quantitative and qualitative tests: a transaction or event affecting 2% or more of consolidated turnover or net worth (whichever is lower) is deemed material. Qualitative materiality applies to information that would, in the board's judgment, be regarded as significant by investors in making investment decisions.

This is where most companies fail. The qualitative standard requires judgment. Judgment requires a framework. The framework is the Material Event Policy that LODR mandates every listed company to maintain. Most companies either do not have one, or have one that was drafted five years ago and never revisited.

Common failure patterns

The most common Reg 30 failures fall into three buckets. First, timing failures — the event was material and was eventually disclosed, but not within 24 hours. The most common cause is internal escalation lag: someone in operations or finance learns of the event but does not immediately escalate to the CS or compliance officer.

Second, judgment failures — the event was material but was not assessed as such, often because the Material Event Policy was inadequate or unused. Examples include early signs of customer default, internal restructuring decisions, or operational events with downstream regulatory consequences.

Third, format failures — the disclosure was made but in inadequate detail, often omitting the quantitative impact or the management commentary that LODR contemplates. SEBI has been increasingly aggressive about format adequacy in recent years.

The 24-hour rule and its exceptions

The standard timeline is 24 hours from the trigger event. The trigger is typically the board decision, the regulatory order, the customer notification — whichever crystallised the event. There are limited exceptions, most notably for events that are themselves subject to ongoing negotiation or where premature disclosure would harm the company's legitimate interests. These exceptions are narrow and frequently misapplied.

Building a working framework

A workable Reg 30 framework rests on three elements: a current Material Event Policy that defines materiality in concrete terms for the specific company, an internal escalation protocol that ensures information reaches the compliance officer quickly, and a documented assessment process for borderline cases. Most companies need to refresh at least one of these every 12 months. Most do not.

The companies that fail Reg 30 most spectacularly are not the ones that hide bad news. They are the ones that genuinely did not realise the event was material, because nobody asked the question in time.