Skip to content
AskSolique - AI tax research platform for India
Board agenda and calendar on a meeting-room desk, illustrating SEBI LODR prior-intimation planning.

SEBI LODR Regulation 29: The Prior Intimation Rules Your Checklist Probably Gets Wrong

• By AskSolique.ai Team • Securities Law

Most prior intimation failures are not judgement calls. They are counting errors — a board meeting fixed for Thursday, an intimation filed on Tuesday evening, and a compliance officer discovering too late that the exchange counts working days differently from the calendar. Regulation 29 is one of the shortest provisions a company secretary deals with under SEBI LODR, and one of the most frequently misapplied, largely because the timeline changed in May 2024 and a great many internal checklists never caught up. This article sets out what the provision requires now, which events it covers, how the two-working-day window is actually counted, and where intimation ends and disclosure begins — the everyday arithmetic of SEBI LODR compliance for company secretaries.

What Regulation 29 of SEBI LODR actually covers

Regulation 29 requires a listed entity to tell the stock exchanges in advance that its board will meet to consider certain proposals. It is not a disclosure of the decision. It is notice that a decision is coming, and its purpose is to give the market a fair warning window before price-sensitive information exists.

The events are a closed list. A board meeting called to consider any of the following needs prior intimation:

Event requiring prior intimationProvision
Financial results - quarterly, half-yearly or annualReg. 29(1)(a)
Proposal for buy-back of securitiesReg. 29(1)(b)
Proposal for voluntary delistingReg. 29(1)(c)
Fund raising - public issue, rights issue, FCCBs, ADRs/GDRs, preferential issue, QIP or debt securitiesReg. 29(1)(d)
Declaration or recommendation of dividend, or conversion of convertible securitiesReg. 29(1)(e)
Proposal for declaration of bonus securitiesReg. 29(1)(f)
Alteration in the form or nature of listed securities, or in the rights attached to themReg. 29(2)
Alteration in the date of interest payment on debentures, or redemption of redeemable securitiesReg. 29(3)

A board meeting for anything outside this list - a related party transaction, a resignation, a policy - does not attract prior intimation, though the outcome may still be a disclosable material event.

The uniform two-working-day rule that replaced the five-day timeline

This is where out-of-date checklists fail. Until May 2024, SEBI LODR ran a split timeline: five clear days' notice for a board meeting considering financial results, and two working days for everything else. The 2024 amendment to the listing regulations, effective 17 May 2024, removed the split. Every event under Regulation 29 now carries the same requirement - prior intimation of at least two working days, excluding both the date of the intimation and the date of the meeting.

Two consequences follow. A checklist that still says "five days for results" imposes a burden the regulation no longer contains, which sounds harmless until it forces a board meeting to be deferred for no reason. More dangerous is the team that has internalised *results are different* and ends up applying the shorter window to results and the longer one elsewhere - the error runs in exactly the wrong direction.

The intimation must also state the date of the board meeting. An intimation announcing an intention without fixing a date does not start the clock.

How to count two working days

Working days means days on which the recognised stock exchanges are open for trading. That is narrower than business days: exchange trading holidays are published annually and do not always align with bank holidays or the company's own calendar.

The count excludes both ends. A board meeting on Thursday therefore needs the intimation filed no later than Monday, assuming Tuesday and Wednesday are both trading days. Insert one exchange holiday and Monday becomes the previous Friday. This is precisely the arithmetic that collapses when a meeting is rescheduled at short notice.

If a meeting is postponed, file a fresh intimation. The original one covered a date that no longer exists.

Intimation is not disclosure

Regulation 29 governs what happens before the meeting. Regulation 30 governs what happens after it, and the timelines are not remotely comparable: the outcome of a board meeting on a Regulation 29 matter must reach the exchanges within thirty minutes of the meeting concluding.

Treating the two as one obligation is a structural error. A team that files a flawless prior intimation and then takes two hours to release the outcome has complied with one provision and breached another. They need separate owners, separate templates and separate escalation paths - the same discipline that stops routine procedural slips turning into penalties, as the pattern of ROC action on everyday compliance lapses shows.

