Building a SEBI LODR Compliance Calendar That Does Not Drift

A SEBI LODR compliance calendar is a control, not a list of dates. It has to survive amendments to the regulations, changes in the company's own market capitalisation band, and changes in the class of securities the company has listed. A calendar built correctly once, usually by a company secretary working carefully from the regulations and the applicable master circular, will drift unless the structure forces re-verification, because the regulatory position keeps moving and the spreadsheet does not. The design question is therefore not what the deadlines are today. It is what structure keeps the calendar correct twelve amendments from now.

What LODR is, and what a calendar built only from LODR will miss

The Securities and Exchange Board of India (Listing Obligations and Disclosure Requirements) Regulations, 2015 were notified in September 2015 under the SEBI Act, 1992 and the Securities Contracts (Regulation) Act, 1956, and came into force later that year, replacing the erstwhile Listing Agreement with a regulatory framework enforceable directly by SEBI. That change matters for calendar design: the obligation now sits in a regulation that SEBI amends on its own timetable, rather than in a negotiated agreement with the exchanges.

A LODR compliance calendar built only from the bare text of the regulations will be incomplete. The operative obligation set for an Indian listed entity is the regulations, plus SEBI circulars that prescribe formats, timelines and procedures and are periodically consolidated into a master circular for listed entities, plus the stock exchanges' own filing systems, XBRL formats and procedural requirements. A row that captures the regulation number but not the current circular and format will produce a filing that is late, in the wrong shape, or both.

LODR is also not the whole obligation set for a listed entity. It runs alongside the Companies Act, 2013, the SEBI (Prohibition of Insider Trading) Regulations, 2015 including trading window closure and the structured digital database requirement, the SEBI (Substantial Acquisition of Shares and Takeovers) Regulations, 2011 including the acquisition and encumbrance disclosure obligations under Regulations 29 and 31, the SEBI (Depositories and Participants) Regulations, 2018 for the periodic reconciliation of share capital audit report, and any sectoral regulator's requirements. A calendar that treats these as separate documents held by separate people is a calendar with gaps at the seams.

Resolve applicability first: obligations vary by class of securities and by size

The LODR Regulations are structured so that a common set of obligations applies to all listed entities, and further chapters apply according to what has been listed. Entities with listed specified securities on the main board carry the corporate governance and equity disclosure chapters. Entities with only listed non-convertible securities carry a different chapter, with its own intimation, financial results, security cover, credit rating, debenture trustee and record date obligations. Separate chapters address Indian depository receipts, securitised debt instruments, security receipts, mutual fund units and commercial paper. An entity that has listed only non-convertible debentures does not carry the equity issuer obligation set, and a calendar copied from an equity issuer will be wrong in both directions.

Regulation 15 of the LODR Regulations provides that specified corporate governance requirements, broadly those in Regulations 17 to 27 along with certain website disclosure requirements and parts of Schedule V, do not apply to a listed entity whose paid-up equity share capital and net worth fall below prescribed thresholds, and to entities listed on the SME platform. The thresholds, the measurement date and the conditions attached to the exemption, including what happens once an entity crosses the threshold, have been amended over time. Verify the current text of Regulation 15 before you exempt an entity from anything, and record in the calendar the date on which that verification was done.

A further layer of applicability runs on market capitalisation rank. Several LODR obligations attach only to entities within a specified band of listed entities by market capitalisation, determined as on a specified cut-off date. Requirements framed this way include constitution of the risk management committee, business responsibility and sustainability reporting, the dividend distribution policy and the market rumour verification obligation. Bands and their contents change, and an entity can enter or leave a band without doing anything itself. Build an explicit annual step into the calendar to re-derive which bands the entity falls into and to add or retire the corresponding rows.

Category one: periodic disclosures, which are date-driven

• Financial results under Regulation 33 for entities with listed specified securities, and under Regulation 52 for entities with listed non-convertible securities, on a quarterly and annual basis with the applicable limited review or audit.
• Shareholding pattern under Regulation 31.
• Corporate governance compliance report under Regulation 27(2).
• Statement on investor complaints under Regulation 13(3).
• Annual secretarial audit and the annual secretarial compliance report from a practising company secretary under Regulation 24A, extending to material unlisted subsidiaries as prescribed.
• Annual report under Regulation 34, including the business responsibility and sustainability report under Regulation 34(2)(f) for entities in the specified band.
• Statement of deviation or variation in the use of issue proceeds under Regulation 32, and the corresponding statement for non-convertible securities.
• Periodic disclosure of related party transactions to the stock exchanges under Regulation 23(9), in the format specified by SEBI.
• Reconciliation of share capital audit report under the SEBI (Depositories and Participants) Regulations, 2018, and applicable disclosures under the SEBI (Substantial Acquisition of Shares and Takeovers) Regulations, 2011.

