How Do You Build a Labour Law Compliance Calendar?

A compliance calendar records when an obligation falls due. A checklist records whether the required compliance measure is in place. Both draw on the same underlying obligations, so the risk is maintaining two inconsistent lists. Treat them as one dataset with three views. The compliance register is the third of them, and it is where the row itself is designed, before any view is rendered. A row that omits its State, its owner, the instrument prescribing it and the date someone last checked that instrument is not ready for any view. Ritu Kulkarni runs HR at a 140-person software firm in Pune with a 12-person Bengaluru sales office, and she inherited a 60-row spreadsheet whose rows cite nothing. Every one of those 60 rows is missing the same four fields.

The row schema contains twenty-two fields, and the four in bold are the ones an inherited calendar never carries.

A vendor calendar or a generic labour law compliance calendar arrives with the date and none of the four bold fields, which is why pasting one into your register makes the register worse rather than better. Separate FY 2026-27 deadlines from recurring obligations, and establish which Labour Code applies before assigning a date.

Create a compliance calendar in seven steps and add the dates last, because working out what applies to you is what actually takes the time. Build your own rather than adopting anyone else's. List every establishment and the State in which it is located. Count and classify the people at each one, contract workers and platform-engaged people included. Test which Codes, rules and schemes apply on those facts. Decide whether the Centre or a State is your appropriate Government for each obligation. Identify the instrument that sets the date and record its citation. Give the row one named owner and a backup. Publish it last, with a status and a next-review date.

Step one produces a list of establishments, not a list of offices. Step two produces a dated headcount by category, and worker classification determines which people belong in each category. Step three produces an applicability conclusion for each Code, rule and scheme, written down with the facts it is based on. Step four produces one answer per obligation rather than one per company, because the appropriate Government test can split within a single business. Step five records an instrument citation for each row. Step six produces two names. Step seven produces a published row with source_status, last_checked and next_review filled in.

Ritu and Devang Shah run identical steps and produce different registers, and the divergence starts at step three. Ritu gains a second-State overlay for Bengaluru and nothing else. Devang, who leads compliance for a 220-worker manufacturing establishment in Maharashtra with 60 contract workers through two contractors and a 35-person Tamil Nadu warehouse, gains contractor rows, factory rows and a third set of establishment-level records. Same seven steps, different facts, different registers. That is why a copied calendar cannot work, and why the honest answer to "send me your calendar" is "send me your worksheet".

One habit prevents most of the damage. A headcount threshold is a test you run on a date, not a permanent property of the business, so record the count and the date beside every applicability conclusion. Repeating step three after a headcount change is itself a row on the calendar, with an owner and an evidence link like any other. One-time transition actions are complete once performed; retain only recurring obligations in this calendar. Where platform or aggregator work is in the mix, gig and platform worker duties belong to the Social Security Code rather than to this register's ordinary rows.

Sort every row into monthly, quarterly, annual or event-based, and check for missing event-based obligations in an inherited calendar. Those four categories include every labour-law compliance task applicable to an establishment, and the compliance deadlines that follow from them. Monthly is your wage day: wages on a monthly wage period fall due before the expiry of the seventh day of the succeeding month, under section 17(1)(iv) of the Code on Wages, 2019. Quarterly is usually a review rather than a filing: no worker may work overtime exceeding 144 hours in any quarter of a year, under the first proviso to rule 69(4) of the OSH Central Rules. The annual category includes two returns that fall in the same week of February. Event-based rows start when the specified event occurs: gratuity must be arranged for payment within thirty days from the date it becomes payable, under section 56(3) of the Code on Social Security, 2020.

Each category must identify the applicable rule. The monthly wage row must reflect the wage-payment deadlines, and the monthly contribution row must reflect provident fund and ESI rates. The quarterly row must reflect the overtime ceiling. The two annual returns concern registration and licensing and the unified annual return. The gratuity event concerns gratuity on a fixed term.

Annual obligations are often recorded incorrectly, and both annual-return rows now carry a date. Rule 74 of the OSH (Central) Rules, 2026 requires every employer to send an annual return in Form XVII, covering categories of employees, health and welfare facilities, retrenchment or lay-offs, bonus and maternity benefits, to the Inspector-cum-Facilitator having jurisdiction, so as to reach on or before the last day of February following the year ending 31 December. Rule 53(5)(a) of the Social Security (Central) Rules, 2026 requires an employer to whom Chapters V and VI apply to upload a unified annual return in Form XXIII on or before the 28th or 29th day of February in each year on the Ministry's web portal, for the preceding year. The same Rules prescribe two more forms: Form XXII, the register of women employees, and Form XXVI, the yearly Employment Information Return. The OSH Rules add Form XVIII, the contractor's half-yearly return. The Wages (Central) Rules, 2026 and the Industrial Relations (Central) Rules, 2026 prescribe no annual return at all.

Seven events require a time limit to be calculated when they occur rather than an advance fixed date, and every one of them belongs in the register with an event field in place of a due date. An employee's exit starts the two-working-day wage-payment period in section 17(2) of the Code on Wages, 2019. Gratuity becoming payable starts the thirty days in section 56(3). A change in registered particulars starts thirty days on the same Form I, under rule 3(8) of the OSH Central Rules, which is the same thirty days whichever particular changed. A headcount crossing a threshold requires a new applicability test. A new contractor starts a contractor row. A State notification starts an overlay review. And a change of row owner starts a handover.