Fund raising adds a third clock. A board meeting called to consider a rights issue needs the Regulation 29 intimation, the Regulation 30 outcome disclosure and, once a record date is fixed, the separate advance intimation under Regulation 42 - each running independently.

It is also worth noting that Regulation 29 is a number that appears in more than one SEBI rulebook. The obligation under the takeover code is unrelated and sits on the acquirer rather than the company; the SAST disclosure triggers work on an entirely different logic.

Where the master circular matters more than the regulation text

The regulation tells you what to file and when. It does not tell you the format. Formats, XBRL requirements and filing mechanics sit in the SEBI master circular for listed entities and in the exchange circulars issued under it, and they move considerably faster than the regulations do. The listing regulations themselves were last amended in January 2026; the operational layer beneath them changes several times a year.

That gap - current regulation, stale circular, or the reverse - is where most avoidable non-compliance starts. Reading the provision and the circular that operationalises it together is the only reliable method, which is why a research workflow that pulls a provision and its circulars in one pass beats a folder of saved PDFs. What matters there is the underlying sources and coverage, not the interface.

A prior-intimation process that holds up

  • Diary backwards from the board meeting date using the exchange trading calendar, never the company calendar.
  • Fix the meeting date before the intimation is drafted. An undated intimation does not comply.
  • Keep the Regulation 29 intimation and the Regulation 30 outcome as two tasks with two owners.
  • Re-file on every postponement.
  • Re-verify the format against the current SEBI master circular each quarter rather than reusing last quarter's file.

The answer, in one line

Regulation 29 of SEBI LODR requires two working days' prior intimation to the stock exchanges for every event on its list, stating the date of the board meeting, counted on trading days and excluding both the filing date and the meeting date. The five-day rule for financial results has not applied since May 2024.

Pull the current text of the provision alongside the master circular that prescribes the format, check both against your calendar for the next board meeting, and correct the gap before the meeting is called rather than after it.

References

Frequently Asked Questions

Does Regulation 29 apply if the board passes the resolution by circulation instead of meeting?

The provision is drafted around a meeting of the board of directors, so a resolution by circulation sits outside its literal wording. In practice this rarely arises for the listed events: financial results cannot be approved by circulation under the Companies Act, and most of the remaining items are matters boards convene for. Where circulation is genuinely available, market practice is to intimate anyway rather than rely on a technical reading.

Is prior intimation needed for a board meeting considering a scheme of arrangement?

A scheme of arrangement is not on the Regulation 29 list, so no prior intimation arises under that provision. The obligation comes from elsewhere - the outcome is a material event under Regulation 30, and SEBI's scheme framework imposes its own filing and no-objection requirements before the scheme reaches the exchanges. Companies that intimate in advance do so as practice, not as compliance with Regulation 29.

What happens if the intimation is filed late?

Stock exchanges levy fines for listing regulation breaches under SEBI's standard operating procedure for non-compliance, applied provision by provision, with repeat failures escalating to suspension of trading in extreme cases. The amounts are revised periodically, so check the SOP in force rather than an older fine chart. Separately, a late intimation is a reportable item in the quarterly compliance report and will surface in the secretarial audit.

Do debt-listed entities follow the same two-working-day rule?

Entities with only debt securities listed follow the parallel obligation in Chapter V of the listing regulations rather than Regulation 29, which sits in the equity chapter. The prior intimation window there also runs on working days, but the list of triggering events differs and Chapter V has been amended repeatedly in recent years. Verify against the current text rather than assuming the equity position applies.

If a board meeting is adjourned, does the fresh date need a new intimation?

Yes. The intimation attaches to a specific date, and once that date passes or moves, the filing no longer describes a meeting that is going to happen. File a fresh intimation for the adjourned date, observing the full two-working-day window from the new filing. Where the adjournment is announced publicly, the adjournment itself will usually also need disclosure as a material event.

Recent Blog Posts

See All Posts

Transform Your Tax Practice Today

Start Saving Hours Today. Build Next-Generation Advisory Teams.

Empower your professionals with AI-assisted tax intelligence designed for accuracy, speed, and enterprise-scale execution.