The due dates for each of these are prescribed and have been amended since 2015. This is precisely why a calendar row should store the regulation reference and the governing circular alongside the date, rather than the date alone. A row that records only a bare number of days cannot be re-verified by the next person to hold the file. A row that records the regulation, the circular, the format and the date on which all three were last checked can be.

Category two: event-based disclosure, which cannot live in a calendar

Regulation 30 of the LODR Regulations, read with Part A of Schedule III, governs disclosure of material events. Part A distinguishes events that are deemed material and must be disclosed without applying any materiality test from events that are disclosable on application of the materiality policy the board frames under Regulation 30(4). Regulation 30A addresses disclosure of specified agreements, including those that affect management or control of the listed entity or impose restrictions or create liabilities on it. Regulation 30 also carries the market rumour verification obligation for entities in the specified band. Alongside these sit prior intimation of board meetings under Regulation 29, disclosure of voting results under Regulation 44, and reclassification of promoters under Regulation 31A.

The design point for Indian compliance officers is that event-based obligations cannot be scheduled. What can be scheduled is the control that surfaces the event. A recurring failure mode under Regulation 30 is not disagreement about materiality but internal information flow, where the compliance officer learns of a signed agreement, a regulatory order, a resignation or a default several days after the person who signed, received or caused it. The calendar entries that address this are standing ones: a pre-board disclosure checklist, a monthly confirmation from the heads of legal, treasury, human resources, business development and litigation that nothing disclosable has occurred, and a routing rule that copies the compliance officer on defined document types at the point of execution.

Regulation 30 timelines run from the occurrence of the event, the board decision, or the receipt of information, depending on the category, and they are short. Confirm the current timelines directly from the regulation and the applicable SEBI circular, because they have been tightened by amendment. Note also that Regulation 6 requires the appointment of a qualified company secretary as the compliance officer, which places accountability for this flow in a named statutory role rather than in a function.

Category three: related party transactions

Regulation 23 of the LODR Regulations requires a listed entity to formulate a policy on the materiality of related party transactions and on dealing with them, to obtain prior approval of the audit committee for all related party transactions and for subsequent material modifications, to obtain shareholder approval for material related party transactions by resolution in which no related party may vote regardless of whether it is a party to that particular transaction, and to make periodic disclosures to the stock exchanges in the format SEBI specifies. The definitions in Regulation 2 and the materiality thresholds in Regulation 23 have been amended, and SEBI has directed listed entities to follow industry standards on certain aspects of related party disclosure. Verify the current text and the applicable standards before applying a threshold from memory.

Related party transaction compliance is a contract inventory problem before it is a disclosure problem. If a listed entity cannot produce, on demand, every live agreement with a related party together with its value, term, renewal date and amendment history, it cannot reliably compute materiality against a turnover-linked threshold and it cannot reliably identify a subsequent material modification. Renewals and automatic extensions are a common failure point, because they change nothing visible internally while changing the disclosure position.

There is also an overlay with the Companies Act, 2013. Section 188 governs related party contracts and arrangements and Section 177 governs audit committee approval of related party transactions. The definitions, exemptions and thresholds under the Companies Act, 2013 and under the LODR Regulations are not identical, and a transaction must be tested under both regimes rather than under whichever is more familiar to the person reviewing it.

Category four: governance and committee requirements, which are standing obligations

• Board composition under Regulation 17, including minimum board size, the proportion of independent directors which varies according to whether the chairperson is executive and whether the chairperson is related to the promoter, woman director and independent woman director requirements that vary by band, and the requirement to meet at least four times a year with a maximum permissible gap between consecutive meetings.
• Maximum number of directorships under Regulation 17A.
• Limits on committee memberships and chairmanships across listed entities under Regulation 26(1).
• Audit committee under Regulation 18, nomination and remuneration committee under Regulation 19, stakeholders relationship committee under Regulation 20, and risk management committee under Regulation 21 for entities in the specified band, each with its own composition, quorum and meeting frequency requirements.
• Vigil mechanism and whistle blower policy under Regulation 22.
• Governance of subsidiaries under Regulation 24, including the material subsidiary tests and the associated board and audit committee oversight.
• Independent director requirements under Regulation 25, including the separate meeting of independent directors and the familiarisation programme, and obligations of directors and senior management under Regulation 26.
• The website disclosure set under Regulation 46, which is a continuing obligation and a recurring inspection finding because content goes stale rather than missing.