Three dates get pasted into calendars from elsewhere, and each has a different answer. The fifteenth-of-the-month provident fund date is supported, but by a different instrument from the one most calendars cite: paragraph 20(1) of the Employees' Provident Funds Scheme, 2026, notified as G.S.R. 525(E) on 29 June 2026, makes the employer pay both contributions with administrative charges within fifteen days of the close of every month, and paragraph 28(3) requires the remittance through the authorised electronic payment mode in the same period. A twenty-first-of-the-month date for the Employees' State Insurance Corporation is not supported: section 29(4) of the Code on Social Security, 2020 makes contributions payable in respect of each wage period fall due ordinarily on the last day of that wage period, and the regulations fix the day where an employee works part of that wage period or works under two or more employers. A statutory compliance calendar in India therefore carries a State insurance row with a period rather than a day. A 31 January POSH annual report date is not supported either: section 21 of the Sexual Harassment of Women at Workplace (Prevention, Prohibition and Redressal) Act, 2013 requires the report in the form and at the time prescribed, and prints no universal date.

Use one status legend from here on, and use it in every table: confirmed, provisional, superseded, awaiting reviewer, not applicable. Use one evidence vocabulary too: challan, wage register extract, return acknowledgement, notice served, committee minutes, approval email, payment proof.

Responsibility for labour law compliance is assigned to one named person per row, never to a department. "HR owns compliance" is how a missed filing stays invisible for a year. Four more fields make that ownership auditable: a named backup, the evidence that proves the obligation was met, a reviewer who signs it off, and a row state. Row status records the completion status. Source status, from the frequency section above, records whether the instrument cited for the row still applies. Keep the two apart, because a row can be finished and wrong at the same time.

Devang's contractor rows are the hard case, because he stays accountable while the evidence of completion is held in his contractor's files. Contract for it: the same evidence link, the same last_checked date, and a named person on the contractor's side who supplies both. Keep the evidence-retention field in the register, and let the instrument that created the obligation set the period rather than printing a single retention rule across every row. Use these fields to record each recurring obligation, its authority and its completion evidence.

Labour law due dates are not the same in every State. Keep one Central baseline and apply State, scheme and establishment overlays separately to it, so that a State change edits one overlay instead of rippling through the whole calendar. A State, scheme or establishment-specific change may alter a row only if three conditions are met: a current instrument from the issuing authority, applicability facts that match your establishment, and an effective date. Devang's Maharashtra factory rows and his Tamil Nadu warehouse rows share the same baseline and diverge only in the overlay. Never treat a State rule as part of the Central baseline, and never copy one State's date to another.

Devang's two overlays demonstrate how the rule applies. The Maharashtra row can be published because an instrument from that State's own authority supports it. The Tamil Nadu row stays provisional until an equivalent Tamil Nadu instrument is confirmed, and no Tamil Nadu date is published in the meantime. State/UT labour rules are the overlay's authority, and applicability depends on the rules notified by your State or Union Territory under each Code.

Two habits produce most of the wrong dates in published calendars. The first treats a financial-year label as a legal source: FY 2026-27 identifies the twelve months displayed, from April 2026 to March 2027, and it does not establish when an obligation falls due. The second treats a dated government status report as a live authority. A status report describes the position on the day it was compiled, so a row sourced to one is marked superseded unless a current instrument confirms it.

For HR compliance planning, the Codes change the legal authority for a date more often than they change the date itself, because every row you inherited was written against an older Act. Listed provisions of the four Codes were appointed from 21 November 2025, the Social Security schedule being read with its corrigendum, and the four sets of Central Rules were notified on 8 May 2026. What that means for the register is narrower and more useful than it sounds: update each row's cited authority, re-check its form and portal, and preserve the old instrument rather than deleting it. Change a date only where the new instrument changes the deadline. The date each provision started is fixed by its commencement order, not by the calendar.

Migrate the old calendar with a disposition log rather than a rewrite, so nothing disappears without a trace. Every old row ends in one of four states: carried, with the same date and a new authority; re-sourced, where the instrument changed but the obligation did not; superseded, where the obligation itself was replaced; or replaced, where a new row takes its place with supersedes filled in. Record the reviewer and the next review date against each.

Two limits apply to these updates. A Central Rule does not settle a State's procedure, its form or its portal, so a row with an updated citation can still be provisional pending confirmation of the applicable State requirements. And the one-time work the Codes force, from re-papering to re-registration to threshold re-tests, belongs to the one-time transition items; the calendar keeps only what recurs. Several of the Industrial Relations rows are created by standing orders and grievance forums, which the same Code requires.

Every row includes a last_checked date and a next_review date, and a row that cannot show both is provisional whatever date it displays. Two scheduled reviews maintain the register’s accuracy. At month-open the owner reads the next thirty days and confirms each source against the instrument. At month-close the owner attaches evidence and ages anything unfinished. Between them, five events force an unscheduled re-check: a new rule or notification, a State or portal change, a rate or scheme change, a headcount or establishment change, and a change of owner.

Ritu's triage is the case worth working, because 60 unsourced rows is where most people give up. She does not re-source all 60. She marks all 60 provisional in one pass, sorts by next due date, re-sources only the rows falling in the next thirty days, and verifies the remaining rows through start-of-month reviews over a quarter. Three months later every row has a source and a checked date, and no filing was missed while the work was in progress. The register was usable from the first day precisely because provisional is a published state rather than a hidden one.

Five counts let a manager assess the reviews without opening the register: rows due in the next thirty days, rows overdue, rows whose source has not been checked in ninety days, rows sitting provisional, and overlays changed since the last review. Watch the third and fourth together, because a register with no overdue rows but forty unsourced rows is not reliable.

An exported labour law compliance calendar is not the source record, and that export is the same register printed, carrying the same fields. A comma-separated or spreadsheet export includes official_source_url, source_status, last_checked and calendar_as_of alongside the dates, and so does the print view. A file that drops those four is a snapshot rather than a control, which is what makes a downloaded calendar go stale without anyone noticing. Keep the server-rendered register as the source of truth, and let every other format be a view of it.