These obligations break on personnel and structural events, not on dates. The resignation of an independent director, a director crossing the directorship cap under Regulation 17A or the committee membership and chairmanship limits under Regulation 26(1) because of an appointment elsewhere, an audit committee losing its required composition, or a subsidiary crossing a materiality test each starts a cure period. A LODR calendar should therefore carry a monthly composition and eligibility test, with the annual disclosures treated as an output of that test rather than as the test itself.

Category five: approval-gated and structural obligations

• In-principle approval from the stock exchanges before issuing securities, under Regulation 28.
• Schemes of arrangement under Regulations 11 and 37, including the requirement to obtain the observation letter or no-objection letter from the exchanges before filing with the National Company Law Tribunal.
• Minimum public shareholding under Regulation 38, read with Rule 19A of the Securities Contracts (Regulation) Rules, 1957.
• Transfer and transmission of securities under Regulation 40, including the requirement that transfers be effected only in dematerialised form.
• Record date and prior intimation requirements under Regulation 42, and dividend and interest payment obligations under Regulation 12.
• Newspaper advertisement requirements under Regulation 47, and preservation of documents under the policy required by Regulation 9.

The three ways a LODR calendar drifts

• Amendment drift. SEBI amends the LODR Regulations and issues circulars changing formats and timelines on its own schedule, and the master circular for listed entities is periodically updated. A row that stores a date but not the provision it came from cannot be re-verified, so nobody re-verifies it.
• Band drift. Market capitalisation rank changes annually. Obligations attach and detach without any decision by the company, and a calendar built when the entity was outside a band will silently omit the rows it acquired when it entered one.
• Ownership drift. Rows outlive the people who built them. When the named preparer has moved teams or left, a row that still shows a due date but has no live owner is decorative, and it will be discovered only when the filing is missed.

Every row in a compliance calendar should be able to answer one question: which provision requires this, and when did we last confirm that the provision still says so?

How to build a calendar that holds its accuracy

• Model one row per obligation, not one row per date. Each row should carry the regulation or section reference, the governing circular and format, the class of securities it applies to, the applicability test and its result, the trigger type of date or event, named preparer, reviewer and approver, the evidence location, and a last-verified date.
• Put a last-verified-against-source date on every row and make it visible. Rows past a defined age move automatically into a review queue. This single field converts a static spreadsheet into a control with a measurable state.
• Run a quarterly amendment sweep. Read the SEBI amendment notifications, circulars and master circular updates issued since the last sweep, and record against each affected row whether it changed. Record no change explicitly, because a sweep with no recorded outcome is indistinguishable from a sweep that never happened.
• Work backwards from every regulatory date to an internal cut-off. A filing due on a given day needs data assembled, reviewed and approved before it. The date that belongs in the operating calendar is the internal cut-off; the regulatory date belongs in the row as the constraint.
• Attach evidence at the row. The exchange acknowledgement, the filed document or XBRL submission, and the board or committee minute reference should sit with the obligation, not in a shared drive organised by month.
• Report exceptions to the audit committee quarterly. Late filings, near misses, rows overdue for verification and rows without an owner are the four measures that show whether the calendar is a live control or a document.

Where LexVio fits in a LODR programme

LexVio's compliance module monitors SEBI, RBI, MCA/ROC and GST obligations, maintains an automated filing calendar, issues 14-day pre-deadline alerts, and carries a regulatory change feed so that amendments arrive as a queue to be worked through rather than as something a team member has to happen to notice. That change feed maps directly onto the amendment drift problem, which is the failure mode that can quietly disable a LODR calendar without anyone noticing.

On the contract side, which is where related party transaction compliance actually lives, Nexus provides portfolio-wide search, clause benchmarking and drift alerts across the agreement inventory, so questions such as which related party agreements renew this quarter, or which contain a value escalation clause that could push a transaction over a materiality threshold, become searches rather than reading exercises. Contracts under review receive a 0 to 100 Legal Health Score with clause-level risk flags, and redlines export to Word as tracked changes. Vault holds the executed set, Workflows routes approvals, and the Intelligence API and webhooks make LexVio's output available to the systems the secretarial team already uses. For listed entities with data residency or confidentiality constraints, LexVio offers SAML SSO, SCIM provisioning and an on-premise deployment option, with AES-256 encryption at rest, TLS 1.3 in transit and no training on customer data.

What no system decides is whether a particular event is material under Regulation 30, whether a change to a contract amounts to a subsequent material modification under Regulation 23, or how a given disclosure will read to SEBI and to the market. Those are judgments, and under the LODR Regulations the accountability for them sits with the compliance officer, the board and its committees. The value of AI in a LODR programme is that it removes the mechanical layer: locating the governing provision, extracting the relevant clause, tracking the amendment, assembling the evidence and chasing the deadline. The professional time it frees goes to the judgment, which is the part that was always underserved.